Cisco Meraki Global Hackathon 2020 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 Meraki Global Hackathon 2020
Hackathon Website: https://cisco-meraki-hackathon-2020.devpost.com/
1. POSTER & ADMINISTRATOR
Poster (the “Poster”): Cisco Meraki LLC (“Cisco Meraki”), 500 Terry A Francois Blvd, San Francisco, CA 94158
The Poster is the sponsor and entity responsible for the Hackathon.
Administrator (the “Administrator”): Cisco Meraki LLC (“Cisco Meraki”), 500 Terry A Francois Blvd, San Francisco, CA 94158
2. DATES AND TIMING
Hackathon Submission Period: May 26, 2020 (10:45am Pacific Time) – May 28, 2020 (10:45am Pacific Time) (the “Hackathon Submission Period”)
Judging Period: May 28, 2020 (11:00 am PST Pacific Time) – June 1, 2020 (12:00 pm Pacific Time) (the “Judging Period”)
Public Voting Period: June 1, 2020 (12:30pm Pacific Time) – June 5, 2020 (5:00pm Pacific Time) (the “Public Voting Period”)
Winners Announced: On or around June 8, 2020 (9:00am Pacific Time)
The Administrator will be the official timekeeper for the Hackathon.
- The Hackathon is open to teams (“Teams”) of 4 to 6 IT professionals currently employed by and representing an authorized Cisco Meraki reseller or service provider (each a “Partner”).
- Each Team member must be at least the age of majority in their jurisdiction of residence and have the permission of the applicable Partner to participate in the Hackathon and accept the prizes described below if awarded to such Team.
- Team members are solely responsible for informing the applicable Partner of their participation in the Hackathon, and compliance with any applicable laws, contractual limitations and procedures established by the Partner related to their participation.
- If a Team is entering the Hackathon, they must appoint and authorize one (1) individual (the “Representative”) to represent, act, and enter a Submission (defined below), on their behalf. The Representative must meet the eligibility requirements above. By entering a Submission on the Hackathon Website on behalf of a Team you represent and warrant that you are the Representative authorized to act on behalf of your Team.
- The Hackathon is void where prohibited or restricted by law.
Ineligible Participants The Hackathon is not open to:
- Individuals who are residents of, or Teams representing Partners domiciled in, a country, state, province or territory where the laws of the United States or local law restricts participating or receiving a prize in the Hackathon (including, but not limited to, Brazil, Quebec, and Cuba, Sudan, Iran, North Korea, Syria, Myanmar (Burma), Hong Kong, Macau, Taiwan and any other jurisdiction 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
Teams must do the following to participate in the Hackathon:
- Register for the Hackathon on the Hackathon Website at http://cisco-meraki-hackathon-2020.devpost.com 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. Only one Devpost account created by a Team’s Representative is required per Team.
- Create a developer account on Cisco DevNet at https://developer.cisco.com/. There is no charge for creating a developer account or for using the Cisco Meraki developer tools required in the Hackathon. Only one Cisco DevNet account created by a Team’s Representative is required per Team.
- Visit the Resources page of the Hackathon Website and the Cisco Meraki Developer Hub page to learn more about the Cisco Meraki APIs, and how to get started.
- Build a working Cisco Meraki application, integration, or solution using Cisco Meraki APIs that fits into one (1) of the following categories: Retail/Hospitality, Smart Spaces, Healthcare/Manufacturing or IT Operations (each an “Application”). Further Application requirements are below.
- Select a theme from the dropdown
- Select a challenge from the dropdown
- Select technologies used from the dropdown
- Respond to the question “What does it do?” on how the Application is to be used
- Respond to the question “How the Application was built?” by describing the programming languages, storage or any additional relevant information pertaining to the Application that the Team would like to disclose
- Respond to the question “Challenges Faced” by sharing any challenges the team encountered while building the Application
- Create and submit a video using Vimeo or YouTube that meets the requirements described in Paragraph C below.
- Create and submit screenshots or photographs of the Application (in PDF format) that meet the requirements described in Paragraph C below.
- Complete and enter all of the required fields on the “Enter a Submission” page of the Hackathon Website during the Hackathon Submission Period (May 26, 2020 at 10:45am PST - May 28, 2020 at 10:45am PST) and follow the required drop down and open text boxes below:
- Once the above video, image, and Hackathon Website text submission requirements (collectively, the “Submission”) are complete, submit your Submission beforeMay 28, 2020 at 10:45am PST for Judges to begin reviewing.
All Submission materials must be in English or, if not in English, the Team must provide an English translation of the demonstration video, text description, and all other materials submitted.
(i) What to Create: Teams are required to create a working Cisco Meraki Application using at least one (1) API from the Cisco Meraki developer tools available at https://developer.cisco.com/meraki (each an “Application”) and one (1) Additional Developer Tool (defined below). Teams are encouraged to make varied and creative use of Cisco Meraki API endpoints and Additional Developer Tools to create their Application.
(ii) Integration of Additional Developer Tools: Teams are required to integrate at least one (1) of the following tools with their Application: Cisco AppDynamics APIs, Cisco Stealthwatch APIs, Cisco WebEx Teams APIs, Cisco Duo APIs, or Cisco Umbrella APIs or an Ecosystem Partner Listed Sponsor Application from those listed on the Hackathon Website at the beginning of the Hackathon Submission Period (each an “Additional Developer Tool”). Applications may integrate other APIs and data, provided the Team is authorized to use them.
(iii) Categories: Applications must be entered into only one (1) of the following categories (the “Categories”):
- Retail or Hospitality
- Smart Spaces
- Healthcare or Manufacturing
- IT Operations
As part of your Submission, you must select one (1) Category which best applies to your Solution. At any time, and in 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 prizes. See Section 7 for prize details.
(iv) 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, text description, and screenshot images.
(v) Platforms: A submitted Application must run on at least one (1) of the following platforms (each a “Platform”):
- 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)
(vi) New & Existing: Applications must be either newly created by the Team or, if the Application existed prior to the Hackathon Submission Period, must have been substantially updated after the start of the Hackathon Submission Period. Teams 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.
(vii) Public Distribution: Teams may make their Application available to the public via a website or online store, but are not required to do so.
(viii) Multiple Submissions: Each Team may submit more than one (1) Submission, however, each Submission must be unique and substantially different from each of the Team’s other Submissions, as determined by the Poster and/or the Administrator.
(ix) Intellectual Property: Your Submission must: (a) be your Team’s original work product; (b) be solely owned by your Team, or the Partner represented by your Team, 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 integrated into the submitted Application which is owned or branded by Poster or the owner or brand of any integrated Additional Developer Tool, or (ii) disparages Poster, its affiliates, partners, customers, competitors or any third party, including Ecosystem Partner Listed Sponsors and the owners/brands of other Additional Developer Tools, in any way. A Team may contract with a third party for technical assistance to create the Submission provided the Submission components are solely the Team’s work product and the result of the Team’s ideas and creativity, and the Team owns all rights to them. A Team may submit a Submission that includes the use of open source software or hardware, provided the Team 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.
(x) 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. The foregoing is not intended to serve as any general limitation on use of the Meraki APIs or Additional Developer Tools described above.
Text Description, Image, Video, and Additional Submission Materials
(i) Text Description: The text description should clearly and concisely explain the features and functionality of your Application and what makes it unique.
- What does the Application do
- How was the Application built
- What challenges did the team face building the Application
(ii) Images: The image(s) must be photographs or screenshots of your working Application.
- PDF format
- Capture the Application in one or more still images
(iii) Video: The video portion of the Submission:
- must be less than seven (7) minutes;
- must include footage that clearly explains the Application’s features and functionality through a comprehensive demonstration;
- must be uploaded to YouTube or Vimeo, and a link to the video must be provided on the submission form on the Hackathon Website; and
- must not include third party trademarks, or copyrighted music or other material unless the Team has permission to use such material.
(iv) Additional Submission Materials: Teams are encouraged to submit varied forms of presentation and documentation to demonstrate their Application, including a Website, Blog post, or pitch deck.
- Draft Submissions: Prior to the end of the Hackathon Submission Period (May 28, 2020 at 10:45am PST), 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 (May 28, 2020 at 10:45am PST), you may not make any changes or alterations to your Submission, but you may continue to update the project in your Devpost portfolio.
- 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
- Team Rights: Subject to the licenses and rights to feedback described below, any applicable intellectual property rights to a Submission will remain with the Team.
- Poster Rights: By entering the Hackathon, each Team (including the Partner it represents and its individual Team members) grants 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. Poster will be the exclusive owner of and each Team (including the Partner it represents and its individual Team members) hereby assigns and agrees to assign all right, title, and interest in and to all intellectual property rights to feedback provided to Poster in association with the Hackathon regarding any of Poster’s or its affiliates’ products, services, and solutions. Teams and the Partners they represent each represent and warrant that the Poster, Administrator, and Hackathon partners are free to use the Teams’ Submissions 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 the Teams or Partners they represent.
Submission Display: The following Submission components may be displayed to the public: name of Partner, Team, solution description, images and video of Application andTeam members), Application 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 and as otherwise permitted in these Official Rules.
- 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.
- Criteria: The Judges will score eligible Submissions using the following equally weighted criteria (the “Judging Criteria”):
(i) Quality of the Idea (Is the idea a strong minimal viable product for the customer to use today?)
(ii) Implementation (How well the idea was designed and implemented by the Team, as well as the complexity of the build and creative use of Cisco Meraki developer tools.)
(ii) Potential Impact to the Business Category (Judges will focus on the quality of the video submission and text description. Participants’ Application should be able to drive and improve business processes based on the challenge provided by the Poster.)
(iii) Value to the Persona (Measured on whether the Application solves for the customer scenario and requirements outlined in the scenario videos.)
(iv) Complexity (Includes the practicability and ease of implementation in a customer environment.)
(v) APIs Used (Includes meeting minimum requirements of at least one (1) Meraki API and one (1) Additional Developer Tool.)
The Teams 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.
- 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.
- 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.
One (1) winning Team will be selected from each of the following Categories:
- Retail and Hospitality,
- Smart Spaces,
- Healthcare and Manufacturing, and
- IT Operations.
- Overall Hackathon Winner
- Public Voting Award
The winning Team in each category will be eligible to be featured in a Meraki Blog spotlight and the Meraki Unboxed podcast and to receive visibility in the Meraki Community (collectively, the “Prize”).
**Please review the Devpost Hackathon Terms of Service at https://info.devpost.com/hackathon_terms for voting rules.
8. Verification of Potential Winners
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.
Required Forms: Potential winners will be notified using the email address associated with the registration form and Devpost account used to enter the Submission. In order to receive a Prize, the potential winner (including all participating team members may 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, or as otherwise stated in the Required Forms.
- 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, is disqualified for any other reason in the discretion of the Poster and/or Administrator.
In the event of a disqualification, the Poster and/or Administrator may award the applicable Prize to an alternate potential winner.
9. PRIZE DISTRIBUTION
Substitutions & Changes: Limit one (1) Prize per eligible Team. The Prize has no retail value. No substitution, assignment, transfer or cash redemption of any Prize is allowed. The Poster has the right, in its sole discretion, to make Prize substitutions. If applicable, a Prize may be awarded in the form of voucher(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 Teams or Submissions for a specific Prize.
Awarding of Prizes: Prizes will be awarded to the Partner represented by the winning Team. It will be the responsibility of the Partner represented by the winning Team and/or the Team’s Representative (on behalf of the Partner and Team) to coordinate with Poster to receive and/or take advantage of the Prize, as appropriate.There are no monetary Prizes.
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 Team, 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. In no event will Poster be responsible for awarding more than or substitutions of the stated Prizes.
- Prize Delivery Timeframe: Following conclusion of the Hackathon and not more than 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.
- Fees & Taxes:. Winners are responsible for reporting and paying all applicable taxes (if any) in their jurisdiction of residence (federal, state/provincial/territorial and local). Winners may be required to provide certain information to facilitate receipt of the Prize, including completing and submitting any tax or other forms necessary for compliance with applicable withholding and reporting requirements.. 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 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
By entering the Hackathon, each Team, the Partner represented by such Team, and each individual participant agree(s) to the following:
(i) The relationship between you, the Team, and/or the Partner on the one hand and the Poster and Administrator on the other, is not a confidential, fiduciary, or other special relationship.
(ii) Each Team, Partner and all participants 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) Each Team, Partner and all participants 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 or privacy, infringement of trademark, copyright or other intellectual property rights, property damage, or death or personal injury arising out of or relating to a Team’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. The foregoing release applies to all claims, expenses, and liabilities whether known or unknown or suspected to exist.
- 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 Team’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 Teams. Proof of sending or submitting will not be deemed to be proof of receipt by the Poster or Administrator.
If for any reason any Team’s Submission is determined to have not been received or been erroneously deleted, lost, or otherwise destroyed or corrupted, the Team’s (and applicable Partner’s) sole remedy is to request the opportunity to resubmit its Submission. Such requests must be made promptly after the Team 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 each individual Team member consents to the use of all submitted personal information about such Team member by the Poster, Administrator, and third parties acting on their behalf. Such personal information includes, but is not limited to, the Team member’s name, likeness, photograph, video, voice, opinions, comments, hometown,country of residence, and business email address. It may be used in any existing or newly created media, worldwide without payment or consideration or right of review, unless prohibited by law. Authorized use includes general advertising and promotional purposes including, but not limited to, on Cisco Meraki’s website at https://meraki.cisco.com/. Each Team member further represents that they understand their participation and acceptance of these Official Rules is voluntary and that they are not obligated to permit Poster or Administrator or their affiliates to use the submitted content
12. GENERAL CONDITIONS
- 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.
- Poster and Administrator reserve the right in their sole discretion to disqualify any individual or Team 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.
- 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 Partner or Team and its members to cooperate with an investigation and referral to criminal and civil law enforcement authorities.
- 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.
- The terms and conditions of the Official Rules are subject to change at any time, including the rights or obligations of the Teams, Team members, Partners, 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. A Representative’s click-accepting these Official Rules and participation by a Team in the Hackathon each constitute a Team, its Team members, and the represented Partner’s express agreement to abide by these Official Rules, as they may be amended or modified.
- If at any time prior to the deadline, a Team or prospective Team believes that any Official Rule is or may be unclear or ambiguous, they must submit a written request for clarification.
- 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 Team or its members, 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.
- 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 Teams (including all participating members and the Partners represented by such Teams) agree to be bound by the Official Rules and hereby release and discharge the Released Parties from any and all liability in connection with the Prizes or Team’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.
Except where prohibited by law, as a condition of participating in this Hackathon, each Team 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.
- Under no circumstances will a Team be permitted to obtain awards for, and contestants hereby waive all rights to claim, punitive, incidental or consequential damages, or any other damages, including attorneys’ fees, other than actual out-of-pocket expenses (i.e., costs associated with entering this Hackathon), and each Team further waives all rights to have damages multiplied or increased.
- All issues and questions concerning the construction, validity, interpretation and enforceability of these Official Rules, or the rights and obligations of each Team and Poster in connection with this Hackathon, shall be governed by, and construed in accordance with, the substantive laws of the State of California, USA without regard to California 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 each Team’s (including the Team members' and Partner’s represented by the Team) full and unconditional agreement to these Official Rules. By entering, a Team 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 email@example.com.