This hackathon has important stipulations around datasets, likeness of the Olympics and athletes. Be sure to read through the FAQs to ensure your Project meets all requirements and doesn't break any of the official rules. 

Frequently Asked Questions

AI & Media Guidelines

Q: Can I use GenAI to create images for my project?

A: Yes, however all GenAI Media MUST be animations ONLY (ie: no real people/athletes). There is a strict prohibition on the use of any athlete’s Name, Image, or Likeness (NIL) in your submission. Your project can analyze data that is associated with an athlete by name, but the output should not be at the individual level.

Q: Can I use other Generative AI tools (like ChatGPT) to process the data?

A: No. Only Google Cloud Generative AI tools (such as Gemini models via Vertex AI, analytics services from Google Cloud, Cloud Functions, and relevant APIs) are permitted for processing Team USA data. Other than artificial intelligence tools, the Project should primarily leverage primarily Google Cloud products for its functionality and implementation.

Data & Intellectual Property

Q: Which Datasets can I use in my Project? 

A: Data Strategy: Public Focus (Mandatory): Projects must rely exclusively on publicly available Team USA datasets. Participants are explicitly instructed to use the following publicly accessible sources for their projects:

  • Official Team USA Website (www.teamusa.com. Results data, athlete profiles, and blog content).
  • Open Source Repositories (historical athlete performance and macro Olympics data) filtered for Team USA athletes only.
  • Public weather data (e.g., from open source sites like NOAA).
  • Permitted Data: 
    • Participants may use finish placement (e.g., 1st, 2nd, 3rd) and medals.
  • Prohibited Data: 
    • Participants are strictly prohibited from using finish times or specific scoring results.
    • Participants are strictly prohibited from using Team USA multimedia in their submissions that show individual athlete name, image, or likeness (NIL).
US Scope: Only data pertaining to Team USA (Olympic and Paralympic) may be used; larger international Olympic/Paralympic data sets are prohibited unless filtered for US-scope only.

Q: Can I use any Olympics / IOC Content in my Project? 

A: No. You must not use any official International Olympic Committee (IOC) or USOPC intellectual property. This includes:

  • The Rings: No five-ring logo.

  • The Torch: No official Olympic torch imagery.

  • Likeness: No names, photos, or video of specific Team USA athletes.

  • Terminology: Avoid "Olympic Games" as your app title—stick to “Team USA x Google Cloud Hackathon”

Focus on the vibe of the sport and the data-driven solutions, rather than official branding.

Restricted Content: Submissions must not contain Games footage, unlicensed music, or restricted terminology.

Q: Can I use Olympic terminology in my project?

A: No. You must not use any olympic terminology and should use generic terms throughout your project.

  • Restricted Terminology:
  • Winter Games: Must be referred to as “Olympic Winter Games [City] [Year]” or “Paralympic Winter Games [City] [Year]” (e.g. “Olympic Winter Games Beijing 2022”). Secondary approved references include “The Winter Olympics” or “[City] [Year].”
  • Summer Games (Non-LA): Must be referred to as “Olympic Games [City] [Year]” (e.g. “Olympic Games Paris 2024”).
  • LA28 Games: Preferred references are “LA28 Games” or “LA28 Olympic and Paralympic Games.”
  • “Former” Olympians: Once an athlete is an Olympian/Paralympian, they are always an Olympian/Paralympian; you must never use the terms “former” or “past” Olympian/Paralympian.
  • Sport Names: You must use the official sport terminology, not the name of the National Governing Body (NGB) that represents the sport, unless prior NGB approval is obtained. For example, swimming vs. USA Swimming.

Technical Requirements & Deployment

Q; Which tools and technologies are required for my project? 

A: You must use the following two tools and you may use any additional Google tools/products

Gemini API: Your app must utilize Gemini models (likely via Google AI Studio) to power its core logic or features.

Google Cloud: Your application must be deployed and hosted on Google Cloud (using services like Cloud Run or App Engine) so the judges can access a live, working URL.

Q: What type of URL are you looking for for the Hosted Project?

A: This should be a hosted project such as web UI, Chrome Extension, mobile app, etc. A hosted project is highly encouraged.

Q: Can I submit a project I started before the hackathon?

A: The rules state you should vibe code with Gemini to transform Team USA and publicly available data into NEW interactive dashboards, web apps, or AI agents that showcase the collective power of Team USA. While you can leverage your existing knowledge or libraries, the specific project, its integration with Gemini, and its Google Cloud deployment should be built specifically for this challenge.

Q: Does "Public Code Repository" mean I have to open-source my idea?

A: Yes. To be eligible for judging, your repository must be public so the judges can review your code and reproducibility. Make sure your README includes clear testing instructions!

Q: How do I prove my project is running on Google Cloud? 

A: Proof would either be (1) a quick screen recording that shows the behind-the-scenes of their app running on GCP (e.g. console logs or console view of a deployment) or (2) a link to a code file in their Github repo that demonstrates use of Google Cloud services and APIs (e.g. API calls to Vertex AI endpoints)

You can upload and host videos directly within a Github repo. Other popular code repositories such as Gitlab and Bitbucket also support video uploads. It is straightforward to accomplish and the participants just treat the video file (e.g. mp4) the same way they treat a code file that they commit to their repo. Here is an example: http://github.com/huntharo/video-test

Google Cloud Credits & Billing

Q: How can I get Google Cloud credits for the hackathon?

A: You can obtain access to Google Cloud developer tools by signing up for a no-cost trial at cloud.google.com/free or by using an existing Google Cloud account or if you already have an account, requesting $100 in Google Cloud credits by completing this form. Be aware that you are responsible for fees if your usage exceeds the credit amount.

Q: How do I keep costs down? 

A: The best way to save credits is to develop and test locally or using the free tier as much as possible during the build phase. We recommend not fully deploying your app to a high-availability production setting on Google Cloud until March 30th. This ensures your credits last through the critical judging period when the panel will be reviewing your live backend.

  • Use Free Tiers: Stick to the free tiers for Google AI Studio and Cloud Run whenever possible.
  • Set Budget Alerts: Head to your Google Cloud Billing Console and set a budget alert. It will "blow the whistle" (send you an email) if you approach a specific spending limit.
  • Shut Down Unused Labs: If you aren't actively testing a heavy deployment, scale it down to ensure you aren't burning through credits while you sleep.

Submissions & Judging

Q: How can I share my project with the judges?

A: Provide a link to your website, functioning demo, or a test build. If your website is private, you can include login credentials in the submission form which will not be shown to the public.

Q: Will the judges test my project? 

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

Support & Communication

Q: Can I share my Project on social media?

A: No, you CANNOT share your Project on any social media channels before or after the hackathon unless given express permission.

Per the official rules: 

  • Restricted Content: Participants are strictly prohibited from publicly sharing project details, source code, or demo videos including on any social media platform (including LinkedIn, X, and YouTube) except the demo video as unlisted on YouTube for the purposes of submission or unless otherwise authorized by the Sponsor.
  • No Marketing Rights: Participation in or winning this hackathon does not grant any individual marketing rights. Entrants may not post or publicly promote their participation. Winners may not post about their achievement except as specifically authorized by the Sponsor, and never in a way that suggests a personal sponsorship or endorsement by the United States Olympic & Paralympic Committee / Team USA / LA28.
  • Authorized Sharing Only: If authorized to share, posts must follow specific messaging criteria provided by the Sponsor.

Please read the Official Rules for details.