Pre-release privacy notice

Private identity. Public competition.

Sprint collects only the identity, competition, notification, eligibility, and operational data needed to run and protect invitation testing and the Founding Public Beta.

Last updated July 23, 2026
01

Account information

Google supplies a verified account identifier, email, and may supply a display name after you consent to sign in. Sprint links the stable Google account identifier to one durable manager account, authorizes protected actions through a private app session, and may use the verified email for competition messages when transactional email is enabled.

Sprint does not request or retain Google Drive, Gmail, contacts, calendar, access tokens, or refresh tokens.

Your email, provider identity, and full name are not published on league, draft, profile, recap, or leaderboard pages.

02

Public Sprint information

Your chosen username, draft selections, club association, lineups, results, standings, championships, completion history, and Sprint Rating are part of the shared competition record. Public manager profiles use the username rather than private login identity.

03

Operational information

Sprint stores authoritative deadlines, idempotency records, audits, notification state, a limited last-seen signal for reconnect and incident diagnosis, and one private activity record per UTC day that an official manager opens an official competition room. Private request logs use an opaque fingerprint instead of raw email and exclude request bodies, secrets, authentication headers, and provider responses.

Presence is operational only. It cannot change a seat, deadline, pick, lineup, simulation input, result, champion, or rating.

04

Recruitment measurement

When you follow a Sprint recruitment link, an allowlisted campaign code may identify the source channel. Sprint stores landing visits only as campaign-by-day totals and may attach the campaign code to a newly enrolled public-beta manager account so the owner can measure username setup, lobby participation, draft completion, completed Sprints, and repeat play.

Sprint does not use advertising pixels, fingerprinting, cross-site tracking cookies, or browser storage for recruitment measurement. Campaign information does not decide access, draft position, simulation inputs, results, ratings, or support treatment.

05

Notifications

In-app lifecycle notifications are part of the durable account record. Transactional email is optional and can be disabled in the notification inbox. Disabling email cancels pending unsent delivery and prevents new email delivery records while leaving the in-app notice intact.

06

Service providers

OpenAI Sites provides hosting and authenticated access. Cloudflare provides the Worker and D1 infrastructure used by the Site. If transactional email is released, Resend processes only the delivery information needed to send those messages.

Sprint does not sell participant data or use transactional contact data for marketing.

07

Retention and requests

Completed competition, rating, and audit records are retained so results remain reproducible and cannot be silently rewritten. Short-lived scheduler replay claims expire after their documented retention window; rate-limit windows expire automatically.

When pre-release access is revoked, active Sprint sessions are ended immediately. The access and authentication audit remains private, while completed shared competition history remains attached to the public username.

Use the Sprint support page to request access help, an email-notification change, deletion review, or review of private account information. A request cannot require Sprint to falsify or remove another manager's shared competition history.