The Docusign Hackathon: Unlocked Official Rules – (the  “Official Rules”) 

NO PURCHASE OR PAYMENT NECESSARY. A PURCHASE OR PAYMENT OF ANY KIND WILL NOT INCREASE YOUR CHANCES OF WINNING.  

SUBMISSION OF ANY ENTRY CONSTITUTES AGREEMENT TO THESE OFFICIAL RULES AS A CONTRACT BETWEEN Entrant (AND EACH INDIVIDUAL MEMBER OF ENTRANT), THE HACKATHON SPONSOR, AND DEVPOST.

Hackathon Name: The Docusign Hackathon: Unlocked (the “Hackathon”)

Hackathon Website: unlocked.devpost.com (the “Hackathon Website”)

1. SPONSOR & ADMINISTRATOR

Sponsor (the “Sponsor”): Docusign, 221 Main St., Suite 1550, San Francisco, CA 94105

Administrator: Devpost, Inc. (“Devpost”), 222 Broadway, Floor 19, New York, NY 10038

The Sponsor is the sponsor and entity responsible for the Hackathon. The Administrator will be the official timekeeper for the Hackathon.

2. DATES AND TIMING 

Hackathon Early Registration Period: October 29, 2024 (8:00 am Pacific Time) – November 20, 2024 (8:59 am Pacific Time) (the “Hackathon Early Registration Period”)

Hackathon Registration and Submission Period: November 20, 2024 (9:00 am Pacific Time) – January 27, 2025 (5:00pm Pacific Time) (the “Hackathon Submission Period”)

Judging Period: January 31, 2025 (2:15 pm Pacific Time) – February 16, 2025 (5:00 pm Pacific Time) (the “Judging Period”)

Feedback Period: November 20, 2024 (5pm Pacific Time) through January 27, 2025 (5:00 pm Pacific Time) (the “Feedback Period”).

Winners Announced: On or around February 19, 2025 (11:00 am Pacific Time) 

