Privacy

Effective November 14, 2026.

The short version

StackScan works without an account. Your stack lives on your phone. If you sign in, a backup of it also goes to your account on the StackScan server, in the app on its own and on the website when you ask: Your account and Backups say what that keeps. If a vendor turns on Keep it up to date for an inventory link, the app also sends that link’s new snapshot to the StackScan server on its own, while the app is open. The server sees a card photo only long enough to identify it, unless you report a wrong match or confirm a right one. No ads, no outside analytics, no tracking, and nothing is sold. StackScan does keep its own record of how each scan came out, so it can tell how often a scan is wrong: How scans are measured says exactly what is in it, and what never is.

Scanning

When you scan, the app sends a photo of the card and the games you scan for (Settings, Games) to the StackScan server, which answers with the card and its price. The server also reads a barcode in the photo: a sealed product’s UPC, or a graded slab’s certificate code. With the 4K camera on, a strip from the card’s bottom edge goes along to read small collector numbers. Scan photos are not kept. The photo is sent only to identify the card: the server holds it in memory while it answers (a large photo in a temporary file that is deleted once the answer is sent), never saves it and never writes it to its log. How scans are measured says what is kept in its place.

How scans are measured

To tell how often a scan is wrong, the server keeps a short record of every scan’s answer. It holds: a random id the app makes for the photo, the time, the game you scanned for and the game the answer is in, how sure the scanner was, whether the scan was Auto-Scan’s, whether it turned out to be a graded slab or a sealed product (a yes or no each), whether the request came from the StackScan owner’s own devices (a yes or no), the cards the scanner suggested (up to eight, each with how closely its art matched the photo’s), the first 40 lines of text it read, each cut to 80 characters, how long each step took and how long the whole scan took on the server. When the 4K camera sent a strip from the card’s bottom edge, it also holds the strip’s size in pixels and which lines of text the strip’s own read added, cut the same way. When the scanner compared the card it named with that card’s ball pattern printing, it holds whether that check held the answer back from Sure, or would have, and how much closer the photo was to the plain card’s picture than to the pattern’s. For a graded slab, or a photo whose text reads like a slab’s label, it keeps none of the text, the strip’s included.

When you change a scanned card, undo that change, or delete a row, the app adds one line to the same record: the same random id, which of the three it was, the id of the card the row showed before and the one it shows after, how many milliseconds passed since the scan, which button did it, and whether the row was your phone’s own guess. It teaches the scanner nothing. Clear, a card added from a search and the server’s answer replacing your phone’s guess send no such line. A report you send carries the same random id, so it can be matched to its scan.

When the scanner reads no text on a photo and the app keeps your phone’s guess as the row for that reason, it adds a line of the same kind on its own: the same random id, the id of that card, the id of the server’s first card where it named another, how many milliseconds passed since the scan, and that the art kept it.

To tell how long a scan keeps you waiting, the app also adds a line on its own when a card’s answer lands as a row, at most one every 30 seconds: the same random id, how long the scan took on your phone in milliseconds (from the tap to the answer, from the tap to the upload starting, and from the upload starting to the answer), and whether the scan was Auto-Scan’s. Where your phone’s own match ran too, it adds how long that took, and which on-device model ran and where it ran (in the app itself, or on the web view’s GPU or WebAssembly). It names no card.

If your phone clears the app’s storage and the app brings your cards back from the copy it keeps on your phone, it adds one more line: a new random id, how many cards and deals came back, and whether your phone had agreed to keep the app’s storage. It names no card.

The record never holds the photo, your IP address, your device or browser type, an account, device or user id, the owner’s key, or a graded slab’s certificate number, grade or label. Apart from any text the photo itself showed, nothing in it carries a name, an account or a device, so nothing in it ties a scan to you.

Live scans on the front page

When the scanner is sure which card it is, or you confirm a card it suggested (This is right, or a report naming one of its suggestions), the server keeps that card and the minute it was scanned, the newest 50 scans, and shows them on getstackscan.com in the Live scans band and on the stats page, where they are also counted and totaled. For a graded slab it also keeps the grader and grade, such as PSA 10, and the slab’s Card Ladder value, but never its certificate number. Nothing else about the scan is kept with it: not the photo, your device or your address, so nothing ties it to you.

