Privacy

Z-Maps Car runs entirely on the device. There is no account to sign in to, no server of our own, and no journey is uploaded anywhere.

What the app uses

• GPS location — to compute speed, identify the road you are on, and compare it to the limit. Processed on the device and not retained after the app closes.
• Trip figures — distance, time, average and maximum speed and overspeed count, stored in a database on the device so you can look back at them. The route itself is not stored, only the journey's totals. Delete one trip or all of them from the history screen.
• Speed limits you correct yourself — stored in a database on the device, readable only by your device.

What leaves the device

Exactly two things, and neither carries anything that identifies you.

• Map tile requests to OpenFreeMap. Each carries the coordinates of the map square to be drawn, exactly as a browser fetching map images does. No account and no journey accompanies it. Fetched tiles are cached on the device so they are not requested again.
• An ad request to our server, about once an hour. It carries the name of the display slot and how many ads to return — no GPS position, no journey, no device id and no identifier of any kind.

Advertising

The app carries an advertising corner. Worth stating plainly, because this is exactly where most other apps start collecting:

• Ads are not personalised. Every device asking for the same slot is sent the same set of ads and rotates them locally. There is no user profile, no interest segment and no behavioural targeting.
• There is no third-party ad SDK. No Google AdMob, no ad network. The app talks only to our own server.
• We count deliveries, not people. The server records how many times each ad was sent out per day, so advertisers can be given a report. That number belongs to the ad, not to any device or person.
• The server sees the request's IP address, as every web server does. It is used to block abuse and is not stored alongside the advertising figures.
• Tapping an ad leaves the app. A browser opens the advertiser's page, and from that point their privacy policy applies, not ours.

Permissions requested

• Location — required; without it the app can measure nothing.
• Foreground service — so the trip and the speed alerts continue when another app takes over the screen.
• Notifications — to show the 'Z-Maps Car is running' notification that a foreground service requires.

None of the following

No analytics SDK, no cross-app tracking, no third-party ad network, no data sold. The app contains no third-party code beyond the MapLibre mapping library.

Deleting data

All three things the app stores can be deleted from inside it: the map cache and your limit corrections from Settings, and trip history one journey at a time or all at once from the history screen. Uninstalling removes all three.