RideGlass records rides on your iPhone. You can use the app without an account; if you sign in, your rides are also backed up so you can restore them on another device. This policy explains what the app touches, what is uploaded, and what only ever leaves your phone because you chose to send it.
1 · Who we are
RideGlass is written and published by Greg Raine, an individual developer based in the United Kingdom, who is the data controller for everything described here. There is no company behind the app and no other party with access to your rides.
For anything in this policy — including a request to see, export or erase your data — write to greg@rideglass.com. You will get a reply within 5 working days.
2 · What the app records
A recorded ride holds your GPS track, accelerometer, gyroscope, device attitude, barometric altitude and pressure, plus the ride summaries computed from them. It is written to your iPhone first, and that copy stays there.
Samples are written 30 times a second for the whole time a ride is recording, so an hour on the bike is around a hundred thousand rows. Completed rides live in the app's own private storage inside RideGlass's app container — a Core Data database — where iOS file protection keeps them encrypted until the first time you unlock the phone after a restart.
Two directories hold work in progress: the raw capture spool for a ride that is still recording, and the queue of rides waiting to upload. Both are explicitly excluded from iPhone backups, so raw traces never ride along to iCloud. Completed rides in the database are not excluded — if you back your iPhone up, they are in that backup, under Apple's terms rather than ours.
Your settings — units, theme, livery, high-contrast mode, the learned speed and G scales for your bike — are stored on the device alongside them and are never uploaded.
3 · Location & motion data
Location and motion permissions are used to draw your dashboard and record your route. Recording itself does not depend on a network connection.
RideGlass asks for exactly three permissions, and never asks for more:
- Location — While Using the App. Not “Always”. It draws live speed, heading and altitude, and records your route. While a ride is recording, iOS keeps location running in the background so the track survives the screen going off or the phone going in a pocket.
- Motion & Fitness. The accelerometer, gyroscope and device attitude behind lean angle and G-force, live on the dashboard and recorded during a ride.
- Media & Apple Music. Only so the dashboard can show what is playing and offer glove-sized skip and pause controls. It reads the now-playing item; it does not read your library, your playlists or your listening history.
Any of the three can be withdrawn at any time in iOS Settings → Privacy & Security, or under Settings → RideGlass. Withdrawing location stops route recording; withdrawing motion stops lean and G; withdrawing media removes the audio panel. Nothing else in the app is affected, and nothing already recorded is lost.
4 · Accounts & cloud backup
Sign in with Apple is optional. Once you are signed in, your rides upload to our backup service so they can be restored on another device — and you can delete your account from inside the app. No profile is built from your riding, and nothing about where you ride is used for advertising.
When you sign in, Apple gives the app one thing: a stable identifier that is unique to you and to RideGlass, and means nothing anywhere else. The app does not ask Apple for your name or your email address, so it never receives them. Your account record is that identifier, the device keys it is bound to, and the rides you have uploaded — nothing more.
Backed-up rides are held in Amazon Web Services in the eu-west-1 region (Ireland), in storage that is private, encrypted at rest and reachable only over HTTPS. AWS is the only processor involved and acts on our instructions alone. Your rides and your account are never shared with, sold to, or licensed to anyone else, and nothing about them reaches the analytics described in the next section.
5 · Diagnostics & analytics
RideGlass includes Google Firebase for three narrow jobs: Crashlytics for crash and error reports, Analytics for anonymous counts of which screens and features get used, and Messaging for the notification token. Google is a processor for all three.
What those send is diagnostic, not personal: crash traces, performance data, a device identifier, which parts of the app were opened, and the advertising-related measurement data Google's analytics SDK gathers by default. None of it is linked to your account or to your rides, none of it is used to track you across other apps or websites — RideGlass never asks for App Tracking Transparency permission, because it does not track — and no route, coordinate or ride file is ever included in a crash report.
Once, on the first launch after install, the app also asks Apple whether this install came from an Apple Search Ads advert and records the campaign against the anonymous analytics profile. It is how ad spend is measured, it happens exactly once, and it says nothing about you — an install that came from anywhere else simply reports that it did.
If you opted in to sharing analytics with developers in iOS Settings, Apple separately sends aggregate crash and usage statistics that identify nobody.
6 · Purchases
RideGlass Pro is bought through Apple. We never see your payment details — only whether the unlock applies to your device.
The check happens entirely on your device. RideGlass reads the entitlement StoreKit already holds and verifies Apple's signature on it locally; no receipt is sent to a server of ours, and we run no purchase database. Apple is the merchant of record and the processor for the transaction itself, so refunds and payment queries go to Apple, not to us.
7 · Exports & sharing
When you export a CSV or share a ride card, the data goes wherever you send it via the iOS share sheet. That destination's own privacy terms then apply.
It is worth knowing exactly what each one carries before you send it:
- A ride card is a short summary — date and time, distance, moving time, average and top speed, maximum lean each way and peak G. No coordinates, so it does not reveal where you rode.
- A CSV export is the complete record: every sample, with precise latitude and longitude, a timestamp, speed, altitude, lean, G-force, heading, GPS accuracy and the raw motion vectors — 38 columns in all, plus a JSON sidecar of ride context. Anyone you send it to can reconstruct your exact route, including where you started and where you stopped.
8 · Retention & deletion
Rides stay until you delete them. Deleting the app removes its stored rides from the device; deleting your account removes the backed-up copies.
- One ride. Delete it from Ride History. It goes from the device immediately, and its backed-up copy is removed too if you are signed in.
- “Forget my bike”. Clears the learned speed and G scales the gauges adapt to. A settings reset, not a data deletion — your rides are untouched.
- Your account. Delete it in Settings. The request is queued and worked through in the background, removing every uploaded ride and every version of it, then the account record and the device key bound to it. It starts after a short delay so that any upload still in flight cannot re-create what has just been deleted, and it runs to completion on its own. Rides on your phone are deliberately left alone: deleting the account stops the backup, it does not wipe your riding.
- The app. Deleting RideGlass removes its device storage with it. Copies inside an existing iPhone or iCloud backup persist until that backup is replaced or deleted, which is Apple's to control rather than ours.
9 · Your rights
Backed-up rides are held on the basis of the agreement you entered into when you signed in — the backup is the service you asked for, and it stops when you delete the account. Diagnostics rest on a legitimate interest in the app not crashing, which you can object to at any time.
Under the UK GDPR and the EU GDPR you may ask for a copy of what is held, ask for it corrected, ask for it erased, object to processing or ask for it in a portable form. Under the CCPA, California residents have the equivalent rights to know, delete and opt out; RideGlass does not sell or share personal information, so there is nothing to opt out of.
Two of those you can exercise yourself, immediately and without asking: export every ride as CSV from inside the app, and erase everything backed up by deleting your account in Settings. For anything else, write to greg@rideglass.com and you will get a reply within 5 working days. If you are not satisfied, you may complain to the UK Information Commissioner's Office, or to your own country's supervisory authority.
10 · Children & changes
RideGlass is rated 4+ on the App Store because it contains nothing objectionable, but it is built for licensed riders and is not directed at children. It does not knowingly collect anything from a child, and it asks for no age, date of birth or any other detail that could identify one.
When this policy changes, the date at the top of the page changes with it, and a change that affects what is collected or where it goes will also be called out in the release notes for the version that introduces it. The page always shows the current policy; earlier wording is in the site's public source history.
Privacy questions: greg@rideglass.com