Skip to content

Last updated November 12, 2026

Privacy Policy

What we collect, what we don't, who else sees it and how to get it deleted. This describes what the site actually does, not what a template says it might.

The short version

We use Google Analytics and advertising tags from Google, Meta, Reddit and X to measure our ads and see which ones bring people to the site. They set their own cookies and tell Google, Meta, Reddit and X about your visit (and, when you sign up, give them a scrambled copy of your email address to match it with), which California law counts as “sharing”. You can turn them off on any browser in one click: Do Not Sell or Share My Personal Information. We don't sell your email address or your account data to anyone.

This policy explains how Stat Grades Media LLC handles information on statgrades.com and in our mobile app. Writing to [email protected] reaches a person, not a form.

What we collect

If you never make an account: nothing that identifies you. The site reads no cookie and stores no record of your visit beyond the temporary security logging described below (the advertising and analytics tags described under Advertising and analytics collect their own data). If you arrived through a tagged link or from another website, your own browser keeps a note of which one (see Cookies and browser storage); it stays in your browser unless you make an account.

If you make an account, we store:

  • Your email address. Required. It's your login and how we send account email. Stored lower-cased.
  • Your name. Optional: only if you give it to us, or the name on your Google account if you sign in with Google.
  • A notification address for each phone. Only if you turn on notifications in our phone app: the push token Expo gives the app on that phone, so we can send it injury alerts, lineup checks and picks you've chosen, and which kinds you've switched off. It identifies the app on that phone, not the phone itself, and it's deleted when you sign out of the app, remove the app or delete your account.
  • A password hash. Never your actual password. We store a scrypt hash, which can't be reversed back into your password. An account made with Google has no password until you set one.
  • Your Google account id. Only if you sign in with Google. You sign in on Google's own page and we never see your Google password. Google tells us your account's id number, your email address (only once Google has confirmed it) and your name, and nothing else: no contacts, no Drive, no Gmail. We keep the id so the same Google account signs you in next time. You can remove our access from your Google account's security settings at any time. On the sign-up page and our ad landing pages, if you aren't signed in to StatGrades, Google may offer to sign you in with your Google account in a small box; to show it, your browser loads a script from Google, which tells Google you visited that page. We don't load it if you've turned on Do Not Sell or Share or your browser sends Global Privacy Control.
  • Which page you signed up from. Just the section (home, odds, StatGrades Picks, fantasy), so we can tell what people come here for.
  • What brought you here. If, in the 30 days before you signed up, you arrived through a tagged link (an ad, a newsletter, a post — the utm_ labels on the address) or by following a link from another website: that campaign's labels or that website's name, the page you landed on and when. We keep the first such visit, not later ones. If that visit was a click on a Google ad, we also keep the click's id number that Google adds to the address (gclid), so we can count signups by ad. Never the full address you came from. It tells us which promotions work, and it isn't passed to the ad platform or anyone else.
  • Account activity. When you created the account, when you last signed in, whether you've confirmed your email, and whether alerts are on.
  • Your sessions. One row per signed-in browser, holding a hash of the session token and the browser's user-agent string, so you can see and end sign-ins.

