Data flows
Which data TapRun sends where.
Route calculation runs on the device. This page lists which data the app transmits anyway. The legally binding version is the privacy policy.
Data flows at a glance
| What | Where to | How long |
|---|---|---|
| Location for route calculation and navigation | Stays on the device. The app sends no coordinates to a routing server. | Not stored outside the device. |
| Path data and map (tiles) | From tiles.taprun.app, servers of e12.media at Hetzner in Finland. The requested tile identifiers reveal an approximate region. | The server access log keeps only time, status and duration, without IP address, URL or query. It rotates daily and is kept for 14 rotations. |
| Run history and settings | On the device only. Not in cloud backups, not on new devices. | Until the app is deleted. |
| Detailed diagnostics | On the device only, off by default. Switched on only for an agreed test. No automatic upload. | Locally, until you delete them. |
| Report a problem (optional) | Only after you deliberately press “Send”, to a service of e12.media at Hetzner in Finland. | At most 30 days on the server. Reports can be deleted and consent can be withdrawn. |
The tile identifiers of a map request reveal an approximate region. They go only to servers that e12.media operates itself.
Principles
Only what a feature needs
What is not needed for the map and navigation, TapRun does not collect.
Local wherever possible
Calculation, history, settings and map storage stay on the device.
No profiles
No advertising or interest profiles, no sale of personal data.
No advertising ID, no account
TapRun reads no advertising or hardware identifier and requires no sign-in.