Azure Sentinel Hackathon 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: Azure Sentinel Hackathon (the “Hackathon”)
Hackathon Website: https://azuresentinelhackathon.devpost.com/ (the “Hackathon Website”)
These Official Rules govern the operation of the Hackathon. Microsoft Corporation, One Microsoft Way, Redmond, WA, 98052, USA, is the Hackathon sponsor (“Sponsor”).
Devpost is a Hackathon Party (“Devpost”) and will host the Hackathon on their platform and be the official timekeeper for the Hackathon. Devpost will also notify winners and fulfill prizes.
2. DATES AND TIMING
Hackathon Submission Period: May 6, 2020 (9:00am Pacific Time) – July 1, 2020 (9:00pm Pacific Time) (the “Hackathon Submission Period”)
Judging Period: July 2, 2020 (9:00am Pacific Time) – July 22, 2020 (9:00am Pacific Time) (the “Judging Period”)
Winners Announced: On or around July 24, 2020 (9:00am Pacific Time)
Devpost 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 at of the time of entry (“Eligible Individuals”)
- Teams of Eligible Individuals (“Teams”)
(the above are collectively, “Makers”)
An Eligible Individual may join more than one Team or Organization and an Eligible Individual who is part of a Team or Organization may also enter the Hackathon on an individual basis.
If a Team or Organization is entering the Hackathon, they must appoint and authorize one 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 Site on behalf of a Team or Organization you represent and warrant that you are the Representative authorized to act on behalf of your Team or Organization.
PLEASE NOTE: It is your sole responsibility to review and understand your employer’s policies regarding your eligibility to participate in trade promotions, including this Hackathon. If you are participating in violation of your employer’s policies, you may be disqualified from entering or receiving prizes. Sponsor and Devpost disclaim any and all liability or responsibility for disputes arising between an employee and their employer related to this matter, and prizes will only be awarded in compliance with the employer’s policies.
B. The Hackathon IS NOT open to:
- Individuals who are residents of, or 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 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 Sponsor and Devpost (“Promotion Entities”)
- Employees, 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
- Any other individual or organization whose participation in the Hackathon would create, in the sole discretion of the Sponsor and/or Devpost, 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.
- Makers must build the submission to work in Azure Sentinel or using Azure Sentinel. To do so, Makers must sign up for an Azure Sentinel workspace, if Makers do not have access to an already existing Azure Sentinel workspace. There is no cost for creating an Azure Sentinel workspace; Makers only pay for the data Makers ingest. A free 31-day trial combined with a number of free cloud data sources will help keep Makers costs down.
- Azure Sentinel workspace setup – There are a few options here. Maker can choose one or more of these options.
- Maker can set up their own workspace as per their choice
- Maker can use their own existing Azure Sentinel workspace to start with
- Maker can follow the guidance and tools that will be provided to easily ingest data to help build the Maker’s Azure Sentinel environment, if it does not exist.
- Build or update functioning software or program or Azure Sentinel content files. Details on Azure Sentinel content files and / or the functioning software or program is listed below. This is termed as ‘submission’ for this hackathon.
- Azure Sentinel content files are as follows: Details on how to build these and examples are provided in the Azure Sentinel GitHub repository.
a. Azure Sentinel Analytic rule templates, hunting, investigation/exploration and/or parsers delivered via Kusto queries or YAML files
b. Azure Sentinel Data connectors delivered via json files and associated/dependent programs (as applicable),
c. Azure Sentinel Workbooks delivered via Azure Monitor json files
d. Azure Sentinel Playbooks delivered via Logic App playbook json files
e. Azure Sentinel advanced investigation Notebooks Azure Notebooks files
2. One or many of the abovementioned content files can be delivered as Azure deployment templates to deliver an end-to-end solution on Azure Sentinel platform. Including multiple content files in the submission can earn extra credit while judging the submission.
3. The functioning software or program can extend or integrate with Azure Sentinel via different APIs. Details on how to build this and what APIs can be used for different scenarios is covered in the integrating and extending Azure Sentinel blogpost.
- The submission must clearly provide one or more of the following:
- Improved data collection/ingestion, threat detection, hunting, investigation, response, security management experiences in Azure Sentinel
- Unlock the full potential of security operations scenarios in Azure Sentinel
- Enable enterprises to easily migrate to Azure Sentinel
- Submissions can be in the form of:
- Content including more than one content types listed above, like data connectors, workbooks, playbooks, analytic rule templates, investigation / exploration that can be delivered as-is or via deployment templates.
- Azure Sentinel API integrations or extensions or tools or templates that delivers enterprise value
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. Submission Requirements
(i) What to Create: Makers must build end-to-end solutions on Azure Sentinel platform that delivers enterprise value by helping users detect, investigate and respond to cybersecurity threats. This can be delivered via improved data collection/ingestion, threat detection, hunting, investigation, response, security management on Azure Sentinel and/or enable enterprises to be able to migrate to Azure Sentinel.
(ii) Functionality: The Submission 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.
(iii) Platforms: The Submission must run on at least one of the following:
- a smartphone or tablet (iOS or Android)
- a web browser (mobile or desktop)
- a desktop computer (Windows PC, Mac Desktop)
- machine learning models
(iv) New & Existing: Submissions must be either newly created by the Maker or, if the Submission (content or application or templates) existed prior to the Hackathon Submission Period, must have been updated after the start of the Hackathon Submission Period.
(v) Testing: The Maker must make the Submission available free of charge and without any restriction, for testing, evaluation and use by the Sponsor, Devpost and judges during the Hackathon and until the Judging Period ends.
If the Submission 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 Sponsor reserve the right, at their sole discretion, to require the Maker to provide physical access to the Application hardware upon request.
For Submissions running on widely available smartphones, tablets, or desktop computers, Makers may make their Submissions available using one of the following methods:
a. Android Applications: Upload an .apk file on the Enter a Submission form or provide a link for downloading the Submission in the “Testing Instructions” field on the Enter a Submission form.
b. iOS Applications:
- If your Submission 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 Submission, you must provide a promo code.
- If your Submission is not yet publicly available on the iTunes App Store, you must send a test build to the Devpost before the end of the Hackathon Submission Period using iTunes Connect. Enter Devpost’s email address to share a build for testing. Devpost’s iTunes account email is: email@example.com.
Devpost UDID: iPhone 8 (iOS 13.3.1) a2d30c918b5b7184172fe7c000caa2241d9cb710
c. Windows Phone applications: Upload an .xap file in the Enter a Submission form or provide a link for downloading your Submission 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. 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.
f. Web/Mobile Web:Provide a link for accessing your Submission on the “Testing Instructions” field on the Enter a Submission form.
(vi) Public Distribution: The Maker may make the Submission available to the public via a website or online store, but is not required to do so.
(vii) Multiple Submissions: A Maker may submit more than one Submission, however, each Submission must be unique and substantially different from each of the Maker’s other Submissions, as determined by the Sponsor.
(viii) SDKs, APIs, & Data: Submissions may integrate SDKs, APIs and data, provided the Maker is authorized to use them.
(ix) Intellectual Property: Your Submission must: (a) be your (or your Team or Organization’s) original work product; (b) be solely owned by you, your Team or your Organization with no other person or entity having any right or interest in it; and (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. 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.
(x) Financial or Preferential Support: A submission must not have been developed, or derived from a submission developed, with financial or preferential support from the Sponsor or Devpost. Such submissions 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 Sponsor or Administrator any time prior to the end of Hackathon Submission Period. The Sponsor, at their sole discretion, may disqualify a submission, if awarding a prize to the submission would create a real or apparent conflict of interest.
C. Text Description, Image, and Video Requirements
(i) Text Description: The text description should explain the features and functionality of the solution and describe how the Submission could help enterprise cybersecurity using Azure Sentinel .
(ii) Images: The image(s) should be photographs or screenshots of the working solution.
(iii) Video: The video portion of the Submission:
a. should be less than five (5) minutes
b. must include footage that clearly explains the solution features and functionality through a comprehensive demonstration
c. should describe how the solution can help enterprise cybersecurity on Azure Sentinel
d. must be uploaded to YouTube, Facebook Video, Vimeo, or Youku and be made public, and a link to the video must be provided on the submission form on the Hackathon Website; and
e. must not include third party trademarks, or copyrighted music or other material unless the Maker has permission to use such material.
D. Submission Modifications
i. Draft Submissions: Prior to the end of the Submission Period, you may save draft versions of your Submission on Devpost to your portfolio before submitting the Submission materials to the Competition 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.
ii. Modifications after the Submission Period. The Sponsor may permit you to modify part of your Submission after the Submission Period for the purpose of acquiring additional consent forms, adding a Competition hashtag to the demonstration video, or 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 Sponsor 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. Sponsor Rights:By entering the Hackathon, you grant to the Sponsor, Devpost, and any other third parties acting on the Sponsor’s behalf, a royalty-free, non-exclusive, worldwide perpetual license to display publicly and use for promotional purposes the Submission, in perpetuity. This license includes, but is not limited to, posting or linking to the Submission on Sponsor’s, Devpost’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 Sponsor, Devpost, and Judges for screening and evaluation.
D. Makers represent and warrant that the Sponsor, Devpost, and Hackathon partners are free to use Makers’ Submission in the manner described above, as provided or as modified by Devpost, without obtaining permission or license from any third party and without any compensation to Makers.
E. Submissions may be included in customer evidence or case studies for Azure Sentinel.
A. Judges: Eligible Submissions will be evaluated by a panel of judges selected by the Sponsor (the “Judges”). Judges may be employees of the Sponsor 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 Sponsor.
B. Criteria: The Judges will score eligible Submissions using the following equally weighted criteria (the “Judging Criteria”):
(i) Quality of Idea Indicates creativity, originality, and the potential to significantly improve organizational security using Azure Sentinel
(ii) Value to Enterprise Demonstrates usefulness to an enterprise, for example by streamlining or automating security operations, reducing threat detection and response times, or improving the effectiveness of existing security tools or enables migration to Azure Sentinel
(iii) Technical Implementation Assesses how well the idea was executed by the submitter, including the user experience, the complexity of the scenarios, blending in Microsoft and non-Microsoft entities or data or other APIs with Azure Sentinel, and whether it performs as expected
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.
C. Submission Review: JUDGES ARE NOT REQUIRED TO TEST THE SUBMISSION 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 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 or more Submissions are tied on all applicable criteria, the panel of Judges will vote on the tied Submissions.
Applicable Judging Criteria
All eligible Makers
i, ii, iii
All eligible Makers
i, ii, iii
Popular Choice Award
All eligible Makers
Determined by public voting**
**Please review the Devpost Terms of Service at http://Devpost.com/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 Sponsor.
B. Required Forms: Potential winners will be notified by Devpost 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 or Organization). In order to receive a Prize, the potential winner (including all participating team members in the case of a Team or Organization) will be required to sign and return to Devpost, 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 Sponsor and/or Devpost 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 or Organization, is disqualified for any other reason.
In the event of a disqualification, the Sponsor and/or Devpost may award the applicable Prize to an alternate potential winner.
9. PRIZE DISTRIBUTION
A. Substitutions & Changes: The Sponsor has the right to make a Prize substitution of equivalent or greater value. The Sponsor 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 from Devpost to the Maker, if an individual, to the Maker’s Representative, if a Team, or to the Organization, if the Maker is an Organization. It will be the responsibility of the winning Maker’s Representative to allocate the Prize among their Team or Organization’s participating members, as the Representative deems appropriate. A monetary Prize will be mailed from Devpost to the winning Maker’s address (if an individual) or the Representative’s address (if a Team or 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.
C. Prize Delivery Timeframe: Within 60 days of Devpost’s receipt of the Required Forms
D. Fees & Taxes: Winners (and in the case of Team or Organization, all participating members) are responsible for any fees associated with receiving or using a prize, including but not limited to, wiring fees. Winners (and in the case of Team or 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 SPONSOR, DEVPOST, 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 SPONSOR JURISDICTION, OR THOSE OF A WINNER’S JURISDICTION.
10. ENTRY CONDITIONS AND RELEASE
A. By entering the Hackathon, you (and, if you are entering on behalf of a Team or Organization each participating members) agree(s) to the following:
(i) The relationship between you, the Maker, and the Sponsor and Devpost, 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 Sponsor, Devpost, 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 Sponsor, Devpost, 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 Sponsor or Devpost’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 Sponsor or Devpost.
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 Sponsor.
By participating in the Hackathon you consent to the use of personal information about you, if you are a winner, by the Sponsor, Devpost, 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 years following the conclusion of the Hackathon. This consent applies, as applicable, to all members a Maker’s Team, or Organization that participated in the winning Submission.
12. GENERAL CONDITIONS
A. Sponsor and Devpost 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. Sponsor and Devpost 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 Sponsor or Devpost 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 Sponsor and the Devpost. The Sponsor and Devpost 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 Sponsor or Devpost’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 Sponsor’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 Sponsor and/or Devpost. 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 Sponsor or Devpost 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 or 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 Sponsor 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 Washington 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 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 Sponsor and/or Devpost.
If you have any questions or comments, or wish to send us any notice regarding this Hackathon, please email us at Support@Devpost.com.