Analyse one ride. No account, nothing stored.
Choose a .FIT or .TCX file. Your browser opens it on your device, reads power, cadence, speed, distance, time and elevation, and sends only those number series to our server. The server computes the figures below and discards them. The file itself is never sent.
Depending on your device, the file also holds GPS coordinates, a device serial number and the real date and time of the ride. Coordinates and serial number are not read: the code that opens your file knows no field for them, so there is nothing it could send. The clock time of each sample is read, in your browser only, to work out the seconds between samples. What is sent is the time since the start of the ride, never the date or the time of day.
Nothing of this is written anywhere: no database, no disk, no account, no third party, no AI processing. Our server log notes only that a calculation ran, how many data points it had and how long it took. To keep the tool available we briefly count requests per source address in working memory; the application's counter holds a keyed hash, not the address, and expires within the hour. The request carries no cookie.
What these numbers are, and what they are not.
They describe what is in your file and nothing beyond it: a calculation on your own values. They are not a statement about your health, not medical advice, and not a medical device within the meaning of Regulation (EU) 2017/745. How you train is your decision. If something looks different from your usual, that is a conversation to have with a doctor. This page cannot have it.
- Pacing card for your route
The GPX of your event plus your Critical Power becomes watt targets per climb and a time range, ready to print for the top tube.