The same scans are also added up for the stats page’s All time view, and those totals are kept with no end date: for each day and game, how many cards were named, what they were worth and the minute of the first one; for each card, and for a graded slab its grade, how many times it was named, the minute it was last named, and the slab’s latest Card Ladder value. They are totals only, with nothing about who scanned or from where.

Graded slabs and sealed products

A slab’s certificate number, read from its label or barcode or typed in Add a slab, goes to the StackScan server, which looks it up with the grader and with Alt, and asks Card Ladder for the slab’s value. The server keeps those answers so the same certificate is not looked up twice. A slab row the grader’s records did not confirm is checked again on its own, about once a day and with each new version of the app: the app sends its grader, certificate number, the label’s text and the card’s name. In Repacker mode in the app, a slab in a bin with Backlog on has its value asked for again about once a day: the app sends its grader, certificate number and game. In any mode, the app also asks again on its own for the value of a slab the grader’s records confirmed whose value lookup failed or is waiting its turn: while the app is open, starting a couple of minutes after the scan, or at the time the server gave for a slab waiting its turn, and then at longer and longer gaps, up to a day, until a value comes or the lookup says there is none. It sends the same: grader, certificate number and game.

When a sealed product’s barcode is new to StackScan, you pick the product it belongs to. That pairing of barcode and product is kept and used for everyone’s scans: as a guess, shown at Unsure, until a second person picks the same product, and as that barcode’s product from then on. It holds nothing about you. Until a second person picks the same product, the server keeps in memory alone your IP address (on IPv6, the block of addresses it belongs to) and a random id your device makes once and keeps for these picks. The app sends that id with your picks and with nothing else, so your own second pick is not counted as someone else’s. Neither is ever written down or tied to your account, and both are dropped once the second pick comes, if not sooner. On a sealed product, This is right sends only your pick: no photo and no report.

Reports and confirmations

When you report a wrong match (swipe a row right, or Teach StackScan under Change), or press This is right on an unsure match, the app uploads that scan’s photo to the StackScan server with its details: the game, the text the scanner read (and, when the 4K camera sent a strip, which lines of it the strip added and the strip’s size), how sure it was, the cards it suggested, the card you picked, any note you wrote, when you scanned it, the scan’s random id (How scans are measured), and your app’s or browser’s user agent (the device type and system version). For a graded slab it also sends the grader, the grade, the certificate number and the slab’s Card Ladder value. Reports are kept on the StackScan server, where StackScan measures and tunes the scanner against them. Your report teaches the scanner nothing that anyone else’s scans read: only a report from the StackScan owner’s own devices can become a card’s reference picture or something the scanner learns from. The server takes a new report while it holds fewer than 3,000 and their files together, the new one’s included, stay within 1 GB, and turns new ones away past that rather than deleting older ones. The owner’s own reports are kept past that limit.

If the server is down when you send a report, the report and its photo wait in the app’s storage on your device and are sent once the server answers again.

Undoing This is right, or changing a row you confirmed, withdraws its report: the report itself stays, marked withdrawn. For a report from the owner’s devices, the reference picture it added is removed and the scanner stops learning from it.

Prices, sales and search

Price updates send the ids of the cards in your stack, and a condition’s price sends the card’s TCGplayer id. A card’s recent sales, a price from eBay’s listings and a slab’s comps send the card with its printing and condition, or the slab’s card, grader, grade and certificate number. A manual search sends the words you typed, importing a TCGplayer pull sheet sends its products’ names to find each card, and a TCGplayer export looks up the cards’ TCGplayer ids. To answer, the server asks TCGplayer, eBay, Card Ladder, Alt, Goldin, PriceCharting and the graders about that card or slab. None of these requests carries anything about you.

In Collector mode, to show how much of each set you own, the Collection tab sends the ids of the cards in your collection. The server counts them, answers, and keeps none of them.

The server’s request log records each request’s path, which for a search or a lookup includes its words or numbers, to keep the service running. For a scan it also records the first lines of text the scanner read, the card it picked and how long each step took; for a graded slab, its certificate number, or the label’s first lines when no certificate was found; a sealed product’s barcode that names no product; and each sealed pick’s barcode and product. It never records your IP address: the server blanks it out of every line it writes.

What stays on your device

