RideBook Privacy Policy

Last updated: October 19, 2026 (version 2.0)

RideBook (package app.web.fueldiary) is an offline fuel, mileage, service and running-cost log for motorbikes, scooters and cars, for phone and tablet. Everything is calculated and stored on your device. This policy explains what the app does with your information. In short: we don't collect it.

What we collect

Nothing. RideBook has no account, no server, no analytics, no advertising SDK and no crash reporting. The app has no internet permission, so Android does not let it send anything anywhere. We, the developers, never receive your data. Nothing is shared or sold.

No location

RideBook does not request any location permission (precise, approximate or background) and does not track your rides. Distances come only from the odometer or trip readings you type in. The trip log (version 1.1) records only the start and end odometer, times, purpose and client you type; it uses no GPS.

What stays on your device

Everything you enter is stored only in the app's private storage on your device:

• your vehicles (type, name, optional plate, make and model, units, currency, odometer settings);
• fill-ups and charges (date, odometer or trip distance, volume, price, total, fuel grade, station, notes);
• services, service types, intervals and reminders;
• documents such as insurance, registration, road tax or inspection, with their dates and an optional document number

(hidden on screen by default);

• other expenses and, if you turn on rider mode, income entries (amount, platform, optional trips, hours and distance);
• trips (start and end odometer or a distance, times, a purpose such as Work or Personal, an optional client or place,

notes), tyre sets with pressure and tread checks, a monthly fuel budget, and the last price paid at each station (worked out from your own fill-ups);

• receipt photos you choose to attach to an entry (version 1.1). They are taken by your own camera app or picked by

you from your images, then reduced to a small JPEG (at most 1280 pixels) and stored in the app's private storage. RideBook does not request the camera or photo-library permission and never sees your other photos;

• drivers you add (version 1.2): a first name or nickname and a colour for each person who drives your vehicles, and

which driver each fill-up, service, expense or trip was;

• for sharing (version 1.2): a random identifier per entry, a record of entries you deleted (so a merge on another phone

can remove them too) and a list of the shared vehicles you imported;

• version 1.3: fixed costs you set up (a name such as insurance or road tax, an amount, how often and from when; RideBook

adds them as expenses on their due days), quick odometer readings without a fill-up, an optional fleet group per vehicle, the battery source of an electric vehicle (own, rented or swapped, with an optional monthly distance allowance), and on fill-ups an optional discount, battery swaps with the number of packs, the charge level before and after charging, the range the vehicle showed, and a plug-in hybrid's electric distance; shop names worked out from your services;

• version 2.0: a vehicle's purchase and sale (date, price, odometer) for its total cost of ownership; **riding

conditions you tick on a fill-up (such as city, highway or pillion, and names you add); storage periods with an optional note; spare-can fill-ups (fuel bought into a can and poured later); engine hours on services, odometer readings and reminders; a parts stock** (part names, units, quantities and what was bought or used, including the parts a service used); and the numbers you type into "Compare with electric";

• your settings, and daily local snapshots (the last 7) inside the app's private storage.

More › Privacy & data shows what is stored and lets you delete it.

Exports and backups

Nothing leaves the app unless you create a file yourself:

• Encrypted backup: "Back up now" writes a .ridebookbackup file to a location you choose with the system file

picker. With a passphrase of your own, the file is encrypted (AES-GCM); without the passphrase it cannot be restored.

• Receipt photos in backups: photos are left out of backups unless you turn on "Include photos in backups" in

More › Privacy & data. Daily snapshots and the JSON export never contain the images (the JSON export lists only which entries have photos).

• CSV and JSON exports, and PDF reports: created only when you tap Export, Create PDF or Share, and saved only to the

location or app you choose.

• Sharing a vehicle with another phone (version 1.2): "Share this vehicle" writes a .ridebookshare file with that

