Privacy Policy
Last updated November 5, 2026
This policy explains what personal data StackChase ("we", "us") collects when you use the Service, what we do with it, and your choices. StackChase is based in the United States and offers the Service only to people in the United States. You can reach us about privacy at the address at the bottom of this page. If you're outside the United States, please don't create an account; if you think we've collected your data from outside the United States, email us and we'll delete it.
We don't sell your personal data or use it for advertising, and we don't use advertising cookies or trackers. We count page visits with Umami, which sets no cookies.
1. What we collect
Information you give us:
- Account details: your email address, name, username and password. Passwords are handled by our authentication provider and we never see them in plain text. If you sign in with Google, we receive your name and email address from Google.
- Card photos you upload, front and back, and the corner and edge close-ups we make from them if you ask for them in an eBay export. Close-ups are stored with your other photos at a public web address so eBay can fetch them, and are deleted when you delete the card, make your Stack private, or after a week, whichever comes first.
- Card details you enter or confirm: player, year, set, card number, parallel, serial number, grade and certification number.
- If you import a collection from a spreadsheet: the contents of the file you choose or the text you paste, or of a Google Sheet whose link you give us, and the cards we make from it, including what you paid and any notes or other columns you kept. We read the sheet to make the cards and keep the cards and a note of what the sheet said about each one; we don't keep the file, and we don't keep the link.
- Collection records: when cards were added, and if you record them, sales (price, listing link, notes) and trades.
- SubStacks, if you use them: groups of cards you are working on, either a rainbow (one card in every colour of a parallel) or a list of cards you are after. A list saves, for each card, the catalog's description of it and the web address of its photo, and any note you write. Your rainbows can be shown on your Stack. Your lists, including the one called My Chases, are private unless you choose to show a list on your Stack. A list you show is visible to visitors, and may be found by search engines, with each card you don't own described in words and without the catalog's photo. You can make it private again at any time. Notes are never shown on your Stack or to visitors. If your Stack is private, so are all your SubStacks. They are deleted with your account. As with the rest of your account (section 4), a small number of StackChase administrators can see them.
- Messages you send us, including any copyright notice or counter-notice, which we may pass on to the other person involved.
- If you join our Discord server: what you post in its bug-reports, release-notes and feature-requests channels. Please don't post passwords or anyone's personal details there.
- If you use the optional feature that lists your cards on eBay (offered to some accounts): the connection to your eBay account, which is a token that lets us save and publish listings for you (kept encrypted), your eBay user ID and the date you connected; and a record of which of your cards we have sent to eBay, with their eBay listing numbers. We never see your eBay password.
Information collected automatically:
- Technical data: your IP address, browser type and the pages and API routes you request, recorded in server logs and used for security and rate limiting. When you create an account we also check, from the country Cloudflare reports for your connection, that you are in the United States; we log that country (and nothing more precise) and don't keep it with your account.
- Usage statistics, for every visitor: Umami, an open-source analytics tool we run on our own server, counts each page you visit. It records the page, the site that sent you there, your browser, operating system, device type, screen size and language, and your approximate location (country, region and city), worked out from your IP address. It also counts ten actions, as a name and nothing else (never which card, which username or what anything cost): that an account was made, that a first and a tenth card were added, that a card was approved and published, that a Stack was made public, that a sale was recorded, that a card was identified from its photo, that a file of eBay drafts was made, that a spreadsheet was imported, and that a card was added to one of your lists by searching the catalog. It sets no cookies, stores nothing on your device, doesn't keep your IP address, and isn't linked to your account.
- Sign-in data: when you signed up and last signed in, and when you confirmed your age and agreed to the Terms.
- On your device: your browser's local storage keeps your sign-in session and small preferences (for example, gallery layout and whether you've seen the welcome tour). None of these are advertising cookies, and we never use cookies to advertise to you.
2. Photo metadata, including location
Photos taken on a phone often contain hidden information (EXIF metadata), which can include the date, the device, and the GPS location where the photo was taken. We remove this metadata from every photo as soon as you upload it, before the photo is stored or sent to any of our service providers, so the location where you took it is never kept, shown or shared. Photos uploaded before we introduced this have been cleaned the same way.
The one thing we keep is the photo's colour profile, which tells a screen how to display its colours accurately. It contains nothing about you or where the photo was taken.
3. How we use it
We use what we collect for these purposes:
- To provide the Service: running your account, storing and showing your collection, identifying cards from photos, reading serial and certification numbers, and estimating values.
- To show your Stack to others according to the visibility you choose, which you can change at any time.
- To keep your SubStacks, and to show the ones you choose to show on your Stack.
- To keep the Service secure and working: preventing abuse, rate limiting, and investigating problems.
- To count visits and see which pages are used, so we can improve the site (Umami). We've limited it to what that needs: no cookies, nothing stored on your device, no link to your account, and nothing used for advertising. You can opt out at any time (see section 8).
- To contact you about your account, security or changes to our terms.
- To keep prohibited content off the Service: every photo you upload is checked automatically for whether it shows a trading card and for content our Terms don't allow, and a photo the check flags is looked at by a StackChase administrator. We do this to keep the Service safe and lawful, and to act on illegal content where the law requires us to.
- To handle bug reports and feature requests, and check our release notes: an automated assistant reads the bug-reports, release-notes and feature-requests channels of our Discord server, sorts the reports and requests, checks our release notes against what was released, and opens a summary of each bug in our issue tracker. It also puts a summary of each new feature request there (in a running tally, and in its own issue once it has been asked for repeatedly or turns out to be a large one). The summaries don't contain usernames. It also counts requests over time, to see what features members ask for; it only counts and sorts, and decides nothing. A count is not tied to a person: the numbers that replace usernames are different every time the assistant reads, so it cannot tell that the same person wrote on two different days, other than through anything the automatic changes described in section 5 miss.
- To comply with the law.
4. Who can see your collection
Public (the default): anyone can see your Stack, including photos, card details, values and your record of sold and traded cards, including sale prices. Public Stacks are listed in our sitemap for search engines, and our site explicitly allows AI systems to index them and use them for training. Cards on public Stacks also count towards our shared card pages, which list every parallel of a card and how many times each is held on StackChase. Those pages show counts only: not your username, your photos or your values.
Unlisted: anyone with the link or who knows your username can see the same information, but we don't list it anywhere and ask search engines not to index it. Usernames can be guessed, so unlisted is not the same as private.
New Stacks used to start Unlisted. When Public became the default, every Stack that was Unlisted at that time was made Public. You can change your Stack's visibility at any time in Account settings.
Private: other members and visitors can't see your Stack. One limitation: photos you add after making a Stack private are currently stored at a web address that is long and unguessable, but not access-controlled. Anyone who obtained that exact address could open the photo.
Whatever your setting, a small number of StackChase administrators can see all accounts' profile details, email addresses and collections, to run and support the Service.
5. Who we share it with
We use the following service providers to run the Service. They process your data on our behalf, only to provide their service to us:
- Supabase: authentication, database and photo storage.
- Railway: hosting for our servers, including server logs and our Umami analytics server. Umami is open-source software we run ourselves, so the usage statistics it collects aren't sent to anyone else.
- Cloudflare: sits in front of the site. Every request to stackchase.app passes through it, so it handles your IP address, the pages you request and your browser details, to deliver the site and protect it from attacks and abuse; if a connection to the site fails, your browser may also report the failure to Cloudflare. It also receives the emails you send to our contact address and forwards them to the mailbox we read. Cloudflare keeps its own records under its own privacy policy.
- Card Hedge: card identification and market pricing. Your photos, with their metadata already removed, are sent to Card Hedge when you upload a card or ask to re-identify one, card details are sent when we look up prices, and the words that describe each card you import from a spreadsheet (as the sheet gave them, for example the year, set, player and card number) are sent when we match the imported cards to its catalog. The words you type or confirm when you search its catalog, to add a card to one of your lists (a SubStack of cards you are after) or to find the right match for a card you are correcting, are sent when you search.
- Google Cloud Vision: image analysis. Every photo you upload, with its metadata already removed, is sent to Google Cloud Vision to check whether it shows a trading card and whether it contains prohibited content, and to read serial and certification numbers printed on it. If you use "Read the text on the card" or "Find this card" on a card that couldn't be identified, its photos are sent again so the words printed on them can be offered as suggestions for its details or its catalog search. The same is done, for the photos in your review queue and the cards missing a back, when you use "Match fronts and backs", so we can suggest which photo is the back of which card. Google processes the photo to return the result.
- eBay: only if you use the feature that lists your cards on eBay. When you save or publish a card, at your request, we send eBay that card's title, description, details, price, photos (including any corner and edge close-ups, which eBay fetches from a public web address) and weight, to your own eBay account. eBay handles it under its own terms and privacy notice, and we ask eBay for permission only to manage your inventory and read your selling policies and eBay user ID, not for anything about buying, messages or payments. You can disconnect at any time in the feature, or remove StackChase in your eBay account's permissions.
- Google: if you choose to sign in with Google. Google Sheets: only if you import by giving us the link to a Google Sheet. Our server then asks Google for that sheet once, on your behalf, to read it (the sheet has to be shared with anyone who has the link, and we only ever ask Google, at its own address). Google can see that the sheet was read, from our server's address and not yours. We don't keep the link.
- Anthropic: the AI model behind the assistant described in section 3. It receives the text of those three Discord channels, to read and summarise it, but only after these changes have been made automatically: usernames are replaced by numbers, and @mentions, email addresses, phone numbers and anything that looks like a password or key are taken out. Because that is automatic it can miss things, such as a name or detail written in the middle of a message, and anything it misses is received. Anthropic handles what it receives under its own terms and privacy policy.
- GitHub: our issue tracker, which holds our summaries of reported bugs and feature requests. They don't contain usernames.
- Discord: not one of our service providers, but a separate service that you use under Discord's own terms and privacy policy, which we don't control. The assistant reads only the bug-reports, release-notes and feature-requests channels of our server, never direct messages or any other channel, and it can't post or change anything there.
We may also disclose data if the law requires it, to protect the rights and safety of our users or the public, or as part of a merger or sale of the Service (in which case we'll tell you first). We don't share your data with anyone else.
6. Where your data is processed
We are based in the United States, and our service providers process data in the United States and possibly other countries.
7. How long we keep it
- Account data, photos and collection records: for as long as your account exists. When you delete a card, we delete its record and its photos straight away, whichever way your Stack is shared.
- When you delete your account, from Account settings, we delete your account, your collection and every photo at once, and your public Stack stops working immediately. If you'd rather ask us to do it, we'll do it within 30 days. Copies in backups are overwritten in the normal course, after which they're gone.
- The exception: if an account is suspended, or something on it is waiting on a review for illegal content, we may hold off deleting it until that is settled, and we keep what the law requires us to keep. In that case deletion goes through us rather than the button in Account settings.
- Copies that a visitor's browser or a web cache already holds, and what our identification providers received when a photo was identified, are outside our control; the providers keep it under their own policies.
- Server logs: kept for a limited period for security and troubleshooting, then deleted.
- Usage statistics (Umami): kept for as long as they're useful for seeing how the site is used. They aren't linked to your account.
- eBay connection: kept until you disconnect, delete your account, or eBay tells us you have deleted your eBay account (we then remove the connection and our record of your listings). Listings already live on eBay are on eBay and stay there until you end them there.
- SubStacks, and the notes in them: for as long as your account exists, or until you remove the SubStack or a card from it. A list you have shown stops being public as soon as you make it private, though a search engine may keep a copy for a while.
- Cached market pricing is about cards in general, not about you, and may be kept longer.
- Discord messages: we don't keep an archive of them; they stay in Discord until they are deleted there. The assistant's own working records, on the computer it runs on, can hold the text it read (changed as described in section 5) for up to about two months, and are then cleared. Our summaries of bugs and feature requests in the issue tracker stay while they are open, and are kept afterwards as a record of them. Our running count of requests stays as long as the issue that holds it does.
8. Your rights
You can see and correct your collection in the app, change your Stack's visibility, and download your collection as a spreadsheet from the Stack Portal.
If you live in a US state with a consumer privacy law, such as California, you may have rights to know, access, correct and delete your personal data, and not to be discriminated against for using them. We don't sell or share personal data for cross-context behavioural advertising.
To object to usage statistics, block the Umami script in your browser (most content blockers do). Because these statistics aren't linked to you, we can't look up or delete a particular person's page views; blocking the script stops any being collected.
You can delete your account yourself in Account settings; you'll be asked to sign in again and confirm, so no one else can do it from a session you left open. To use any other right, email us from the address on your account. We'll respond within one month, and may need to confirm it's really you first.
9. Security
We protect your data with measures including encrypted connections, database access controls, and restricted administrator access. No online service is completely secure, though, so please use a strong password that you don't use anywhere else.
10. Children
The Service isn't directed at children under 13, and we don't knowingly collect personal data from them. When you choose your Stack URL we ask you to confirm that you are at least 13. If you believe a child under 13 has created an account, contact us and we'll delete it.
11. Changes to this policy
We'll update this policy when the Service changes, and change the date at the top. If a change is significant, we'll tell you by email or in the app before it takes effect.
12. Contact
For privacy questions or to use your rights, email us at the address below.