Contact Us

How to reach us

Email hello@gpsspeedometer.bond. There is no account to create and no contact form that stores your message on a server first — this page uses a simple mailto link so your email goes directly from your mail app to us. Tap the email button on this page and your mail client will open with the address filled in. If the button does not open a client (for example on a shared computer), copy the address manually into your preferred email app. Please use a subject line that summarizes the issue, such as “Weak GPS on train — Android Chrome” or “Suggestion: average pace display”.

What to include for the fastest help

A short, specific report lets me reproduce and fix issues much faster. Where relevant, please include:

• Device and OS — for example, Pixel 7 on Android 14, iPhone 13 on iOS 17, or Windows 11 laptop.
• Browser and version — for example, Chrome 126 on Android, Safari 17 on iOS, Firefox 128 on desktop.
• Page and language — for example, /car-speedometer/ in English or /hi/train-speed-test/ in Hindi.
• What you expected vs. what you saw — for example, “expected live speed outdoors, saw Searching for 60 seconds”.
• GPS context — were you outdoors with open sky, near a window, indoors, in a tunnel, in a moving train, car, bike, or boat? What did the accuracy badge show (±8 m, ±35 m, searching)?
• Steps to reproduce — what you tapped before the issue (Start, Pause, unit switch, keep-awake toggle).
• Screenshot if possible — a screenshot of the readout and any banner helps more than a long description.

You do not need to include precise coordinates to get help, and I will never ask for them as a first step. If location context is genuinely needed to diagnose a smoothing issue, I will explain why and ask explicitly — you can always decline.

What I can help with

I welcome every constructive message, and I prioritize in this order: breakage and safety wording first, then accuracy confusion, then feature ideas.

• Bug reports — the tool does not start, permission help does not match your browser, numbers freeze, units do not switch, or the page is unreadable on your device.
• Accuracy questions — the readout jumps, stays at zero while moving, or disagrees strongly with a vehicle dashboard on open road at steady speed.
• Privacy questions — how location, analytics, cookies, or ads work on this site, or a request related to an email you sent.
• Content corrections — a factual error, outdated browser steps, or unclear wording I should fix.
• Feature suggestions — for example, a new unit, a clearer weak-signal message, or a more helpful FAQ. I cannot promise every idea, but I read and consider each one.

What I cannot do

To keep expectations honest: I cannot provide legal, driving, marine, or aviation advice, certify your speed for any official purpose, or interpret traffic law for your country. I cannot recover a past trip or export a history file because the site deliberately stores no location trail — once you close or reset the tab, that session is gone by design and there is nothing on a server to retrieve. I also cannot offer phone or live-chat support; as an independent developer, direct email is the sustainable channel that keeps this tool free and privacy-respecting.

Response time and how messages are handled

I aim to reply within a few days, often sooner for clear bug reports. There is no large support team — replies come from Bhagya Masalawala, the developer and creator of the site. Every report is handled privately and is never published. If you report a bug that I can reproduce, I will confirm the fix and update the affected page with a new review date. If your suggestion is adopted, it will appear in a future update; if not, I will briefly explain why (for example, it would require storing location or adding a heavy third-party script that conflicts with the privacy promise).

Privacy note — contacting us

This contact method is intentionally minimal. Because there is no server-side form, no message is stored on our server before it reaches us — your email lives only in your outbox and our inbox under our email provider’s standard handling. Do not include passwords, precise home coordinates, or other sensitive personal data in your email. Any personal information you choose to share is used only to answer your message and is never sold, never used for ad targeting, and never published. See the Privacy Policy for how the site itself handles location, analytics, cookies, and advertising separately from email correspondence.

Before you write — quick self-checks

Many GPS issues resolve without an email. If the readout says Searching or Weak, try these first and mention what you tried:

• Move outdoors or next to a window with a clear view of the sky and hold the phone steady for 20–30 seconds while the accuracy badge settles.
• Check that Location Services are on at the OS level and that your browser is set to Allow for this site, then reload and tap Start again — the on-page permission guide shows steps for Chrome, Safari, and Android.
• Judge average speed over 10 or more seconds rather than instant spikes, especially on trains or in cities where fixes arrive unevenly.
• Turn the screen-brightness down and close other heavy apps if the phone is hot — thermal throttling can slow GPS updates.

If the problem persists after those checks, email me with the details above and I will investigate. Thank you for helping improve GPS Speedometer for everyone.