Skip to content

50,000 free calls a month, card-free. Get an API key →

MapMap Nav

MapMap Nav privacy policy

Last updated: 11 August 2026

MapMap Nav is built so your location never has to leave your phone: with a downloaded territory, routing, guidance, voice and search all run on the device. Online features send only what section 6 lists, and nothing is kept as a history of you. This page covers the app specifically; the hosted API and this website are covered by the main privacy policy.

1. The short version

With a downloaded territory, navigation, routing, voice guidance and search all run on your device, and your GPS position, routes and search queries are never sent to us or to anyone else. In that mode the app's only network requests are downloading map data and verifying your licence key.

The app also has online features: online maps, routes computed by our hosted engine with landmark instructions, live traffic, safety-camera alerts. Using them sends specific, listed things to api.mapmap.ai (section 6), each used to answer that request and none kept as a location history tied to you.

In both modes: we do not track you, we do not build a location history of you, and we do not sell or share data with advertisers. There is no analytics SDK and no advertising identifier in the app.

2. Location

MapMap Nav asks for “While Using the App” location access so it can show your position on the map and guide you turn by turn. That position is read directly from your device's location services, used only to render your position and compute guidance locally, never transmitted to MapMap or any third party, and not stored once you close the app. No location history is kept.

The app does not request background location. It does not follow you when it is closed or not in use.

If you decline location access, MapMap Nav still works fully. Your position simply is not shown, and you can search and preview routes as normal.

3. Search queries and destinations

Searching for a place and setting a destination happen entirely against the map data stored on your device, in the territory you downloaded. Search terms and destinations are not sent anywhere.

4. Territory downloads

To work offline, MapMap Nav downloads a territory: the map, routing and search data for a region you choose, such as the UK, from api.mapmap.ai. This is a one-off download, with occasional updates. It is a request for map data, not a report of anything about you.

The request includes your licence key so we can verify your download allowance. It does not include your location, your search history or your routes.

5. Licence key verification

MapMap Nav carries a licence key used to verify the app is entitled to use the MapMap SDK and to enforce fair-use download limits. Verifying that key is the only other network call the app makes. It confirms the key is valid and checks the remaining allowance, and carries no personal or location data.

6. Online features, and exactly what each one sends

Online maps. With no territory installed (or the map source set to Online), map tiles and styles are fetched from our servers as you pan and zoom. Like any online map, a tile request implies the area you are looking at; tile requests are not logged against your identity as a browsing history.

Hosted routes. In Online mode, when you ask for a route the request sends its origin and destination (and your position again if you go off-route and it recomputes) to our routing engine. That is what makes landmark instructions possible, like “Turn right just after the Shell garage”, and real turn-lane guidance. The route comes back, and the request is not stored against your identity; our servers keep only a de-identified demand log with coordinates truncated to roughly 5 km cells and no key, account or IP attached, as described in the main MapMap privacy policy.

Faster-route checks. During guidance with a connection, the app periodically re-asks the routing engine whether a faster route exists from roughly where you are to your destination. Same data, same handling, as a hosted route request.

Safety cameras. When camera alerts are on, the app sends the route's geometry (the line of the planned route, not your live position) to fetch the fixed safety cameras along it.

Live traffic. The traffic overlay downloads country-wide traffic files with fixed names. The request carries no location, no route and no query; turning traffic on reveals nothing about where you are. It is off by default.

Every one of these degrades silently offline, and none of them runs at all when you navigate on a downloaded territory without a connection.

7. What the app does not collect

No account and no sign-in. No advertising identifiers. No analytics SDK. No crash reporting. No contacts, no photos, no microphone and no camera access. No background location tracking: the app never reads your position when it is closed or not in use.

8. Voice guidance

Spoken turn-by-turn directions are generated and played entirely on your device, using the operating system's own text-to-speech engine. Nothing about your journey is sent anywhere to produce voice guidance.

9. Data retention

Offline journeys leave nothing on our servers to retain or delete. Online route requests are answered and dropped; what persists is the de-identified ~5 km demand log described above, which cannot be traced back to you. Territory files and your licence key are stored locally on your device, and are removed when you delete the app or remove a territory in Settings.

10. Children's privacy

MapMap Nav is not directed at children, and does not knowingly collect personal data from anyone of any age, as set out above.

11. Changes, and who to ask

If this policy changes we will update the date above and, for any material change, note it in the app's release notes.

MapMap Nav is published by MapMap AI Ltd, registered in England and Wales (company 17345596), trading as MapMap. Questions about this policy or how the app handles data: hello@mapmap.ai.

Anything unclear, or a request about your data: hello@mapmap.ai.