Effective date: 4 November 2026
Developer: APE Studios
Contact: apestudios.io@gmail.com
Published at: https://apestudios.app/offroad-gauges/privacy/
Offroad Gauges is a gauge cluster for off-road driving: tilt dials, compass, speed, altitude, and optional trip recording. It is the same app on Android and on iPhone, backed by the same service, and this one policy describes what either version does with your data. Where the two differ — which company signs you in, sells the upgrade, or draws the map — it says so.
The short version: if you do not sign in, your location and your recorded trips stay on your device. If you do sign in, your recorded trips — including their routes — are backed up to our database so they come back on a new phone, and nothing else changes. We also collect anonymous information about the app itself — that it was installed, what kind of phone it is on, and which screens get used — so we can tell whether the app works. None of that is your location.
Signing in is optional. The app offers "continue as guest", and a guest's drives are never uploaded.
How to delete your account and your data
There are two ways, and either one erases everything we hold for you — your account, every trip backed up to it, and the record of this install.
In the app. Profile → the gear → Account → Delete my account. It asks once to be sure, and then it is done immediately. Trips saved on the phone itself stay on the phone; you can delete those from the Trips tab.
By email, if you no longer have the app. Write to apestudios.io@gmail.com from the address you signed in with and ask us to delete your account. You do not need a reason, and you do not need to reinstall anything. We will confirm when it is done.
If you used the app as a guest we may be unable to find your record from an email alone, because a guest record is not linked to any address — that is a consequence of collecting as little as we do, not a refusal. Uninstalling ends a guest record permanently in any case.
What stays on your device
Precise location (GPS). Used while the app is open to display speed, altitude, and heading, and — only when you start a recording — to build the route of a trip. Also used to work out the sun's position for the sunset readout and the automatic day/night theme.
Your trips, if you have not signed in. Recorded trips, including their routes, are written to the app's own private storage. As a guest there is no copy anywhere else, and we cannot see them. Signing in changes this — see Trip backup below.
Your settings never leave the phone, including the approximate last position the sunset calculation needs.
Uninstalling the app deletes all of it — unless you have signed in, in which case see Your account below. Individual trips can be deleted at any time from the Trips tab.
Trip backup (only if you sign in)
If you sign in — with Google on Android, or with Apple on iPhone — each drive you record is uploaded to our database and stored against your account, so that reinstalling the app or moving to a new phone brings your drives back.
What a backed-up trip contains: the route itself — the sequence of GPS coordinates the drive followed — along with its start and end time, distance, duration, speeds, tilt figures, altitude, and any name you gave it.
A route is location data, and this is the one place the app sends your location to us. We say so plainly because the rest of this policy says we do not, and both are true depending on whether you sign in.
What it is used for: giving your drives back to you, and nothing else. It is not used for advertising or profiling, is not sold, and is not shared with data brokers. No one but you can read your trips: the database enforces, per row, that a trip is readable only by the account that recorded it.
How to avoid it entirely: continue as guest. Guests get the whole app — every gauge, the map, trip recording, trophies — with no upload of any kind.
How to delete it. Deleting a trip in the app deletes it from the database too. Deleting your account deletes every trip stored against it, along with everything else we hold for you. Email apestudios.io@gmail.com to have your account deleted; we do not need a reason.
Signing out stops further uploads and leaves the drives on your phone. Trips already backed up stay in the database against that account until you delete them or delete the account.
Your account (only if you sign in)
Signing in is optional and the app works fully without it. If you choose Continue with Google (Android) or Sign in with Apple (iPhone), we hold:
- Your email address, so the account can be recognised as yours on a new phone. If you use Apple's Hide My Email, what we hold is the private relay address Apple creates for you, not your real one — mail we send to it is forwarded by Apple, and you can turn that off in your Apple ID settings at any time.
- Whatever else your provider includes when it signs you in, which for Google is typically your display name and the web address of your profile picture, and for Apple is nothing beyond the address. We do not ask for these separately; they arrive inside the sign-in token and are stored with the account.
That is the whole of it. We do not receive your password, your contacts, or anything else from your Google or Apple account, and we never post anything.
One account across both phones. Your account is your email address. Sign in with the same address on an Android phone and an iPhone and they are one account: your backed-up trips and your Pro purchase follow it to both. An Apple relay address is a different address, so an account created with Hide My Email is a separate account from one created with your Gmail address.
Signing in also makes your identity outlive the install — that is its purpose. Uninstalling no longer erases everything: your account and the trips backed up against it stay until you delete them. Email apestudios.io@gmail.com to have the account and everything in it deleted.
What we collect
All of this is about the app, not about you. It is sent over an encrypted connection to our own database, and nowhere else.
An anonymous install identifier. When you first open the app it signs itself in anonymously and receives a random identifier. Until and unless you sign in it is not linked to your name, email, phone number, Google or Apple account, or advertising ID — we cannot use it to work out who you are, and neither can anyone else. It exists so that two app openings can be recognised as the same install rather than two different ones. For a guest it is created and destroyed with the install: uninstalling the app ends it permanently. If you sign in, this same identifier becomes your account and stops being disposable — see Your account above.
Basic device and app information, attached to that identifier: your phone's model, its Android or iOS version, the version of Offroad Gauges you are running, your language and region, your Offroad Gauges settings (metric or imperial, day or night theme), and the vehicle make and model you pick — which is a choice from a fixed list, not free text, and which you can skip.
How the app is used. Anonymous events recording which screens you reach and which actions you take — for example that a trip was recorded, that the Pro screen was shown, or that a trophy was earned. These carry no coordinates, no route data, and no trip names.
Your Pro purchase, if you make one. When you buy Pro, the app sends the store's receipt identifier — a Google Play purchase token or an App Store transaction number — to our server. Our server asks Google Play or the App Store whether that purchase is genuine and records the answer against your identifier: which plan (annual, monthly or lifetime), whether it is active, in its free trial, cancelled or expired, when it expires, and the country of the store. The stores also notify our server when a subscription renews, lapses, is cancelled or refunded, so that Pro is switched on and off correctly. This is how a purchase made on one phone is recognised on another. Payment details — cards, billing addresses — are handled entirely by Google Play or the App Store and never reach us.
Pro goes through RevenueCat. The Android app, and the iPhone app from version 1.1, use RevenueCat (revenuecat.com), a subscription service that acts on our behalf as our processor, to load the Pro offer, check whether you have Pro, and record a purchase. RevenueCat receives an app user ID — a random ID if you are a guest, or our identifier for your account if you signed in, so Pro follows your account to a new phone — plus the app version, device model, Android or iOS version and language, your store country and currency, the IP address any internet request carries, on iPhone Apple's identifier for vendors, and, when you buy or restore, the purchase record the store issues: which plan, the price, trial and renewal dates, and Google's purchase token or Apple's transaction ID. It never receives your email, your name, your location or your payment details, and it is not used for advertising or tracking. Even if you never buy anything, the app contacts RevenueCat when it starts, to load the Pro offer. RevenueCat keeps the record while the purchase exists and as long as needed for accounting. Its privacy policy: https://www.revenuecat.com/privacy/. iPhone version 1.0 talks to the App Store directly.
Crash reports. If Offroad Gauges crashes, it records the type of error, a single line identifying where in our own code it happened, and whether it happened on the main thread — and sends that with the same anonymous identifier as everything above, the next time you have a connection. We deliberately do not record the error's message text, because an error message can quote things you typed, such as the name you gave a trip. The report tells us that a release is broken and roughly where; it tells us nothing about where you drove.
What we deliberately do not collect
- Your location, in analytics. No coordinates, no routes and no trip names ever go into our analytics events, into advertising, or to any data broker. Routes reach our database only through the trip backup described above, only for signed-in accounts, and only to be handed back to you. A second exception is unavoidable and is not us: to draw a map, the map service — Google Maps on Android, Apple Maps on iPhone — must be asked for the map of the area you are looking at, and on the Map tab that area is where you are. See Third parties below. Turning to a different tab stops it; nothing about the gauges, the sunset readout, or trip recording needs it.
- Your identity, unless you sign in. As a guest we hold no account, no email address and no name for you, and we never ask for one. If you do sign in, we hold what your provider hands us — see Your account above. Your phone number and your contacts we never collect either way, and on iPhone we do not ask for your name.
- Your advertising ID, and no advertising or tracking networks. Offroad Gauges shows no ads and does not sell or share data with data brokers.
- Your photos, files, microphone, or camera.
Third parties
Which company is involved depends on the phone. On Android it is Google, under Google's privacy policy (https://policies.google.com/privacy); on iPhone it is Apple, under Apple's (https://www.apple.com/legal/privacy/). The roles are the same on both:
- The map — Google Maps on Android, Apple Maps on iPhone — draws the Map tab, the map behind trip cards, and the map on a shared trip image. Drawing a map means asking that service for it, so the area being viewed is sent to Google or Apple. On the Map tab that area is centred on you, so this amounts to your approximate position; behind a trip card it is the area that trip covered. This is the map service receiving it in order to draw, not us collecting it — we get nothing back.
- The store — Google Play Billing on Android, the App Store on iPhone — processes Pro subscriptions and the one-time purchase, and tells our server about the purchase as described under What we collect. Payment details are handled entirely by the store; the app never sees or stores payment information.
- The rating prompt — on Android it opens the app's Play Store listing; on iPhone it is Apple's own rating sheet, which Apple shows or withholds.
- Sign-in — Sign in with Google or Sign in with Apple, only if you choose it. The provider shows its own account screen and tells us which account you picked so we can create or find your account. The provider learns that you signed in to Offroad Gauges.
Choosing "continue as guest" involves neither company's sign-in or store, and the map service only as the viewport of a map you look at.
Our own database is hosted by Supabase (supabase.com), which stores the install record, the anonymous usage events, your account and — if you are signed in — your backed-up trips, on our behalf and does not use any of it for its own purposes.
RevenueCat (revenuecat.com) checks and records your Pro purchase on our behalf, as described under What we collect, and does not use it for its own purposes or for advertising.
Sharing a trip
Sharing a trip card creates an image containing that trip's route and statistics and hands it to the app you choose. That image goes wherever you send it. Nothing is shared unless you tap Share and pick a destination, and no copy reaches us.
Permissions
- Location (precise, while using the app) — the gauges and trip recording, as described above. As a guest your position is never transmitted to us; it reaches the map service only as the viewport of a map you are looking at. If you sign in, the routes of the trips you record are uploaded to us as described under Trip backup.
- Recording with the screen off — a recording you started keeps running while the screen is locked, so the route is not cut short mid-drive. On Android this is a foreground service with its ongoing notification; on iPhone it is the location background mode, and iPhone shows its own indicator while it runs. Neither version asks for "always" location access, and neither records when you have not started a trip.
- Motion sensors (iPhone asks; Android does not) — the pitch and roll dials. Readings never leave the phone.
- Notifications (Android) — shows the ongoing notification while a trip is recording. Declining it only hides that notification.
- Internet — required by the map, store, sign-in, RevenueCat and Supabase services listed above.
Children
Offroad Gauges is not directed at children. We do not knowingly collect personal information from anyone, including children.
Your rights
As a guest, your trips, routes and settings are yours alone and never reach us, so there is nothing on our side to export or correct — delete individual trips in the app, or uninstall to remove everything. For the anonymous install record we do hold:
- Deleting the app deletes it. Uninstalling ends the anonymous identifier permanently. We keep no way to link a future install to a past one.
- You can ask us to erase it sooner. Email apestudios.io@gmail.com from the device in question and we will delete the record and the identifier behind it.
Because a guest identifier is anonymous by design, we may be unable to locate a specific record from an email alone — which is a consequence of collecting as little as we do, not a refusal.
If you are signed in, we hold your account and your backed-up trips, and uninstalling no longer removes them. You can:
- Delete individual trips in the app; each one is deleted from the database too.
- Sign out, which stops further uploads and leaves your drives on the phone. What is already backed up stays until you delete it or delete the account.
- Delete your account and everything in it — every trip, the account record, and the install record behind it — by emailing apestudios.io@gmail.com. We do not need a reason, and because a signed-in account has an email address we can find it.
- Ask for a copy of what we hold for you, at the same address.
- Ask us to delete your purchase record at RevenueCat, at the same address. Guests can ask too.
Data retention
Install records are kept while the install exists and for up to 24 months after it stops being seen, then deleted. Usage events are attached to the install record and are deleted with it.
Changes
Material changes to this policy will be posted here with an updated effective date, and, where required, announced in the app's store listing.