Privacy

Privacy Policy

Last updated: August 5, 2026

Beautiful GPX (https://beautiful-gpx.com) is a free web tool to customize and export GPS tracks. This policy explains what data is processed, how, and why. It applies to the entire site, including the editor.

1. Data controller

The data controller is Léo C, developer and creator of Beautiful GPX, acting as an individual (no dedicated legal entity).

For any questions about your personal data, email contact@beautiful-gpx.com.

2. Summary

  • No account required: you can use the tool without signing up.
  • GPX / FIT file import: GPS coordinates are processed entirely in your browser. These files are not uploaded to our servers.
  • Strava connection (optional): your activities are fetched directly from the Strava API in your browser. An access token is stored locally on your device.
  • Audience analytics: we use Matomo to measure site traffic (page views, usage events).
  • Kilometer counter: on PNG export, only the total distance (in meters) is sent for a public aggregated counter, with no GPS coordinates.
  • Support form (optional): if you contact us from the editor, we receive your message and, when applicable, diagnostic data (screenshot, project configuration).
  • No data resale: your data is never sold or shared with third parties for advertising purposes.

3. Data we do not collect (normal use)

When you import a .gpx or .fit file, the file is read and processed locally in your browser. GPS coordinates, elevation, and related metadata do not pass through our servers for rendering or PNG export.

Track customization (colors, POIs, layers, basemap) and image rendering also remain client-side. On export, only an aggregated distance may be sent (see section 7).

4. Strava connection (optional)

If you choose to connect your Strava account, Beautiful GPX uses OAuth 2.0 to obtain read-only access to your activities (scope activity:read_all).

  • You are redirected to Strava to authorize access.
  • The authorization code is exchanged for an access token via a minimal technical service (/api/strava/token). This service returns the response to your browser and does not store your token on the server.
  • The access token is stored in your browser’s local storage (localStorage) under the key strava_access_token.
  • Calls to the Strava API (activity list, GPS coordinate download) are made directly from your browser to Strava’s servers.
  • You can disconnect at any time from the editor; this removes the token from your browser.
  • Processing of your Strava data is also governed by Strava’s Privacy Policy.

5. Garmin Connect (planned integration)

We plan to add an optional Garmin Connect connection, following the same principles as Strava: read-only OAuth authorization, activity retrieval in the browser, with no GPS track storage on our servers.

This section will be updated when the integration is available. Garmin data will then also be subject to Garmin’s privacy policy.

6. Audience analytics (Matomo)

We use Matomo, an analytics platform, to understand how the site is used (pages viewed, button clicks, language choice, etc.).

Matomo may set cookies or use similar identifiers. Collected data is aggregated and is not used to profile you for advertising.

You can block cookies in your browser settings. This does not prevent use of the editor.

7. Public exported-kilometers counter

On a successful PNG export, Beautiful GPX sends to our servers only a meter count for the visible tracks in the editor (POST /api/stats/km).

These values are summed to display a total on the homepage. No GPS coordinates, track files, or user identifiers are transmitted for this purpose.

8. Support form and diagnostics

From the editor, you can send us a message via the “Support & Diagnostics” form. Only in this case is some data transmitted to our servers:

  • Your email address (optional): used to reply to you.
  • Your message: description of the issue or suggestion.
  • Diagnostic data (attached automatically when possible): map screenshot, project configuration (including GPS coordinates of tracks loaded in the editor), app version, and browser type.

9. Local browser storage

Beautiful GPX uses your browser’s local storage to improve your experience:

  • beautiful-gpx-lang: language preference (French / English).
  • strava_access_token: Strava token, only if you connected.
  • hasSeenTutorial: first-visit tutorial flag.

You can clear this data at any time through your browser settings.

10. Third-party services

To display basemaps, your browser contacts map tile providers (e.g. OpenStreetMap and contributors, or other layers you select). These services may receive your IP address and standard technical information when tiles are loaded.

If you connect Strava, your browser communicates with Strava’s servers. If you use the support form, data transits through our email delivery service.

11. Purposes and legal bases

  • Tool operation: performance of the service you request.
  • Strava / Garmin connection: consent, given when you authorize OAuth.
  • Audience analytics: legitimate interest in improving the site and measuring traffic, respecting your rights.
  • Kilometer counter: legitimate interest in displaying an aggregated, anonymized usage indicator.
  • User support: legitimate interest in responding to your requests, or pre-contractual steps at your initiative.

12. Retention periods

  • GPS tracks (file import): in browser memory only, until you close the tab or clear it manually.
  • Strava token: kept in your browser until you disconnect or delete it manually.
  • Support messages: kept as long as needed to handle your request, then archived or deleted reasonably.
  • Kilometer counter: aggregated total kept as long as the feature is offered.
  • Matomo data: according to our instance configuration (typically a few months, aggregated data).

13. Your rights (GDPR)

Under the General Data Protection Regulation (GDPR), you have the right to access, rectify, erase, restrict, object, and data portability (where applicable).

To exercise these rights, contact us at contact@beautiful-gpx.com. We will respond within the timeframes required by law.

You may also lodge a complaint with your local supervisory authority (in France: CNIL).

14. Security

We implement reasonable technical measures to protect data sent via the support form (HTTPS, restricted access to the email service).

Beautiful GPX is deliberately designed to minimize collection: GPS track processing stays in the browser whenever possible.

15. Minors

Beautiful GPX is not specifically directed at children under 16. If you believe a minor has sent us personal data, contact us to request deletion.

16. Changes

This policy may be updated to reflect site changes (new features, third-party integrations). The last updated date is shown at the top of this page.

Questions about this policy: contact@beautiful-gpx.com