Baseline Tooling Hackathon Official Rules 

NO PURCHASE NECESSARY TO ENTER OR WIN. VOID WHERE PROHIBITED. CONTEST IS OPEN TO EVERYONE EXCEPT FOR RESIDENTS OF QUEBEC, CRIMEA, CUBA, IRAN, SYRIA, NORTH KOREA, SUDAN, BELARUS, RUSSIA, VIETNAM, AND THE SO-CALLED DONETSK PEOPLE’S REPUBLIC OR LUHANSK PEOPLE’S REPUBLIC.

ENTRY IN THIS CONTEST CONSTITUTES YOUR ACCEPTANCE OF THESE OFFICIAL RULES.

The Baseline Tooling Hackathon (the “Contest”) is a skill contest where participants must develop an application that integrates Baseline data about web features in a new or existing open source developer tool.  The application that you develop will be evaluated by judges, who will choose the winner(s) in accordance with these Official Rules.  The prize(s) will be awarded to participant(s) with the highest score for the judging criteria.  See below for the complete details.

 

1. BINDING AGREEMENT:

In order to enter the Contest, you must agree to these Official Rules (“Rules”). Therefore, please read these Rules prior to entry to ensure you understand and agree. You agree that submission of an entry in the Contest constitutes agreement to these Rules. You may not submit an entry to the Contest and are not eligible to receive the prizes described in these Rules unless you agree to these Rules. These Rules form a binding legal agreement between you and Google with respect to the Contest.

 

2. ELIGIBILITY:

To be eligible to enter the Contest, you must be: (1) above the age of majority in the country, state, province or jurisdiction of residence (or at least twenty years old in Taiwan) at the time of entry; (2) not a resident of  Quebec, Crimea, Cuba, Iran, Syria, North Korea, Sudan, Belarus, Russia, Vietnam or the so-called Donetsk People’s Republic or Luhansk People’s Republic; (3) not a person or entity under U.S. export controls or sanctions; and (4) have access to the Internet as of September 2, 2025. Contest is void in Quebec, Crimea, Cuba, Iran, Syria, North Korea, Sudan, Belarus, Russia, Vietnam, and the so-called Donetsk People’s Public or Luhansk People’s Republic, and where prohibited by law.  Employees, Google Developer Experts (GDEs), interns, contractors, and official office-holders of Google, Devpost, Inc., the Web Developer Experience Community Group (WebDX CG), and their parent companies, subsidiaries, affiliates, and their respective directors, officers, employees, advertising and promotion agencies, representatives, and agents (“Contest Entities”), and members of the Contest Entities’ and their immediate families (parents, siblings, children, spouses, and life partners of each, regardless of where they live) and members of the households (whether related or not) of such employees, officers and directors are ineligible to participate in this Contest. Sponsor reserves the right to verify eligibility and to adjudicate on any dispute at any time.

If you are entering as part of a company or on behalf of your employer, these rules are binding on you, individually, and/or your employer.  If you are acting within the scope of your employment, as an employee, contractor, or agent of another party, you warrant that such party has full knowledge of your actions and has consented thereto, including your potential receipt of a prize.  You further warrant that your actions do not violate your employer’s or company’s policies and procedures.   

 

3. SPONSOR:

The Contest is sponsored by Google Inc. (“Google” or “Sponsor”), a Delaware corporation with principal place of business at 1600 Amphitheater Parkway, Mountain View, CA, 94043, USA.

 

4. ADMINISTRATOR:

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

 

5. CONTEST PERIOD:

The Contest begins at 9:00:00 A.M. Pacific Time (PT) Zone in the United States on September 2, 2025 and ends at 05:00:00 P.M. PT on October 6, 2025 (“Contest Period”). ENTRANTS ARE RESPONSIBLE FOR DETERMINING THE CORRESPONDING TIME ZONE IN THEIR RESPECTIVE JURISDICTIONS.

 

6. HOW TO ENTER:

