Codegeist 2022 (the “Hackathon”) Official Rules

NO PURCHASE OR PAYMENT NECESSARY TO ENTER OR WIN. A PURCHASE OR PAYMENT 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.

 

1. Dates and Timing

Submission Period: September 6, 2022 (10:00 am Eastern Time) – October 31, 2022 (5:00 pm Eastern Time) (“Submission Period”).

Judging Period: November 8, 2022 (10:00 am Eastern Time) – November 15, 2022 (5:00 pm Eastern Time) (“Judging Period”).

Winners Announced: On or around November 21, 2022 (2:00 pm Eastern Time).

 

2. Sponsor and Administrator

Sponsor: Atlassian Pty Ltd - Level 6, 341 George Street, Sydney, NSW, 2000, Australia 

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

 

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”);
  • Teams of Eligible Individuals (“Teams”); and
  • 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.

(the above are collectively, “Entrants”)

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. By entering a Submission 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 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, Russia, Crimea, Belarus, Cuba, Iran, North Korea, Syria, Sudan, Myanmar and any other country designated by the United States Treasury's Office of Foreign Assets Control) 
  • Individuals or Organizations on the U.S. Commerce Department’s Denied Persons, Entity, or Unverified Lists or the U.S. Treasury Department’s list of Specially Designated Nationals and Consolidated Sanctions list
  • Organizations involved with the design, production, paid promotion, execution, or distribution of the Hackathon, including the Sponsor and Administrator (“Promotion Entities”).
  • Employees, representatives and agents** of such Promotion Entities, 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 

*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. How To Enter

