Last updated 23 August 2026
Navigation Pro compares driving routes from Google Maps, Apple Maps and Yandex Maps side by side, then guides you along the one you pick. Doing that requires your location. This page explains exactly what is collected, who it reaches, and what you can switch off.
In this policy “we” means Navigation Pro. For privacy questions — including a request to see or delete your data — write to info@navigationpro.app, which reaches a person.
We never ask for your name, email address, phone number or date of birth. There is no sign-up screen and no password for you to choose. We do not sell personal data, and we do not use your data for advertising.
The app asks for location permission “While Using the App”. With that permission it also keeps receiving your position while a navigation you started is running and the screen is locked — that is what makes turn-by-turn work when the phone is in your pocket or on a cradle. iOS shows its blue location indicator whenever this is happening.
Your position is used to:
To calculate and follow routes, your start and destination coordinates — and, during navigation, your ongoing position — are sent to the map providers whose routes you are comparing. Each provider handles that data under its own privacy policy:
| Provider | What it receives | Its policy |
|---|---|---|
| Google (Routes API, Places, Navigation SDK) | Start and destination coordinates, search terms, and your position during navigation on the Google tab | policies.google.com/privacy |
| Apple (MapKit) | Start and destination coordinates, and map tile requests | apple.com/legal/privacy |
| Yandex (MapKit / NaviKit) | Start and destination coordinates, and your position during navigation on the Yandex tab | yandex.com/legal/confidential |
Yandex is a Russian company and its servers are outside the European Economic Area. Choosing the Yandex tab, or comparing routes while Yandex is enabled, means your coordinates are transferred there. If you would rather that did not happen, do not use the Yandex map.
We do not keep a history of your trips on our own servers. Your recent searches and your saved Home, Work and starred places are stored only on your device, and are deleted when you delete the app.
To understand where the app confuses people, we use Amplitude Session Replay, which records a video-like reconstruction of the screens you see and the taps you make.
Because most of this app's screens are a map, those recordings show your position, your route, and any saved places visible on screen. In other words: session replay collects location data in visual form. It is currently enabled for all sessions.
Recordings are processed by Amplitude, Inc. and are not used to identify you by name — they are attached to the random identifier described below.
On first launch the app generates a random identifier and sends it to our server with each request. It survives reinstalling the app and moving to a new Apple device, so you are counted once rather than twice. That identifier is all we know you by: no name, no email address, no account.
The app reports what happens in it to Google Analytics for Firebase and to Amplitude. The events are about actions, not content: which onboarding step you reached and whether you allowed the permission it asked for, that a comparison was made and how far apart the three estimates were, which map you picked, that a drive started and ended, and which settings you changed. Destination names are not sent as event data.
Firebase Crashlytics receives a report when the app crashes, and also when it absorbs an error it can recover from — a failed sign-in, a failed route request, a guidance engine that would not start. Reports include the device model, the OS version, and the random identifier above. Firebase Performance measures how long the route comparison takes.
If you allow notifications, the app registers with Apple Push Notification service and stores the resulting Firebase Cloud Messaging token on our server, so a device we may need to reach can be reached. No remote notifications are sent at present. The alerts you do receive — traffic building on a route you compared, and a summary when a drive ends while the app is in the background — are scheduled on your own device.
Turning notifications off in iOS Settings, or turning off “Trip & Traffic Alerts” inside the app, stops the alerts. Revoking the permission also deletes the stored token.
Purchases are processed by Apple. We never see your payment details. Subscription status is managed for us by RevenueCat, Inc., which receives a purchase identifier and the random identifier above — not your Apple Account.
Sending a message from Settings → Help & Support creates a support record on our server. It holds what you wrote, your identifier, your app version and build, your device model, your iOS version, and the language and region the app is set to — so that a reply does not have to begin by asking. If you fill in the optional email field, that address is stored too, and it is the only thing on the ticket that could identify you outside the app; leave it out and we can read your message but not answer it.
You get a reference back, and the same screen is where a request for a copy of your data or its deletion is made. Tickets are kept for up to 24 months, because a request has to stay answerable months later.
| Processor | Purpose |
|---|---|
| Google / Firebase (Authentication, Firestore, Cloud Functions, Crashlytics, Performance, Analytics, Cloud Messaging, Remote Config, App Check) | Identity, routing backend, diagnostics, analytics, notifications |
| Google Maps Platform | Search, routes and Google turn-by-turn navigation |
| Apple | Maps, routing, push delivery, payments |
| Yandex | Yandex maps, routes and turn-by-turn navigation |
| Amplitude, Inc. | Analytics and session replay |
| RevenueCat, Inc. | Subscription status |
We keep each kind of data only as long as it is useful for the purpose it was collected for:
| Data | Kept for |
|---|---|
| Analytics events (Firebase, Amplitude) | Up to 14 months |
| Session replay recordings | Up to 30 days |
| Crash and error reports | Up to 90 days |
| Route comparison records (coarsened, as described below) | Up to 90 days |
| Support tickets and our replies | Up to 24 months |
| Your identifier and push token | Until you ask us to delete them, or the app is uninstalled and the token expires |
| Recent searches and saved places | On your device only, until you clear them in Settings or delete the app |
One record per route comparison is kept on our own server, so that we can see how much the app is used and how accurate each map's estimate turned out to be. It holds your identifier, the start and destination rounded to about a kilometre, the distance, the estimated durations and the name of the main road — not your precise addresses and not a continuous trace of where you drove. Your position during navigation is never sent to us; it goes only to the map provider whose guidance you are following.
Depending on where you live you may have the right to ask for a copy of your data, to have it corrected, or to have it deleted. Because we hold no name or email address, we cannot look you up by either — a request has to carry the app's own identifier for you.
The app makes the request for you: Settings → Help & Support, where “Request a copy of my data” and “Delete my data” each send the identifier along with the request and give you a reference. You can also write to info@navigationpro.app — quote a reference from an earlier request if you have one, because without it there is nothing for us to match you by. Either way we will respond within 30 days.
You can also switch most of this off without asking anyone: turn off notifications or location in iOS Settings, turn off Trip & Traffic Alerts in the app, and clear your recent searches and saved places under Settings → Privacy.
Under Turkish law (KVKK) the data controller (veri sorumlusu) is Navigation Pro, reachable at the email address above.
The legal bases we rely on under the GDPR are:
Transfers outside the EEA — to Google, Apple, Amplitude and RevenueCat in the United States, and to Yandex in Russia — happen because those providers are what the app is built on. You have the right to complain to your local supervisory authority.
Navigation Pro is not directed at children and we do not knowingly collect data from anyone under 13.
If this policy changes materially we will update the date at the top and, where the change affects what is collected, say so in the app.