The short version. ChipScan collects nothing. It makes zero network calls. It has no accounts, no logins, no analytics, no telemetry, no advertising, and no third-party trackers. Camera frames are processed on-device and discarded. Anything you save lives only on your phone, in the app's private sandbox. Delete the app and every byte associated with it is gone.
The rest of this page is a longer version of that paragraph, broken out the way app stores and regulators like to see it. There is no fine print waiting to contradict the summary above.
Data We Collect
None.
ChipScan is a native mobile app that runs entirely on your device. It does not require, request, or accept:
- An email address, name, phone number, or any other identifier
- An account, login, or user profile
- Payment information
- Location data (the app does not use GPS or any other location service)
- Contacts, photos library access (other than for files you explicitly pick), or any other personal data
You can use ChipScan without ever telling the app anything about yourself, because there is no field in which to tell it anything about yourself.
Camera Frames
ChipScan needs camera access to do what it does: look at chips and count them. Here is exactly what happens when you grant camera permission:
- Frames are streamed from the camera to the app's in-memory chip-detection pipeline.
- Each frame is analyzed for chip stacks, chip counts, and chip colors.
- The resulting numbers (counts, colors, totals) are displayed on screen and held briefly in memory.
- The raw frame is then discarded. It is not saved to disk, not uploaded anywhere, and not retained between frames.
By default ChipScan does not write camera images to disk. Each frame it captures for a scan is analysed in memory and discarded; only the resulting numbers — a count, a color, a value — are saved when you choose to save a session. Anything stored lives in the app's private sandbox on your device and is never transmitted.
If you turn on “Keep scans I correct”
There is one setting, off by default, that changes this. Counting chips from a photo is hard, and the app improves fastest from examples where it got the number wrong and you fixed it. If you switch that setting on, ChipScan keeps a small sample of scans on your phone:
- Only doubtful scans are kept — ones where you changed the count, where the two counting methods disagreed, or where confidence was low. A scan it got right and you accepted is not stored, because there is nothing to learn from it.
- What is kept is the cropped region inside the aim box — the chips themselves, not the rest of the room — along with the numbers involved and the count you accepted.
- It stays on your phone, in the app's private storage. It is still never uploaded; ChipScan makes no network calls whether this setting is on or off.
- Storage is capped at a few hundred samples, roughly 15 MB, with the oldest removed first.
- You can see how much is stored, export it, or delete all of it at any time in Settings. Deleting the app removes it too.
Sharing an export is entirely your choice and takes a deliberate action — ChipScan cannot send it anywhere on its own.
What's Stored On Your Device
ChipScan uses a local SQLite database in its private app sandbox to store:
- Color-to-denomination presets that you create
- Scan results that you explicitly save
- App settings (active preset, color tolerance, display preferences)
- Kept scan samples — only if you switched on “Keep scans I correct”, which is off by default
That data never leaves your device. It is not backed up to our servers (we don't have servers). It may be included in your phone's normal device backup (e.g., iCloud Backup on iOS or Google's Android backup) if you have that feature enabled in your phone's system settings — that's between you and your phone manufacturer, not us.
Network Activity
ChipScan makes zero network calls. The app does not connect to any server we operate, any analytics service, any crash-reporting service, any advertising network, or any third-party service of any kind.
You can verify this yourself with a network monitoring tool: install ChipScan, take a few scans, and watch the network — you will see no traffic from the app.
If we ever add an optional network-connected feature in the future (for example, an opt-in crash reporter to help diagnose problems), it will be:
- Off by default
- Explicitly opt-in via a setting
- Clearly documented on this page before the feature ships
Analytics, Telemetry, and Crash Reporting
ChipScan ships without any of these. There is no analytics SDK, no Firebase Analytics, no Google Analytics, no Mixpanel, no Amplitude, no Sentry, no Crashlytics, and no equivalent of any of those.
If the app crashes on your phone, your phone's operating system may log the crash in its standard developer logs, and you can choose to share that with the developer through your phone's normal "share crash data" mechanism. We never receive crash data automatically.
Third-Party Services
None. ChipScan does not embed any third-party SDKs that collect or transmit data. The chip-detection algorithm is fully implemented in the app's own code using standard mobile platform APIs (camera, image processing, SQLite). There is no third-party analytics, advertising, attribution, A/B testing, or feature-flagging service.
Advertising
ChipScan does not show ads, does not contain advertising SDKs, and does not share any data with advertising networks.
Cookies
ChipScan is a native mobile app, not a website. It does not use cookies because cookies do not exist in this context.
This marketing website (chipscan.app) similarly does not set any tracking cookies. It uses Google Fonts to load the Inter typeface; Google may log that font request the way any CDN logs a hit. We do not place an analytics cookie on this site.
Children's Privacy
ChipScan is not directed at children under the age of 13. Because ChipScan collects no personal information from anyone, it also collects no personal information from children. We do not knowingly market the app to children.
Your Rights
Because we hold no information about you, requests for access, correction, or deletion of "your data" are trivial: there is nothing to access, correct, or delete on our end.
To delete the data ChipScan stored on your device (presets, scan history, settings), do one of the following:
- Clear in-app: open ChipScan → Settings → Reset App Data, which wipes the local SQLite database.
- Delete the app: uninstalling ChipScan removes the entire app sandbox, including the database. Everything is gone.
See the Data Deletion page for full instructions.
International Users / GDPR / CCPA
ChipScan does not process personal data, so the obligations that arise under the GDPR, CCPA, and equivalent laws when a service processes personal data largely do not apply to us. We do not "sell" data (we have none to sell), do not "share" data with third parties for behavioral advertising, and do not transfer data internationally (we transfer no data, period).
If your local law gives you specific rights regarding data we hold, our answer is the same one we give everyone: we hold none.
Important Disclaimer
ChipScan is a counting tool, not a gambling product. The values it computes are best-effort estimates from computer vision and may be incorrect. Do not rely on ChipScan for real-money decisions without verifying the count yourself. ChipScan is not affiliated with any casino, card room, or gambling operator.
Changes to This Policy
If we ever change how the app handles data, we will update this page and update the "Last updated" date at the top. Because the current policy is "we collect nothing," any change in that direction will be a meaningful announcement — not a quiet rewording.
Contact
Questions about this policy? Get in touch:
Privacy: privacy@chipscan.app
Support: support@chipscan.app