FitFixer is a free tool for fixing GPS glitches in FIT files. This page explains what data is processed and how.
Uploaded FIT files are stored temporarily (max 24 h) and automatically deleted. FitFixer does not share your file or its contents with any third party. No account or personal data is required to use the tool.
If you choose to upload a fixed file to Strava from the results page, FitFixer requests only the activity:write scope — the minimum required to upload that one file on your behalf. The access token is used once for the upload and is not stored.
Connecting your account to the Strava Locality Explorer is a separate, longer-lived authorization using the activity:read_all,activity:write scope. It's used to list your existing Strava activities and read their GPS tracks so each ride can be checked against OpenStreetMap boundary data to see which cities, towns, and villages it crossed, and — only if you click Update on Strava — to write the recognized places into that activity's title or description. Your Strava OAuth tokens are encrypted and kept so the connection survives between visits, but your raw GPS track itself is never stored — it's only used in memory while an activity is being analyzed. If you tick Save recognized localities to my FitFixer history when connecting (or later, from the Locality Explorer page), FitFixer additionally stores the activity id, name, date, and the recognized locality names/types/distances — never your GPS track — so you can review a localities/regions dashboard later. This is checked by default when connecting, but you can switch it off at any time.
The Get corrupted activity from Strava button next to the upload area uses the same connection as the Locality Explorer above to list your 5 most recent activities and read the GPS stream of the one you pick. FitFixer rebuilds a raw FIT file from that data and runs it through the normal fixer — the result is stored the same way, and for the same length of time, as a file you upload directly (see "What data is processed" above). Nothing about this is saved to your FitFixer history, regardless of the save-to-history setting described above.
You can revoke access to any of these flows at any time in Strava → Settings → My Apps. For the persistent connection specifically (used by both the Locality Explorer and the Strava-fetch picker), clicking Disconnect on the Locality Explorer page also deauthorizes it and deletes your stored OAuth tokens immediately; any locality history you'd already saved is kept so it's still there if you reconnect later — email us (below) if you'd like that history deleted too.
EN
UA