NO PURCHASE NECESSARY TO ENTER OR WIN. To enter the Contest, visit the Contest website located at baseline.devpost.com (“Contest Site”) during the Contest Period and follow the instructions for developing an application that integrates Baseline data about web features in a new or existing open source developer tool (“Project”).  The Project must meet Submission Requirements as outlined in Section 6 (hereinafter, “Project Requirements”).   

All entries must be received by 5:00 p.m. (PT) on October 6, 2025.  Entries are void if they are in whole or part illegible, incomplete, damaged, altered, counterfeit, obtained through fraud, or late. All entries will be deemed made by the authorized account holder of the email address submitted at the time of entry, and the potential winner may be required to show proof of being the authorized account holder for that email address. The "authorized account holder" is the natural person assigned to an email address by an Internet service provider, online service provider, or other organization responsible for assigning email address for the domain.

 

To access the challenge and submit the solution, follow the steps below: 

  • Obtain access to the submission portal. You must have a Devpost account to register for the Contest as they will administer the Contest. If you do not have a Devpost account already, you can sign up for a Devpost account at no cost from baseline.devpost.com.

  • Entry in the Contest constitutes consent for the Sponsor and Devpost to collect and maintain an entrant’s personal information for the purpose of operating and publicizing the Contest.

  • Create a project in line with the Project Requirements below (hereinafter, “Project”). 

  • Submit your Project to the Contest Site. Make sure to complete and enter all of the required fields on the “Enter a Submission” or similar worded page of the Contest Site (each a “Submission”) during the Contest Period. 

 
PROJECT REQUIREMENTS: 

A. Build a Project that integrates Baseline data about web features with new or existing developer tools (e.g. linters, transpilers, IDEs, analytics, documentation) to make it easier for web developers to adopt modern web features. Sources of Baseline data include the web-features npm package and the Web Platform Dashboard.

B. ESSENTIAL COMPONENTS OF SUBMISSION. The Submission must conform to the following requirements 

  • Project Team: You may submit your Project as an individual, a team, or on behalf of an organization. A Team must consist of only Eligible Individuals, have all team members added as members of the Project on Devpost. If a team or organization is entering the Submission, one individual must be appointed and authorized (the “Representative”) to represent, act, and enter the Submission, on the team’s behalf.

  • Functionality: The Project must be built using Baseline data about web features. The Project must be capable of being successfully installed and run consistently as depicted in the video and/or expressed in the text description that you submit with the Project.

  • New & Existing Projects: Projects must be either newly created by the Entrant or, if the Entrant’s Project existed prior to the Hackathon Submission Period must have been created after August 7th, 2025 for the #WhatsMyBaseline campaign. Note that this requirement applies to the creation time of Projects, not the underlying developer tools.

  • Third-Party Integrations: If a Project integrates any third-party SDK, APIs, data and/or any information belonging to a third party, Entrants must be authorized to use these third-party tools and information in accordance with any terms and conditions or licensing requirements of the tool.

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

  • If the Project includes software that runs on proprietary or third party hardware that is not widely available to the public, including software running on devices or wearable technology other than smartphones, tablets, or desktop computers, the Sponsor and/or Administrator reserve the right, at their sole discretion, to require the Entrant to provide physical access to the Project hardware upon request.

 

