Power Up Automation 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: Power Up Automation (the “Hackathon”)
Hackathon Website: uipath2019.devpost.com (the “Hackathon Website”)
1. POSTER & ADMINISTRATOR
Poster (the “Poster”): UiPath, Inc. 3500 S DuPont Highway, City of Dover, Delaware, United States of America
The Poster is the sponsor and entity responsible for the Hackathon.
2. DATES AND TIMING
Hackathon Submission Period: May 6, 2019 (10:00am Eastern Time) –July 22, 2019 (5:00pm Eastern Time) (the “Hackathon Submission Period”)
Judging Period: September 16, 2019 (10:00am Eastern Time) – September 27, 2019 (5:00pm Eastern Time) (the “Judging Period”)
Winners Announced: On or around October 1, 2019 (2:00pm Eastern 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 as of the time of entry (“Eligible Individuals”)
- Teams of Eligible Individuals (“Teams”)
- Organizations (including corporations, not-for-profit corporations and other nonprofit organizations, limited liability companies, partnerships, and other legal entities) that exist and have been organized or incorporated at the time of entry (“Organizations”)
(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.
B. The Hackathon IS NOT open to:
- Individuals who are residents of, or Small Organizations or Large Organizations domiciled in, a country, state, province or territory where the laws of the United States, European Union or United Nations 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, and Commission of the European Union or Security Council of the United Nations)
- Organizations involved with the design, production, paid promotion, execution, or distribution of the Hackathon, including the Poster and Administrator (“Promotion Entities”)
- 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
Additional Prize specific eligibility requirements are stated below in Section 8.
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.
- Sign up for UiPath Studio and request the free Community Edition.
- Create a reusable component in one of the required categories using the UiPath Studio
- Submit your project on UiPath Connect! using these tags [PUA] [Virtual] at the start of your project name - eg: [PUA][Virtual] Project1
- Must make the code open source is under one of the following three licenses:
- MIT - https://opensource.org/licenses/MIT
Apache 2.0 - https://opensource.org/licenses/Apache-2.0
3-Clause BSD - https://opensource.org/licenses/BSD-3-Clause
and provide it free of charge, and without any restriction, for testing, evaluation and use by the Poster, Administrator and judges during and after the Hackathon. Makers will be required to provide a link for accessing the code repository on the Enter a Submission form. Repositories must contain all source code files, dependencies, including the file types specific to the component category. (Specific files listed on the categories tab).
- Create a video that includes footage that clearly explains your component’s features and functionality through a comprehensive demonstration.
- Complete and enter all of the required fields on the “Enter a Submission” page of the Hackathon Website (each a “Submission”) during the Hackathon Submission Period, and follow the requirements below.
- After the initial evaluation and pre-judging, all finalists will be invited to submit their components onto UiPath Go! to be eligible for the final round of judging and awards. The first part of submitting onto Connect is to fulfill all the submission requirements for the component that was created. Afterwards, by uploading it onto Go! Marketplace, we will expand the RPA community by making these components more widespread and accessible for the UiPath Community at large.
A. Language Requirements
All Submission materials must be in English or, if not in English, the Maker must provide an English translation of the demonstration video, text description, and testing instructions as well as all other materials submitted.
B. Application Requirements
(i) What to Create: Makers must create an open source reusable component in one of the required categories using the UiPath Studio that automate repetitive tasks in the workplace. (each a “Component”).
- Enterprise: Build automation reusable components and projects that accelerate business transformation and expand UiPath Suite capabilities.
- Automate for a cause: Help a local NGO to automate a process or build a scalable solution that will drastically improve their operations, or find innovative automation solutions for local and national government agencies.
- RPA for Fun: Automation is here to stay. How can we, humans, benefit from it to improve and make day to day lives easier
- Other: Have a disruptive idea that doesn't quite fit in the categories above? Tell us more!
Snippet component for Citizen Developers: XAML or Workflow Snippets are ready-made workflows which you can invoke/include in your own workflows in UiPath Studio. They should be reusable for as many users, environment and processes as possible. These workflows use the same deployment, versioning and release management like the binary activities.
(iii) Functionality: The Component must be capable of being successfully installed and running consistently on the platform for which it is intended, and must function as depicted in the video and/or expressed in the text description.
(iv) New & Existing: Components must be either newly created by the Maker or, if the Component 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 Component available free of charge and without any restriction through a Github or other publicly available code repository, for testing, evaluation and use by the Poster, Administrator and judges during and after the Hackathon.
(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 Poster and/or the Administrator.
(viii) SDKs, APIs, & Data: Component 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 and you acknowledge that you will hold Poster harmless of any claim from a third party referring to the breach of its intellectual property rights or other rights. You acknowledge that in case there is a reasonable suspicion that your Submission is not compliant with this section, your Submission will be disqualified.
(x) Financial or Preferential Support: A Component 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 Component 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 Component.
(ii) Images: The image(s) should be photographs or screenshots of your working Component.
(iii) Video: The video portion of the Submission:
a. should be less than five (5) minutes;
b. must include footage that clearly explains the Component’s features and functionality through a comprehensive demonstration;
c. must be uploaded to YouTube, Vimeo, or Youku, and a link to the video must be provided on the submission form on the Hackathon Website; and
d. must not include third party trademarks, or copyrighted music or other material unless the Maker has permission to use such material.
D. Submission Modifications
a. Draft Submissions: 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. This also applies to your project that is submitted onto Connect. 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. For your project submitted on Connect, you may not edit any part of the project as that will compromise the judging process.
b. Modifications after the Submission Period. The Poster 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 Poster permits. The administrator may add the Competition hashtag to the demonstration video on behalf of the submitter.
5. SUBMISSION RIGHTS
A. Maker Rights: Subject to the licenses described herein, any applicable intellectual property rights to a Submission will remain with the Maker.
B. Poster Rights: By entering the Hackathon, you grant to the Poster, Administrator, and any other third parties acting on the Poster’s behalf, a royalty-free, non-exclusive, worldwide perpetual license to display publicly and use for promotional purposes and commercial purposes the Submission, in perpetuity. This license includes, but is not limited to, posting or linking to the Submission on Poster’s, Administrator’s, and partners’ websites and applications, including the Hackathon Website, and display and promotion of the Submission in any other media, worldwide.
C. Submission Display: The following Submission components may be displayed to the public: name, description, images, video URL, website, URL, team members, the Submission category and platform, and submitter type. Other Submission materials may be viewed by the Poster, Administrator, and Judges for screening and evaluation.
D. Makers represent and warrant that the Poster, Administrator, and Hackathon partners are free to use Makers’ Submission in the manner described above, as provided or as modified by the Administrator, without obtaining permission or license from any third party and without any compensation to Makers or any other third parties.
A. Judges: Eligible Submissions will be evaluated by a panel of judges selected by the Poster (the “Judges”). Judges may be employees of the Poster or third party individuals. Judging will take place in two rounds. The first round will be judged by a panel made only by Poster’s personnel which will test the functionality of the reusable components. The second round will be judged by a panel made by third parties appointed by Poster and Poster's personnel, who will determine the winners of each of the Prizes.
B. Submission Judging Criteria: Submissions will be evaluated by the Poster during the Submission Review Period in two stages.
Stage One) The first stage will determine via pass/fail whether the submissions meet a baseline level of viability, in that there is a reasonable chance they reasonably fit the theme and requirements of the competition.
Stage Two) All submissions that pass Stage One will be evaluated by the Poster in Stage Two based on the following equally weighted criteria (the “Judging Criteria”):
(i) Structure How clear is the implementation structure, and what is the quality of the frameworks used?;
(ii) Functionality How well executed is the developer’s idea?;
(iii) Potential Impact To what extent will the solution help enterprises automate workflows?
(iv) Presentation How well did the developer present their idea via the video demo?
The Judging Criteria above may not apply to every Prize. See Section 8 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 APPLICATION AND MAY CHOOSE TO JUDGE BASED SOLELY ON THE TEXT DESCRIPTION, IMAGES AND VIDEO PROVIDED IN THE SUBMISSION.
D. Tie Breaker: For each Prize listed in Section 7 below, if two 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
● Intro to UiPath customers
● Featured in social media post
● Featured on UiPath website and newsletter
● Invited a to key UiPath event to showcase the solutions
● Invited to hold a live webinar to entire community
All eligible entries that pass stage one judging
i, ii, iii, iv
**Please review the Devpost Terms of Service at http://Devpost.com/terms for voting rules.
Poster will grant one Prize for each of the above categories.The Poster reserves the right to not award a Prize for one or more categories if there are not sufficient quality submissions.
8. PRIZE SPECIFIC ELIGIBILITY & CATEGORY REQUIREMENTS
A. Academy Prize Eligibility Requirements
In addition to the requirements in Section 3, submissions must use the best practices taught in the UiPath Academy courses to create their components. UiPath will perform code review of potential winners.
B. Eligible submissions must pass stage one judging to be eligible for stage two judging.
9. VERIFICATION OF POTENTIAL WINNERS
A. Verification Requirement: THE AWARD OF A PRIZE TO A POTENTIAL WINNER IS SUBJECT TO VERIFICATION OF THE IDENTITY, QUALIFICATIONS AND ROLE OF THE POTENTIAL WINNER IN THE CREATION OF THE SUBMISSION. The final decision to designate a winner shall be made by the Poster and/or Administrator.
B. Required Forms: Potential winners will be notified using the email address associated with the Devpost account used to enter the Submission (the submitter is the “Representative” in the case of a Team 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 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”) and the personal data necessary in order to provide the Prize.
Deadline for Returning Required Forms: ten (10) business days after the Required Forms are sent.
C. Disqualification: The Poster and/or Administrator may deem a potential winner (or participating team members) ineligible to win if:
(i) the potential winner’s Representative or any participating member does not respond to multiple emails or fails to sign and return the Required Forms by the deadline listed above, or responds and rejects the Prize;
(ii) the Prize or Prize notification is returned as undeliverable; or
(iii) the Submission or the potential winner, or any member of a potential winner’s Team or Organization, is disqualified for any other reason stipulated in the Official Rules.
In the event of a disqualification, the Poster and/or Administrator will award the applicable Prize to the Maker with the next highest score.
10. PRIZE DISTRIBUTION
A. Substitutions & Changes: The Poster has the right to make a Prize substitution of equivalent or greater value. If Poster decides to chnage the Prizes, it will amend these Official Rules and publish the addendum before appointing the winners. The Poster will not award a Prize if there are no eligible Submissions entered in the Hackathon, or if there are no eligible Makers or Submissions for a specific Prize.
B. Prize Delivery: Prizes will be payable to the Maker, if an individual, to the Maker’s Representative, if a Team, or to the Organization, if the Maker is a Small Organization. It will be the responsibility of the winning Maker’s Representative to allocate the Prize among their Team or Organization’s participating members, as the Representative deems appropriate. A monetary Prize will be mailed to the winning Maker’s address (if an individual) or the Representative’s address (if a Team or Organization), or wired to the Maker, Maker Representative, or 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 45 days of the Poster or Administrator’s receipt of the Required Forms
D. Fees & Taxes: Makers are not bound to pay any fees or taxes in order to participate in the Hackathon.
Winners (and in the case of Team or Small Organization, all participating members) are responsible for any fees associated with receiving or using a prize, including but not limited to, wiring fees. Winners (and in the case of Team or Small Organization, all participating members) are responsible for reporting and paying all applicable taxes in their jurisdiction of residence (federal, state/provincial/territorial and local). Winners may be required to provide certain information to facilitate receipt of the award, including completing and submitting any tax or other forms necessary for compliance with applicable withholding and reporting requirements. United States residents are required to provide a completed form W-9 and residents of other countries are required to provide a completed W-8BEN form. Winners are also responsible for complying with foreign exchange and banking regulations in their respective jurisdictions and reporting the receipt of the Prize to relevant government departments/agencies, if necessary. THE POSTER, ADMINISTRATOR, AND/OR PRIZE PROVIDER RESERVE THE RIGHT TO WITHHOLD A PORTION OF THE PRIZE AMOUNT TO COMPLY WITH THE TAX LAWS OF THE UNITED STATES OR OTHER POSTER JURISDICTION OR THOSE OF A WINNER’S JURISDICTION IF SUCH ARE BOUND BY APPLICABLE LAW TO WITHHOLD THE TAXES DUE FOR PRIZES OFFERED DURING CONTESTS.
E. Publication. All winners of the Prizes will be displayed on the Hackathon Website after such are validated.
11. 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 Poster and Administrator is not a confidential, fiduciary, or other special relationship.
(ii) You will be bound by and comply with these Official Rules and the decisions of the Poster, Administrator, and/or the Hackathon Judges which are binding and final in all matters relating to the Hackathon.
(iii) You release, indemnify, defend and hold harmless the Poster, Administrator, Promotion Entities, and their respective parent, subsidiary, and affiliated companies, the Prize suppliers and any other organizations responsible for sponsoring, fulfilling, administering, advertising or promoting the Hackathon, and all of their respective past and present officers, directors, employees, agents and representatives (hereafter the “Released Parties”) from and against any and all claims, expenses, and liabilities (including reasonable attorneys’ fees), including but not limited to negligence and damages of any kind to persons and property, defamation, slander, libel, violation of right of publicity, infringement of trademark, copyright or other intellectual property rights, property damage, or death or personal injury arising out of or relating to a Maker’s entry, creation of Submission or entry of a Submission, participation in the Hackathon, acceptance or use or misuse of the Prize (including any travel or activity related thereto) and/or the broadcast, transmission, performance, exploitation or use of the Submission as authorized or licensed by these Official Rules.
B. Without limiting the foregoing, the Released Parties shall have no liability in connection with:
(i) any incorrect or inaccurate information, whether caused by the Poster or Administrator’s electronic or printing error, or by any of the equipment or programming associated with or utilized in the Hackathon;
(ii) technical failures of any kind, including, but not limited to malfunctions, interruptions, or disconnections in phone lines, internet connectivity or electronic transmission errors, or network hardware or software or failure of the Hackathon Website;
(iii) unauthorized human intervention in any part of the entry process or the Hackathon;
(iv) technical or human error which may occur in the administration of the Hackathon or the processing of Submissions; or
(v) any injury or damage to persons or property which may be caused, directly or indirectly, in whole or in part, from the Maker’s participation in the Hackathon or receipt or use or misuse of any Prize.
The Released Parties are not responsible for incomplete, late, misdirected, damaged, lost, illegible, or incomprehensible Submissions or for address or email address changes of the Makers. Proof of sending or submitting will not be deemed to be proof of receipt by the Poster or Administrator.
If for any reason any Maker’s Submission is determined to have not been received or been erroneously deleted, lost, or otherwise destroyed or corrupted, the Maker’s sole remedy is to request the opportunity to resubmit its Submission. Such request must be made promptly after the Maker knows or should have known there was a problem, and will be determined at the sole discretion of the Poster.
With your explicit consent we can use personal information about you, such as, but not limited to, your name, photograph, voice, opinions, comments and hometown and country of residence for promotion purposes.
13. GENERAL CONDITIONS
A. Poster and Administrator reserve the right, in their sole discretion, to cancel, suspend and/or modify the Hackathon, or any part of it, in the event of a technical failure, fraud, or any other factor or event that was not anticipated or is not within their control. Poster and Administrator reserve the right, in their sole discretion, to amend these Official Rules. The amendments will be notified to all Makers by posting them on the Hackathon website.
B. Poster and Administrator reserve the right in their sole discretion to disqualify any individual or Maker it finds to be actually or presenting the appearance of tampering with the entry process or the operation of the Hackathon or to be acting in violation of these Official Rules or in a manner that is inappropriate, unsportsmanlike, not in the best interests of this Hackathon, or a violation of any applicable law or regulation.
C. Any attempt by any person to undermine the proper conduct of the Hackathon may be a violation of criminal and civil law. Should Poster or Administrator suspect that such an attempt has been made or is threatened, they reserve the right to take appropriate action including but not limited to requiring a Maker to cooperate with an investigation and referral to criminal and civil law enforcement authorities.
D. If there is any discrepancy or inconsistency between the terms and conditions of the Official Rules and disclosures or other statements contained in any Hackathon materials, including but not limited to the Hackathon Submission form, Hackathon Website, advertising (including but not limited to television, print, radio or online ads), the terms and conditions of the Official Rules shall prevail.
E. The terms and conditions of the Official Rules are subject to change at any time, including the rights or obligations of the Maker, the Poster and the Administrator. The Poster and Administrator will post the terms and conditions of the amended Official Rules on the Hackathon Website. To the fullest extent permitted by law, any amendment will become effective at the time specified in the posting of the amended Official Rules or, if no time is specified, the time of posting.
F. If at any time prior to the deadline, a Maker or prospective Maker believes that any Official Rule is or may be unclear or ambiguous, they must submit a written request for clarification.
G. The Poster or Administrator’s failure to enforce any term of these Official Rules shall not constitute a waiver of that provision. Should any provision of these Official Rules be or become illegal or unenforceable in any jurisdiction whose laws or regulations may apply to a Maker, such illegality or unenforceability shall leave the remainder of these Official Rules, including the Rule affected, to the fullest extent permitted by law, unaffected and valid. The illegal or unenforceable provision shall be replaced by a valid and enforceable provision that comes closest and best reflects the Poster’s intention in a legal and enforceable manner with respect to the invalid or unenforceable provision.
H. Excluding Submissions, all intellectual property related to this Hackathon, including but not limited to copyrighted material, trademarks, trade-names, logos, designs, promotional materials, web pages, source codes, drawings, illustrations, slogans and representations are owned or used under license by the Poster and/or Administrator. All rights are reserved. Unauthorized copying or use of any copyrighted material or intellectual property without the express written consent of its owners is strictly prohibited. Any use in a Submission of Poster or Administrator intellectual property shall be solely to the extent provided for in these Official Rules.
14. 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 Poster in connection with this Hackathon, shall be governed by, and construed in accordance with, the substantive laws of the State of New York, USA without regard to New York choice of law rules.
SOME JURISDICTIONS DO NOT ALLOW THE LIMITATIONS OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE MAY NOT APPLY TO YOU.
16. ADDITIONAL TERMS THAT ARE PART OF THE OFFICIAL RULES
Please review the Devpost Terms of Service at http://devpost.com/terms for additional rules that apply to your participation in the Hackathon and more generally your use of the Hackathon Website. Such Terms of Service are incorporated by reference into these Official Rules. If there is a conflict between the Terms of Service and these Official Rules, the latter terms shall control with respect to this Hackathon only.
Participation in the Hackathon constitutes Maker’s full and unconditional agreement to these Official Rules. By entering, a Maker agrees that all decisions related to the Hackathon that are made pursuant to these Official Rules are final and binding, and that all such decisions are at the sole discretion of the Poster and/or Administrator.
17. PERSONAL DATA PROTECTION
If you have any questions or comment, or wish to send us any notice regarding this Hackathon, please email us at Support@Devpost.com.