If you use fantasy or member features, we also store:

  • Your connected leagues. For each league you import: which platform it's on (Sleeper, ESPN, Yahoo, CBS, Fleaflicker or MyFantasyLeague), the league id, its name and season, which team is yours and that team's name, and your user id on that platform where it gives us one (Sleeper and Yahoo; ESPN, CBS, Fleaflicker and MyFantasyLeague don't). We keep this until you remove the league.
  • A copy of each football league as we last read it. When we read a football league, we save part of what the platform shows us: your team's players and who is in your lineup, this week's opponent's team name and lineup, your league's lineup slots, scoring, roster size and waiver budget, and which players are on a team somewhere in the league. We don't keep the rest of the other teams' rosters. We use the copy for two things: to send your injury and practice alerts, without asking the platform about every league every few minutes, and to fill in the all-my-leagues page straight away while it reads each league again. A single league's page still reads the platform when you open it. If you get injury or practice alerts we update the copy every few hours and shortly before kickoffs; otherwise we update it when you open the league. Each update replaces the last, so there is one copy per league. It has no time limit: it stays, even after a season ends or after you disconnect a sign-in, until you remove the league or your account is deleted. For NBA leagues we save no copy, only the link above and when we last read the league successfully.
  • Your Yahoo connection. Only if you connect Yahoo. You sign in on Yahoo's own page and we never see your Yahoo password. Yahoo gives us a read-only access token, which lets us read your fantasy leagues and nothing else, and we store it encrypted, along with the refresh token that keeps the connection working and your Yahoo account id. Disconnecting Yahoo on My Team deletes both tokens; you can also revoke our access from your Yahoo account settings.
  • Your ESPN sign-in. Only if you connect it, to import a league ESPN keeps private. ESPN offers other sites no way to ask permission, so this is the pair of cookies ESPN sets when you sign in at espn.com (espn_s2 and SWID), which you copy in or our Chrome extension sends from this site. We never see your ESPN password. We store both encrypted, use them only to read your fantasy leagues, and delete them when you press Disconnect on My Team, or when ESPN stops accepting them (signing out of espn.com ends them). The extension reads those two ESPN cookies only when you press its connect button on statgrades.com, and sends them nowhere but here.
  • Your CBS sign-in. Only if you connect it, to import a CBS league. CBS offers other sites no way to ask permission either, so this is the handful of cookies CBS sets when you sign in at cbssports.com that say who you are, which our Chrome extension sends from this site or you copy in. If you copy in more than that, we throw the rest away without storing it. We never see your CBS password. We store them encrypted, use them only to read your fantasy leagues, and delete them when you press Disconnect on My Team (signing out of cbssports.com also ends them). The extension reads them only when you press its connect button on statgrades.com, and sends them nowhere but here.
  • Your MyFantasyLeague API key. Only for a MyFantasyLeague league its settings keep private: the API key MFL shows you for that league, which you copy in. MFL's key only reads that one league as you and can't change anything; we never see your MFL password. We store it encrypted, use it only to read that league, and delete it when you remove the league from My Team.
  • Your Reality Sports Online sign-in. Only if you connect it. RSO offers other sites no way to ask permission, so this is the sign-in cookies your browser holds for realitysportsonline.com, which you copy in; we throw away its advertising and analytics cookies. We never see your RSO password. While the RSO import is new, connecting also saves a copy of what RSO shows us for your leagues (rosters, contracts, cap space, league history), which we use only to fix and improve the import. Both are stored encrypted and deleted when you press Disconnect on My Team; signing out of RSO also ends the sign-in.
  • How your league imports went. Each time you look up, connect or import a league, and when a league you imported can't be read: which site, the league id, when, and if it didn't work, what went wrong. Never your passwords, cookies or keys. We use it only to fix imports that fail, sometimes by emailing you about one, and delete it after 90 days.
  • AI answers we generated. Roster advice and waiver claims, each with a fingerprint of what it was based on, so asking the same question twice doesn't cost us twice. We also count them against your monthly allowance. Each is saved with the league id and week it was for and names the players it discusses. They have no time limit, and removing a league doesn't delete them: they stay until your account is deleted.
  • League report cards you share. Only if you press share on a league report card. We save your team's name, its players and their stats and grades for that week, along with the league id, so the link works without reading your league again. Anyone with the link can see the card. It has no time limit, and removing the league doesn't delete it or stop the link working; it stays until your account is deleted, or email [email protected] and we'll take a card down.
  • Which alerts we've already sent you. So you get told about an injury once rather than every hour.

For security, briefly: when you sign in, sign up or ask for AI advice, we record the event against your IP address or account id to enforce rate limits — this is what stops someone guessing passwords. These records are automatically deleted after 24 hours. We keep no general access log tied to you.

Advertising and analytics

We load these through Google Tag Manager on every page. If you've opted out (see your choices), they're told so before any of them runs, as described there:

  • Google Analytics. Counts visits and which pages and features get used: the pages you view, roughly where you are (city level, from your IP address), your device and browser, and which link or ad brought you here.
  • Google Ads. Tells Google when someone who clicked one of our ads goes on to sign up or buy, so we can see which ads work, and lets us show our ads again to people who have visited.
  • Meta Pixel. The same for our ads on Facebook and Instagram: Meta learns that your browser visited, signed up or bought, and can match that to your Meta account if you have one.
  • Reddit Pixel. The same for our ads on Reddit: Reddit learns that your browser visited, signed up or bought, and can match that to your Reddit account if you have one.
  • X Pixel. The same for our ads on X (formerly Twitter): X learns that your browser visited, signed up or bought, and can match that to your X account if you have one.

Beyond the pages you visit, we tell these tags only these things: when you sign up, that it happened and whether it was by email or Google, with a scrambled copy of your email address (a one-way SHA-256 hash, which can't be turned back into the address, but which Google, Meta, Reddit and X can match against the addresses of their own users); when you confirm your email address, that you did; when you add a fantasy league, that you did and which platform it's on; and when you buy a membership, the plan, the price and an order number. We don't give them your email address itself, your name, your league or team names, or anything else about your fantasy teams.

What we don't collect

  • No fingerprinting, and nothing about you from data brokers.
  • No precise location, contacts, photos, advertising IDs or hardware device identifiers.
  • No payment card numbers — our payment processor, Stripe, handles those and we never see them.

Cookies and browser storage

One cookie, named sg_session. It is set only when you sign in, holds a random token and nothing about you, is marked HttpOnly and Secure, and expires after 30 days or when you sign out. It is strictly necessary to keep you signed in.

The advertising and analytics tags above set their own cookies (Google's start with _ga and _gcl, Meta's with _fb, Reddit's with _rdt, X's _twclid), lasting up to two years. We set two small ones of our own for them: sg_evt, for up to ten minutes after you sign up or confirm your email address, to pass that on to the tags (with the scrambled email address described above, after a sign-up); and sg_optout, for a year, if you opt out. If you've opted out, Google's tags set none of their cookies, the Meta, Reddit and X Pixels don't run, and we pass nothing on.

When you arrive through a tagged link or from another website, the page saves a small note in your browser's own storage (not a cookie, and never sent to us with your visits): the campaign labels or the website's name, the page you landed on and the time. It is read only if you sign up, to fill in “What brought you here” above, and it is ignored after 30 days. Clearing your browser's site data removes it. Ad click ids that ad platforms add to links are only used to note that the click came from an ad — the id itself is never saved.

The installable app registers a service worker that caches the site's static files and an offline page so it opens without a connection. It never caches pages or API responses, so nothing of yours is stored on the device by it.

How we use what we collect

  • To sign you in and keep you signed in.
  • To show you your own leagues, rosters, advice and record.
  • To send account email: confirming your address and resetting your password. Payment receipts come from Stripe.
  • To send the alerts and emails you've turned on (the fantasy emails — waiver plan, trade ideas, start or sit — and the picks), each of which you can turn off at any time.
  • To keep the site up and secure, and to enforce rate limits and our terms.
  • To understand in aggregate which features get used, so we build the right things.
  • To measure our advertising and show our ads again to people who have visited.

We don't build an advertising profile of you ourselves (Google, Meta, Reddit and X may, from what their tags see, under their own policies), and we do not make automated decisions about you that have legal or similarly significant effects.

Who else sees it

We don't sell your email address or account data. Google, Meta, Reddit and X receive what their tags see (above), which is “sharing” under California law, and you can opt out of it. Beyond them, a small number of service providers process data on our behalf, under contract, only to provide their service:

  • OVHcloud. Hosts the site and its database on a dedicated server in Oregon, USA, rented to us alone. OVHcloud provides the machine and the network; we run everything on it ourselves.
  • Axcient. Keeps backup copies of that server, so the site and your account can be restored if the server fails.
  • Cloudflare. Sits in front of the site to serve it and absorb attacks, so it processes connection data including your IP address. Its Turnstile check on the signup form also looks at your browser to tell people from bots.
  • Anthropic. Writes the plain-English explanations of our picks, roster advice and waiver claims. When we ask about your team, we send the football side of it: the players on your roster and on the waiver wire, your league's name and scoring, and this week's opponent's team name and lineup. We never send your email address, your name or your account details.
  • Your fantasy platform. We read your leagues from the platform you choose, and send it only what it needs to find them: your username for Sleeper, the league id you enter for ESPN (plus your ESPN sign-in, if you connected it for a private league), and for Yahoo the access token you gave us when you connected; for CBS, your CBS sign-in and your league's address; for Fleaflicker and MyFantasyLeague, the league's number (and your MFL API key for a private one); for Reality Sports Online, your RSO sign-in. We send it nothing else about you.
  • DraftKings. Only on the DFS optimizer page: your browser loads that page's slates and salaries directly from DraftKings, so DraftKings receives that request, including your IP address, like any visit to its site. We send DraftKings nothing about you.
  • Google. Through its analytics and advertising tags, as described above. And if you sign in with Google, Google knows you used your Google account to sign in here.
  • Meta. Through the Meta Pixel, as described above.
  • Reddit. Through the Reddit Pixel, as described above.
  • X. Through the X Pixel, as described above.
  • Expo, Google and Apple (phone notifications). Only if you turn on notifications in our phone app: we send the notification and your phone's push token to Expo, which hands it to Google (Firebase Cloud Messaging) on Android or Apple on iPhone to deliver. Nothing else about you.
  • Our email provider. Receives your email address and the message in order to deliver it.
  • Our payment processor. Stripe receives what it needs to take payment for a membership — your email address, card and billing details — and tells us only that you paid, which plan, and until when.

We may also disclose information if the law requires it, to protect our rights or someone's safety, or in connection with a sale of the business — in which case we'd tell account holders first.

How long we keep it

  • Your account and its data: until you ask us to delete it.
  • The saved copy of a football league: until you remove the league or your account is deleted.
  • Saved AI answers and shared league report cards: until your account is deleted, even if you remove the league.
  • Records of how your league imports went: 90 days, deleted automatically.
  • Sessions: 30 days, or immediately when you sign out.
  • A phone's notification address: until you sign out of the app on that phone, remove the app or delete your account.
  • Security and rate-limit records: 24 hours, deleted automatically.
  • One-time links for confirming an address or resetting a password: short-lived, single-use, and only ever stored as a hash.
  • Encrypted backups: kept on a rolling schedule, so deleted data can persist in a backup for a short period before ageing out.

Your choices and rights

  • Turn off email. Every alert has an unsubscribe link that works without signing in, and you can switch alerts off on your account page.
  • Remove a league. Remove it on My Team; we delete the link and our saved copy of that league. Saved AI answers and any report card you shared stay until your account is deleted. Disconnecting a sign-in doesn't remove the league or its saved copy.
  • Disconnect Yahoo. Disconnect on My Team; we delete the stored tokens.
  • Get a copy, or a correction. Email [email protected] and we'll send you what we hold or fix what's wrong.
  • Delete your account. Email [email protected] and we'll delete your account and everything attached to it. There is no self-service delete button yet; until there is, we do it by hand, promptly.

We won't charge you, degrade the service, or treat you differently for exercising any of these.

If you live in California, you have the right to know what we collect, to delete it, to correct it, and to opt out of sale or sharing. We don't sell personal information for money; the advertising tags above are “sharing”, and you can opt out of them below. The lists above are our notice at collection.

Do Not Sell or Share My Personal Information. Opting out tells every tag on the site that you've said no, before any of them runs: Google's analytics and advertising tags set no cookies and send only anonymous pings with no identifiers, the Meta, Reddit and X Pixels don't run, and we don't pass on the scrambled email address or anything else. We also treat your browser's Global Privacy Control signal as an opt-out automatically. The choice is kept in the browser you make it on, not in your account, so repeat it on other browsers and devices.

Checking this browser's setting…

If you live in the EEA or the UK, our lawful bases are performing our contract with you (running your account), legitimate interests (keeping the site secure), and consent (optional email, which you can withdraw). You may also have the right to object, to restrict processing, to data portability, and to complain to your data protection authority. Our servers are in the United States, so using the site involves transferring your data there.

Children

StatGrades is not for children. You must be 18 or older to hold an account, and betting content is intended for adults of legal gambling age. We don't knowingly collect information from anyone under 13, and if we learn we have, we delete it. If you believe a child has created an account, write to [email protected].

How we protect it

Passwords are stored as scrypt hashes. Session tokens and one-time email links are stored only as SHA-256 hashes, so a stolen copy of our database couldn't be used to sign in as anyone. The site is served over HTTPS only, personalised responses are marked never to be cached, and backups are taken nightly. No system is perfectly secure, but if a breach ever affects your information we will tell you and the relevant regulators as the law requires.

Changes to this policy

If we change what we collect or who we share it with, we'll update the date at the top and, for anything material, email account holders. We won't apply a materially different use to information we already hold without telling you first.

Contact

Stat Grades Media LLC, a Wisconsin limited liability company — [email protected]. The agreement covering use of the site is in our Terms of Service.