What to Submit:

  • Include a Project built with the required developer tools and meets the above Project Requirements.

  • Include a comprehensive text description that should include a summary of the Project’s features, functionality, and technologies used. Written parts of entries must be in English to be eligible. The Project must, at a minimum, support English language use. 

  • Include a thorough and complete answer to all submission questions. 

  • Include a URL to your public code repository to show how your project was built. The code repository must be public to allow access for judging and testing.

  • Include a Permissive Open-Source License for your Project in a LICENSE.txt file granting judges the right to open, test, and evaluate the project. The repository must contain all necessary source code, assets, and instructions required for the project to be functional. The repository must be public and open source by including an open source license file. This license should be detectable and visible at the top of the repository page (in the About section)

  • Include a URL to the hosted Project (if applicable) for judging and testing

  • Include a demonstration video of your Project. The video portion of the Project:

    • Should include footage that shows the Project functioning on the platform(s) for which it was built.

    • It should be around 3 minutes. If it is longer than 3 minutes, judges may only watch the first 3 minutes. 

    • It must conform to the technical requirements set forth on the Contest site, including that the Submission must be uploaded to and made publicly visible on YouTube or Vimeo, and a link to the video must be provided on the Submission form on the Contest Site.

    • It must be in English or include English subtitles.

  • No parts of the submission can be derogatory, offensive, threatening, defamatory, disparaging, libelous or contain any content that is inappropriate, indecent, sexual, profane, indecent, tortuous, slanderous, discriminatory in any way, or that promotes hatred or harm against any group or person, or otherwise does not comply with the theme and spirit of the Contest.

  • No part of that submission contains content, material or any element that is unlawful, or otherwise in violation of or contrary to all applicable federal, state, or local laws and regulations in any country, state or applicable territory where you created the video and in the United States.

  • The Submission must not contain any content, material or element that displays any third party advertising, slogan, logo, trademark or otherwise indicates a sponsorship or endorsement by a third party, commercial entity or that is not within the spirit of the Contest, as determined by Sponsor, in its sole discretion.

  • The Submission must be an original, unpublished work that does not contain, incorporate or otherwise use any content, material or element that is owned by a third party or entity.

  • It cannot contain any content, element, or material that violates a third party’s publicity, privacy or intellectual property rights.

To be considered for the Most Valuable Feedback bonus prizes, Entrants must be registered for the hackathon on Devpost and complete an online form (each a “Feedback Submission”). Feedback must be submitted during the Feedback Period between September 2, 2025 and October 8, 2025 at 5pm PT. To be eligible for a Feedback Prize, the Feedback Submission must be complete with actionable comments that Google can use to improve Baseline or related tools, data sources, or documentation (for example, bug reports, user interface improvements, suggested integrations, and more). One Feedback Submission per Entrant.

 

7. SUBMISSION MODIFICATIONS:

Prior to the end of the Contest Period, you may save draft versions of your submission on Devpost to your portfolio before submitting the Submission materials to the Contest for evaluation. Once the Contest 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. After the Contest Period, fully at their discretion, the Sponsor and Devpost may permit you to modify part of your Submission after the Contest 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.

 

8. JUDGING:

Each Project will be judged by a panel of judges selected by the Sponsor (“Judges”).  On or about the period between October 7, 2025 and October 22, 2025, each Entry will be evaluated by the Judges based on the following criteria:

Stage One: The first stage will determine via pass/fail whether the Entry meets a baseline level of viability, in that the Entry reasonably fits the theme and reasonably applies the required data sources featured in the Contest.

Stage Two: All Entries that pass Stage One will be evaluated in Stage Two based on the following equally-weighted criteria:

  • Innovation: Is the Project integrating Baseline data in new and interesting ways, for example solving a problem that no existing tool solves, or doing so in a totally novel way?

  • Usefulness: Does the Project solve real-world developer needs, for example by integrating Baseline with tools used by a significant number of developers or by creating something new that an average developer would use?

Judges will evaluate and attribute a score to each Project made up of scores based upon the above-listed criteria. The entries that receive the highest overall scores will be selected as the potential winner(s). In the event of a tie, the Project that received the higher score from the Judges in the category of “innovation” will be selected as one of the potential winner(s).  In the event a potential winner is disqualified for any reason, the Project that received the next highest total score will be chosen as the potential winner. 

On or about October 22, 2025, the potential winner(s) will be selected and notified by email, at Sponsor’s discretion. If a potential winner does not respond to the notification attempt within 2 days from the first notification attempt, then such potential winner will be disqualified and an alternate potential winner will be selected from among all eligible entries received based on the judging criteria described herein. If required, potential winners must return all such required documents within 5 days following attempted notification or such potential winner will be deemed to have forfeited the prize and another potential winner will be selected based on the judging criteria described herein. All notification requirements, as well as other requirements within these Rules, will be strictly enforced.

Winners will be publicly announced on or around October 27, 2025

