RangeRing is a touring companion app for Australian motorcyclists and riders. This page explains what data the app collects, why, where it goes, and what choices you have. It is written for Australian users in plain English and covers only what the app and its server actually do.
📋 Summary
- No account is required. You do not need to sign in.
- No advertising. No third-party analytics. No crash reporting SDKs.
- Location is used only while the app or one of its foreground services is running. There is no silent background collection.
- Location and other data are sent to our server at rangering.au only when you use a feature that needs it (live share, group ride, submitting a road report or ride).
- All server traffic is over HTTPS.
🔎 What we collect and why
📍 Location
The app uses your device's precise location (GPS) to show you on the map, work out your fuel range, find nearby stations and points of interest, record rides you choose to record, and stream your position during a live share or group ride.
- Foreground map use. Location stays on the device. Nothing is sent to any server just because the map is open.
- Ride recording (foreground service). If you start recording a ride, GPS breadcrumbs (latitude, longitude, timestamp, speed, bearing, accuracy) are written to the app's local database so you can review the ride afterwards. This runs as an Android foreground service with a persistent notification while active. Nothing is uploaded automatically.
- Ride submission. You can choose to submit a completed ride to rangering.au to improve public road surface data. When you do, the app uploads a downsampled trail of GPS points and any hazard marks you added, plus your overall condition and surface ratings and a random device ID (see below). Ride submissions are used to verify road segment conditions for other riders.
- Live location sharing (foreground service). If you start a share, the app sends your GPS position, speed, heading, battery percentage, movement and pause state to rangering.au every few seconds for the duration you chose. This runs as an Android foreground service with a persistent notification while active. The share ends automatically at the timer you set, or immediately when you stop it.
- Group rides (foreground service). If you host or join a group ride, your live share stream is visible to other riders who have the group's join code, and their positions are visible to you. Ends when the group timer expires or you leave.
- Community road reports. When you tap Report on the map, the report's latitude and longitude, the condition rating, surface type, problem tags, an optional comment, an optional travel direction and a random device ID are sent to rangering.au.
The app declares the Android permissions ACCESS_FINE_LOCATION
and ACCESS_COARSE_LOCATION. The app does not
request the ACCESS_BACKGROUND_LOCATION permission. The three
services that use location (ride recording, ride tracking, and live
share) run as Android foreground services with a persistent
notification. They stop when you stop them or when their timer expires.
🏍️ Ride and hazard content you create
- Ride breadcrumbs and hazard marks recorded during a ride.
- Community reports: condition rating, surface type, hazard tags (potholes, corrugations, loose gravel, broken bitumen, flood damage, mud, washouts, debris, edge damage, other), an optional free-text comment and an optional travel direction.
- Station "closed" flags: you can flag a fuel station as closed or report it back as open.
Ride content is stored locally on your device. It is uploaded only if you submit a ride or submit a community report.
👤 Rider display name (optional)
You can enter a display name in Settings that other members of a group ride will see. It is stored on your device and sent to rangering.au only when you join or host a group ride. It is capped at 50 characters. You can change or clear it at any time in Settings.
🔑 Device identifiers
- Community report device ID. A random UUID generated the first time you submit a community report or a ride. It is stored in the app's local preferences and sent with community report and ride submissions so the server can rate-limit and deduplicate. It is not derived from any hardware ID and does not identify you as a person.
- Group / flag device hash. A one-way SHA-256 hash of your device's Android ID. It is sent with station flag/unflag requests and when you create or join a group ride, so the server can prevent one device from voting many times or spinning up many groups. The raw Android ID never leaves the device.
📡 Live share and group ride tokens
When you create a live share or a group ride, the server issues a random session token, a rider secret (only the creator gets this), and, for groups, a join code. These are held locally in the app so it can send position updates and stop the session, and are held on the server until the session expires. Anyone with the share link or join code you give out can see the position stream while the session is live.
🚩 Optional journey checkpoints on a share
When you create a share, you can optionally attach a planned journey: a name and up to 30 waypoints (each with a name, latitude, longitude, kind and planned distance). If you attach one, it is sent to rangering.au with the share so viewers can see your planned route and progress.
🌐 IP address
Like any web request, calls from the app to rangering.au include your device's public IP address at the network layer. The live share endpoints hash your IP with a secret salt (SHA-256) and store only the hash, and use it only to enforce a per-IP rate limit (currently 10 live share sessions per hour). The plain IP is not stored in our application tables. Standard web server request logs on the hosting infrastructure may contain IP addresses for a short period as is normal for web hosting.
🚫 What we do not collect
- No email address, phone number, real name, address or date of birth.
- No account sign-in. No password.
- No contacts, calendar, SMS, files, photos or microphone access. (The app does not request those permissions.)
- No advertising ID. No cross-app tracking.
- No third-party analytics or crash reporting SDK (no Firebase, no Crashlytics, no ads SDK).
- No payment or financial data. The app has no in-app purchases and no subscriptions.
- No health or fitness metrics such as heart rate.
🔗 Third-party services the app talks to
Beyond our own server at rangering.au, the app makes network requests to the following third parties. Each of them will see your device's public IP address for the requests they receive, and is subject to their own privacy policies.
- Google Play Services (location). Used to obtain GPS fixes on the device via the Fused Location Provider. Required for any location-using feature to work. Google's handling of that data is covered by the Google Play Services privacy terms.
- OpenStreetMap tile servers. Map tiles are fetched from the standard OpenStreetMap tile service to render the map. The tile server sees the map area you are viewing.
- Australian government transport and road APIs. Used to fetch traffic events, hazards, cameras, rest areas and other public-safety information relevant to your area. Includes NSW Transport, NSW Fuel Check (via our server as well), QLD Traffic, VIC OpenData Roads, NT road reports, ACT open data, WA Main Roads, SA data portal and Tasmanian LIST services.
- Traffic camera image feeds. When you open a traffic camera, its live image is loaded from the operator's URL.
- Android Auto (Car App Library). If you use the app on Android Auto, the head unit talks to the phone via Android Auto. No extra data is sent to us from the head unit.
We do not sell your data. We do not share your data with third parties for their marketing.
📱 Where data is stored on the device
- An app-private SQLite database (Android Room) holds ride recordings, cached station and POI data, and other local records.
- Preference stores (Android DataStore / SharedPreferences) hold your settings, your optional display name, the community-report device ID, station flag history, and any live share or group state while active.
- Android auto-backup: the preference stores are excluded from Google Drive auto-backup so a reinstall gives you a fresh setup experience. The Room database follows Android's default auto-backup behaviour, which means it may be included in the standard Google Drive backup of your device unless you disable that in Android Settings.
⌛ How long we keep it
- Live share positions. Purged 7 days after the session's created_at. Session-owned check-in state is purged along with the parent session.
- Group rides. Ended and purged shortly after their expires_at (a short buffer window prevents a stale join code being reused immediately).
- Community road reports. Kept until the report's expires_at, which is chosen by problem type: flood damage 7 days; loose gravel and debris 30 days; potholes 90 days; other hazards up to 180 days. Reports past their expiry are hidden and are eligible to be removed.
- Submitted ride data. Aggregated into the road surface data set (road segment condition, verified flag). We keep this so future riders benefit from the report.
- Station flags. Kept while the flag is active.
- Ride recordings on your device. Kept until you delete them in the app or uninstall the app.
🗑️ How to delete your data
- On your device. Uninstalling RangeRing removes the app's local data on your device. You can also clear the app's storage from Android Settings > Apps > RangeRing > Storage.
- Live share and group rides. Stop the share or leave the group in the app; the server session is ended immediately. Position data is then purged within the retention window above.
- Community reports, ride submissions and station flags. To request deletion of records tied to your device, email [email protected] from the address you would like us to reply on. Include enough detail to identify the submissions (for example the approximate date, area, and if you still have the app installed, the device ID shown on request). We will remove matching records from our database.
Note that once a live share link or a group join code has been shared with someone, anyone who received it may have seen your live position while the session was active. We cannot recall what a viewer already saw.
🔒 Security
- All app-to-server traffic uses HTTPS.
- Live share tokens live in the URL fragment of viewer links (after
the
#), so they are not sent to intermediaries such as CDN referers. - The rider secret that is required to stop a share is issued only to the creating device.
- IP addresses used for rate limiting are stored as SHA-256 hashes with a secret salt, not as plain IPs.
👦👧👧 Children
RangeRing is a general-audience app aimed at adult riders. It is not directed at children under 13, and we do not knowingly collect data from children. If you believe a child has used the app, contact us and we will remove any related records.
🔔 Changes to this policy
We may update this page as the app changes. When we do, we will update the "Last updated" date at the top. Material changes to what we collect or how it is used will be flagged in the app's release notes.
✉️ Contact
Questions, deletion requests or privacy concerns: [email protected].