Privacy Policy
Last updated: October 27, 2026
Overview
MapsToGPX converts a Google Maps directions URL into a GPX file. There are no user accounts, no sign-up, and no login — you paste a URL and get a file back. This page explains exactly what data is processed to make that happen, and what we deliberately don't collect.
Converting a route
When you paste a URL and click Convert:
- If you pasted a short link (
goo.glormaps.app.goo.gl), our server follows the redirect to expand it to a full Google Maps URL before doing anything else. That request goes to Google's redirect servers. - The URL is parsed on our server to extract the stops, travel mode, and route options it encodes. Any stop that's a place name or address (rather than a pin with coordinates) is looked up using OpenStreetMap Nominatim, a free geocoding service, to turn it into coordinates.
- The resulting coordinates are sent to the Google Directions API to calculate the exact route (roads, turns, distance) — the same routing engine Google Maps itself uses.
- The GPX file is generated from that route and returned directly to your browser. We don't store your routes, URLs, or addresses in a database.
We do temporarily cache Google Directions responses (up to 24 hours) and geocoding results (up to 7 days) so that converting the same route twice doesn't burn through Google's or Nominatim's request quotas. Cache entries are keyed by a one-way SHA-256 hash of the rounded coordinates, travel mode, and route options (or the normalized address text, for geocoding) — not by anything that identifies you — and expire automatically. This cache lives in Vercel's shared Runtime Cache plus a small, bounded in-memory cache on the server.
Rate limiting
To keep the service available for everyone, requests to convert a route or resolve a short link are limited per IP address (10 per minute). Your IP address is read from standard proxy headers and held only in the server's memory to count requests in the current window — it's never written to a database, and the counter resets automatically.
Feedback
The optional feedback form lets you submit a star rating (1–5), a message, and/or an email address — all optional, though at least a rating or a message is required to submit. If you submit feedback, exactly those fields (rating, message, email) are stored in our database (Supabase/Postgres). Row-level security is enabled on that table with no public access policies, so only our server, using a private key, can read or write it. We don't attach your IP address or any other metadata to feedback submissions. A hidden field on the form helps us silently discard automated/bot submissions without storing them.
Analytics
We use Google Analytics 4 (measurement ID G-E4P5HTG25D) to understand overall usage. It only loads when the site is visited at maptogpx.com or www.maptogpx.com in production — not in local development or preview deployments. Google Signals and ads personalization are turned off. We only send a small, fixed set of events: a route was converted, a GPX file was downloaded, feedback was submitted, a donate link was clicked (with which link), and — if a conversion fails — a short error-category code (e.g. “rate limited” or “location not found”). We never send the URL you pasted, any address or coordinate, your feedback text, or raw error messages to analytics. Google Analytics sets first-party cookies on maptogpx.com (such as _ga) to distinguish visitors; see Google's partner sites policy for how that data is used, or install the Google Analytics opt-out browser add-on to opt out.
We also use Vercel Web Analytics and Speed Insights, which are cookieless and report aggregated traffic and page-performance metrics without identifying individual visitors.
No accounts
MapsToGPX doesn't have user accounts, logins, or passwords. The only cookies set on the production site are those set by Google Analytics (such as _ga) — see the Analytics section above for details. Vercel Web Analytics and Speed Insights are cookieless.
Donations
The donate links on the home page go to PayPal and Venmo, third-party payment processors. If you choose to donate, your payment is handled entirely by them under their own privacy policies — we only see that a donate link was clicked, not any payment or personal details.
Changes to this policy
If how this site handles data changes, we'll update this page and the “last updated” date above.
Contact
Questions about this policy? Use the feedback form on the home page.