In the event that no entries are received, no prize will be awarded.  Determinations of judges are final and binding.

During the Contest Period, the Sponsor, its agents and/or the Judges (defined below) will be evaluating each Project to ensure that it meets the Requirements.  The Sponsor reserves the right, in its sole discretion, to disqualify any entrant who submits a Project that does not meet the Requirements. 

 

Feedback Submission Criteria 

Eligible Feedback Submissions will be evaluated based on the completeness, viability, potential impact of the feedback and written description.

 

9. PRIZES:

The following Prizes will be awarded:

Prize 

Item

Qty

Eligible

1st Place

  • $5,000 USD 
  • Social promo on Chrome for Developers
  • Feature in web.dev blog post and web.dev newsletter
  • 30-minute meeting with Chrome Team 

1

All eligible submissions

2nd Place

  • $3,000 USD
  • Social promo on Chrome for Developers
  • Feature in web.dev blog post and web.dev newsletter
  • 30-minute meeting with Chrome Team 

1

All eligible submissions

3rd Place

  • $1,000 USD
  • Social promo on Chrome for Developers
  • Feature in web.dev blog post and web.dev newsletter
  • 30-minute meeting with Chrome Team 

1

All eligible submissions

Most Valuable Feedback

  • $100 USD

10

All eligible feedback submissions

  • Important Note on Multiple Prize Eligibility: A Project can win either 1st Place, 2nd Place, OR 3rd Place AND one (1) Most Valuable Feedback Prize.

  • Feedback Prizes are awarded to individuals, not to Projects and will not be visible on the platform.

 
Terms Applicable to All Prizes.  

 

Cash Prize Delivery: Cash Prizes will be payable to the winner, if an individual; to the winning team’s Representative, if a team; or to the organization, if the winning team is an Organization. It will be the responsibility of the winning team’s or organization’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 winner’s address (if an individual) or the Representative’s address (if a team or organization), or sent electronically to the winner,  winning teams 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 individual, team or organization or forfeiture of a Prize. Prizes will be delivered within sixty (60) days of Devpost’s receipt of the completed Required Forms. Odds of winning any prize depends on the number of eligible entries received during the Contest Period and the skill of the entrants.  No transfer, substitution or cash equivalent for prize(s) is allowed, except at Sponsor’s sole discretion. Sponsor reserves the right to substitute a prize, in whole or in part, of equal or greater monetary value if a prize cannot be awarded, in whole or in part, as described for any reason.  Value is subject to market conditions, which can fluctuate and any difference between actual market value and ARV will not be awarded. The prize(s) may be subject to restrictions and/or licenses and may require additional hardware, software, service, or maintenance to use. The winner shall bear all responsibility for use of the prize(s) in compliance with any conditions imposed by such manufacturer(s), and any additional costs associated with its use, service, or maintenance. Contest Entities have not made and Contest Entities are not responsible in any manner for any warranties, representations, or guarantees, express or implied, in fact or law, relating to the prize(s), regarding the use, value or enjoyment of the prize(s), including, without limitation, its quality, mechanical condition, merchantability, or fitness for a particular purpose, with the exception of any standard manufacturer's warranty that may apply to the prize(s) or any components thereto. 

 

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 submitter shall be deemed a winning entry 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.

 

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.

 

10. TAXES & FEES:

PAYMENTS TO POTENTIAL WINNERS ARE SUBJECT TO THE EXPRESS REQUIREMENT THAT THEY SUBMIT TO GOOGLE ALL DOCUMENTATION REQUESTED BY GOOGLE TO PERMIT IT TO COMPLY WITH ALL APPLICABLE STATE, FEDERAL, LOCAL AND FOREIGN (INCLUDING PROVINCIAL) TAX REPORTING AND WITHHOLDING REQUIREMENTS. ALL PRIZES WILL BE NET OF ANY TAXES GOOGLE IS REQUIRED BY LAW TO WITHHOLD. ALL TAXES IMPOSED ON PRIZES ARE THE SOLE RESPONSIBILITY OF THE WINNERS. In order to receive a prize, potential winners must submit the tax documentation requested by Google or otherwise required by applicable law, to Google or the relevant tax authority, all as determined by applicable law, including, where relevant, the law of the potential winner’s country of residence. The potential winner is responsible for ensuring that (s)he complies with all the applicable tax laws and filing requirements. If a potential winner fails to provide such documentation or comply with such laws, the prize may be forfeited and Google may, in its sole discretion, select an alternative potential winner.

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

 

