TapRunPrivacy
Which data TapRun sends where.
A running app needs your location. That is why this page spells out exactly what happens with it. The legally binding version is the privacy policy.
Data flows at a glance
| What | Where to | How long |
|---|---|---|
| Location for route and navigation | On the device. For the route search, coordinates go to e12.media’s routing service at Hetzner in Finland. | 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. |
| Map and tiles | From tiles.taprun.app. The requested tile identifiers reveal an approximate region. | Access logs rotate daily and are kept for 14 rotations. |
| Run history and settings | On your device only. Not in cloud backups, not on new devices. | Until you delete the app. |
| 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 run by e12.media at Hetzner in Finland. | At most 30 days on the server. You can delete reports and withdraw consent. |
One special case remains: a route request contains coordinates, and coordinates can be personal data. That is why they go only to services that e12.media operates itself.
Our rules
Only what a feature needs
What is not needed for route, map and navigation, we do not collect.
Local wherever possible
History, settings and map storage stay on the device.
No profiles
We do not sell personal data and do not build advertising or interest profiles.
No advertising ID, no account
TapRun reads no advertising or hardware identifier and requires no sign-in.