RollbookPrivacy policy
In one paragraph
Rollbook keeps your trips in a database on your phone. There is no account and no Rollbook server, and the app shows no ads. Your trips, dates and countries are never sent to us. If you use daily check-ins (Rollbook Pro), the app reads your approximate location while you check in and turns it into a country on the phone; the location is never sent anywhere. The app does send anonymous usage statistics to Google Firebase, and it talks to Google Play, through RevenueCat, for the Rollbook Pro subscription. Android’s own backup can copy the app’s data into your Google account. This page lists exactly what that involves, who processes it, and how to delete it.
What stays on your device
- Your ledger. Each trip you add or that a check-in records: the country, a US state or Canadian province if there is one, the first and last day, and whether it is a planned trip. It is stored in a local database inside the app’s private storage.
- Your limits (Rollbook Pro): the country, the number of days, the period and the counting convention of each limit you set.
- Settings: your home country (the United Kingdom unless you change it), whether alerts and check-in reminders are on, the reminder hour, the day each alert was last shown (so it appears at most once a day), and a counter the app uses to decide when to ask for a Google Play review.
- Files you save. An exported ledger file, and a PDF or CSV report (Rollbook Pro), go where you choose to save them, or to the app you share them with. From then on they are yours, and Rollbook doesn’t read them again unless you import a ledger file.
Alerts and check-in reminders are worked out on the phone and shown as notifications by the phone; nothing about them is sent anywhere.
Location (daily check-ins, Rollbook Pro)
Rollbook asks for approximate location (Android’s ACCESS_COARSE_LOCATION) the first time you check in. It never asks for precise location and never for location in the background. It reads one approximate location fix only while you check in, from the check-in screen that you open, or that the daily reminder opens when you tap it.
The fix is turned into a country (and a US state or Canadian province) on the phone, using country borders from Natural Earth, a public-domain map built into the app. Rollbook then records the day in your ledger and discards the coordinates: they are not stored and never sent anywhere by Rollbook. Near a border the app asks you which country you are in instead of guessing. The location fix itself comes from your phone’s location service, which works according to your phone’s own location settings.
You can stop check-ins at any time by turning off the reminder in the app, or remove the permission in Settings → Apps → Rollbook → Permissions → Location. Free users never reach the check-in screen.
Your Google backup
Rollbook lets Android include its data in Android’s automatic backup, on purpose: a record of days can matter for years, and losing it when you change phones is the worst thing a day counter can do. If backup is turned on for your phone, Android copies the app’s private data, including your ledger, limits and settings, to your own Google account, and restores it when you set up a new phone from that backup. The backup is stored by Google under your account, under Google’s terms; Rollbook and its developer cannot see or read it.
To keep Rollbook’s data out of your Google backup, turn off backup of app data for your phone: on most phones it is in Settings → Google → Backup (on some, Settings → System → Backup). Android has no switch for one app alone, so this applies to every app on the phone. You can still move your trips yourself with Settings → Export the ledger in Rollbook. To remove a backup that already exists, manage your backups in your Google account (Google Drive → Backups, or your Google One storage).
What leaves your device
Rollbook uses Google Firebase Analytics to understand whether the app works and which features are used, and RevenueCat with Google Play Billing for the subscription. These send:
- Usage events that Rollbook logs: that a trip was added and whether it was planned; that a planned trip was checked, whether it fit and by how many days it went over; that the border statement or “How this was counted” was opened; the result of a check-in as a short code (for example “recorded”, “no fix” or “near a border”); that the ledger was exported, or imported and how many stays it held; that the purchase screen was shown or closed and from which feature; that a purchase completed or was restored, or a free trial started; that the review prompt was shown; and, if billing can’t start, a short reason such as “no Play Store”. Countries, dates, places and locations are never part of an event.
- Events Firebase records by itself, such as the first open, sessions and app updates, with the device model, Android version, app version, language and an approximate country derived from the network connection.
- An app instance identifier that Firebase uses to tell one installation from another. It is not linked to your name or email. The Advertising ID permission is removed from this app and the ID is not collected, and Firebase’s advertising-ID collection is switched off.
- Purchase and subscription status. Google Play handles the payment; RevenueCat receives the purchase receipt under an anonymous app user ID, so the app knows whether Rollbook Pro is active and you can restore it on another device. We never see your payment details.
The app also includes Firebase Remote Config and Firebase App Check (Play Integrity) through code shared by our apps. Rollbook does not use either today; if it starts to, Remote Config would download app settings using a Firebase installation identifier, and App Check would ask Google Play to confirm the app is genuine. Rollbook does not include a crash-reporting SDK. If you have allowed your phone to share usage and diagnostics with Google, Google Play may show us crash and performance statistics that do not identify you.
On Google’s own test devices (the Play pre-launch report), Rollbook turns analytics off so robots are not counted.
This data is used to fix faults and to decide what to improve. It is not sold, and it is not used for advertising.
Processors
- Google LLC — Firebase Analytics (and the unused Remote Config and App Check), Google Play Billing, Android backup, and the Google Play in-app review card (Firebase privacy, Google privacy policy). A review you write in that card goes to Google Play under your Google account; Rollbook never sees it.
- RevenueCat, Inc. — manages the subscription and its status (RevenueCat privacy policy).
- Cloudflare, Inc. — serves this website.
Deleting your data
This section applies to Rollbook: Schengen Calculator (dev.machado001.rollbook), published on Google Play by machado001.
Data on your device (your trips and planned trips, limits, settings, alert and review-prompt counters): delete a trip or a plan from its screen in the app, or remove everything at once in Settings → Apps → Rollbook → Storage → Clear storage, or by uninstalling the app. Ledger files and reports you saved or shared stay where you put them; delete them there.
Data in your Google backup (a copy of the same on-device data, if your phone’s backup is on): it is held in your own Google account, not by us. Turn off app-data backup as described above, and delete the backup from your Google account (Google Drive → Backups, or Google One storage).
Data held by our processors (usage events and app instance identifiers in Firebase Analytics; purchase records and the anonymous app user ID in RevenueCat): email machadowg@gmail.com with the subject “Rollbook data deletion”. Because the app has no account, it helps to say roughly when you used the app and on which device model. We delete the data we can associate with your request and confirm by reply within 30 days. Firebase Analytics data is also deleted automatically when the project’s retention period runs out. Purchase records that Google Play and RevenueCat must keep for tax, fraud-prevention and accounting reasons are kept as long as the law requires, then deleted. Cancelling Rollbook Pro is done in Google Play and does not by itself delete any data.
Children
Rollbook is a travel tool for adults and is not directed at children. It does not knowingly collect information from anyone under 13.
Your rights
Depending on where you live, you may have rights under the GDPR, the UK GDPR, the LGPD or the CCPA to access, correct, delete or export your data, and to complain to your data protection authority. Write to the address below and say which app you are writing about; requests are answered within 30 days.
Terms
Rollbook has no terms of service of its own. Your use of the app and your subscription are covered by the Google Play Terms of Service. Rollbook counts days from what you enter; it is not an official record and not legal or tax advice.
This website
This site runs no JavaScript (its content security policy forbids scripts entirely), sets no cookies and loads nothing from other sites: its fonts are served from this domain. Cloudflare, which serves it, sees each request and the IP address it came from, as any web host does.
Changes
If this policy changes, the date at the top changes with it, and earlier versions remain in the history of the repository this site is built from.