Settings Login to GpxFix using your Strava account

GpxFix Blog

How to Anonymize a GPX File Before Sharing It Online

By on . Last updated .

Every time you post a run or ride to a public platform, you are potentially publishing a precise map of where you live, where you work, and the routes you travel most often. GPX files are even more explicit than the activity view on Strava — they are plain XML documents containing every recorded coordinate, timestamp, and sometimes device identifiers. Stripping the sensitive portion of a track before sharing is a straightforward step that most people never think to take until something goes wrong.

What information a GPX file exposes

A raw GPX export from your watch or phone typically contains:

  • A sequence of track points, each with an exact latitude and longitude, recorded every one to five seconds.
  • Timestamps for every point — meaning an observer can deduce not just where you live, but what time you leave home each morning.
  • Elevation data, heart rate, cadence, and power if your device recorded them.
  • Device name or creator metadata embedded in the file header, which may identify your specific unit.

When you share that file on a forum, attach it to a route planning tool, or make a Strava activity fully public, all of that data travels with it.

The privacy zone approach versus full anonymization

Strava offers a built-in privacy zone feature that hides the start and end of activities within a defined radius of a saved address. This is convenient but has important limitations:

  • It only applies to activities viewed on Strava. If you export the GPX and share it elsewhere, the full track including your home coordinates is present in the file.
  • Privacy zones can be inferred or brute-forced by someone who knows the general area and has enough of your public activities to triangulate the hidden centre point.
  • It does not help at all for files shared on third-party platforms, route directories, or attached to emails and forum posts.

Physically removing the track points near sensitive locations — before the file ever leaves your device or computer — provides a much stronger privacy guarantee because the data simply does not exist in the file.

How much to remove

There is no universal answer, but a practical starting point is to remove enough of the route that the nearest remaining track point is at least a few hundred metres from any address you want to protect. On a residential street, three to five minutes of walking or running typically covers 300–600 metres — enough to make the precise source location ambiguous. For cycling the same time covers considerably more distance, so think in metres rather than minutes.

Tip: After trimming, open the edited file and zoom in on the new start and end points on the map. Check that neither point sits on a recognisable driveway, car park, or building entrance that would still identify the location even without the surrounding track.

Step-by-step: trimming a GPX file with GpxFix

1) Remove the approach to your home from the start of the track

Scenario: Your morning run starts from your front door. You want the public track to begin at the end of your street.
Workflow with GpxFix:
  1. Load the GPX file and watch the dot move along the map as you drag the timeline slider.
  2. Pause the slider at the point where the route reaches a public location you are comfortable sharing — a junction, a park entrance, a bus stop.
  3. Note the track point number shown in the interface.
  4. In the crop/cut panel, enter that track point number in the End of section to remove field and leave the other field empty — this removes everything from the very beginning up to that point.
  5. Click Remove and verify the new start location on the map before exporting.

2) Remove the return leg to your home from the end of the track

Scenario: Your ride finishes back at your garage. You want the public track to end at the same junction where the shared portion started.
Workflow with GpxFix:
  1. Drag the timeline slider near the end of the session to find where the track re-enters your privacy area.
  2. Note that track point number.
  3. Enter it in the Start of section to remove field and leave the end field empty — this removes everything from that point to the final recorded position.
  4. Click Remove and check the new end point on the map.

3) Trim both ends in one session

Scenario: An out-and-back run that starts and finishes at home — you want to hide both ends.
Workflow with GpxFix:
  1. Use GpxFix's ability to apply multiple crop/cut operations in sequence.
  2. First, remove the opening section as described above and export the intermediate file.
  3. Re-load the intermediate file and then remove the closing section.
  4. The final exported file has sensitive location data removed from both ends.

Remove personal sensor data with the Strip feature

Location data is not the only private information in a GPX file. Heart rate, cadence, power, and timestamps can reveal health conditions, fitness levels, and your daily schedule. GpxFix's Strip feature lets you selectively remove these data streams before sharing a file, without touching the GPS coordinates themselves.

What the Strip feature can remove

  • Timestamps and speed data — removes all <time> elements from track points. Useful when you want to share a route shape without revealing when or how fast you travelled it.
  • Heart rate — removes heart rate extension elements. Heart rate data can be sensitive as it may indicate a medical condition or fitness level.
  • Cadence — removes cadence extension fields that some devices record automatically.
  • Power — removes power output readings often present in cycling files.
  • Elevation — removes <ele> values when altitude data is not relevant or could be used to infer a specific location.
  • Temperature — removes ambient temperature readings when present. Note that stripping all data preserves temperature by default; select the Temperature option explicitly to remove it.
  • Metadata — removes the top-level <metadata> block and strips name, description, and link fields from track elements. Activity titles sometimes contain personally identifying information such as a home address, gym name, or workplace.

Strip all versus selective stripping

Choosing Strip all removes every sensor stream in a single step and is the fastest way to produce a coordinate-only file. If you only need to hide one category — for example, keeping elevation for a route-planning audience while removing heart rate — tick only the relevant options. Unused extension wrapper elements are cleaned up automatically so the output is a well-formed, minimal GPX file.

Example — sharing a route publicly without personal health data:
  1. Load your GPX file into GpxFix.
  2. Select the Strip data operation.
  3. Tick Heart rate, Cadence, and Power.
  4. Optionally tick Timestamps if you also want to hide pacing information.
  5. Click Apply and export the resulting file. The coordinates and elevation profile are preserved while the health metrics are gone.

Combine the Strip feature with the Crop/cut feature described above for the most thorough anonymization: crop the sensitive start and end of the track, then strip any remaining personal sensor data before sharing.

Other metadata to be aware of

  • File creator tag: some devices write a <creator> attribute in the GPX header that includes the device model and serial number. This does not expose your location but does identify your hardware. If that concerns you, it can be removed with a plain text editor.
  • Waypoints and route names: if you have named waypoints (e.g., "Home", "Office") embedded in the file, check those are removed before sharing.
  • Timestamps: even with location points removed, timestamps reveal your daily schedule. Strava's segment leaderboards expose relative times, but the raw GPX timestamps are absolute. If temporal privacy matters, consider whether the file needs to be shared at all rather than just linked from an activity URL.

A note on Strava privacy settings versus file-level privacy

Editing the GPX file is the only method that protects your location regardless of where the file ends up. Platform privacy controls — Strava's privacy zones, followers-only visibility, mute-from-activity-feeds — are valuable, but they operate at the platform level and do not alter the underlying file. Anyone who obtains the raw GPX through any channel will see the unmodified coordinates. File-level trimming is therefore the more durable approach, especially for routes you intend to share broadly on route libraries, challenge pages, or community forums.

Closing thoughts

Sharing routes and activities is a natural part of training with a community, but there is no reason that sharing has to include a precise map of your home address and daily schedule. A couple of minutes spent trimming the sensitive ends of a track before export is a straightforward habit that meaningfully reduces the information you broadcast with every shared workout. GpxFix makes that trimming fast and precise — load your file, identify the points you want removed, and export a clean version that shows the route without revealing the destination.

Other blog posts

Share to