https://splitmetrics.com/Only apps who's 1st version is released to the App Store or Google Play Store between August 1st and September 30th will be eligible.

RevenueCat Shipaton (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

Registration Period: Wednesday, July 2, 2025 (8:00 am Pacific Time) – Tuesday, September 30, 2025 (11:45 pm Pacific Time) (“Registration Period”).

Submission Period: Thursday, July 31, 2025 (8:00 am Pacific Time) – Tuesday, September 30, 2025 (11:45 pm Pacific Time) (“Submission Period”).

#BuildInPublic Engagement Period: on or around Thursday, July 31, 2025 (8:30 am Pacific Time) – Tuesday, September 30, 2025 (11:45 pm Pacific Time) (“#BuildInPublic Engagement Period”)

Judging Period: Wednesday, October 1, 2025 (12:00 am Pacific Time) – Monday, October 13, 2025 (12:00 pm Pacific Time) (“Judging Period”).

Winners Announced: On or around Tuesday, October 14, 2025 (4:00 pm Pacific Time).

2. Sponsor and Administrator

Sponsor and Administrator : RevenueCat, 1032 E Brandon Blvd, #3003ii, Brandon, FL, 33511 

3. Eligibility

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.
• Employees of RevenueCat or Sponsor company employees that meet the above requirements (Employees are eligible to win the “Staff and Sponsor” Prizes only).

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

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, Cuba, Iran, North Korea, Syria and any other country designated by the United States Treasury's Office of Foreign Assets Control) 
• Organizations involved with the design, production, paid promotion, execution, or distribution of the Hackathon, including the Sponsor and 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. 

***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 revenuecat-shipaton-2025.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 developer tools/platform and complete a Project described below in Project Requirements. Use of the developer tools will be subject to the license agreement related thereto. 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.
• Required tools can be found at https://www.revenuecat.com/docs/welcome/overview
• Software applications must be built for iOS, macOS and/or Android and must be fully published by the submission deadline. Note: The App Review process can take multiple days or more. We recommend submitting to the store early to get through the review process and make updates as you add more to your app.
• 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.
• #BuildInPublic Prizes: See Section 6 below for specific requirements to be considered for the #BuildInPublic prizes.
• Best Vibes Award Prizes: See Section 6 below for specific requirements to be considered for the Best Vibes Award prizes.

Project Requirements

• What to Create: Entrants must create a working software application that uses the RevenueCat SDK to power in-app purchases (each a “Project”). Apps must be built for iOS, iPadOS, macOS, or Android. 
  • Note: All apps must be accessible from the United States.
• 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.
• Platforms: A submitted Project must run on either iOS, macOS or Android. 
• Newly Submitted Apps Only: Apps must be either newly created by the Entrant or, if the Entrant’s Project existed prior to the Hackathon Submission Period, it can not have already been published in the App Store before the Submission Period. Pre-existing apps already submitted to the app store before the Hackathon Submission period are not eligible and may not be updated. 
• Third Party Integrations: If a Project integrates any third-party SDK, APIs and/or data, Entrant must be authorized to use them in accordance with any terms and conditions or licensing requirements of the tool.

Submission Requirements 

Submissions to the Hackathon must meet the following requirements:

• Include a Project built with the RevenueCat SDK and meets the above Project Requirements.
• Include a text description that should explain the features and functionality of your Project.
• Include a demonstration video of your Project. The video portion of the Submission:
  • Judges are not required to watch beyond three 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, Youku, Twitter, LinkedIn, Mastodon, or Threads, 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.
• Include a URL to a fully published app in Apple’s App Store or Google Play Store
• Include a 1024x1024 app icon
• Include at least one screenshot of the app with a resolution of 1179px width and 2556px height WITHOUT device frames.
• App must either offer a free trial or Entrant must include a promo code for judges to unlock the in-app purchase and test all premium features
• For Projects that want to be eligible for the Build & Grow Award:
  • Include a description outlining what the developer has done since launch to grow their app and any relevant numbers (downloads/revenue/etc) that show growth since launch
• For Projects that want to be eligible for the #BuildInPublic Award:
  • Include links to any relevant social accounts and/or links to specific content you want to highlight where progress was shared in public
  • Include a short text description of how building in public helped benefit the app (motivation/feedback from others/etc)
• For Projects that want to be eligible for the Buzziest Launch Award:
  • Include a description outlining the launch marketing strategy and outcomes
• For Projects that want to be eligible for the HAMM Award: 
  • Include a description of the app’s monetization model with an explanation of why that model was chosen
• For Projects that want to be eligible for the Best Vibes Award:
  • Include a description of how the developer used any tools in our vibe-coding partners list to help them build the app
• For Projects that want to be eligible for the RevenueCat Peace Prize:
  • Include a description of how the app was designed to benefit individuals, the community, or society at large
• For Projects that want to be eligible for the RevenueCat Design Award:
  • Include a description of the app’s unique design elements and what areas judges should look for to see standout design and animations
• For Projects that want to be eligible for the OneSignal Award:
  • Include a description of how the developer used the OneSignal API to help elevate engagement in the app
  • Include your app's OneSignal App ID
• For Projects that want to be eligible for the the Kotlin Multiplatform Reach Award:
  • Include a description of how the developer used Kotlin Multiplatform and/or Compose Multiplatform along with any links to relevant social media posts where you shared these insights publicly
  • Include a URL to a fully published app on both Apple’s App Store AND Google Play Store

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.

Submission ownership

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.

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

To facilitate testing and evaluation, the Entrant must ensure the Project is accessible for download within the United States.

Access can be provided to the Sponsor and Administrator by providing a URL to the published app in the app store. If the app cannot be accessed with a free trial, a promo code must be provided for judges to unlock the in-app purchase and test all premium features of the app.

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.  

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

5. Submission Modifications

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.

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

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 criteria below for each respective prize category. (the “Judging Criteria”)

Stage Three) The Judges will rate each submission based on the stated criteria to determine the potential winners of the applicable prizes. The Entrant(s) that are eligible for a Prize, and whose Submissions are chosen based on the applicable Judging Criteria, will become potential winners of that Prize.