3. ELIGIBILITY

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”) (*NOTE: The age of majority is the threshold of adulthood as recognized or declared by law. Most countries set the age of majority at 18 including the US, UK, Germany https://en.wikipedia.org/wiki/Age_of_majority).
• Teams of Eligible Individuals (“Teams”)

(the above are collectively, “Entrants”)

An Eligible Individual may join more than one Team and an Eligible Individual who is part of a Team may also enter the Hackathon on an individual basis.  

If a Team 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 you represent and warrant that you are the Representative authorized to act on behalf of your Team.

B. The Hackathon IS NOT open to:

• Individuals who are residents of, or Organizations domiciled in, Brazil, Quebec, or any 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, Russia, Crimea, Cuba, Sudan, Iran, North Korea, Syria and any other country designated by the United States Treasury's Office of Foreign Assets Control)
• 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 (“Organizations”)
• Organizations involved with the design, production, paid promotion, execution, or distribution of the Hackathon
• 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 Administrator, a real or apparent conflict of interest
• Any Individuals or Organizations as Sponsor determines for any reason and in its sole discretion, this includes, but is not limited to, Individuals and Organizations in countries in which the Sponsor services and developer accounts are not currently available.

*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, an Organization involved with the design, production, paid promotion, execution or distribution of the Hackathon 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.

Additional Prize specific eligibility requirements are stated below in Section 7.

4. SUBMISSION REQUIREMENTS

Entrants may enter by visiting unlocked.devpost.com (“Hackathon Website”). Entrants 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 free developer account at https://www.docusign.com/developers/sandbox  to build an API or extension app 
• Choose at least one category to build (or update) an application or integration using any Docusign API or other Docusign technology. See category explanations in Section B below.
• Provide a URL to the publicly visible code repository. 
• Complete a text description that explains the features and functionality of your Project. 
• Create a video that includes footage that clearly explains your application’s features and functionality through a comprehensive demonstration.
• A 5-minute demo video (hosted on YouTube, Facebook Video, Vimeo, or Youku). Your video should include a demo of your working application via a step-by-step visual demo. 
• A way to access your working application for judging and testing by providing a URL to the publicly visible code repository, including an applicable open source license. https://opensource.org/licenses  
• Please include a link to a GitHub repository containing your project. You must clearly disclose which code you wrote yourself within the timeframe of the hackathon and let the judges know about any libraries or APIs you used.
• 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.
• All projects must be submitted here through Devpost to be eligible for judging.

Submissions open at 9:00 AM PT on Thursday, November 20, 2024. Submissions close at 5:00 PM PT on January 27, 2024. Requests for late submissions will not be accepted.

 A. Language Requirements 

All Submission materials must be in English or, if not in English, the Entrant must provide an English translation of the demonstration video, text description, and testing instructions as well as all other materials submitted. 

B. Project Requirements - Hackathon Categories

(i) What to Create: Entrants must choose at least one category to build an open-source application or integration using any Docusign API or other Docusign technology:

• AI-ify your world
• In this category, you’ll use the power of AI to glean insights into the data that is trapped within your Docusign agreements. You can use any AI technology, such as Microsoft Copilot, Salesforce Einstein, Amazon AI services, your own LLM models, or any other AI technology that showcases the power of AI to unlock agreement data. 
• Hack-for-good
• In this category, we challenge you to use the power of the Docusign for Developers platform to help others. Create an innovative end-to-end solution that helps fill the mission of a non-profit organization anywhere in the world that you are passionate about. Whether it is to save the rainforests, find homes for pets, address world hunger, or any other mission you care about, use your hacking skills to show how you can help a non-profit organization, especially showing how to connect end-to-end data from disconnected systems. 
• Making the impossible…possible
• In this category, the sky’s the limit! Think outside-the-box and try to code something that uses Docusign technologies to solve what seems impossible (or perhaps just impractical). Innovation is the key to this category. 

(each a “Project”).

(ii) Functionality: The Project 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: A Project must run on the platform for which it is intended and which is specified in the Project Requirements. 

(iv) New: Projects must be newly created by the Entrant after the start of the Hackathon Submission Period. Updates should be described in Project Description.

(v) Testing: Access must be provided to an Entrant’s working Project for judging and testing by providing a public link to a website, functioning demo, or a test build. The Entrant must make the Project available free of charge and without any restriction, for testing, evaluation and use by the Sponsor, Administrator and Judges until the Judging Period ends. Judges are not required to test the Project and may choose to judge based solely on the text description, images, and video provided in the Submission.

If the Project 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 and/or Administrator reserve the right, at their sole discretion, to require the Entrant to provide physical access to the Project hardware upon request. 

(vi) Public Distribution: The Entrant must make the Project available to the public with a public code repository. 

(vii) Multiple Submissions: A Entrant may submit more than one Submission, however, each Submission must be unique and substantially different from each of the Entrant’s other Submissions, as determined by the Sponsor and/or the Administrator. See Section 7 for details on multiple prize eligibility.

(viii) SDKs, APIs, & Data: Projects may integrate SDKs, APIs and data, provided the Entrant 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 Entrant may contract with a third party for technical assistance to create the Submission provided the Submission components are solely the Entrant’s work product and the result of the Entrant’s ideas and creativity, and the Entrant owns all rights to them. A Entrant may submit a Submission that includes the use of open source software or hardware, provided the Entrant 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 Project must not have been developed, or derived from an application developed with financial or preferential support from the Sponsor/Administrator. Such Projects 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/Administrator any time prior to the end of Hackathon Submission Period. The Sponsor, 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, and Video Requirements 

(i) Text Description: The text description should explain the features and functionality of your Project.

(ii) Images: The image(s) should be photographs or screenshots of your working Project. 

(iii) Video: The required video portion of the Submission: 

a. should be less than five (5) minutes;

b. must include footage that clearly explains the Project’s features and functionality through a comprehensive demo of the software; 

c. must be uploaded to YouTube, Vimeo, Facebook Video, 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 Entrant 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 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. The administrator may add the Competition hashtag to the demonstration video on behalf of the submitter.

E. Most Valuable Feedback Submissions

To be considered for the Most Valuable Feedback prizes, participants must be registered for the Hackathon on Devpost, have started a Project, and complete an online form (each a “Feedback Submission”). Feedback must be submitted during the Feedback Period. Participants who have begun a Project must complete the survey with actionable comments that Docusign can use to improve the APIs or extension apps or related documentation (for example, bug reports, user interface).

5. SUBMISSION RIGHTS

A. Entrant Rights: Subject to the licenses described below, any applicable intellectual property rights to a Submission will remain with the Entrant.

B. Sponsor Rights:  By entering the Hackathon, you grant to the Sponsor, Administrator, 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, 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 Sponsor/Administrator, Devpost, and Judges for screening and evaluation.

D. Entrants represent and warrant that the Sponsor, Administrator, and Hackathon partners are free to use Entrants’ 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 Entrants.

6. JUDGING

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”):

