Skip to main content
viewmygpx

Contact

viewmygpx has one address: hello@viewmygpx.com. There is no contact form, no support portal, no ticketing system, no chat widget. We are a small group of off-road hikers and cyclists who run the site in our spare time, and a single inbox is the most honest way to handle correspondence.

We read every message that lands there. We reply when a reply is helpful — when you have asked a question we can answer, flagged something we can fix, or proposed something we want to discuss. We don't reply just to acknowledge receipt, and we don't promise a specific turnaround. The next two sections describe what we especially want to hear about, and what makes a message easy to act on.

What we welcome

Anything that helps us make viewmygpx more useful or more accurate. Specifically:

  • Factual corrections. If a guide page says something wrong about the GPX format, about a platform's import behavior, about a device's file path, about a converter's output — tell us. Mention the URL and what is wrong. We treat corrections as high-priority because a wrong page is worse than a missing page. The editorial policy covers how we handle corrections, including when we add a visible note to the page.
  • Bug reports. Files that the viewer mishandles, edits that don't round-trip, conversions that drop data, broken interactions, layouts that crack at certain widths, screen-reader or keyboard-navigation breakage. Specifics in the next section.
  • Accessibility issues. Anything that gets in the way of using the site with a screen reader, keyboard, voice control, magnifier, or reduced-motion setting. Put "accessibility" in the subject and the report will be triaged the same way as a functional bug. Background and limitations are on the accessibility statement.
  • Privacy questions. If something about how the site handles data is unclear or seems wrong. Put "privacy" in the subject. The full policy is at privacy policy; the inbox is for things the policy doesn't answer.
  • Feature requests. A converter pair we don't handle, a metadata field the editor should expose, a stat the panel should compute, a sample file you wish we shipped. We can't promise we'll build any specific request, but we read all of them and they shape the roadmap.
  • Partnership inquiries. Genuine integrations with other tools that handle GPX, mutual-link partnerships with legitimate trail or platform sites, or platform contacts who want their import path documented accurately. Put "partnership" in the subject. We do not accept paid placements, sponsored content, or affiliate-link insertions in exchange for editorial coverage.
  • Press and research. Journalists working on format-portability, GPS-data, or open-mapping stories; researchers studying outdoor-activity datasets; podcast hosts. Put "press" in the subject. We are happy to talk about why GPX remains the open standard, the practical limitations of GPS data, and the case for client-side processing of personal location data.
  • Notes from teachers and instructors. If you use the tool with a class — geography, GIS, outdoor education, computing — we want to hear about it. We may add classroom-friendly notes or example files based on what you tell us.

What helps us help you

A useful message names the specific thing. Vague reports waste your time and ours. The pattern that gets the fastest response:

  • The URL. Which page are you on? A copy of the URL settles it instantly.
  • What you tried. "I dropped this file on the viewer and the elevation profile is empty" is far more actionable than "the elevation profile is broken."
  • What you expected vs what happened. If a converter dropped a field, tell us which field, and what you expected the output to contain.
  • The file (if relevant) or a small reduced version. A GPX file we can't reproduce against is a guess. If the file has personal data, you can usually trim it to a few trackpoints that still trigger the bug. We do not retain attachments beyond what is needed to reproduce and fix.
  • Your browser and OS. "Chrome on macOS" or "Firefox on Windows" is enough. For mobile, the device model is helpful since touch-handler bugs are common.
  • Assistive tech, if relevant. Screen reader name and version, voice control software, keyboard-only navigation.
  • A screenshot, when it's a layout or visual issue. Annotated arrows or circles save back-and-forth.

You don't need all of this — a one-line bug report with a clear URL is welcome. The list is what makes a hard bug solvable, not what we require to read your message.

What we don't do

  • Account support. There are no accounts on viewmygpx, so there is nothing to recover, reset, or restore. If you are looking for help with your Strava, Komoot, Garmin, or AllTrails account, those platforms run their own support; we cannot reach into your account from outside.
  • Recover lost files. Because GPX files never reach us, we cannot retrieve a file you closed without saving. The architecture that protects your privacy also means there is no backup to ask us for.
  • Fix data on third-party platforms. If your route imported into Strava with the wrong stats, or Garmin Connect rejected a file, we can usually explain why — but we can't edit the data on the destination platform. That is the destination's job.
  • Provide individualized navigation advice. We can help you read a GPX file. We can't tell you whether a specific route in a specific season under specific conditions is safe for you. The disclaimer covers the shape of that limit.
  • Sponsored content, paid links, or affiliate placements. We don't accept them, so a pitch in that direction will not get a reply. Real integration proposals are different — see above under partnerships.

Response time

Honest answer: it depends. Some messages get a same-day reply because we're at our keyboards and the question is quick. Others wait — sometimes a week or two — because the people who can answer are away from their screens, on a trail, or thinking through something non-trivial.

We are not a support team and we don't promise an SLA. What we do promise: every message is read, factual corrections are addressed in the order they come in, and we don't silently drop things on the floor. If your message is time-sensitive (a press deadline, a class starting tomorrow), say so in the subject line and we will do our best.

What we don't ask you to send

Don't send personal information that isn't needed to answer your question. Don't send credentials. Don't send copyrighted material that isn't yours. If you are forwarding a bug report on someone else's behalf, ask their permission first before sending us their file.

We do not ask for, and do not want, payment-card numbers, government IDs, account passwords, or social-security/insurance numbers — none of those are useful to us and none are appropriate to send to an inbox like this.

Where to go for what

For background on the choices behind a specific area of the site, these pages are usually a faster answer than an email:

The address, again

hello@viewmygpx.com. Plain English, specific subject line, and we'll take it from there.