Entrants may enter by visiting codegeist.devpost.com (“Hackathon Website”) and following the below steps:

  • Register for the Hackathon on the Hackathon Website by clicking the “Join Hackathon” button. To complete registration, sign up to create a free Devpost account, or log in with an existing Devpost account. This will enable you to receive important updates and to create your Submission.
  • Entrants will obtain access to the required Atlassian developer tools and complete a Project described below in Project Requirements. Use of the developer tools will be subject to the Atlassian developer terms available at https://developer.atlassian.com/platform/marketplace/atlassian-developer-terms/. Entry in the Hackathon constitutes consent for the Sponsor and Devpost to collect and maintain an entrant’s personal information for the purpose of operating and publicizing the Hackathon.
  • Sign up for a free Atlassian Cloud Developer License (https://developer.atlassian.com/cloud/) to access the Forge platform (https://developer.atlassian.com/platform/forge/getting-started/).
  • Create a video that includes footage that explains your project’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 Submission Period and follow the requirements below.
  • Optionally, complete one or more of the below Bonus Submissions to be eligible for the associated Bonus Participation Prizes. 
    • Feedback Submission: To be considered for the Most Valuable Feedback bonus prizes, participants must be an Eligible Individual registered for the hackathon on Devpost and submit a Jira ticket that is tagged codegeist2022 with product feedback to https://ecosystem.atlassian.net/secure/RapidBoard.jspa?rapidView=749&projectKey=FRGE. Feedback must be submitted prior to the Submission Period deadline and must include actionable feedback that Atlassian can use to improve the product (for example, bug reports, user interface improvements, suggested integrations, and more). Feedback Submissions will NOT be eligible for any additional prizes.
    • Storytelling Submission: To be considered for the Most Valuable Storytelling bonus prizes, participants must have submitted an eligible Forge-built application into the Codegeist 2022 hackathon and a Storytelling Submission. To complete a Storytelling Submission, please complete the form here: https://codegeist.devpost.com/details/storytelling. Content must be submitted through the form before  the Submission Period deadline. Storytelling Submissions will NOT be eligible for any additional prizes.
  • Optionally, submit the Project to the Atlassian Marketplace using the marketing tag Codegeist2022. To be eligible for the Best on Marketplace Prize, the Project must be submitted on Devpost and to the Marketplace prior to the Submission Period deadline (each a “Marketplace Submission”). Submitting an app to the Atlassian Marketplace is subject to the  Atlassian's brand guidelines and Marketplace Partner Agreement. Instructions for how to submit the Project to the Atlassian Marketplace is here:  https://marketplace.atlassian.com/manage/apps/create
Project Requirements

(i) What to Create: Entrants must create a working software application using Atlassian’s Forge platform in one of the following categories (each a “Project”). 

Categories:

  • Apps for DevOps Teams: Addresses an internal or publicly shared need within DevOps teams for better collaboration, automation, and intelligent workflows.
  • Apps for IT Teams: Addresses an internal or publicly shared need within IT service management teams to deliver faster and collaborate effortlessly.
  • Apps for Business teams: Addresses an internal or publicly shared need within the workplace to create, collaborate, and organize work in one place.

The Sponsor and Administrator reserve the right to reassign an Entry from one category to another if applicable.

(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 submitted Project must run on the platform for which it is intended and which is specified in the Submission Requirements. 

(iv) New & Existing: Projects must be either newly created by the Entrant, not yet published prior to The Hackathon Submission Period, or, if the Project existed prior to the Hackathon Submission Period, must have been updated or rebuilt in the Forge platform after the start of the Hackathon Submission Period.

(v) Third Party Integrations: If a Project integrates any third-party SDK, APIs and/or data, Entrant must be authorized to use them.

(vi) Testing: 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. 

Entrants must make their Project available using the following methods:

  • Provide a URL to your Project code repository for judging and testing within your Submission. Access must be given by making your Project code repository public or by giving access to:
    • testing@devpost.com and codegeist@atlassian.com (GitHub)
    • testing@devpost.com and codegeist-bot@atlassian.com (Bitbucket)

Your repository is NOT required to contain your full codebase - you may redact all or part of your code. Your repository should contain what you wish the judges to consider when evaluating your work.

  • Provide a means of testing your app (for example an installation link or access to a test instance).

 

Submission Requirements.

Submissions to the Hackathon must meet the following requirements:

  • Include a Project built with the required developer tools and meets the above Project Requirements.
  • Include a text description that should explain the features and functionality of your Project and how it fits within the selected Category.
  • Select the Category for your Project to be submitted into. 
  • Include a demonstration video of your Project. The video portion of the Submission:
    • should be less than three (3) minutes
    • should include footage that shows the Project functioning on the device for which it was built
    • must be uploaded to and made publicly visible on YouTube, Vimeo, Facebook Video, or Youku, and a link to the video must be provided on the Submission form on the Hackathon Website; and
    • must not include third party trademarks, or copyrighted music or other material unless the Entrant has permission to use such material.
  • Be the original work of the Entrant, be solely owned by the Entrant, and not violate the IP rights of any other person or entity.
  • Provide a URL to your Project code repository for judging and testing within your Submission. Access must be given by making your Project code repository public or by giving access to:
    • testing@devpost.com and codegeist@atlassian.com (GitHub)
    • testing@devpost.com and codegeist-bot@atlassian.com (Bitbucket)

Your repository is NOT required to contain your full codebase - you may redact all or part of your code. Your repository should contain what you wish the judges to consider when evaluating your work.

  • Provide a URL to test your app. This might be access to a test instance or an installation link found through the follow steps: https://developer.atlassian.com/platform/forge/distribute-your-apps/#start-sharing-your-app 
  • Select which Geographical Regions represent yourself and your team members. This selection will help determine which Regional Bonus Prize your Project may be eligible for. Please note that Submissions will be associated by the region selected on the Submission form, regardless if Team members reside in various regions. 
  • Optionally, identify if the Project was also submitted to the Atlassian Marketplace by providing the Marketplace Link for the Submission.
  • Multiple Submissions: An 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 Devpost in their sole discretion.
  • Feedback Submissions: To be considered for the Most Valuable Feedback bonus prizes, participants must be an Eligible Individual registered for the hackathon on Devpost and submit a Jira ticket that is tagged codegeist2022 with product feedback to https://ecosystem.atlassian.net/secure/RapidBoard.jspa?rapidView=749&projectKey=FRGE. Feedback must be submitted prior to the Submission Period deadline and must include actionable feedback that Atlassian can use to improve the product (for example, bug reports, user interface improvements, suggested integrations, and more). Feedback Submissions will NOT be eligible for any additional prizes.
  • Storytelling Submissions: To be considered for the Most Valuable Storytelling bonus prizes, participants must have submitted a Forge-built application into the Codegeist 2022 hackathon and a Storytelling Submission. To complete a Storytelling Submission, please complete the form here: https://codegeist.devpost.com/details/storytelling. Content must be submitted through the form before the Submission Period deadline. Storytelling Submissions will NOT be eligible for any additional prizes.

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. 

Team Representation

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 Hackathon Website 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.

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

Financial or Preferential Support: A Project must not have been developed, or derived from a Project developed, with financial or preferential support from the Sponsor or 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 or Administrator any time prior to the end of Hackathon Submission Period. The Sponsor, at their sole discretion, may disqualify a Project, if awarding a prize to the Project would create a real or apparent conflict of interest.

Submissions that meet all of the Project Requirements above will be considered “Eligible Submissions.”

5. Submission Modifications.

A. 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 Hackathon for evaluation. Once the Submission Period has ended, you may not make any changes or alterations to your Submission, but you may continue to update the project in your Devpost portfolio.

B. Modifications After the Submission Period. The Sponsor and Devpost may permit you to modify part of your Submission after the Submission Period for the purpose of adding, removing or replacing 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 and Devpost permits. 

 

6. Judges & Criteria.

Eligible Project and Bonus Submissions will be evaluated by a panel of judges selected by the Sponsor (the “Judges”). Judges may be employees of the Sponsor or third parties, 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. 

Project Submissions

Stage One) The first stage will determine via pass/fail whether the ideas meet a baseline level of viability, in that the project reasonably fits the theme and reasonably applies the required APIs/SDKs featured in the Hackathon.

Stage Two) All Submissions that pass Stage One will be evaluated in Stage Two based on the following equally weighted criteria (the “Judging Criteria”), and according to the sole and absolute discretion of the Judges:

  • Quality of the Idea (Includes creativity and originality of the idea.)
  • Implementation of the Idea (Includes how well the idea was executed by the developer.
  • Potential Impact (Includes the extent to which the solution can help the most Atlassian users.)

 

Bonus Submissions

  • Most Valuable Storytelling: A panel of Judges selected from an internal Marketing team at Atlassian will review all Storytelling Submissions and apply the following Judging Criteria: quality, relevance to the Atlassian community, and completeness of the content.
  • Most Valuable Feedback: The Judges will review all Feedback Submissions and apply the following Judging Criteria:  completeness, viability, and potential impact of the feedback.
  • Regional Prizes: All Eligible Project Submissions will be evaluated based on the region represented by team members and the above Judging Criteria.
  • Best on Marketplace: The Judges will review all eligible Marketplace Submissions and apply the following Judging Criteria:  completeness of the listing page, content provided, and description of value proposition.

The scores from the Judges will determine the potential winners of the applicable Prizes. 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 Prize.

Tie Breaking. For each Prize listed 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. Intellectual Property Rights.

All Submissions remain the intellectual property of the individuals or organizations that developed them. By submitting an Entry, Entrants agree that the Sponsor will have a fully paid, non-exclusive license to use such Entry for judging the Entry. Entrants agree that the Sponsor and Devpost shall have the right to promote the Submission and use the name, likeness, voice and image of all individuals contributing to a Submission, in any materials promoting or publicizing the Hackathon and its results, during the Hackathon Period and for three years thereafter.  Some Submission components may be displayed to the public. Other Submission materials may be viewed by the Sponsor, Devpost, and Judges for screening and evaluation. By submitting an Entry or accepting any Prize, Entrants represent and warrant that (a) submitted content is not copyrighted, protected by trade secret or otherwise subject to third party intellectual property rights or other proprietary rights, including privacy and publicity rights, unless Entrant is the owner of such rights or has permission from their rightful owner to post the content; and (b) the content submitted does not contain any viruses, Trojan horses, worms, spyware or other disabling devices or harmful or malicious code.

 

8. Prizes.

Winner

Prize

Qty

Prize Eligibility 

Grand Prizes

First Place

  • $20,400 USD
  • Meeting with Atlassian R&D teams (virtual)
  • Atlassian event package* or cash equivalent of $4,600**
  • Atlassian blog post featuring winner

* Atlassian event package includes two (2) tickets for a future Atlassian event and a cash stipend to help cover travel, lodging and other expenses.

**Winners must request to receive the cash equivalent of the prize in USD within 10 days of the Winner Announcement.

3 (1 per category)

All Eligible Submissions

Second Place

  • $13,400 USD
  • Atlassian blog post featuring winner
  • Set of Oculus VR headsets (up to 4, 1 per team member) or cash equivalent of $1,600*

*Winners must request to receive the cash equivalent of the prize in USD within 10 days of the Winner Announcement.

3 (1 per category)

All Eligible Submissions

Third Place

  • $12,500 USD
  • Atlassian blog post featuring winner

3 (1 per category)

All Eligible Submissions

Fourth Place

  • $7,500 USD

3 (1 per category)

All Eligible Submissions

Honorable Mentions

  • $5,000 USD

15 (5 per category)

All Eligible Submissions

Bonus Project Prizes

Best on Marketplace

  • $1,000 USD

5

All Eligible Marketplace Submissions***

Regional Prizes

  • $5,000 USD

4 (1 per Geographical Region)

All Eligible Submissions

Bonus Participation Prizes

Most Valuable Feedback

  • $1,000 USD

10

All Eligible Feedback Submissions

Most Valuable Storytelling

  • $1,000 USD
  • Includes the opportunity for Atlassian to post the content to their blog within 12 months of the hackathon winner announcement

10

All Eligible Storytelling Submissions

Participation Prizes

Participation Prize

  • Atlassian Developer Swag Pack (approximate retail value $30 USD)

Awarded to those who enter an Eligible Submission (max 4 per Submission)

400

Entrants of Eligible Submissions

***Compass applications are not currently supported on the Marketplace; Submissions with Compass applications are not eligible for the category.

 

IMPORTANT NOTES ON MULTIPLE PRIZE ELIGIBILITY:

  • The same Submission can win up to one Grand Prize and one Bonus Project Prize.
  • The same Entrant can submit multiple unique Submissions.
  • The same Entrant can only win up to one Participation Prize and one Bonus Participation Prize, no matter how many unique Submissions.
  • Participation Prizes are available to the first 400 Entrants who submit an Eligible Submission (limit 4 per Submission)

A. Substitutions & Changes: Prizes are non-transferable by the winner. Sponsor in its sole discretion has the right to make a Prize substitution of equivalent or greater value. 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. 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. No Submission or Entrant shall be deemed a winning Submission or winner until their post-competition prize affidavits have been completed and verified, even if prospective winners have been announced verbally or on the competition website. The final decision to designate a winner shall be made by the Sponsor and/or Administrator.

C. 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. A monetary Prize will be mailed to the winning Entrant’s address (if an individual) or the Representative’s address (if a Team or Organization), or sent electronically to the Entrant, Entrant’s Representative, or Organization’s bank account, only after receipt of the completed winner affidavit and other required forms (collectively the “Required Forms”), if applicable. 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. Prizes will be delivered within 60 days of the Sponsor or Devpost’s receipt of the completed 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 or currency exchange 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 may be required to provide a completed form W-9 and residents of other countries may be 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 reserves 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.

 

9. Entry Conditions and Release.

A. By entering the Hackathon, you (and, if you are entering on behalf of a Team or Organization each participating member) 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 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 the aforementioned 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 a 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.

 

10. Publicity.

By participating in the Hackathon, Entrant consents to the promotion and display of the Entrant’s Submission, and to the use of personal information about themselves for promotional purposes, 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 but is not limited to advertising and promotional purposes. 

 

11. 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 if 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 the 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 an 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, or advertising, 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 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, an Entrant or prospective Entrant believes that any term in the Official Rules is or may be 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 an 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’s intellectual property shall be solely to the extent provided for in these Official Rules.

 

12. Limitations of Liability.

By entering, all Entrants (including, in the case of a Team or Organization, all participating members) agree to 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.

 

13. Disputes.

A. Except where prohibited by law, as a condition of participating in this Hackathon, Entrant agrees that:

  1. 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;

  2. the Federal Arbitration Act shall govern the interpretation, enforcement and all proceedings at such arbitration; and

  3. 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 Entrant 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 the 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 LIMITATIONS OF LIABILITY MAY NOT APPLY TO YOU.

 

14. Additional Terms.

Please review the Devpost Terms of Service at https://info.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, including that the term "Poster" in the Terms of Service shall mean the same as "Sponsor" in these Official rules." If there is a conflict between the Terms of Service and these Official Rules, these Official Rules shall control with respect to this Hackathon only.

 

15. Entrant’s Personal Information.

Information collected from Entrants is subject to the Devpost’s Privacy Policy, which is available at https://info.devpost.com/privacy.

For questions, send an email to support@devpost.com.