← Back

Privacy Policy

Last updated July 31, 2026

This app runs live fantasy football auction drafts. It's built for a private group running its own draft, not a public social platform — this page explains exactly what data exists and where it goes.

What we collect

Running a league itself needs no account or sign-up. Almost nothing is collected beyond what you voluntarily put into a league:

  • A league code — a random 6-character code identifying a draft. Not tied to your identity.
  • A commissioner PIN — chosen by whoever creates the league. We never store the PIN itself; only a one-way cryptographic hash of it (SHA-256), so even we cannot see or recover your actual PIN.
  • Team names, player picks, and prices — whatever your league's commissioner and members enter while running the draft.
  • Optional Fan Messages — free-text messages your league can choose to post to the shared ticker, if that feature is turned on.

Buying or restoring the optional Pro upgrade is the one place a real account is involved:

  • Signing in with Google — used only to prove a Pro purchase or restore request is genuinely yours, so nobody else can claim it. We receive your Google account's email address from this sign-in; we never receive your Google password, contacts, files, or anything else about your account. Handled via our database provider's (Supabase) standard Google sign-in integration, which follows Google's own OAuth security standards.
  • Your email address — recorded when you buy or restore Pro, solely to match that purchase across platforms (e.g. the website and the Android app). Never used for marketing, never sold, and never shared with anyone besides our payment processor (Stripe), database host (Supabase), and Google (for the sign-in itself) — all acting purely as infrastructure on our behalf, not as recipients of your data for their own purposes.

We do not collect names, phone numbers, precise location, contacts, photos, or any device identifiers beyond a randomly generated on-device ID used only to enforce the free tier's league-count limit (see below).

Where your data is stored

League and pick data is stored in a Postgres database hosted by Supabase, a third-party database provider. We do not sell, share, or use your data for advertising. Supabase acts purely as our database host — see their own privacy policy for how they handle infrastructure-level data.

How long we keep it

Drafts aren't kept forever:

  • Free-tier leagues are automatically deleted after 7 idle days if the draft is unfinished, or 14 idle days once it's complete.
  • Pro leagues are automatically deleted after 60 idle days, regardless of completion status.

Once a league is deleted, everything tied to it is gone permanently and cannot be recovered — every pick, every setting, and the Recap page (including its stats and roast text). If you want to keep a permanent copy of your results, download the CSV export or the Recap page before that window closes.

Who can see your league

Anyone with your league's 6-character code can view its board and rosters — this is intentional (it's how the TV display and QR-code sharing work) and is the same trust model as a shared physical draft board in a room. Editing a league (logging picks, changing settings) additionally requires the commissioner's PIN, which is checked on our server before any change is allowed.

Third-party content

The Draft Board's news ticker pulls public sports headlines directly from ESPN's and CBS Sports' public RSS feeds, and season odds/scores from ESPN's public API. These requests go directly from your device/browser to those services; we don't proxy or log them ourselves.

Children's privacy

This app is intended for general audiences running fantasy football drafts and is not directed at children under 13. We do not knowingly collect data from children.

Changes to this policy

If this policy changes, the "Last updated" date above will change too. Material changes will be reflected here before they take effect.

Contact

Questions about this policy or your data can be sent via GitHub Issues on this project.