Privacy Policy

Last updated September 11, 2026.

This policy describes the RoboBattles app at hub.robobattles.com, operated by the Grant Imahara STEAM Foundation ("we," "us"). It does not describe every separate Foundation website or external service.

Information we collect

• Account information: email, account name if supplied, email confirmation status, account dates, sign-in activity, and any existing player/educator preference. A preference is not proof of a person's role or authority.
• Registration information: your 13-or-older declaration and its date, team names and numbers, player counts, organization names and types, city and ZIP code, listing status, and optional public contact email and website.
• Management information: organization memberships, staff roles, invitation email addresses and acceptance status, event details, team entries, player-count snapshots, and registration dates.
• Technical information: session cookies, authentication tokens, browser session storage, and request information needed for delivery, security, and troubleshooting, such as IP address and browser information. Rate-limit identifiers are hashed; hosting logs may contain request information.

The current app does not offer named student rosters or fields for birth dates, gender, race or ethnicity, household income, disability, or Title I status. Do not put these details in names, venue fields, or other free-text fields.

How we use information

We use information to send sign-in emails, maintain accounts, display listings, provide approximate ZIP-based discovery, manage staff access and event entries, prevent abuse, provide support, and understand program participation. Registrations and player counts are not proof of attendance or unique individuals. This app does not automatically subscribe you to marketing emails.

Public and restricted information

When a team is listed, its name, number, organization association, city, ZIP, player count, availability for new players, and optional contact information are public. Published event details include the host name, venue, schedule, capacity, and registration count. Public listings are accessible through the directory API without an account and may be copied by others. Entering an email in the interface does not make the directory private.

Unlisted teams and draft events are not part of public discovery. Access is limited by management and registration permissions. Organization staff can see their organization's staff information. Event hosts can see registered team names, numbers, player counts, and registration times; this is not a named student roster. Authorized Foundation personnel and service providers may access information as needed to operate, secure, and support the service.

Your sign-in email is not automatically published as a team contact. Public contact fields are optional and must be entered separately. Use a program or adult-managed address that you have permission to publish. Do not publish student personal emails or residential addresses.

External contact and providers

RoboBattles does not collect or forward requests to join teams. Contact links open an email application or external website. Sending an email or submitting another site's form shares information with that recipient under their practices, not through a RoboBattles inbox. We do not vet external contacts or control what they retain.

Cloudflare provides hosting, database, session storage, and security infrastructure. Amazon Web Services SES delivers authentication emails. ZIP lookups send the ZIP code to Zippopotam.us, not your account email; results are cached. Google Fonts delivers fonts to your browser and receives the associated network request. Providers may process data in the United States and other locations.

The current app does not include advertising trackers or sell personal information. We may disclose information when required by law, to protect people or the service, or to service providers assisting us with those purposes.

Cookies and storage

Authentication uses cookies shared across configured RoboBattles subdomains. Sessions can last up to 30 days and may renew with use. Browser session storage remembers an entered email for the current browsing session. Signing out ends the app session; blocking required cookies can prevent sign-in. These mechanisms are not an age or identity verification service.

Retention and deletion

Account and registration records currently remain stored until removed; the app does not yet automatically delete inactive accounts or old event records. Expiring authentication data has separate cleanup. Archiving a team or cancelling an event preserves its records and is not deletion.

Contact us to request access, correction, or deletion. We may need to verify your control of the account and resolve organization ownership or shared registrations. We will review what can be deleted and explain any information retained for legal, security, or legitimate recordkeeping needs. Copies in backups or hosting logs may persist for the relevant provider retention period. We cannot remove copies of public information or emails already retained by others.

Children and teenagers

Accounts are intended for people 13 or older. A younger player should ask a parent or guardian to use their own account and contact information. This declaration is not verified age, guardian consent, or proof of adulthood. Do not submit a child's personal information on their behalf through these registration fields. If you believe a child under 13 has supplied personal information, contact us so we can review and address it.

Teenagers should involve a parent or guardian before contacting unfamiliar people or attending an event. The app does not establish that a listed host is an adult, school representative, or vetted supervisor.

Your choices and contact

You can edit managed team and event details, remove public contact fields, unlist or archive a team, and withdraw an event entry. For privacy, deletion, support, or safety reports, email support@robobattles.com. Do not send identity documents or sensitive student information unless a necessary, secure process has been agreed.

Policy changes

We will update this page and its revision date when practices change, and provide additional notice or obtain consent where required. New demographic collection or materially different sharing requires review and updated disclosures before it is enabled.