Privacy

Two purposes, kept apart

Your file is processed for two things, and they rest on different legal footing.

• Analysing your run — Art. 6(1)(b) GDPR. You upload a file in order to get an analysis; the processing is the service you asked for.
• Improving the course profiles — Art. 6(1)(f) GDPR. Your run becomes a contribution to the elevation profile of the course you ran. Our legitimate interest is a more accurate profile for everyone; your interest in confidentiality is protected by the contribution containing nothing that leads back to you. What is technically enforced to that end is in the next section.

What is read from the file — and what is not

A watch writes far more into a FIT file than a running analysis needs. On reading, heart rate, heart rate variability, power, cadence and step length are therefore discarded before anything computes with them. They are not filtered, not anonymised and not briefly cached — they are not taken in.

What is processed is time, distance, elevation and the pace that follows from them, and nothing else.

Heart data is health data under Art. 9 GDPR. It could not be justified on a legitimate interest, and we do not want it.

How the contribution to the course profile is made

The contribution is made in a fixed order, and the order is the point:

• First we check whether your track lies on a checked course at all. If it does not, no contribution is made.
• Then the start and the end that are not on the course are cut off — the way to the start and the way away from the finish. Those two stretches say the most about you and the least about the course.
• Only from what remains is anything taken, and only elevation over course distance: a series of the form “at kilometre 12.35 the watch was at 48.2 metres”.

What does not end up in the course profile

The stored contribution holds no coordinates, no timestamps, no reference to your upload and no reference to your analysis. Besides the elevation series it holds only the year of the race, a measure of the noise in the recording, the quality of the match, and an identifier that recognises the same file again without being reversible into it.

Neither a person nor an individual run can be reconstructed from a contribution.

What is stored in your analysis

Your analysis is a different thing from the contribution to the course profile, and it is yours. What is stored is your times per kilometre and per mile, the figures of the run, and — so the map can show something — your route as a line with elevations, thinned to one point per 50 metres and without timestamps.

It is reachable only through the link you get after the upload. There is no account and no index; anybody without the link will not find it.

At the upload you can also say which race it was and in which year. Both are optional, and both describe the event rather than you: this site asks for your name nowhere.

Deletion

• The original file: deleted after the analysis. It is never written to a disk for that purpose, only held in the memory of the request. A cleanup job removes anything that is left behind against expectation, at the latest after 48 hours.
• The analysis: kept for 90 days, then deleted automatically. Before that, whenever you like: every analysis page carries a delete button, and it is gone immediately and for good. The date is printed on the analysis page, so you do not have to remember it.
• The contribution to the course profile: stays as long as the course is unchanged. When a course is re-routed, the contributions of the older editions are removed.

Right to object (Art. 21 GDPR)

You may object at any time to the processing for improving the course profiles, which rests on legitimate interest — without giving a reason and without a deadline. We then take that contribution out of the course profiles and exclude it permanently, so that it does not return if the same file is uploaded again.

The quickest way is the link to your analysis: it identifies the run unambiguously without you having to tell us anything else.

Analytics

Vercel Analytics, without cookies and without recognising you across visits. What is recorded is the page view, the referring page, country, device type and browser — none of which reconstructs a person or a history. That is also why there is no consent dialog here: nothing is stored on your device that would need one.

Contact

For objections, access requests and deletion: guenther_matzinger@gmx.at