RTrack privacy policy
Effective date: 2026-10-21. Applies to the RTrack Android app (cc.bezgalm.rtrack), the optional RTrack sync service at rsync.bezgalm.cc, and this website (rtrack.bezgalm.cc).
RTrack is a motorcycle ride recorder. This policy explains what the app records, where that data goes, and what you control. Short version: your rides stay on your phone. RTrack needs no account and has no analytics, no ads and no crash reporting. Unless you turn on the optional end-to-end encrypted sync (section 3), the developer receives none of your data. A few map, elevation and weather services see the area you look at or rode in, as described below.
Contact: rtrack@bezgalm.cc
1. What the app records on your phone
While you record a ride, RTrack stores in its private database on the device:
- Precise location (GPS, about once per second): latitude, longitude, altitude, speed, heading, accuracy, time.
- Motion sensors (accelerometer and gyroscope, up to ~200 samples per second), used for lean angle, braking/acceleration events and road roughness.
- Satellite status (number of satellites, signal strength) for the Sensors screen.
- What you add: ride names, ratings, condition tags, notes on events, fuel prices, settings.
- Derived data: statistics, achievements, weather and elevation summaries for each ride.
This data is stored only in the app's private storage. Other apps can't read it. Uninstalling the app, or Settings → Clear all trips & data, deletes it.
Background location. A ride you start yourself keeps recording with the screen off using ordinary "while using the app" location, shown by a persistent notification. RTrack asks for location "all the time" only if you turn on Fully automatic recording (Settings → Auto-detect rides), after explaining why: it lets RTrack start recording by itself when it detects you riding, even while the app is closed. Even then, location is recorded only during a ride (with the notification shown), and RTrack does not track your location when no ride is being recorded.
Physical activity (optional). If you turn on automatic ride detection, Android's activity recognition (part of Google Play services) tells RTrack when you seem to start or stop driving, so it can suggest recording. RTrack doesn't store these events.
Android backup. RTrack opts out of Android's backup: your rides, settings and sync state are not included in Google (Google One) device backups, and are not copied by Android's phone-to-phone transfer when you set up a new phone. To move your rides to a new phone, use Export / Import (a ZIP file you control) or the optional end-to-end encrypted sync described below.
2. Services the app contacts
RTrack talks to the following third-party services directly from your phone. None of them receives your ride recordings, sensor data, notes or any account identifier, but like any web server they see your IP address and the request itself.
| Service | When | What it receives |
|---|---|---|
OpenFreeMap (tiles.openfreemap.org) | Whenever a map is shown (Record, ride details, Stats heatmap) | Requests for map tiles covering the area on screen, so it can infer which area you are viewing. |
Esri World Imagery (server.arcgisonline.com) | Only if you pick the Satellite map style | Same as above (tiles for the area on screen). |
Mapterhorn (tiles.mapterhorn.com), with AWS Terrain Tiles (s3.amazonaws.com, Amazon Web Services) as fallback | After a ride, to correct its altitude profile, and when you export a share image/video with terrain | Requests for elevation tiles covering the ride's route (each tile covers roughly 5 to 10 km across), so they can infer the area of the route at that scale. |
Open-Meteo (api.open-meteo.com, archive-api.open-meteo.com) | After a ride, to add the weather during the ride | The approximate centre of the ride (latitude/longitude rounded to a 0.05° grid, about 5 km) and the ride's date(s). |
Bright Sky (api.brightsky.dev, Germany's DWD weather data) | Only if Open-Meteo fails, and only for rides in Europe | The approximate centre of the ride (rounded as above) and its start/end time. |
| wttr.in | Only if both above fail, and only for rides from today | The approximate centre of the ride (rounded as above). |
| Google Play services (Fused Location Provider, Activity Recognition) | While recording / when auto-detection is on | Handled on the device by Google Play services under Google's privacy policy; depending on your phone's location settings, Google may use Wi-Fi and mobile network information to improve location accuracy. |
These requests are sent over HTTPS. The weather and elevation results are cached on the phone, so each ride is looked up once.
3. Optional sync (end-to-end encrypted)
Sync is off by default. If you turn it on, you connect the app to a sync server. By default that is the RTrack sync service at rsync.bezgalm.cc, operated by the developer on Cloudflare (Workers, Durable Objects and R2 storage). You can enter a different address instead, including a server you run yourself (the server software is part of RTrack).
- Before anything leaves the phone, each ride is encrypted on the phone with a key derived from your sync passphrase (libsodium: Argon2id + XSalsa20-Poly1305). The server stores only encrypted blobs and cannot read your rides, locations, sensor data or notes. The passphrase never leaves your devices.
- To work, the server does see some metadata, unencrypted:
- random identifiers for your sync account and each device (no name, email or phone number), and the device name you register (by default your phone's manufacturer and model, e.g. "Samsung SM-S911B");
- for each ride: a random ride id, start and end time, the number and size of the encrypted parts, and when it was changed or deleted;
- when each device was last seen, and its IP address (as with any web request; the server doesn't store it, except as the hash described next).
- On the RTrack sync service, IP addresses are used only for abuse limits on sign-up and recovery: they are stored as a keyed hash (HMAC), never in plain form, and deleted after 24 hours. Each account has a storage limit (2 GB) and a device limit (10).
- You can delete your account and everything stored on the server at any time in Settings → Sync → Delete account and server data. Your rides stay on your phone. If you no longer have the app, email the rider ID from your recovery kit to rtrack@bezgalm.cc and the account will be deleted within 30 days (details: rtrack.bezgalm.cc/delete-account). After deletion the server keeps only a note that the random account id was deleted, and when, so the id is never reused. A copy of the deleted account database may be retained in Cloudflare's backups (Durable Objects storage recovery history) for a limited time before it expires.
- Deleting a ride on the phone deletes it from the server. A deletion marker without content (the ride's random id, start and end time, and when it was deleted) is kept for 90 days so your other devices learn about it. Disconnecting a device is done in Settings → Sync.
- If you use a server run by someone else, its operator is responsible for it and the developer of RTrack has no access to it.
4. This website
rtrack.bezgalm.cc is a static website hosted on Cloudflare. It sets no cookies, runs no scripts and loads nothing from other sites, and the developer runs no analytics on it. Like any web host, Cloudflare processes your IP address and the request to deliver the page.
5. Sharing and exports
When you export or share a ride (JSON, GPX, CSV, ZIP, image, video), RTrack creates the file and hands it to the app you choose through Android's share sheet. What happens next is up to you and that app. By default RTrack can trim the start and end of a shared route and hide the date, to avoid revealing where you live.
6. What RTrack does not do
- No sign-in and no email, name or phone number collection. The optional sync account is identified only by a random id.
- No analytics, advertising, tracking SDKs or crash-reporting services.
- No selling or sharing of data with data brokers or advertisers.
- No access to contacts, photos, microphone or camera.
7. Children
RTrack is intended for adult motorcycle riders and is not directed at children under 13.
8. Your choices
- Deny or revoke location "all the time" access; rides you start yourself still record with the screen off, and ride detection falls back to a "tap to record" notification instead of starting by itself.
- Keep sync off, or disconnect it at any time. Delete your sync account and its server data in Settings → Sync → Delete account and server data, or by email as described in section 3.
- Delete individual rides, or everything (Settings → Clear all trips & data), or uninstall.
9. Changes
If this policy changes, the new version will be published at this address with a new effective date, and significant changes will be mentioned in the app's release notes.