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
Receipts, notes, sources, prices already fetched and settings live in a local database and local files on the phone. The server stores no receipts and no personal data. "Erase the whole ledger" in Settings removes everything on the device.
02What can leave the phone
| Call | Condition | Content |
|---|---|---|
| Co-sign request | When a receipt is sealed and a server is configured | The 64-character hash of the receipt. The server keeps the hash and the time it first saw it. The receipt's asset, prices, source and note are not sent. |
| Price requests | When the app scores a call and a server is configured | The asset and the dates asked for (from, to). They are asked of your server, which may ask the price provider. |
| Config request | Only if you build with API_BASE_URL | Platform and app version in the query. No receipt data, no user id. |
| Usage ping | Only if the user switches on 'Share anonymous usage counts' (off by default) | A random install id, platform, app version, Pro or not (once a day). 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 app contains no advertising or analytics package. Without a server nothing leaves the phone except store purchases.
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 receipts are stored on the device, and describe the co-sign hash, the price requests, the opt-in ping and purchases if you use them. The iOS project includes a privacy manifest (ios/Runner/PrivacyInfo.xcprivacy): it declares no tracking, no tracking domains, one collected data type (product interaction, for analytics, not linked to the user, not used for tracking: this is the opt-in count) and one required-reason API (user defaults, reason CA92.1). Check it against your own build.