Cisco Spark Chatbot Challenge Official Rules – (the “Official Rules”)
NO PURCHASE OR PAYMENT NECESSARY. A PURCHASE OR PAYMENT OF ANY KIND WILL NOT INCREASE YOUR CHANCES OF WINNING.
Hackathon Name: Cisco Spark Chatbot Challenge (the “Hackathon”)
Hackathon Website: http://ciscospark.devpost.com (the “Hackathon Website”)
1. POSTER & ADMINISTRATOR
Poster (the “Poster”): Cisco Systems, Inc. (“Cisco”), 170 West Tasman Drive, San Jose, CA 95134.
The Poster is the sponsor and entity responsible for the Hackathon.
Administrator (the “Administrator”): Devpost, Inc. (“Devpost”), 222 Broadway, 19th Floor, New York, NY 10038.
2. DATES AND TIMING
Hackathon Submission Period: May 1, 2017 (10:00am Eastern Time) – July 25, 2017 (5:00pm Eastern Time) (the “Hackathon Submission Period”)
Judging Period: August 1, 2017 (10:00am Eastern Time) – August 11, 2017 (5:00pm Eastern Time) (the “Judging Period”)
Public Voting Period: August 1, 2017 (10:00am Eastern Time) – August 11, 2017 (5:00pm Eastern Time) (the “Public Voting Period”)
Winners Announced: On or around August 21, 2017 (2:00pm Eastern Time)
The Administrator will be the official timekeeper for the Hackathon.
A. The Hackathon IS open to:
- Individuals who are at least the age of majority where they reside as of the time of entry (“Eligible Individuals”)
- Teams of Eligible Individuals (“Teams”)
- Organizations (including corporations, not-for-profit corporations and other nonprofit organizations, limited liability companies, partnerships, and other legal entities) that exist and have been organized or incorporated at the time of entry, and employ no more than fifty (50) people (“Small Organizations”)
- Organizations (including corporations, not-for-profit corporations and other nonprofit organizations, limited liability companies, partnerships, and other legal entities) that employ more than fifty (50) people (“Large Organizations”). Please note, however, that Large Organizations will only be eligible to win the Large Organization Recognition Award, which carries no monetary value. Large Organizations will not be eligible to receive any other prize in connection with this Hackathon.
(the above are collectively, “Makers”)
An Eligible Individual may join more than one (1) Team, Small Organization, or Large Organization and an Eligible Individual who is part of a Team, Small Organization, or Large Organization may also enter the Hackathon on an individual basis.
If a Team, Small Organization, or Large Organization is entering the Hackathon, they must appoint and authorize one (1) individual (the “Representative”) to represent, act, and enter a Submission, on their behalf. The Representative must meet the eligibility requirements above. By entering a Submission on the Hackathon Website on behalf of a Team, Small Organization, or Large Organization you represent and warrant that you are the Representative authorized to act on behalf of your Team, Small Organization, or Large Organization.
B. The Hackathon IS NOT open to:
- Individuals who are residents of, or Small Organizations or Large Organizations domiciled in, a country, state, province or territory where the laws of the United States or local law prohibits participating or receiving a prize in the Hackathon (including, but not limited to, Brazil, Quebec, and Cuba, Sudan, Iran, North Korea, Syria, Myanmar (formerly Burma) and any other country designated by the United States Treasury's Office of Foreign Assets Control)
- Organizations involved with the design, production, paid promotion, execution, or distribution of the Hackathon, including the Poster and Administrator (“Promotion Entities”)
- Employees, internally contracted vendors of Poster and/or Administrator, representatives and agents** of such organizations, and all members of their immediate family or household*
- Any other individual involved with the design, production, promotion, execution, or distribution of the Hackathon, and each member of their immediate family or household*
- Any Judge (defined below), or company or individual that employs a Judge
- Any parent company, subsidiary, or other affiliate*** of any organization described above
- Employees or internally contracted vendors of governments and government-affiliated companies or organizations
- Any employee whose employer’s guidelines or regulations do not allow entry into the Hackathon or acceptance of the prize(s)
- Any other individual or organization whose participation in the Hackathon would create, in the sole discretion of the Poster and/or Administrator, a real or apparent conflict of interest
*The members of an individual’s immediate family include the individual’s spouse, children and stepchildren, parents and stepparents, and siblings and stepsiblings. The members of an individual’s household include any other person that shares the same residence as the individual for at least three (3) months out of the year.
**Agents include individuals or organizations that in creating a Submission to the Hackathon, are acting on behalf of, and at the direction of, a Promotion Entity through a contractual or similar relationship.
***An affiliate is: (a) an organization that is under common control, sharing a common majority or controlling owner, or common management; or (b) an organization that has a substantial ownership in, or is substantially owned by the other organization.
4. SUBMISSION REQUIREMENTS
Makers must do the following to participate in the Hackathon:
- Register for the Hackathon on the Hackathon Website by clicking the “Register for this Hackathon” button. To complete registration, sign up to create a Devpost account, or log in with an existing Devpost account. There is no charge for creating a Devpost account. This will enable you to receive important updates and access the “Enter a Submission” page.
- Create a developer account on Cisco Spark at https://developer.ciscospark.com/. There is no charge for creating a developer account or for using the Spark developer tools required in the Hackathon.
- Visit the Resources page of the Hackathon Website to learn more about the Spark APIs, and how to get started.
- Build a working Cisco Spark application, integration, or chatbot using at least one (1) API from the Spark developer tools that fits into one (1) of the following categories: Sales, Healthcare, or Education (each an “Application”). Certification in the Spark Depot (https://depot.ciscospark.com/) is NOT required in order to enter the Hackathon.
- Create a Github repository that contains your Application source code and documentation. Your Github code repository may be public or private. If your repository is private, access must be given in the testing instructions provided with your Submission. Github code will be used only for Application review and testing.
- Provide a way to access your working Application for judging and testing by providing a link to a website, functioning demo, a Spark Depot link, or the email address assigned to your chatbot. If your website is private, you must include login credentials in your testing instructions (see Section 4.B.vi below for additional instructions on making your Application available for testing).
- Create a video that includes footage that clearly explains your application’s features and functionality through a comprehensive demonstration.
- Complete and enter all of the required fields on the “Enter a Submission” page of the Hackathon Website (each a “Submission”) during the Hackathon Submission Period, and follow the requirements below.
A. Language Requirements
All Submission materials must be in English or, if not in English, the Maker must provide an English translation of the demonstration video, text description, and testing instructions as well as all other materials submitted.
B. Application Requirements
(i) What to Create: Makers must create a working Cisco Spark software application, integration, or chatbot using at least one (1) API from the Spark developer tools available at https://developer.ciscospark.com/ (each an “Application”). Makers are encouraged to make varied and creative use of Spark API endpoints (/spaces, /people, / messages) or Video SDK or Widget.
(ii) Categories: Applications must be entered into one (1) of the following categories (the “Categories”). As part of your Submission, you must select the Category which best applies to your Solution.
At any time, and at its sole discretion, the Poster will have the ability to re-assign a submitted Submission from one Category to another. Submissions in each Category are eligible for different prizes. See Section 7 for prize details.
(iii) Functionality: The Application must be capable of being successfully installed and running consistently on the platform for which it is intended, and must function as depicted in the video and/or expressed in the text description.
(iv) Platforms: A submitted Application must run on at least one (1) of the following:
- a smartphone or tablet (iOS, Android, Blackberry, Windows Mobile, or Kindle)
- a web browser (mobile or desktop)
- a desktop computer (Windows PC, Mac Desktop)
- other hardware (including, but not limited to, wearable technology, open source hardware, or proprietary hardware)
(v) New & Existing: Applications must be either newly created by the Maker or, if the Application existed prior to the Hackathon Submission Period, must have updated after the start of the Hackathon Submission Period. Makers will be required to explain updates made to an existing Application at the time of Submission. While Applications may have existed prior to the Hackathon, any Applications that have been selected as a winner in any other contest will be disqualified as a Submission.
(vi) Testing: The Maker must make the Application available free of charge and without any restriction, for testing, evaluation and use by the Poster, Administrator and Judges during the Hackathon and until the Judging Period ends. Makers must provide access to their Application in two (2) ways:
(1) Include a Github repository that contains your source code and documentation. Your Github code repository may be public or private. If your repository is private, access must be given in the testing instructions provided with your Submission. Github code will be used only for Application review and testing.
(2) Include a way to access your working Application for judging and testing. If your Application is on the Spark Depot, provide a Spark Depot link. If your Application is a chatbot, provide the email address assigned to your chatbot. For other Applications, follow the instructions below.
If the Application includes software that runs on proprietary or third party hardware that is not widely available to the public, including software running on devices or wearable technology other than smartphones, tablets, or desktop computers, the Poster and/or Administrator reserve the right, at their sole discretion, to require the Maker to provide physical access to the Application hardware upon request.
For Applications running on widely available smartphones, tablets, or desktop computers, Makers may make their Application available using one (1) of the following methods:
a. Android Applications:Upload an .apk file on the Enter a Submission form or provide a link for downloading the Application in the “Testing Instructions” field on the Enter a Submission form.
b. iOS Applications:
- If your Application is available on the iTunes App Store, provide a link in the “Website URL” field on “Enter a Submission” form. If you charge a fee for downloading your Application, you must provide a promo code.
- If your Application is not yet publicly available on the iTunes App Store, you must send a test build to the Administrator before the end of the Hackathon Submission Period using one (1) of the following methods:
You may send the Administrator a beta test via Crashalytics. Use the Administrator’s testing email (email@example.com) and UDID’s to provision a build and send the Administrator a link via the “Share Links” button. Add the testing link to the “Enter a Submission” form under “iOS Build Link”. Beta by Crashalytics is a free service. Please review the how-to for their Beta Distribution tool.
- iPhone 6S (iOS 10.2.1) 65a94a124c5432275cf161e715779f5f2b5d7f8e
Enter the Administrator’s email address to share a build for testing. The Administrator’s TestFlight account email is: firstname.lastname@example.org. Please note that if you add the Administrator as an “External Tester” your Application will need to go through Beta App Review before you can send your build. This could lead to delay and in order for your Submission to be eligible, you must send your test build before the end of the Hackathon Submission Period. To learn more about TestFlight via iTunes Connect, please review the iTunes Connect Developer Guide and the TestFlight Video Tutorial.
Send a testing link to the Administrator at: email@example.com, and add the testing link on the Enter a Submission form under “iOS Build Link.” Please note that there is a fee to use HockeyApp.
c. Windows Phone applications:Upload an .xap file in the “Enter a Submission” form or provide a link for downloading your Application in the “Testing Instructions” field on the “Enter a Submission” form.
d. Windows PC:Upload the appropriate installation files (.exe) on the Enter a Submission form or provide a link for downloading your .exe file in the “Testing Instructions” field on the “Enter a Submission” form.
e. BlackBerry:Upload the appropriate installation files on the “Enter a Submission” form or provide a link for downloading your installation file in the “Testing Instructions” field on the “Enter a Submission” form.
f. Mac OS:Upload the appropriate installation files on the “Enter a Submission” form or provide a link for downloading your installation file in the “Testing Instructions” field on the “Enter a Submission” form.
g. Web/Mobile Web:Provide a link for accessing your Application on the “Testing Instructions” field on the “Enter a Submission” form. If your website is private, you must include login credentials in your testing instructions.
h. Kindle: Upload the appropriate installation files on the “Enter a Submission” form or provide a link for downloading your installation file in the “Testing Instructions” field on the “Enter a Submission” form.
(vii) Public Distribution: The Maker may make the Application available to the public via a website or online store, but is not required to do so.
(viii) Multiple Submissions: A Maker may submit more than one (1) Submission, however, each Submission must be unique and substantially different from each of the Maker’s other Submissions, as determined by the Poster and/or the Administrator.
(ix) Additional Developer Tools: Makers are encouraged, but not required, to integrate the following with their Application: Cisco Meraki APIs, Cisco’s video call SDK, Cisco Spark widgets, and IBM Watson. Applications may integrate other SDKs, APIs and data, provided the Maker is authorized to use them.
(x) Spark Depot Certification: Makers are encouraged but NOT required to certify their Applications in the Spark Depot during the Hackathon Submission Period.
(xi) Intellectual Property: Your Submission must: (a) be your (or your Team, Small Organization, or Large Organization’s) original work product; (b) be solely owned by you, your Team, your Small Organization, or your Large Organization with no other person or entity having any right or interest in it; (c) not violate the intellectual property rights or other rights including but not limited to copyright, trademark, patent, contract, and/or privacy rights, of any other person or entity; and (d) not include any commercial content that (i) promotes any product or service, other than one owned or branded by Poster, or (ii) disparages Poster, its affiliates, partners, customers, competitors or any third party in any way. A Maker may contract with a third party for technical assistance to create the Submission provided the Submission components are solely the Maker’s work product and the result of the Maker’s ideas and creativity, and the Maker owns all rights to them. A Maker may submit a Submission that includes the use of open source software or hardware, provided the Maker complies with applicable open source licenses and, as part of the Submission, creates software that enhances and builds upon the features and functionality included in the underlying open source product. By entering the Hackathon you represent, warrant, and agree that your Submission meets these requirements.
(xii) Financial or Preferential Support: An Application must not have been developed, or derived from an Application developed, with financial or preferential support from the Poster or Administrator. Such Applications include, but are not limited to, those that received funding or investment for their development, were developed under contract, or received a commercial license, from the Poster or Administrator any time prior to the end of Hackathon Submission Period. The Poster, at their sole discretion, may disqualify an Application, if awarding a prize to the Application would create a real or apparent conflict of interest.
C. Text Description, Image, Video, and Additional Submission Materials
(i) Text Description: The text description should explain the features and functionality of your Application and what makes it unique.
(ii) Images: The image(s) should be photographs or screenshots of your working Application.
(iii) Video: The video portion of the Submission:
a. should be less than five (5) minutes;
b. must include footage that clearly explains the Application’s features and functionality through a comprehensive demonstration;
c. must be uploaded to YouTube, Vimeo, or Youku, and a link to the video must be provided on the submission form on the Hackathon Website; and
d. must not include third party trademarks, or copyrighted music or other material unless the Maker has permission to use such material.
(iv) Additional Submission Materials: Makers are encouraged to submit varied forms of presentation and documentation to demonstrate their Application, including a Website, Github Pages, Blog post, or pitch deck.
D. Submission Modifications
A. Draft Submissions: Prior to the end of the Hackathon Submission Period, you may save draft versions of your Submission on Devpost to your portfolio before submitting the Submission materials to the Hackathon for evaluation. Once the Submission Period has ended, you may not make any changes or alterations to your Submission, but you may continue to update the project in your Devpost portfolio.
B. Modifications After the Hackathon Submission Period. The Poster may permit you to modify part of your Submission after the Hackathon Submission Period for the purpose of removing material that potentially infringes a third party mark or right, discloses personally identifiable information, or is otherwise inappropriate. The modified Submission must remain substantively the same as the original Submission with the only modification being what the Poster permits.
5. SUBMISSION RIGHTS
A. Maker Rights:Subject to the licenses described below, any applicable intellectual property rights to a Submission will remain with the Maker.
B. Poster Rights:By entering the Hackathon, you grant to the Poster, Administrator, and any other third parties acting on the Poster’s behalf, a royalty-free, non-exclusive, irrevocable, worldwide perpetual license to reproduce, encode, store, copy, transmit, publish, post, broadcast, display, publicly perform, adapt, exhibit and use for promotional purposes the Submission, in perpetuity. This license includes, but is not limited to, posting or linking to the Submission on Poster’s, Administrator’s, and partners’ websites and applications, including the Hackathon Website, and display and promotion of the Submission in any other media, worldwide.
C. Submission Display:The following Submission components may be displayed to the public: name, description, images, video URL, website, URL, team members, the Submission category and platform, and submitter type. Other Submission materials may be viewed by the Poster, Administrator, and Judges for screening and evaluation.
D. Makers represent and warrant that the Poster, Administrator, and Hackathon partners are free to use Makers’ Submission in the manner described above, as provided or as modified by the Administrator, without obtaining permission or license from any third party and without any compensation to Makers.
A. Judges: Eligible Submissions will be evaluated by a panel of qualified judges selected by the Poster (the “Judges”), which may include, but not be limited to, judges from the following industries: tech press, venture capital and software/tech. Judges may be employees of the Poster or external, may or may not be listed individually on the Hackathon Website, and may change before or during the Judging Period. Judging may take place in one or more rounds with one or more panels of Judges, at the discretion of the Poster.
B. Criteria: The Judges will score eligible Submissions using the following equally weighted criteria (the “Judging Criteria”):
(i) Quality & Impact
The Judging Criteria above may not apply to every Prize. See Section 7 below for the Judging Criteria that apply for each Prize. The Maker(s) that are eligible for a Prize, and whose Submissions earn the highest overall scores based on the applicable Judging Criteria, will become potential winners of that Prize.
(ii) Execution (Includes how well the idea was designed and implemented by the Maker, the complexity of the build and creative use of Cisco Spark developer tools.)
(ii) Presentation (Includes the quality of the video, description, and Application code.)
C. Submission Review: JUDGES are not required to test the Application and may choose to judge based solely on the text description, IMAGES and video provided in the Submission.
D. Tie Breaker: For each Prize listed in Section 7 below, if two (2) or more Submissions are tied, the tied Submission with the highest score in the first applicable criterion listed above will be considered the higher scoring Submission. In the event any ties remain, this process will be repeated, as needed, by comparing the tied Submissions’ scores on the next applicable criterion. If two (2) or more Submissions are tied on all applicable criteria, the panel of Judges will vote on the tied Submissions.
Applicable Judging Criteria
Best Healthcare App
30 minute virtual pitch meeting with Cisco executive
DevNet Marketing visibility
Cisco Spark “Swag”
All except Large Organizations
i, ii, iii
Best Education App
30 minute virtual pitch meeting with Cisco executive
DevNet Marketing visibility
Cisco Spark “Swag”
All except Large Organizations
i, ii, iii
Best Sales App
30 minute virtual pitch meeting with Cisco executive
DevNet Marketing visibility
Cisco Spark “Swag”
All except Large Organizations
i, ii, iii
Popular Choice Award
All except Large Organizations
Determined by public voting**
Large Organization Recognition Award
Virtual pitch meeting with Cisco Spark business development team
Only Large Organizations
i, ii, iii
**Please review the Devpost Hackathon Terms of Service at https://info.devpost.com/hackathon_terms for voting rules.
8. Verification of Potential Winners
A. Verification Requirement: THE AWARD OF A PRIZE TO A POTENTIAL WINNER IS SUBJECT TO VERIFICATION OF THE IDENTITY, QUALIFICATIONS AND ROLE OF THE POTENTIAL WINNER IN THE CREATION OF THE SUBMISSION. The final decision to designate a winner shall be made by the Poster and/or Administrator.
B. Required Forms: Potential winners will be notified using the email address associated with the Devpost account used to enter the Submission (the submitter is the “Representative” in the case of a Team, Small Organization, or Large Organization). In order to receive a Prize, the potential winner (including all participating team members in the case of a Team, Small Organization, or Large Organization) will be required to sign and return to the Poster or Administrator, affidavit(s) of eligibility (or a similar verification document) and liability/publicity release(s), and any applicable tax forms (“Required Forms”).
Deadline for Returning Required Forms: Ten (10) business days after the Required Forms are sent.
C. Disqualification: The Poster and/or Administrator may deem a potential winner (or participating team members) ineligible to win if:
(i) the potential winner’s Representative or any participating member does not respond to multiple emails or fails to sign and return the Required Forms by the deadline listed above, or responds and rejects the Prize;
(ii) the Prize or Prize notification is returned as undeliverable; or
(iii) the Submission or the potential winner, or any member of a potential winner’s Team, Small Organization, or Large Organization, is disqualified for any other reason.
In the event of a disqualification, the Poster and/or Administrator may award the applicable Prize to an alternate potential winner.
9. PRIZE DISTRIBUTION
A. Substitutions & Changes: Limit one (1) Prize per eligible Maker or Team. The approximate retail values (ARV) are subject to change based on current market conditions at the time of Prize fulfillment. Winners are not entitled to any surplus between actual ARV of a Prize and the stated ARV and any difference between the stated ARV and the actual value of the Prize will not be awarded. No substitution, assignment, transfer or cash redemption of any Prize is allowed by an individual or Team winner. The Poster has the right, in its sole discretion, to make a Prize substitution of equivalent or greater value. If applicable, a Prize may be awarded in the form of voucher(s), coupon(s) and/or gift card(s) in Poster’s sole discretion. The Poster will not award a Prize if there are no eligible Submissions entered in the Hackathon, or if there are no eligible Makers or Submissions for a specific Prize.
B. Prize Delivery: Prizes will be payable to the Maker, if an individual, to the Maker’s Representative, if a Team, or to the Small Organization, if the Maker is a Small Organization. It will be the responsibility of the winning Maker’s Representative to allocate the Prize among their Team or Small Organization’s participating members, as the Representative deems appropriate. A monetary Prize will be mailed to the winning Maker’s address (if an individual) or the Representative’s address (if a Team or Small Organization), or wired to the Maker, Maker Representative, or Small Organization’s bank account, only after receipt of the Required Forms.
Failure to provide correct information on the Required Forms, or other correct information required for the delivery of a Prize, may result in delayed Prize delivery, disqualification or the Maker, or forfeiture of a Prize.
If a potential winner is unable to participate in or accept the Prize or any portion of the Prize for any reason, Poster shall have no further obligation to such potential winner. Neither Poster nor any of its Prize suppliers will replace any lost or stolen Prizes, cards or certificates after being awarded to winners. In no event will Poster be responsible for awarding more than the stated number of Prizes.
C. Prize Delivery Timeframe: Within forty-five (45) days of the Poster or Administrator’s receipt of the Required Forms, Poster or Administrator will notify winner(s) by phone, mail and/or email in their sole discretion.
D. Fees & Taxes: Winners (and in the case of Team or Small Organization, all participating members) are responsible for any fees associated with receiving or using a prize, including but not limited to, travel and wiring fees. Winners (and in the case of Team or Small Organization, all participating members) are responsible for reporting and paying all applicable taxes in their jurisdiction of residence (federal, state/provincial/territorial and local). Winners may be required to provide certain information to facilitate receipt of the award, including completing and submitting any tax or other forms necessary for compliance with applicable withholding and reporting requirements. United States residents are required to provide a completed form W-9 and residents of other countries are required to provide a completed W-8BEN form. Winners are also responsible for complying with foreign exchange and banking regulations in their respective jurisdictions and reporting the receipt of the Prize to relevant government departments/agencies, if necessary. The Poster, Administrator, and/or Prize provider reserve the right to withhold a portion of the prize amount to comply with the tax laws of the United States or other Poster jurisdiction, or those of a winner’s jurisdiction. If any Prize involves travel, all potential winners are responsible for obtaining all necessary travel documents, including valid passports, visas and travel insurance, and complying with all health or other government regulations.
Participant acknowledges and agrees that Poster has neither made, nor is in any manner responsible or liable for, any warranty, representation or guarantee, expressed or implied, in fact or in law, relative to any Prize or the Hackathon. All warranties are hereby disclaimed; and each potential winner will accept the Prize "AS IS." All costs and expenses, including support services, not specifically listed above as part of the Prize, are solely the winner’s responsibility.
10. ENTRY CONDITIONS AND RELEASE
A. By entering the Hackathon, you (and, if you are entering on behalf of a Team, Small Organization, or Large Organization, each participating members) agree(s) to the following:
(i) The relationship between you, the Maker, and the Poster and Administrator, is not a confidential, fiduciary, or other special relationship.
(ii) You will be bound by and comply with these Official Rules and the decisions of the Poster, Administrator, and/or the Hackathon Judges which are binding and final in all matters relating to the Hackathon.
(iii) You release, indemnify, defend and hold harmless the Poster, Administrator, Promotion Entities, and their respective parent, subsidiary, and affiliated companies, the Prize suppliers and any other organizations responsible for sponsoring, fulfilling, administering, advertising or promoting the Hackathon, and all of their respective past and present officers, directors, employees, agents and representatives (hereafter the “Released Parties”) from and against any and all claims, expenses, and liabilities (including reasonable attorneys’ fees), including but not limited to negligence and damages of any kind to persons and property, defamation, slander, libel, violation of right of publicity, infringement of trademark, copyright or other intellectual property rights, property damage, or death or personal injury arising out of or relating to a Maker’s entry, creation of Submission or entry of a Submission, participation in the Hackathon, acceptance or use or misuse of the Prize (including any travel or activity related thereto) and/or the broadcast, transmission, performance, exploitation or use of the Submission as authorized or licensed by these Official Rules.
B. Without limiting the foregoing, the Released Parties shall have no liability in connection with:
(i) any incorrect or inaccurate information, whether caused by the Poster or Administrator’s electronic or printing error, or by any of the equipment or programming associated with or utilized in the Hackathon;
(ii) technical failures of any kind, including, but not limited to malfunctions, interruptions, or disconnections in phone lines, internet connectivity or electronic transmission errors, or network hardware or software or failure of the Hackathon Website;
(iii) unauthorized human intervention in any part of the entry process or the Hackathon;
(iv) technical or human error which may occur in the administration of the Hackathon or the processing of Submissions; or
(v) any injury or damage to persons or property which may be caused, directly or indirectly, in whole or in part, from the Maker’s participation in the Hackathon or receipt or use or misuse of any Prize.
The Released Parties are not responsible for incomplete, late, misdirected, damaged, lost, illegible, or incomprehensible Submissions or for address or email address changes of the Makers. Proof of sending or submitting will not be deemed to be proof of receipt by the Poster or Administrator.
If for any reason any Maker’s Submission is determined to have not been received or been erroneously deleted, lost, or otherwise destroyed or corrupted, the Maker’s sole remedy is to request the opportunity to resubmit its Submission. Such request must be made promptly after the Maker knows or should have known there was a problem, and will be determined at the sole discretion of the Poster.
By participating in the Hackathon you consent to the use of personal information about you, if you are a winner, by the Poster, Administrator, and third parties acting on their behalf. Such personal information includes, but is not limited to, your name, likeness, photograph, voice, opinions, comments and hometown and country of residence. It may be used in any existing or newly created media, worldwide without further payment or consideration or right of review, unless prohibited by law. Authorized use includes advertising and promotional purposes.
The duration of your consent is for a period of three (3) years following the conclusion of the Hackathon. This consent applies, as applicable, to all members a Maker’s Team, Small Organization or Large Organization that participated in the winning Submission.
12. GENERAL CONDITIONS
A. Poster and Administrator reserve the right, in their sole discretion, to cancel, suspend and/or modify the Hackathon, or any part of it, in the event of a technical failure, fraud, or any other factor or event that was not anticipated or is not within their control.
B. Poster and Administrator reserve the right in their sole discretion to disqualify any individual or Maker it finds to be actually, or presenting the appearance of, tampering with the entry process or the operation of the Hackathon or to be acting in violation of these Official Rules or in a manner that is inappropriate, unsportsmanlike, not in the best interests of this Hackathon, or a violation of any applicable law or regulation.
C. Any attempt by any person to undermine the proper conduct of the Hackathon may be a violation of criminal and civil law. Should Poster or Administrator suspect that such an attempt has been made or is threatened, they reserve the right to take appropriate action including but not limited to, requiring a Maker to cooperate with an investigation and referral to criminal and civil law enforcement authorities.
D. If there is any discrepancy or inconsistency between the terms and conditions of the Official Rules and disclosures or other statements contained in any Hackathon materials, including but not limited to, the Hackathon Submission form, Hackathon Website, advertising (including but not limited to television, print, radio or online ads), the terms and conditions of the Official Rules shall prevail.
E. The terms and conditions of the Official Rules are subject to change at any time, including the rights or obligations of the Maker, the Poster and the Administrator. The Poster and Administrator will post the terms and conditions of the amended Official Rules on the Hackathon Website. To the fullest extent permitted by law, any amendment will become effective at the time specified in the posting of the amended Official Rules or, if no time is specified, the time of posting.
F. If at any time prior to the deadline, a Maker or prospective Maker believes that any Official Rule is or may be unclear or ambiguous, they must submit a written request for clarification.
G. The Poster or Administrator’s failure to enforce any term of these Official Rules shall not constitute a waiver of that provision. Should any provision of these Official Rules be or become illegal or unenforceable in any jurisdiction whose laws or regulations may apply to a Maker, such illegality or unenforceability shall leave the remainder of these Official Rules, including the Rule affected, to the fullest extent permitted by law, unaffected and valid. The illegal or unenforceable provision shall be replaced by a valid and enforceable provision that comes closest and best reflects the Poster’s intention in a legal and enforceable manner with respect to the invalid or unenforceable provision.
H. Excluding Submissions, all intellectual property related to this Hackathon, including but not limited to copyrighted material, trademarks, trade-names, logos, designs, promotional materials, web pages, source codes, drawings, illustrations, slogans and representations are owned or used under license by the Poster and/or Administrator. All rights are reserved. Unauthorized copying or use of any copyrighted material or intellectual property without the express written consent of its owners is strictly prohibited. Any use in a Submission of Poster or Administrator intellectual property shall be solely to the extent provided for in these Official Rules.
13. LIMITATIONS OF LIABILITY
By entering, all Makers (including, in the case of a Team, Small Organization, or Large Organization, all participating members) agree to be bound by the Official Rules and hereby release the Released Parties from any and all liability in connection with the Prizes or Maker’s participation in the Hackathon. Provided, however, that any liability limitation regarding gross negligence or intentional acts, or events of death or body injury shall not be applicable in jurisdictions where such limitation is not legal.
A. Except where prohibited by law, as a condition of participating in this Hackathon, Maker agrees that:
(i) any and all disputes and causes of action arising out of or connected with this Hackathon, or any Prizes awarded, shall be resolved individually, without resort to any form of class action lawsuit, and exclusively by final and binding arbitration under the rules of the American Arbitration Association and held at the AAA regional office nearest the contestant;
(ii) the Federal Arbitration Act shall govern the interpretation, enforcement and all proceedings at such arbitration; and
(iii) judgment upon such arbitration award may be entered in any court having jurisdiction.
B. Under no circumstances will Maker be permitted to obtain awards for, and contestant hereby waives all rights to claim, punitive, incidental or consequential damages, or any other damages, including attorneys’ fees, other than contestant’s actual out-of-pocket expenses (i.e., costs associated with entering this Hackathon), and Maker further waives all rights to have damages multiplied or increased.
C. All issues and questions concerning the construction, validity, interpretation and enforceability of these Official Rules, or the rights and obligations of Maker and Poster in connection with this Hackathon, shall be governed by, and construed in accordance with, the substantive laws of the State of New York, USA without regard to New York choice of law rules.
SOME JURISDICTIONS DO NOT ALLOW THE LIMITATIONS OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE MAY NOT APPLY TO YOU.
15. ADDITIONAL TERMS THAT ARE PART OF THE OFFICIAL RULES
Please review the Devpost Hackathon Terms of Service at https://info.devpost.com/hackathon_terms for additional rules that apply to your participation in the Hackathon and more generally your use of the Hackathon Website. Such Terms of Service are incorporated by reference into these Official Rules. If there is a conflict between the Terms of Service and these Official Rules, the latter terms shall control with respect to this Hackathon only.
Participation in the Hackathon constitutes Maker’s full and unconditional agreement to these Official Rules. By entering, a Maker agrees that all decisions related to the Hackathon that are made pursuant to these Official Rules are final and binding, and that all such decisions are at the sole discretion of the Poster and/or Administrator.
If you have any questions or comment, or wish to send us any notice regarding this Hackathon, please email us at Support@Devpost.com.