Your stack and its photos, your settings, your Discord webhook and your custom export presets stay in the app’s storage on your device, with any report waiting to send. In Vendor mode so do your rates, the day’s deals and your inventory of binders and cases; in Collector mode, your collection; and with storage bins on, your bins and the TCGplayer orders you import, which keep no buyer’s name or address. Deleting the app, or clearing this site’s data in your browser, deletes them. In the iPhone app, a few small counts, of your exports, your scanned cards and the days you scanned on, are kept too, with when the app last asked for an App Store rating, so it can tell when to ask. They are not sent to StackScan, and they are left out of both copies below.

In the app, a copy of them with no photos, no owner’s key and no Discord webhook is also kept in a file in the app’s own folder, so the app can bring them back if your phone clears its storage. It goes into your phone’s own backup if you have those on, and deleting the app deletes it.

If you sign in, a backup of them is also kept with your account on the StackScan server, as Backups says, and deleting the app does not delete it. Your sign-in itself stays on your device: Your account says where.

Your account

Signing in is optional, and everything else in StackScan works the same without it. If you sign in, you do it in Settings in the app, or on the website’s account page: with your email address, with Sign in with Apple, or, where it is offered, with Sign in with Google.

With your email address, the StackScan server sends an email to it, through Resend, holding a six-digit code and, when you ask on the website, a sign-in link. Each works once, for 10 minutes. You can ask for a new code after a minute from the same network, and if one is sent it replaces the old one. Until then the server keeps your address beside them, the code only as a salted hash and the link, if there is one, only as a hash, and deletes them once one is used, when a new code replaces them, or, once they have expired, the next time it sends anyone a sign-in email. The address you prove is kept as your account’s. The server sends you no other email about your account.

With Sign in with Apple, Apple gives StackScan a stable id for you and an email address, which can be Apple’s private relay address. The server keeps that id, and the address only where Apple answers for it: an iCloud, me.com or mac.com address, or Apple’s private relay address. It also keeps Apple’s refresh token encrypted, one for each place you signed in, the app and the website. Deleting your account asks Apple to revoke each. The first time, Apple also hands the app your name, and the app sends it nowhere.

If you sign in with Google, the sign-in asks Google for your id and your email address, and nothing else. The server keeps Google’s stable id for you, and the address only where Google answers for it: a Gmail address, or one on the Google Workspace domain the sign-in names. It keeps no token of Google’s.

Each phone or browser you sign in on holds its own sign-in: in the app, in your phone’s secure storage, and on the website, in a cookie for getstackscan.com alone that the page’s scripts cannot read. The server keeps only a hash of each. A sign-in works for 180 days. Sign out deletes it, and deleting your account deletes all of them.

Only the account’s own requests take your sign-in to the StackScan server: who is signed in, your backups, signing out and deleting the account. Scans, reports, searches, barcode picks and everything else go without it, as they do when you are signed out, so signing in ties none of them to you.

To stop anyone guessing codes, the server counts the codes asked for and the wrong codes tried, by a hash of the address and by your network, in its memory alone. Each is held until newer visitors take its place or the server restarts. While a code is live it also remembers, in memory alone, which network asked for it and whether another network has asked for that address since, so that a new code is sent only to the network that asked, and only while no other has. That note is dropped when the code is used, when the account is deleted, or, once the code has expired, when anyone next asks for a code, and a restart drops it too. No address, code or sign-in is written to its log.

Backups

If you sign in, StackScan backs up what the app keeps on your device, so you can bring it back on another phone: your stack, your inventory with its binders, cases and bins, your deals with the money in them, your collection and how its value moved, the TCGplayer orders you imported, and your settings, among them your buying rates, your export presets and your eBay file’s details, such as your ZIP code. Each card goes with what its row holds: the card, its condition, its cost and label, the text the scanner read, and for a graded slab, its grader, grade and certificate number.

A backup never holds a photo, your Discord webhook, an inventory link’s secret, or a sign-in to eBay.

In the app, while you are signed in, a backup is made as you sign in to an account that has none, if your phone holds anything, about once a day when something has changed, and whenever you press Back up now. On the website, one is made only when you press Back up now. Each goes to the StackScan server, which keeps it encrypted with a key StackScan holds: the newest 5 of each account, fewer once they pass 60 MB together, always keeping the newest.

A backup comes back only when you choose it, on a device signed in to the same account. Signing out leaves your backups on the server, and so does deleting the app. Deleting your account deletes them from the server at once, and from its nightly copies as those are replaced (How long we keep it).

