Receipts · Last updated October 26, 2026

Privacy Policy

This explains what Receipts collects, why, and what you can do about it. We collect as little as the game needs to work. We don't sell your data or show ads, and we don't use it to train AI models.

What we collect

• Account email, if you sign in. Used to send your sign-in links and to recognize your account. Nothing else is required to make an account. If you play in a pool, we also email you when a round opens, before a pick deadline if you haven't picked, and when results are in. Every one of those emails has a one-click unsubscribe, and you can turn them off, mute a pool, or set quiet hours on your account page.
• Phone notifications, if you turn them on for a device: the address your browser gives us to reach that device, the keys that encrypt messages to it, a short name for it from your browser's details (like "iPhone Safari"), when you turned it on, and when it last worked. You get your pool notifications there instead of by email. Remove a device on your email settings page, or turn notifications off in your phone's settings.
• What you enter in pools: pool names, questions and options, your display name, your picks, and scores.
• Recovery codes we generate so a player without an account can get back into a pool.
• Assistant connections, if you make one: the name you give it (or, for one you approve by signing in, the name the app gives itself and where it sends access), what it's allowed to do, when it was made, last used and expires, and which of your picks and host actions it made. We store only a scrambled form (a hash) of the token itself, and of any access token an approved app is given. More under "AI assistants" below.
• A Yahoo connection, only if you connect one so a pool can be made from your Yahoo Fantasy league: a token Yahoo gives us to read your leagues, stored encrypted and used only to read a league's matchups and final scores. We never write anything to Yahoo, and we don't keep your Yahoo name or the leagues you didn't pick. Disconnect any time on your account page and the token is deleted. From a league you pick we keep its id, its season, and the week imported.
• An email address for your player code, if you play without an account and ask us to email you your code. We use it to send that one email and don't save it.
• "Notify me" sign-ups for paid (Baller) accounts: which account asked, which limit they'd hit, and when.
• IP addresses, used briefly to limit abuse (for example, how many pools or sign-in links are requested). Rate-limit records are cleared within about a day.
• Server logs kept by our hosting provider, Cloudflare, to run and debug the service: details of each request (like which page or address was asked for, when, and whether it worked) and any errors. They're kept for a few days.
• Error reports, when something breaks on our side: what went wrong, where in our code, and which part of the site it was (like "a host page", never the link itself). No IP addresses, cookies, email addresses or anything you typed.
• Page view counts on our public pages (the home page, these policies, the templates and the help pages), never on pool, host or account pages: which page, the site that linked to it, your browser and type of device, your country and how fast the page loaded. No cookies, and nothing that identifies you.

Cookies

We use four cookies, all needed for the service to work, and no tracking or advertising cookies:

• ep_guest: remembers which player you are in a pool, for 7 days.
• igr_user: keeps you signed in to your account, for 90 days.
• igr_known: remembers that this browser has signed in to your account before, for a year, so you can still get a sign-in link if someone else floods your address with requests.
• __Host-oauth-consent-…: set only while you're approving an assistant's connection, for 10 minutes, so that approval can only come from the browser that opened it.

While you connect a Yahoo account, two more short-lived cookies (igr_yahoo_state and igr_yahoo_next) keep that approval to the browser that started it and remember where to send you after; they expire within minutes.

If you tap "Not now" on the offer to add Receipts to your phone, your browser remembers that in its own storage, so the offer doesn't come back. It never leaves your device.

Who else handles your data

• Cloudflare hosts the service, stores its data on its network (our main database is in North America), and sends our emails. If sign-in links are asked for an address, or from a network, several times within an hour, the sign-in page also shows Cloudflare Turnstile, a check that runs in your browser to tell people from automated scripts. Cloudflare processes only what it needs for that check, such as your IP address and details of your browser, as described in its Turnstile Privacy Addendum. We only get back whether the check passed. Cloudflare Web Analytics counts the page views on our public pages, without cookies.
• Yahoo, if you connect a Yahoo account: you sign in on Yahoo's own page, and we read your league and its matchups from Yahoo. Fantasy data provided by Yahoo Fantasy. Yahoo's own privacy policy covers what it holds.
• Your browser's push service (Apple, Google, Mozilla or Microsoft, depending on your browser), if you turn on phone notifications: it delivers them to your device. Each one is encrypted so only your device can read it; the service sees when one is sent, and to which device.
• Sentry receives our error reports, as described under "What we collect", so we can find and fix what broke. They're stored in the United States.
• The AI assistant you connect, if you connect one. What it reads from your account (see "AI assistants") goes to the company that runs it, and their privacy policy covers what happens to it after that. It gets only what you allowed the connection to read.

We don't sell or share your personal information with anyone else, except if the law requires it.

Who can see what

Everyone in a pool can see its questions, the display names of its players, and the standings. A pool's results link is public: anyone it's shared with can see the called results, the display names of the players who called each one, and the standings, but not how anyone picked a question that hasn't been called yet. The host can see the player list and manage it: whoever holds the host link, or, for a pool saved to an account, that account and any admins its host makes. Your account email is never shown to other players or hosts.

AI assistants

If you connect an AI assistant (like Claude) to your account, here's what changes.

• What we get from it: only what it sends us to do what you asked: a pool code, your picks, a pool's name or questions, a display name, a date or a setting. The same things you'd type on the website.
• What we don't get: your conversation with the assistant. We never see your messages, its replies, or anything else in the chat. We only see the requests it makes to us.
• What it can see: what you allowed when you connected it. With Read, that's your account email, your pools, their questions, standings and host actions, the display names of the players in them, and your own picks. It never sees anyone else's picks or anyone else's email.
• What we keep about the connection: the details under "Assistant connections" above. Host actions it makes are marked AGENT-ASSISTED for everyone in the pool.
• Disconnecting: you can see and disconnect every connection on your account page. A disconnected assistant is cut off at its very next request.

How long we keep it

Pools started without an account become read-only after 3 months, and we may not keep them more than a year after that. Pools and data on an account have no set deletion date today. Sign-in links expire after an hour, guest sessions after 7 days, and account sessions after 90 days.

A personal access token lasts as long as you chose when you made it. An assistant you approved by signing in gets access for an hour at a time, renewed while it's in use, and its connection ends on its own after 90 days unused. A disconnected or expired connection stops working, but we keep its record (its name and dates) until your account is deleted, and the picks and host actions it made keep pointing to it.

Your choices

You can leave a pool from your account page, and hosts can remove players. To get a copy of your data or have your account and its data deleted, email hello@ivegotreceipts.com from the address on your account. We'll handle it by hand while the service is in alpha.

When we delete your account, we end the pools you ran (they stay up, read-only, for the other players), show you as "Deleted user" in pools you played in, and delete your account, sign-ins and assistant connections. Your picks stay in those pools, because they're part of the other players' game too. We keep a short internal note that the deletion happened, including the email address it was for, so we can show we did it.

Children

The service isn't meant for children under 13, and we don't knowingly collect their information. If you think a child under 13 has given us information, email us and we'll delete it.

Changes

We'll update this page as the service changes, and change the date at the top when we do.

Questions: hello@ivegotreceipts.com