• Technological Implementation (25%) - Does the project demonstrate quality software development? Does the project thoroughly leverage the required tool? How is the quality of the code?
• Design (25%) - Is the user experience and design of the project well thought out? Is there a balanced blend of frontend and backend in the software?
• Potential Impact (25%) - How big of an impact could the project have on the target community? How big of an impact could it have beyond the target community?
• Quality of the Idea (25%) - How creative and unique is the project? Does the concept exist already? If so, how much does the project improve on it?

The Entrant(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 Category Prize.

Feedback Submission Criteria

Eligible Feedback Submissions will be evaluated based on the completeness, viability, and potential impact of the feedback provided via a survey executed by Administrator.

• Documentation (Getting Started, Completeness, Clarity)
• Developer Tools and Resources (Sandbox, SDKs, Sample Apps, Reference Implementations)
• API Functionality & Usability (features, API design)
• Extension Types & Usability
• Community (Experience, Support & Engagement)
• User Experience (Dev Center, Dev Console)

C. 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.

7. PRIZES

IMPORTANT NOTES ON PRIZE ELIGIBILITY:

• The same eligible Project may win one Category Prize.
• The same eligible Entrant may submit to multiple categories and win more than one Category Prize.

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 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 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 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 Sponsor 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 or Organization, is disqualified for any other reason.  

In the event of a disqualification, the Sponsor and/or Administrator 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 Entrants or Submissions for a specific Prize. 

B. Prize Delivery: 

Prizes will be payable to the Entrant, if an individual, to the Entrant’s Representative, if a Team, or to the Organization, if the Entrant is an Organization. It will be the responsibility of the winning Entrant’s Representative to allocate the prize among their Team or Organization’s participating members, as the Representative deems appropriate. Prizes are payable via any means of the Sponsor or Administrator's choosing, whether electronic or not, and are payable only after receipt and verification of the Winner Documents and any other required forms. A winning Entrant may be required to provide a mailing address, bank information, and/or create an account with an electronic payment provider of the Sponsor or Administrator’s choosing in order to receive payment. 

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 Entrant, or forfeiture of a Prize.

C. Prize Delivery Timeframe: 

Within 60 days of Administrator’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, 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 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 Entrant, and the Sponsor 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 Sponsor, 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 Sponsor, 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 Entrant’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 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 Entrant’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 Entrants. Proof of sending or submitting will not be deemed to be proof of receipt by the Sponsor or Administrator.

If for any reason any Entrant’s Submission is determined to have not been received or been erroneously deleted, lost, or otherwise destroyed or corrupted, the Entrant’s sole remedy is to request the opportunity to resubmit its Submission. Such request must be made promptly after the Entrant knows or should have known there was a problem, and will be determined at the sole discretion of the Sponsor.

11. PUBLICITY

By participating in the Hackathon you consent to the use of personal information about you, if you are a winner, by the Sponsor, 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 years following the conclusion of the Hackathon. This consent applies, as applicable, to all members a Entrant’s Team, or Organization that participated in the winning Submission.

12. GENERAL CONDITIONS

A. Sponsor 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.  Sponsor and Administrator reserve the right in their sole discretion to disqualify any individual or Entrant 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 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 Entrant 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 Entrant, the Sponsor and the Administrator. The Sponsor 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 Entrant or prospective Entrant believes that any Official Rule is or may be unclear or ambiguous, they must submit a written request for clarification.   

G. The Sponsor 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 Entrant, 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 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 Sponsor or Administrator intellectual property shall be solely to the extent provided for in these Official Rules.

13. LIMITATIONS OF LIABILITY

By entering, all Entrants (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 Entrant’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. 

14. DISPUTES

A. Except where prohibited by law, as a condition of participating in this Hackathon, Entrant 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 Entrant 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 Entrant 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 Entrant 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 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 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 Entrant’s full and unconditional agreement to these Official Rules. By entering, a Entrant 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 Administrator. 

The Administrator collects personal information from you when you enter the Hackathon. The information collected is subject to the privacy policy located here: https://info.devpost.com/privacy. 

16. CONTACT

If you have any questions or comments, or wish to send us any notice regarding this Hackathon, please email us at developers@docusign.com.