Exports

  • Download saves the file on your device. In the app it is Share, which hands the file to an app you choose.
  • Send to computer uploads the file to the StackScan server and gives you a ten-character code. Anyone with the code can download the file for 24 hours. After that the code stops working, and the file is deleted the next time anyone sends a file to a computer. An eBay file carries the ZIP code you entered in its details.
  • Discord passes the file through getstackscan.com to the Discord webhook you set. It is not stored.
  • Connect eBay, in the eBay file’s details, keeps an encrypted eBay sign-in on the StackScan server that can view your eBay account settings but change nothing, used only to list your business policies’ names. It stays until you disconnect, until eBay refuses it the next time it is used, or until the first Connect eBay sign-in after its 18 months are up. Deleting the app does not delete it.
  • Deleting your eBay account deletes that sign-in too. When you connect, StackScan reads your eBay user id once and keeps a SHA-256 hash of it with the sign-in, not the id itself, so when eBay tells StackScan your eBay account was deleted, the server finds the sign-in and deletes it. The hash is unsalted, so anyone who already knows your eBay user id could match it.

Inventory links

In Vendor mode, a vendor can share their inventory of binders and display cases as a link. Sharing uploads a snapshot of it to the StackScan server: each binder’s and case’s name, and each card’s name, set, number, finish, condition or grade, and the price the vendor asks. It holds no buying rates, no market values and none of the vendor’s photos. Anyone with the link can open it. With Keep it up to date turned on for a link (it is off until the vendor turns it on), the app sends a new snapshot by itself when the inventory or its asking prices change, while the app is open, and turning the switch off or taking the link down stops it. Unlike an export, a link does not expire: it stays until the vendor takes it down or updates it, and taking it down deletes the snapshot. The one exception is a server that holds as many links as it can keep: a new link then takes the place of the link whose snapshot was written longest ago, if that was over half a year ago. Only the device that made the link can take it down, so deleting the app leaves the link up. Search engines are asked not to list these pages.

How long we keep it

  • Scan photos: not kept. Each is held only while its scan is answered.
  • Your account, if you sign in: until you delete it, which deletes its email address, any id a sign-in service gave for you, every sign-in and every backup at once, and asks Apple to revoke its tokens.
  • Sign-in codes: a code, and its link when there is one, work once, for 10 minutes. The address they went to is kept with them until one is used, a new code replaces them, or, once they have expired, until the server next sends anyone a sign-in email.
  • Sign-ins: each works for 180 days from signing in. Sign out deletes it, and so does deleting the account.
  • Backups: the newest 5 of an account, fewer past 60 MB, until the account is deleted. Signing out and deleting the app keep them.
  • The request log: kept until its file passes 100 MB, when the oldest lines are removed and the newest 50 MB stay. Its lines hold no IP address.
  • Live scans: the newest 50. The all-time totals are kept with no end date.
  • The scan record: kept in a file that holds 64 MB at most. When the next line would pass that, the file becomes the older one and replaces the older file before it, so the record is always the newest scans and what was done to them, in two files of 64 MB at most, with no other end date.
  • Reports: kept with no end date. Once the server holds 3,000, or their files would pass 1 GB, new ones are turned away and wait on your device; older ones are not deleted to make room. The owner’s own reports are kept past that.
  • Reference pictures: only a report from the owner’s devices becomes one. A report’s photo kept as a card’s reference picture is not deleted with the report. It stays until a newer report’s photo for the same card replaces it, or until its report is withdrawn. Once that game’s reference pictures pass 2 GB, no new one is kept.
  • What the scanner learned: only from the owner’s reports, the scanner keeps a list of numbers that describes each photo (not the photo itself) with the card it shows. It is not deleted with the report: it stays until the report is withdrawn.
  • Graded slab lookups and sealed barcode pairings: kept with no end date.
  • A slab waiting for its value: while a slab’s value lookup waits its turn (Card Ladder limits how often it can be asked), the server holds the slab’s grader, certificate number and the grader’s records of it in memory alone, with no address or account attached: at most 25 slabs at a time, each for at most ten minutes. A restart clears it.
  • Send to computer files: 24 hours to download, then deleted the next time anyone sends a file to a computer.
  • Inventory links: until the vendor takes the link down, or, only when the server holds as many links as it can keep, until a new link needs its place and it has gone over half a year with no new snapshot.
  • eBay sign-ins: until you disconnect, until eBay refuses the sign-in the next time it is used or tells StackScan your eBay account was deleted, or until the first Connect eBay sign-in after its 18 months are up.
  • IP addresses: held only in the server’s memory, and never written down. To share the service fairly between users and to stop anyone guessing sign-in codes, each is held until newer visitors take its place or the server restarts. Beside a barcode pick, it is held until a second person picks the same product, 5,000 newer picks wait, or the server restarts.
  • Testers’ email addresses: until the tester asks to stop.
  • Nightly copies: each night, for safekeeping, the server copies its database, accounts included, the reports, what the scanner learned, the scan record, the live scans, sent files, inventory links and backups to computers StackScan operates. The newest 14 nights’ copies are kept and older ones are deleted as new ones come, so something deleted on the server stays in a copy until 14 newer nights have replaced it.

