Privacy policy

Last updated: 26 October 2026

This policy covers this website (openradlr.com) and the official OpenRadlr server (app.openradlr.com). OpenRadlr is open-source software that anyone can run: servers run by other people are their responsibility, not ours.

Who is responsible

Lethonium, contact details in the imprint.

The short version

Hosting

The website and the server run on a server rented from STRATO GmbH, Otto-Ostrowski-Straße 7, 10249 Berlin, Germany, who processes data on our behalf under a data processing agreement. The server and its data are in Germany; only what you send to Strava leaves it (see below).

This website

The website is static. To deliver a page, the web server processes your IP address, the requested page, the time, your browser and the referrer. The container logs this runs in are capped at 30 MB and overwritten as they fill.

We count visits with our own instance of Plausible Analytics, running on the same server in Germany. Plausible sets no cookies and stores no personal data: your IP address is only used to build a hash that changes every day, and is not stored. We see totals such as page views, referrers, countries and devices.

The app

In your browser: your name, weight, FTP, settings, known Bluetooth devices and your ride history (summaries of past rides, used to estimate your FTP and level) are saved in your browser's storage. While you ride, the ride and its photos are also saved there, so you can continue or save it after a crash; this copy is deleted when you finish or discard the ride, and offered for at most 12 hours. You can delete all of it by clearing the site's data in your browser.

On the server, while you ride: your name, weight, power, cadence, speed, position in the world, the route you ride and your chat messages are processed in memory, so that others can ride with you and the physics work. Other riders see your name, position, power and chat messages. If your connection drops, the server keeps your rider for about a minute so you can reconnect. Nothing of this is written to disk; it is gone when you leave or the server restarts.

Heart rate is health data. It stays in your browser: it is never sent to the server. It is part of ride files you download or upload to Strava.

Bluetooth devices (trainer, heart rate strap, controller) connect directly to your browser, not to the server.

Totals: the server counts the total distance ridden by everyone, and keeps aggregate numbers such as riders online for monitoring. These contain no names or other personal data.

Server logs record errors and events such as server start, plus your IP address when it opens too many connections at once and your Strava athlete ID when you connect Strava. They are capped at 30 MB and overwritten as they fill.

Analytics: if enabled for the official server, the app is counted with the same Plausible instance as this website (see above).

Strava (optional)

If you press Connect with Strava, Strava asks for your consent and sends the server your Strava athlete ID, your name and access tokens. To keep you logged in, the server sets two cookies that are needed for this and nothing else:

Cookie Purpose Kept for
openradlr_oauth_state protects the login against forgery 10 minutes, during the login
openradlr_session keeps you logged in to Strava 30 days

The server stores your login so it survives restarts: the session ID only as a one-way hash, your athlete ID and name, and the Strava refresh token encrypted. It is deleted when you log out, and after 30 days at the latest.

When you upload a ride, the ride file (time, power, speed, cadence, heart rate, elevation and positions in the virtual world, with a title you can edit) goes to Strava; from then on Strava's privacy policy applies. You can revoke OpenRadlr's access at any time in your Strava settings.

Links to other services

This website links to GitHub, the app and our Discord server; the app links to Strava. Nothing is loaded from them until you click a link; then their privacy policies apply.

Legal basis

We process data to provide the service you request (Art. 6(1)(b) GDPR), on the basis of our legitimate interest in a secure, working service and in knowing how it is used, in aggregate (Art. 6(1)(f) GDPR), and, for Strava and for the heart rate in an upload, with your consent (Art. 6(1)(a) and Art. 9(2)(a) GDPR). The Strava cookies are strictly necessary for the login you ask for, so they need no separate consent.

Your rights

You have the right to access, correct and delete your data, to restrict or object to processing, to data portability, to withdraw consent at any time (for Strava: log out and revoke access in your Strava settings) and to lodge a complaint with a data protection authority. Because we keep almost nothing, most requests are answered by "we no longer have it". Write to the address above.

Changes

When the app starts to process data in a new way, we update this page and its date first.