11. GENERAL CONDITIONS: 

All federal, state, provincial and local laws and regulations apply. Google reserves the right to disqualify any entrant from the Contest if, in Google’s sole discretion, it reasonably believes that the entrant has attempted to undermine the legitimate operation of the Contest by cheating, deception, or other unfair playing practices or annoys, abuses, threatens or harasses any other entrants, Google, or the Judges. 

 

12. INTELLECTUAL PROPERTY RIGHTS:

As between Google and the entrant, all Submissions remain the intellectual property of the individuals or organizations that developed them. The entrant retains ownership of all intellectual and industrial property rights (including moral rights) in and to any project materials, or videos provided for the Contest. As a condition of entry, entrant grants Google, its subsidiaries, agents and partner companies, a perpetual, irrevocable, worldwide, royalty-free, and non-exclusive license to use, reproduce, adapt, modify, publish, distribute, publicly perform, create a derivative work from, and publicly display such Project(s) (1) for the purposes of allowing Google and its affiliates and the Judges to evaluate the Project for purposes of the Contest, and (2) in connection with advertising and promotion via communication to the public or other groups, including, but not limited to, the right to make screenshots, animations and video clips available for promotional purposes. To the extent your or your team or organization’s Submission makes use of generally commercially available software not owned by you or your team or organization that was used to generate the Submission, but that can be procured by Google without undue expense, you do not grant the license in the preceding sentence to that software.

 

13. PRIVACY:

Participant acknowledges and agrees that Google may collect, store, share and otherwise use personally identifiable information provided during the registration process and the contest, including, but not limited to, name, mailing address, phone number, and email address. Google will use this information in accordance with its Privacy Policy, including for administering the contest and verifying Participant’s identity, postal address and telephone number in the event an entry qualifies for a prize. 

Participant’s information may also be transferred to countries outside the country of Participant's residence, including the United States.  Such other countries may not have privacy laws and regulations similar to those of the country of Participant's residence.

If a participant does not provide the mandatory data required at registration, Google reserves the right to disqualify the entry. 

Participant has the right to request access, review, rectification or deletion of any personal data held by Google in connection with the Contest by writing to Google at this email address: rviscomi@google.com.

Information collected from Participants is also 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.

 

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

 

15. WARRANTY, INDEMNITY AND RELEASE:

Entrants warrant that their Projects are their own original work and, as such, they are the sole and exclusive owner and rights holder of the submitted Project and that they have the right to submit the Project in the Contest and grant all required licenses.  Each entrant agrees not to submit any Project that (1) infringes any third party proprietary rights, intellectual property rights, industrial property rights, personal or moral rights or any other rights, including without limitation, copyright, trademark, patent, trade secret, privacy, publicity or confidentiality obligations; or (2) otherwise violates the applicable state or federal law.

To the maximum extent permitted by law, each entrant indemnifies and agrees to keep indemnified Contest Entities at all times from and against any liability, claims, demands, losses, damages, costs and expenses resulting from any act, default or omission of the entrant and/or a breach of any warranty set forth herein. To the maximum extent permitted by law, each entrant agrees to defend, indemnify and hold harmless the Contest Entities from and against any and all claims, actions, suits or proceedings, as well as any and all losses, liabilities, damages, costs and expenses (including reasonable attorneys fees) arising out of or accruing from (a) any Project or other material uploaded or otherwise provided by the entrant that infringes any copyright, trademark, trade secret, trade dress, patent or other intellectual property right of any person or defames any person or violates their rights of publicity or privacy, (b) any misrepresentation made by the entrant in connection with the Contest; (c) any non-compliance by the entrant with these Rules; (d) claims brought by persons or entities other than the parties to these Rules arising from or related to the entrant’s involvement with the Contest; and (e) acceptance, possession, misuse or use of any prize or participation in any Contest-related activity or participation in this Contest.