Deleting your data or withdrawing consent

Most of what StackScan keeps carries no name, account or device, so it is not tied to you. What is, you can delete yourself:

  • Your account, if you signed in: Delete account, in Settings in the app or on the website’s account page, asks once more, then ends every sign-in, deletes your backups, asks Apple to revoke its tokens and deletes the account with its email address. The nightly copies follow as they are replaced.
  • On your device: delete the app, or clear this site’s data in your browser.
  • A confirmation: undo This is right, or change the row you confirmed, to withdraw its report: the report and its photo stay, marked withdrawn. A live scan the confirmation added stays too.
  • Connect eBay: Disconnect, in the eBay file’s details, deletes the sign-in from the StackScan server at once. It does not remove StackScan’s access on eBay’s side; remove it in your eBay account’s settings too. Without the app, remove it there: the sign-in StackScan keeps then stops working, and is deleted at the first Connect eBay sign-in after its 18 months are up.
  • An inventory link: Take the link down, in the Inventory tab’s Share, deletes its snapshot.

For anything else, or if you no longer have the app, email support@getstackscan.com. We can find and delete an inventory link from its address and a graded slab’s lookup from its certificate number. We cannot find your reports, your lines in the request log, your live scans or your lines in the scan record: they carry no name, account or device, so we cannot tell which are yours. If you tell us the card and about when you sent a report, we will look for it and delete it if we can tell it is yours.

Service providers

The website runs on Vercel, and every request the app sends to StackScan passes through it too: getstackscan.com forwards scans, reports, sign-ins and everything else to the StackScan server. The StackScan server runs on a computer StackScan operates itself, reached through Cloudflare’s tunnel. Vercel and Cloudflare carry each request whole, its photo, sign-in or backup included, and see network data such as IP addresses to deliver it. StackScan uses them only to deliver its own requests, and shares data only with providers that give it the same or equal protection as this policy.

If you sign in with your email address, Resend, an email service, gets your address and the sign-in email to deliver it. If you use Sign in with Apple, Apple signs you in and tells StackScan the id and email address above, and StackScan asks Apple to revoke its tokens when you delete your account.

When you ask for a code on the website, the page first runs Cloudflare Turnstile, a check that a person is asking. Cloudflare’s script loads from challenges.cloudflare.com when the email form shows, and Cloudflare gets details of your browser and your network address to decide, and hands the page a one-time token. The StackScan server sends that token to Cloudflare to confirm it, and does not keep it. The apps do not run it.

If you test an early version of the app by email, StackScan keeps your address in a list on its own computer and emails you each new version through Resend, which gets your address to deliver it. Reply to ask to stop, or use the email’s unsubscribe link, and your address comes off the list.

If you sign in with Google, Google signs you in and tells StackScan the id and email address above, and StackScan sends Google nothing else about you.

On the website, Auto-Scan loads open-source code (OpenCV) from jsDelivr, a public file host; the app uses its own built-in copy. Some card pictures load straight from the card databases’ own image hosts, such as pokemontcg.io and TCGplayer’s. These hosts see your device’s request as any website’s file host would, and get nothing else from StackScan.

The iPhone app asks Apple which version of StackScan is on the App Store, at most once a day, to tell you when an update is available. That request names the app and nothing about you, and Apple sees it as it sees any request from your device.

Children

StackScan is not directed at children under 13 and does not knowingly collect their information.

Changes

If this policy changes, the new version is posted here with a new effective date.

Contact

Questions about privacy: support@getstackscan.com

Download on the App Store