Build & Grow Award Criteria:

Recognising teams that turn speed into success, the Build & Grow Award honours apps that shipped quickly and can prove people love what they built. Share the story of your earliest release and the measurable wins that followed: Users, subscribers, revenue, or any North-star metric that shows real-world traction.

Entries will be judged on the following criteria, and according to the sole and absolute discretion of the judges:

• Early and Effective Release
  Explain when you first put a live, usable version in front of real users, why you shipped at that moment, and how the initial build allowed you to test or achieve early traction. 
• Growth-by-numbers
  Share the iterations, marketing efforts, and experiments you ran after launch and link them to concrete results: Installs, active users, paying customers, MRR/ARR, or other metrics that clearly climbed because of your efforts.

Buzziest Launch Award Criteria:

Highlights teams that make the biggest splash during their launch (e.g., viral social campaigns, creative marketing stunts) and focus on creating hype and visibility in a short timeframe.

Entries will be judged on the following criteria, and according to the sole and absolute discretion of the judges:

• Visibility:
  How effectively did the team utilize various channels to announce and promote their launch? 
• Creativity:
  Did the team employ any innovative, memorable, or attention-grabbing marketing tactics, stunts, or visual elements during their launch that stood out?
• Audience Engagement and Reach
  Can the team provide any metrics, even anecdotal, of their launch's reach or engagement? Was there noticeable chatter, excitement, or positive reactions from other hackathon participants, mentors, or judges about their project's launch?

HAMM (Help Apps Make Money) Award Criteria:

Awarded to the project that designs the most robust and creative monetization strategy, mixing subscriptions, virtual currency, or other revenue streams. Encourages diverse revenue models and financial viability from the very start.

Entries will be judged on the following criteria, and according to the sole and absolute discretion of the judges:

• Clarity of Monetization Strategy:
  Are the proposed revenue streams clearly articulated and integrated into the app's design? Is the monetization strategy realistic and achievable within the context of the target market and the app's functionality? Does the proposed strategy have the potential to scale as the user base grows?
• Creativity of Monetization Strategy:
  Does the team demonstrate an innovative or unique approach to monetization that goes beyond standard models? Does the strategy incorporate a diverse mix of revenue streams rather than relying on a single one? 
• Financial Viability
  Can the team articulate how their chosen monetization methods could generate revenue? How does their monetization strategy differentiate them from potential competitors, or how does it give them an advantage? Does the strategy suggest a sustainable business model that could operate beyond the hackathon and generate long-term revenue?

Best Vibes Award Criteria:

Awarded to the app with the most compelling vibe-coding story. To be eligible you must have used one of our vibe-coding app partners as part of your development and shared the story of how it helped you ship. Eligible vibe-coding app partners are:

• Perplexity
• Manus AI
• CodeRabbit
• ElevenLabs
• Google Gemini
• Tempo
• Bloom
• FlutterFlow 
• Dreamflow
• Rork
• Vibecode
• A0.dev
• Linearity
• 021

Entries will be judged on the following criteria, and according to the sole and absolute discretion of the judges:

• Integration and Application:
  How did the team utilize the AI tool or service to improve the development, or features of their app? 
• Creativity
  Did the team utilize the vibe-coding app partner in a particularly creative, unexpected, or clever way that enhanced their workflow?

RevenueCat Design Award Criteria:

Awarded to the app with the best design. 

Entries will be judged on the following criteria, and according to the sole and absolute discretion of the judges:

• Innovative ideas
  Does the app introduce any innovative technology or designs? This can be technical innovations integrated into the product, or unique user experiences or animations.
• Aesthetics
  Is the app simply delightful to look at and use? Does the design spark joy? We're looking for fun animations, smooth gesture based interactions, or simply beautiful art integrated into the app.

RevenueCat Peace Prize Criteria:

Awarded to the project that provides the greatest social good, championing impactful solutions that benefit communities or society at large. Celebrates technology-driven initiatives that elevate ethical, inclusive, or philanthropic aims. 

Entries will be judged on the following criteria, and according to the sole and absolute discretion of the judges:

• Impact
  How impactful is the solution? Does the project clearly demonstrate how it will benefit individuals, specific communities, or society as a whole? 
• Feasibility
  Is the technology solution realistic and achievable for solving the problem? Does the project have the potential to reach a significant number of people or have a high positive impact on a smaller group of people?

OneSignal Award Criteria:

Awarded to the best project that uses OneSignal API. 

Entries will be judged on the following criteria, and according to the sole and absolute discretion of the judges:

• Integration:
  Did the project successfully implement fundamental OneSignal features? Was the OneSignal integration clean, stable, and well-executed within the project's codebase?
• Impact:
  How does the OneSignal integration improve the overall user experience or add significant value to the application?
• Creativity
  How resourceful was the team in leveraging the features of the OneSignal API to achieve their desired atmosphere and outcomes? Did the team utilize OneSignal in a particularly creative, unexpected, or clever way? Did the team attempt to utilize any less common or more advanced features of the OneSignal API?

Kotlin Multiplatform Reach Award:

Awarded to the team that ships the best, uncompromising app on both iOS and Android with Kotlin and Compose Multiplatform. Bonus points for sharing your journey and key insights with the community. 

Entries will be judged on the following criteria, and according to the sole and absolute discretion of the judges:

• Quality
  Did the team ship an app with uncompromising quality across both iOS and Android using Kotlin and Compose Multiplatform?
• Community
  Did the team share their journey and insights using Kotlin and Compose Multiplatform with the community in an interesting and engaging way?

Staff and Sponsor Award:

Awarded to the best overall app submission from employees of RevenueCat or any Shipaton sponsors.

Entries will be judged on the following criteria, and according to the sole and absolute discretion of the judges:

• App Concept
  Is the overall idea for the app interesting or novel? Does it solve a new or interesting problem or fun to experience?
• Execution
  Is the app feel well designed and reliable? Are there interesting or novel UX patterns or fun animations?
• Monetization
  Does the app have a strong or novel monetization strategy?

How to Enter and Judging Criteria for the #BuildInPublic Prizes

#BuildInPublic Engagement Period: on or around July 31, 2025 (8:00 am Pacific Time) – September 30, 2025 (11:45 pm Pacific Time) (“#BuildInPublic Engagement Period”).

Entrants who publish their app during the submission period AND submit links to the publicly visible posts on their Devpost submission form will be considered for the #BuildInPublic prizes. Posts should be tagged #BuildInPublic and/or #Shipaton.

Entrants will be judged based on the following criteria by a panel of RevenueCat judges: 

• Sharing your story
  How much do you share your app development journey publicly? How creatively do you share your hackathon process on social media and in online communities? Note that audience size does not matter.
• Engagement
  In what ways have people responded to your app on social media and in online communities? What new ideas were brought into the app based on feedback from your social posts? 
• Lessons Learned
  How did sharing publicly improve the app? Were there interesting lessons learned through the act of sharing or from direct feedback from the public that improved the app in some way?

The Sponsor reserves the right to disqualify any organization, individual or team of individuals who is actually, or presenting the appearance of, tampering with the entry process or the operation of the #BuildInPublic Engagement process.

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.

All Entrants that are Employees of RevenueCat or Shipaton Sponsor employees agree that they are acting in the capacity of their employment with RevenueCat/Sponsor or its affiliates or subsidiaries and are subject to the agreements, policies, and procedures put in place with the Employees of RevenueCat, including without limitation agreements, polices, and procedures related to protection of confidentiality, development of intellectual property, privacy and security, and any releases and waivers, whether or not agreed to otherwise as part of registration and/or submission of any Project, Idea, and/or Submission.  If there is any conflict with these Official Rules, then the agreements, polices, and procedures in place with RevenueCat/Sponsor will govern for its Employees.

8. Prizes

IMPORTANT NOTES ON MULTIPLE PRIZE ELIGIBILITY:

• A project can win one (1) Participation Prize and one (1) Overall prize.
• RevenueCat employees or Shipaton Sponsor employees are only eligible to win one (1) “Staff and Sponsor” prize.

1. 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.
2. 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. 
3. 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. The deadline for returning the Required Forms to the Administrator is ten (10) business days after the Required Forms are sent. 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 of 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.
4. 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, Organization each participating members) agree(s) to the following:

1. The relationship between you, the Entrant, and the Sponsor and Administrator, is not a confidential, fiduciary, or other special relationship.
2. 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.
3. 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: 

1. 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; 
2. 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;
3. Unauthorized human intervention in any part of the entry process or the Hackathon; 
4. Technical or human error which may occur in the administration of the Hackathon or the processing of Submissions; or 
5. 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 

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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. 
7. 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.
8. 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 Devpost’s Privacy Policy, which is available at https://info.devpost.com/privacy.

For questions, send an email to [email protected].