Privacy
what stays on the phone.
Use this page to fill in your own privacy policy and the store data-safety forms. It describes what the code does; you remain responsible for your policy.
01Stays on the phone
The price book, saved prices, targets, settings and the Pro state live in a local database and local files on the phone. Nothing about prices or products is sent to the server. Text and barcode reading run on the device. "Delete all saved data" in Settings removes the book.
02What can leave the phone
| Call | Condition | Content |
|---|---|---|
| Shop pages | When the user opens a page in the in-app browser | A normal web visit to that shop, like any browser. The app never loads shop pages in the background. |
| Config request | Only if you build with API_BASE_URL | Platform and app version in the query. No price data, no user id. |
| Usage ping | Only if the user switches on "Anonymous usage count" (off by default) | A random install id, platform, app version, Pro or not. The server keeps these and the time last seen; installs unseen for 400 days are deleted. |
| Purchase check | Only if you switch on verification | Product id and store receipt or token. The server stores only the revenue event (store transaction id, price, time), not an install id. |
| Store purchase | When the user buys | Handled by Apple and Google, not by your server. |
The server stores no personal data. The app contains no advertising or analytics package. The on-device text and barcode reading uses Google ML Kit, which runs locally.
Publish a privacy policy and put its address in brand.dart or the console (Legal). In the App Store privacy details and the Play data safety form, say that the price book is stored on the device, and describe the opt-in ping and purchases if you use them. The iOS project includes a privacy manifest (ios/Runner/PrivacyInfo.xcprivacy): check it against your own build.