vehicle's entries, documents (including any document number you typed), tyres, reminders and the names of the drivers on its entries. It is always encrypted with a passphrase you choose, and goes only to the app or place you pick (for example a messaging app or Bluetooth). Receipt photos are never included. On the other phone, RideBook reads the file only after the passphrase is entered and shows a preview first; a snapshot is taken before anything is merged.

• Service history PDF (version 1.2): made only when you tap Create PDF. It lists the services, the documents' validity

with their numbers hidden, the average consumption and a QR code with a short text summary; the plate number appears only if you switch it on.

• Calendar file (version 1.2): "Export to calendar" writes an .ics file with service and document due dates. RideBook

does not request calendar access; your calendar app imports the file if you open it there.

• Fleet export and new CSV files (version 1.3): "Export all as CSV zip" in the Fleet table writes a zip with a summary

per vehicle, each vehicle's entries, your fixed costs and odometer readings, saved only where you choose. A shared vehicle file now also carries that vehicle's fixed costs and odometer readings.

• Version 2.0 exports: the CSV zip adds vehicles.csv (with purchase and sale prices), storage.csv and parts.csv, and the

fill-up file lists riding conditions and spare-can rows. A shared vehicle file also carries storage periods, riding conditions and spare-can rows; purchase and sale prices are left out of a shared vehicle file unless you switch on "Include purchase and sale prices" when you make it. Importing a Fuelio or Drivvo export only reads the file you pick.

• On Android 4.3, which has no system file picker, exports and backups are saved to the Download folder.
• Once a file is written, it is under your control. If another app on your device (for example a cloud drive) syncs

that location, that app's own policy applies.

• Import: a CSV, JSON or backup file you pick is read only to bring its entries into the app, after a preview.

Android device backup

Android's own device backup (Auto Backup) of RideBook's data is off by default. It is included in your device backup only if you turn on "Android backup" in More › Privacy & data; Google then handles that backup under its own policy. The PIN lock file is never included. Receipt photos are left out of cloud backups; they move only with a direct phone-to-phone transfer.

Notifications and widgets

Service and document reminders and the home-screen widgets show the vehicle name and the item that is due (for example "Oil change due" or "Insurance expires in 7 days"). They are created on the device; nothing is sent anywhere.

Permissions

• Notifications (POST_NOTIFICATIONS, Android 13+): service and document reminders. Asked only when you turn on your

first reminder.

• Run at startup (RECEIVE_BOOT_COMPLETED): sets the daily reminder check again after the phone restarts.
• Vibration (VIBRATE): a short vibration when you save an entry.
• Fingerprint or face (USE_BIOMETRIC, optional): to unlock the optional PIN lock. Android handles biometric data;

the app never sees it.

• Storage (WRITE_EXTERNAL_STORAGE, Android 4.3 only): saving exports and backups to the Download folder. Newer

Android versions use the system file picker instead.

• Home-screen shortcut (INSTALL_SHORTCUT): adding the "Add fill-up" shortcut on older launchers.
• Not requested: internet, location, camera, photos and media (READ_MEDIA_IMAGES), microphone, contacts, calendar,

phone, SMS, Bluetooth, exact alarms and foreground services. Receipt photos use your camera app or the system image picker, which need no permission in RideBook.

Deleting your data

More › Privacy & data › Delete everything removes all vehicles, entries, documents, receipt photos, settings and the PIN from the app permanently. Uninstalling the app also removes them. Files you exported yourself stay where you saved them until you delete them.

Purchases

RideBook is a paid download from Google Play, handled entirely by Google Play under the Google Privacy Policy. There are no in-app purchases, subscriptions or ads, and the app contains no payment code.

Service intervals

Service intervals in RideBook are general reminders, not manufacturer advice. Check your owner's manual. RideBook does not connect to your vehicle.

Children

RideBook is meant for adults (18+) who own or drive a vehicle. It is not directed to children and collects no data from anyone.

Changes and contact

If this policy changes, the new version will be published at the same address with a new date. Questions: the developer contact on this app's Google Play listing.