Legal

The categories in 1.1 to 1.7 are everything the Service holds about you. Where a category is collected only because you used a particular feature, the clause says so.

We use the information in clause 1 to provide, maintain, and improve the Service; to authenticate you and keep your account secure; to send notifications you have enabled and important account or service notices; to process payments where you use those features; and to detect, prevent, and respond to fraud, abuse, and security issues.

We do not use your content to train machine-learning models. We do not run advertising on the Service.

Where your team has turned on smart tagging, the text of the record being labelled is sent to Google's Gemini API so it can pick from your team's own tags. That is done on a paid tier whose terms prohibit Google from using it to train or improve their models. The feature is off unless someone on your team turns it on, and what it covers is set out on the transparency page. We keep a copy of the text sent and the answer returned for thirty days, so that a bad label can be traced to what produced it and the cost of the feature can be checked. Only platform administrators can read that log and it is deleted on a timer.

We set a cookie to keep you signed in and to protect against cross-site request forgery. Both are required for the Service to function. We do not use advertising or cross-site tracking cookies. Clearing them signs you out.

We share the minimum information necessary with the providers that help us run the Service: Stripe for payments, donations, card issuing, and identity checks; Resend for transactional and notification email; GitHub and Google for sign-in, if you choose that provider; Google Maps Platform for geocoding and map imagery; and our hosting and object storage providers for running the application and storing uploaded files.

These providers are permitted to use your information only to provide their service to us. Data is stored and processed in the United States. The register on the transparency page carries the current list and the date it was last checked against production.

Financial and card-issuing features are processed by Stripe. Payment card details are handled by Stripe and are not stored on our servers. Your use of those features is also subject to Stripe's privacy policy and terms.

If your team connects an integration, such as a Discord webhook for notifications, information about the events you choose to send is delivered to that service and is then governed by its own policies. Financial amounts and receipt links are excluded from webhook payloads by default. Any team owner or admin can disconnect an integration at any time.

We do not sell your personal information. Beyond the providers named in clause 4, we share it only when required by law or to protect the rights and safety of our users and the public.

Content you choose to publish, such as a public team site or team profile, is visible to anyone. Treat those surfaces as public. Inside a team, members and admins can see the team's content according to the permissions they hold.

We use encryption in transit, scoped access controls, and permission checks on every request. No system is perfectly secure and we cannot guarantee absolute security. If you believe you have found a vulnerability, report it through our contact form before disclosing it publicly.

The Service is intended for users who are at least 13 years old. We do not knowingly collect information from anyone under 13. The Service is used by FTC team members, some of whom are under 18, and we collect only the information needed to operate it. If you are a parent or guardian and believe a child under 13 has provided us information, contact us and we will delete it.

We keep information for as long as your account is active or as needed to provide the Service and meet legal obligations. Financial records may be retained longer where law requires it.

You may request access to, correction of, export of, or deletion of your personal information through our contact form. Deleting your account does not automatically delete content your team relies on.

We may update this policy. Material changes are recorded in the amendment log below, with the version number and the date they took effect, and where appropriate we show an in-app notice.

You must be at least 13 years old to access or use the Service. By using it you represent that you meet this requirement. You are responsible for the activity under your account and for keeping your login secure. You must not share credentials or use another person's account without permission, and you must provide accurate information and keep it current.

Robolyst is organised around teams. When you join a team, its owners and admins can see, edit, and delete content in that team's workspace, including content you created, and can remove you from the team. If you leave or are removed, the team's content stays with the team.

You must not misuse, disrupt, or attempt to gain unauthorised access to the Service. You must not upload unlawful, infringing, or harmful content, use the Service to harass others or violate the rights of others, or scrape, resell, or redistribute the Service or its data at scale. You must follow all applicable laws and FIRST program rules.

You retain ownership of content you submit. You grant the Foundation a limited licence to host, store, and display that content solely to operate and provide the Service. You are responsible for the content you create and for holding the rights to share it. The Foundation may remove content that violates these Terms.

Some features involve payments, cards, and financial records processed through Stripe. You are responsible for the accuracy of financial data you enter and for complying with the terms of any third-party payment provider.

Budgets, spending limits, and reports in the toolkit are bookkeeping aids and are not authoritative accounting. The Foundation is not a bank and does not provide financial, legal, or tax advice.

The Service links to and integrates with services the Foundation does not control, including Stripe, GitHub, Google, Discord, and the FIRST Tech Challenge Events API. Your use of those services is governed by their own terms, and the Foundation is not responsible for them.

The Service is provided “as is” and “as available,” without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement.

Competition data is sourced from the FIRST Tech Challenge Events API and may be incomplete, delayed, or inaccurate. Analytics derived from it are estimates. The Foundation does not guarantee uninterrupted or error-free operation and may change or discontinue features. Keep your own copies of anything you cannot afford to lose.

To the maximum extent permitted by law, The Robotics Catalyst Foundation Inc. is not liable for any indirect, incidental, special, or consequential damages, or for lost data, revenue, or competitive standing, arising from your use of the Service. Robolyst is not affiliated with, sponsored by, or endorsed by FIRST.

The Foundation may suspend or terminate access if you violate these Terms or to protect the Service and its users. You may stop using the Service at any time and ask for your account to be deleted.

The Foundation may update these Terms. The version number and effective date below identify the current text, and continuing to use the Service after a change means you accept it. Every change is recorded in the amendment log.

These Terms are governed by the laws of the State of Connecticut and the United States, without regard to conflict-of-law rules. Any dispute arising out of or relating to these Terms or the Service will be brought exclusively in the state or federal courts located in Connecticut, and you consent to the jurisdiction of those courts.