The short version
- No account, no sign-up, no profile. We do not know who you are.
- Your routes, drives and drive memories stay on your device, in a database encrypted with a key held in the iOS Keychain / Android Keystore.
- Location is used to generate routes near you and to record a drive. To build a route, coordinates are sent to mapping and routing providers — see section 4.
- No ads, no analytics, no tracking SDKs, no advertising identifiers.
- Purchases are handled entirely by Apple and Google. We never see your payment details.
1. Who we are
ApexRoute is published by Froggy Eye Ltd, a company registered in the United Kingdom ("we", "us", "our"). This policy explains what happens to data when you use the ApexRoute mobile app on iOS or Android. It does not cover the App Store or Google Play themselves, which are operated by Apple and Google under their own privacy policies.
Because ApexRoute has no accounts and stores your content only on your device, in most cases we are not a controller of any personal data about you at all. Where we are — for example if you email us — the details are in section 9.
2. What ApexRoute stores, and where
Everything you create in ApexRoute is written to a local database on your phone. It is not uploaded to us, and there is no ApexRoute cloud account to sync with. That includes:
- Generated and saved routes, including their start points and waypoints
- Recorded drives — the GPS track, distance, duration, speed and elevation statistics
- Drive memories — photos, videos, audio and notes you attach to a point on a drive
- Route ratings and your own notes
- App settings and preferences, and whether you hold a Pro entitlement
This database is encrypted with AES using a key generated on first launch and held in the platform secure store — the iOS Keychain or the Android Keystore (via encrypted shared preferences). The key never leaves your device and is not known to us.
Your device's own backup system may include this data. If you use iCloud Backup or Google's Android backup, a copy may be held by Apple or Google under their terms; you can control that in your device settings.
3. Location data
ApexRoute is a driving-route app, so location is central to what it does. It is used in two ways:
- While you are using the app ("when in use") — to find your current position so routes can be generated from where you actually are, to show you on the map, and to preview a route.
- In the background ("always") — only if you choose to record a drive. Recording continues with the screen off so the GPS track is not broken; on Android this runs as a foreground service with a persistent notification, and on iOS the system location indicator is shown.
Background location permission is optional. If you do not grant it, everything except uninterrupted background drive recording continues to work. You can revoke any location permission at any time in your device settings, and ApexRoute will stop collecting location immediately.
Recorded tracks are stored locally as described in section 2. We do not receive them.
4. Third-party services that receive data
To draw a map and calculate a driving route, ApexRoute has to ask mapping providers about the area you are in. When it does, coordinates for that request leave your device and go to the provider named below. These requests carry location and the technical details any internet request carries (such as your IP address). They do not carry your name, an account, an advertising identifier, or the contents of your library — we have no such identifiers to send.
| Service | What it receives | Why |
|---|---|---|
| Google Maps Platform (Maps SDK and Directions API) | Map viewport and route coordinates | Displaying the map and calculating road directions |
| TomTom Routing API | Start, waypoint and destination coordinates plus routing preferences | Calculating "thrilling" driving routes over winding and hilly roads |
| OpenStreetMap Overpass API (overpass-api.de, overpass.kumi.systems) | A search area around your start point | Finding candidate roads to build a route from |
| Apple / Google platform geocoding | Coordinates, or a place name you type | Turning coordinates into place names and back |
| Apple App Store / Google Play billing | Purchase and subscription information | Processing purchases and restoring entitlements |
These providers process that data under their own privacy policies: Google, TomTom, OpenStreetMap Foundation, Apple. We do not receive a copy of these requests.
If you tap a route to open it in Apple Maps or Google Maps, or share a route or drive using your device's share sheet, you are handing that content to the app or person you chose. What happens to it then is governed by that app or service.
5. Camera, photos and microphone
ApexRoute asks for camera, photo library and microphone access only so you can attach a "drive memory" — a photo, video, audio clip or note pinned to a point on a drive. These permissions are requested at the moment you use the feature, and the app works without them if you decline.
Captured media is saved into the app's own storage on your device alongside the drive it belongs to. It is not uploaded anywhere, and we cannot see it.
6. Purchases and subscriptions
ApexRoute Pro is sold as a monthly subscription, an annual subscription, or a one-off lifetime purchase. All of it is transacted by the App Store or Google Play using the platform's own in-app purchase system. Your card details, billing address and payment history are handled by Apple or Google and are never sent to us or seen by the app.
The app receives only the store's answer to "is this device entitled to Pro?", which it records locally. Restoring purchases re-asks the store the same question.
7. What we do not do
- We do not show ads, and there is no ad SDK in the app.
- We do not use analytics or crash-reporting SDKs. There is no Firebase, no AdMob, and no third-party telemetry.
- We do not use the advertising identifier (IDFA / Android Advertising ID), and we do not ask for App Tracking Transparency permission because we do not track you.
- We do not build profiles, and we do not sell, rent or share personal data with data brokers.
- We do not require an account or an email address to use the app.
8. Retention and deletion
Because your data lives on your device, you control how long it is kept. Delete an individual route, drive or memory inside the app, or delete everything at once by uninstalling ApexRoute — uninstalling removes the app's local database and its encryption key. There is no server-side copy for us to delete, and no request you need to send us.
Note: if your device backups include app data, a copy may persist in your iCloud or Google backup after uninstalling. Clear it through your device's backup settings.
9. Your rights
Under the UK GDPR and equivalent laws you have rights to access, correct, delete, restrict and port your personal data, and to object to certain processing. In practice, for ApexRoute you exercise all of these directly on your device, because that is the only place your data is held.
If you contact us by email, we will hold your message and email address for as long as needed to answer you and to keep a record of the exchange. That is the one case where we hold personal data about you; you can ask us to delete it at any time by emailing info@froggyeye.com. If you are in the UK and are unhappy with how we have handled your data, you can complain to the Information Commissioner's Office.
10. Children
ApexRoute is a tool for licensed drivers and is not directed at children. We do not knowingly collect personal data from children. If you believe a child has sent us personal data by email, contact us and we will delete it.
11. Changes to this policy
If we change how ApexRoute handles data, we will update this page and change the effective date at the top. Material changes will also be noted in the app's release notes. Continuing to use the app after a change means you accept the updated policy.
12. Contact
Froggy Eye Ltd
United Kingdom
Email: info@froggyeye.com