Entrant releases Google from any liability associated with: (a) any malfunction or other problem with the Contest Site; (b) any error in the collection, processing, or retention of entry information; or (c) any typographical or other error in the printing, offering or announcement of any prize or winners.

 

16. ELIMINATION:

Any false information provided within the context of the Contest by any entrant concerning identity, mailing address, telephone number, email address, ownership of right or non-compliance with these Rules or the like may result in the immediate elimination of the entrant from the Contest.

 

17. INTERNET:

Contest Entities are not responsible for any malfunction of the entire Contest Site or any late, lost, damaged, misdirected, incomplete, illegible, undeliverable, or destroyed Projects or entry materials due to system errors, failed, incomplete or garbled computer or other telecommunication transmission malfunctions, hardware or software failures of any kind, lost or unavailable network connections, typographical or system/human errors and failures, technical malfunction(s) of any telephone network or lines, cable connections, satellite transmissions, servers or providers, or computer equipment, traffic congestion on the Internet or at the Contest Site, or any combination thereof, including other telecommunication, cable, digital or satellite malfunctions which may limit an entrant’s ability to participate.

 

18.  RIGHT TO CANCEL, MODIFY OR DISQUALIFY:

If for any reason the Contest is not capable of running as planned, including infection by computer virus, bugs, tampering, unauthorized intervention, fraud, technical failures, or any other causes which corrupt or affect the administration, security, fairness, integrity, or proper conduct of the Contest, Google reserves the right at its sole discretion to cancel, terminate, modify or suspend the Contest. Google further reserves the right to disqualify any entrant who tampers with the submission process or any other part of the Contest or Contest Site.  Any attempt by an entrant to deliberately damage any web site, including the Contest Site, or undermine the legitimate operation of the Contest is a violation of criminal and civil laws and should such an attempt be made, Google reserves the right to seek damages from any such entrant to the fullest extent of the applicable law.

 

19. NOT AN OFFER OR CONTRACT OF EMPLOYMENT:

Under no circumstances shall the submission of a Project into the Contest, the awarding of a prize, or anything in these Rules be construed as an offer or contract of employment with either Google, or the Contest Entities. You acknowledge that you have submitted your Project voluntarily and not in confidence or in trust. You acknowledge that no confidential, fiduciary, agency or other relationship or implied-in-fact contract now exists between you and Google or the Contest Entities and that no such relationship is established by your submission of a Project under these Rules.

 

20. FORUM AND RECOURSE TO JUDICIAL PROCEDURES:

These Rules shall be governed by, subject to, and construed in accordance with the laws of the State of California, United States of America, excluding all conflict of law rules. If any provision(s) of these Rules are held to be invalid or unenforceable, all remaining provisions hereof will remain in full force and effect. To the extent permitted by law, the rights to litigate, seek injunctive relief or make any other recourse to judicial or any other procedure in case of disputes or claims resulting from or in connection with this Contest are hereby excluded, and all Participants expressly waive any and all such rights.

 

21. ARBITRATION:

By entering the Contest, you agree that exclusive jurisdiction for any dispute, claim, or demand related in any way to the Contest will be decided by binding arbitration. All disputes between you and Google of whatsoever kind or nature arising out of these Rules, shall be submitted to Judicial Arbitration and Mediation Services, Inc. (“JAMS”) for binding arbitration under its rules then in effect in the San Jose, California, USA area, before one arbitrator to be mutually agreed upon by both parties. The parties agree to share equally in the arbitration costs incurred.

 

22. WINNER’S LIST:

You may request a list of winners after October 27, 2025 but before March 27, 2026 by sending a self addressed stamped envelope to:

Rick Viscomi

Google Inc.

1600 Amphitheater Parkway Mountain View, CA 94043 USA

(Residents of Vermont need not supply postage).

 

23. DEVPOST:

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