The short version: your gambling diary is stored on your own device. There is no account, and we do not receive, store or see your sessions. The app contacts Google only when you ask it to look up casinos near you; during the private test it also checks your invite code with stampchip.com, without sending any diary data. If you make a backup, you hold the file and the key. The website keeps no analytics.
1. What the app stores, and where
Everything you enter — sessions, buy-ins, cash-outs, W-2G details, companions, notes, the venue, your check-in locations and their hashes, your tax-rate settings and an optional Google Places API key of your own — is stored in the app's own storage on your device (the browser's IndexedDB and local storage). It is not transmitted to BFVZ. We have no server that holds user data and no way to read what is on your device.
Uninstalling the app, or clearing the app's site data, deletes the diary from the device. A backup you made earlier is not affected.
2. Location
Location is used only when you tap Use my location or Check in. The fix (latitude, longitude, accuracy, time) is saved with that session on your device and is shown in the diary and the exports. The app does not track you in the background and does not request location at any other time.
3. Google Places
When you tap Use my location in a build that includes venue lookup, the app sends your coordinates to Google's Places API to list nearby casinos. That request goes from your device to Google under Google's privacy policy; BFVZ does not see it. Google may associate the request with BFVZ's API key and with your device's IP address. You can skip the lookup and type the venue instead; the built-in casino list works entirely on the device without any request.
4. Backups
A backup is a single file encrypted on your device with a key derived from a passphrase you choose and from a recovery code generated on the device. You decide where the file goes (your cloud drive, your email, your computer) through your phone's share sheet or a download; the file is not sent to BFVZ. Neither the passphrase nor the recovery code leaves the device, and we cannot open a backup or reset either secret. The file format is published so you can open it with other tools.
5. Purchases
The Preparer Pack will be sold inside the app through Google Play Billing. Google processes the payment and holds your payment details under its own terms and privacy policy. BFVZ receives a purchase confirmation from Google (an order identifier and the product bought), not your card details. The report itself is produced on your device from your own diary.
6. The website, the private test and tester feedback
stampchip.com is served by Cloudflare, which processes visitors' IP addresses and request details to deliver the site and protect it from abuse, under Cloudflare's privacy policy. The site runs no analytics scripts and sets no cookies.
If you ask for a test invite, we keep what you submit (your Google account email, and if you give them, your name, phone type and model, how often you play, your state and your note), the time of the request, the country it came from and your browser's user-agent string. It is emailed to us and stored with Cloudflare so we can add you to the Google Play test list, send the invite and follow up about testing. We do not use it for anything else and do not share it, and we delete it when the test ends or when you ask, whichever comes first.
If you send feedback through the site, we keep the note and the details you attach to it (your email, the app version, your phone, and what happened), the time and country of the request and your browser's user-agent string, the same way. We use it to fix and improve StampChip and to reply to you. If you tick the box allowing it, we may quote the note without your name or email when describing the test, for example to Google Play. Feedback you send through the Play Store instead is handled by Google under its own policy and shown to us in Google Play Console.
Test builds ask for an invite code the first time they open. The app sends the code, a random identifier it generates for that device, and the app version to stampchip.com, and repeats the check about once a week while you use the app; nothing from your diary is sent. We keep, with each code, the name and email we issued it to, the device identifiers, the times of the checks and the country they came from, so that a code works on at most two devices and can be withdrawn. Leave the test in the app's settings removes the identifier from the device; we delete the record when the test ends or when you ask. Public releases will not ask for a code.
7. What we do not do
- No accounts, no sign-in, no profiles. Test builds ask for an invite code, described in section 6.
- No analytics, advertising or tracking SDKs in the app or on the site.
- No selling, renting or sharing of personal information. We have none to share beyond the test sign-ups and feedback described above.
- No copy of your diary anywhere but your own devices and your own backups.
8. Children
StampChip is for adults who are legally allowed to gamble. It is not directed at anyone under 18, and we do not knowingly collect information from them.
9. Your choices and rights
Because your diary is on your device, you control it directly: edit, void, delete, back up and restore are all in the app, with no request to us needed. For test sign-up and feedback details, write to hello@stampchip.com to see, correct or delete what we hold. Where state privacy laws give you additional rights, we honor them on request.
10. Changes
If this policy changes, the new version is posted here with a new effective date, and a material change is noted in the app's release notes. Continued use after a change means you accept it.
11. Contact
BFVZ LLC, Oregon, United States · hello@stampchip.com