Legal
Privacy policy
This English version is a translation for information. If the versions differ, the German version is binding.
1. Controller
The controller for data processing on this website and in the Radrunde app is:
Simon Hübner
Roermonder Str. 397
41068 Mönchengladbach
Germany
Email: info@radrunde.app
2. Principle: this site does not track
This website is purely static. It sets no cookies, embeds no external scripts, fonts or analytics services and uses no tracking. There is no contact form and no user account.
3. Hosting and server log files
The website is operated on a self-managed server of Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany (server location: Helsinki data centre, Finland — European Union). Hetzner provides only the server infrastructure and has no access to the content of the data processed; we run and manage the web server and the log files ourselves. A data processing agreement pursuant to Art. 28 GDPR is in place with Hetzner.
When the website is accessed, the web server processes technically necessary access data (IP address, date and time, file requested, referrer, browser type) in server log files to deliver the site, ensure its technical operation and be able to detect attacks or errors. The legal basis is Art. 6(1)(f) GDPR (legitimate interests in secure, trouble-free operation). The log files are rotated automatically and deleted after 14 days at the latest.
To measure reach, we analyse the log files on the server with GoAccess. This produces aggregated statistics only (e.g. page views per day); IP addresses are anonymised for this purpose. No cookies and no scripts are used in visitors’ browsers; the statistics do not allow any conclusions about individual persons.
The same applies to the API subdomain api.radrunde.app, through which the
Radrunde app downloads map data (region packs), has loops calculated and saves or
retrieves shared loops: here too, server log files are created to the extent described
above (IP address, time, endpoint requested), which are deleted after 14 days at the
latest. What the app features transmit in detail is set out in section 4.
4. Privacy in the Radrunde app
The Radrunde app uses no user account, no third-party analytics or
advertising services and no cross-device tracking. Up to version 1.x, the
cycle network data is fully contained in the app; from version 2.0, the app downloads
it from our server api.radrunde.app and the loops are calculated there
(for details see the section “Route calculation, network data and shared loops” and
section 3). If the server is unreachable, the app calculates the route locally on the
device.
Your location is processed only locally on the device — to show your
position on the map and for navigation (in navigation mode also in the background). If
you choose your current location as the start point for a loop or a one-way route,
from version 2.0 the app transmits this one start coordinate to api.radrunde.app
to calculate the route and (from iOS version 3.6 and Android version 2.4) to
retrieve the weather at the start. If you request new ways during navigation via
“Another Way” (from iOS version 3.7 and Android version 2.6), it transmits your current
position. What the server stores of this and passes on is set out in the section
“Route calculation, network data and shared loops”. Beyond that, your location does not
leave the device. It is not transmitted to third parties; for the weather, Apple receives
from our server only a rounded grid point with no link to your device (see “Weather”).
Granting location access is voluntary and can be revoked at any time in the system settings.
To display the map, the app uses a map service: on the iPhone Apple Maps/MapKit, on Android devices the Google Maps SDK (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). When the map tiles are loaded, the respective provider receives the device’s IP address for technical reasons. The Google Maps SDK may also transmit diagnostic data and device identifiers to Google, including to the USA (third-country transfer on the basis of the EU-US Data Privacy Framework). This processing is governed by the respective provider’s privacy policy (Apple: apple.com/legal/privacy, Google: policies.google.com/privacy).
Route calculation, network data and shared loops (from app version 2.0)
From version 2.0, the app downloads the node network from our server
api.radrunde.app on first launch and with data updates. This creates
the server log files described above; no account is required and no
usage profiles are created. Once the network data has been downloaded, the app also
works without a connection: if the server is unreachable, it calculates loops locally on the device.
Route calculation. When you search for a loop, from version 2.0 the app
transmits to api.radrunde.app the selected start point (coordinate) and the
distance you want — for a one-way route from A to B, the selected destination
(coordinate) instead. The server uses this to determine the
sequence of nodes and sends it back; the app draws the course of the route locally. The
server log files contain only the technical access data from section 3 (IP address, time,
endpoint requested), which are deleted after 14 days at the latest; they do not contain
the content of the request (coordinates, distance).
Another Way (from iOS version 3.7 and Android version 2.6). If you
request new ways during navigation, the app transmits your current position, the
coordinate of the destination node, the remaining distance and the section of the planned
route you were last riding on to api.radrunde.app. From this, the server
calculates up to three new ways to the same destination and does not store the request;
it is not one of the stored route requests (see below). The server log files contain
only the technical access data from section 3; they do not contain your position.
Weather (from iOS version 3.6 and Android version 2.4). As soon as the app
suggests routes, it shows the weather at the start point. To do so, it sends the start
coordinate to api.radrunde.app. Our server rounds it to a grid of 0.05 degrees
(in NRW about 5.5 × 3.5 km) and uses this grid point to request the forecast from Apple
Weather (WeatherKit, Apple Inc.). Apple receives neither your IP address nor a
device identifier. The server keeps the forecast in memory for each grid cell until it
expires. It does not store the start coordinate for the weather, and the
server log files do not contain it. The legal basis is Art. 6(1)(f) GDPR
(legitimate interests in showing you the weather for the planned ride).
Stored route requests. So that we can improve the route suggestions, we store one record for each route calculation: a pseudonymous device identifier (see “Abuse protection”), the time, the start point (coordinate) and the nearest node, the region, the distance you want or, for one-way routes, the straight-line distance between start and destination, the suggested routes (node sequence and length) and, where applicable, which of them you select and whether you open the photo of a route (from iOS version 3.8). The record contains no name, no account and no IP address. The legal basis is Art. 6(1)(f) GDPR (legitimate interests in good route suggestions). There is currently no fixed deletion period; we keep the records for as long as they are necessary for this purpose.
Aggregated usage counters. To monitor server load, we keep daily totals with no reference to persons or devices: the number of route requests per region, start node, type (loop or one-way route) and distance class, and the number of cases in which the app fell back to local calculation. These counters contain no IP address and do not allow any conclusions about individual persons or devices.
Abuse protection (App Attest, Play Integrity). To ensure that only the genuine Radrunde app can access our server’s write interfaces, the app uses Apple’s “App Attest” procedure on the iPhone. In this process, your device creates a cryptographic key, the public part of which we store together with a counter and the time it was last used. On Android devices, the app uses Google’s Play Integrity API: it obtains a verification token via Google Play, which our server has evaluated by Google, and sends a randomly generated installation identifier along with it. The key or installation identifier serves to protect the API against automated abuse and as the pseudonymous device identifier of the stored route requests (see above); it does not identify you as a person and is not linked to any shared loop.
Anyone who actively shares a loop via a short link stores this loop (node sequence, coordinates of the nodes, optionally name and distance) on our server. This data contains no reference to persons or devices and remains stored permanently so that shared links stay valid. Favourites and saved loops that are not shared remain exclusively on the device.
5. Contact by email
If you write to us by email, we process the information you provide in order to handle your enquiry. The legal basis is Art. 6(1)(f) GDPR (handling enquiries), and for contract-related enquiries Art. 6(1)(b) GDPR. The data is deleted as soon as it is no longer necessary for the purpose.
6. Your rights
You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20), as well as a right to object (Art. 21 GDPR). To do so, please contact the controller named above.
7. Right to lodge a complaint
You have the right to lodge a complaint with a data protection supervisory authority, for example the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW).
Last updated: 16 October 2026