Privacy Policy

Who we are

This site is operated by Bhagya Masalawala, an independent web developer who builds useful online tools and resources. There is no large company, data broker, or ad-tech subsidiary behind GPS Speedometer. If you have any privacy question, you contact the same person who writes the code and the content: hello@gpsspeedometer.bond (see the Contact Us page). This policy applies to all pages on gpsspeedometer.bond, including the home page, tool pages (train, bike, car, boat, converters, explainer), and the information pages (About, Contact, Terms, Disclaimer, Privacy itself), in all languages.

Location data — stays on your device

Location data is processed entirely client-side, is never transmitted to or stored on any server operated by us, and is not retained after the browser tab closes. When you tap Start and allow location, your browser's Geolocation API (navigator.geolocation.watchPosition) delivers coordinates, speed where available, and accuracy directly to JavaScript running in your browser. Those numbers are used only in memory to compute current, average and maximum speed, distance, and elapsed time for the current session. They are never sent to us, never written to a database, never included in analytics payloads, and never shared with advertisers. Close, reload, or reset the tab and they are gone. Deny or dismiss the permission prompt and nothing is collected at all — the tool simply shows a help block explaining how to enable location if you change your mind.

No account, no stored trail

There is no account, no login, no signup, and no stored trail. Your trail lives only in memory for the current session. Reset or close the tab and it is gone. We do not have a server-side copy because there is no server side for location — the GPS engine is a small client-side module and the site is served as static files. That also means there is nothing to export, transfer, or delete on request for location history: there is simply nothing retained to provide. If you email us (see Contact), that email is handled as correspondence, not merged with any location record, because no such record exists.

What analytics does — and doesn't — do

To understand which pages are useful and fix broken experiences, I use privacy-respecting pageview analytics. Two systems may be present, both limited to standard pageview/route analytics and both with no access to your coordinates:

• Plausible Analytics (cookie-less): counts pageviews by URL path (for example /how-fast-am-i-going/), referrer, browser language, device type and viewport size, plus an anonymized daily hash derived from IP + User-Agent. The raw IP is discarded, never stored; the hash rotates daily and cannot track you across days or sites. No cookies are set by Plausible and no cross-site fingerprint is built.
• Google Analytics 4 (GA4, ID G-GWEGJX9PE1, loaded lazily on idle): counts pageviews and basic engagement the same way Google documents for GA4 — page path, referrer, language, device and OS. Unlike Plausible, GA4 may set first-party cookies (such as _ga) to distinguish sessions. Those cookies contain random identifiers, not coordinates, speed, or personal names.
• What is NEVER sent to either system — explicitly never collected or transmitted: your geolocation coordinates (latitude, longitude, altitude), any GPS-derived stats (current, average or maximum speed, distance, elapsed time, accuracy in meters, signal quality), email addresses, precise identifiers, or cross-site fingerprints. The analytics scripts have no access to the Geolocation API and no GPS variable is ever passed to them. I have verified this separation in the code: GPS logic lives only in the client-side speedometer module, analytics lives only in the layout head.

Analytics payloads are aggregated to answer questions like “is the permission guide helping?” — individual visitors are not profiled across days or sites for advertising by me. You can block either system in a content blocker and the speedometer keeps working fully.

Cookies and local storage — the full list

I keep client-side storage minimal and I list it here so there are no surprises. No storage on this site contains your location:

• Preferences in localStorage (gps:prefs-v1 and legacy theme key): your theme choice (dark, light, or system), preferred speed unit (km/h, mph, m/s, knots), accent and density choices, and whether Keep screen awake is on. This stays on your device and is never sent to a server.
• Plausible: sets no cookies and uses no localStorage for analytics.
• Google Analytics 4 (if loaded): may set first-party cookies such as _ga and _ga_<container> to count sessions. These hold random IDs, expire automatically, and never contain coordinates or speed. Blocking third-party or first-party cookies in your browser will simply reduce analytics counting; the tool still works.
• Google AdSense (only if ads are enabled with a publisher ID): may set or read advertising cookies including the DoubleClick cookie to serve, limit frequency, and — where you have consented — personalize ads. See Advertising below. GPS data is never in those cookies because it never leaves your browser.
• Google Fonts: the font stylesheets themselves do not set cookies from this site, but fetching them contacts Google’s servers under Google’s terms (see Third parties).

You can clear site data at any time via your browser’s Site Settings or developer tools. Clearing localStorage only resets theme and unit to defaults; it does not delete any location trail because none is stored.

Advertising (Google AdSense) — how it works here

To keep this tool free, the site may display ads served by Google AdSense. Ad slots on legal and tool pages are reserved boxes that remain empty until a valid publisher ID is configured — no ad request fires before approval. When ads are active, Google may use cookies (including the DoubleClick cookie) to serve, personalize where applicable, measure, and prevent fraud — for example to limit how often you see the same ad or, where you have consented, to show ads based on your visits to this and other sites.

• GPS data is never shared with advertisers: your coordinates and speed are processed in your browser and never leave your device, so they are never available for ad targeting, building profiles, or sale. This is an architectural guarantee, not just a policy promise.
• Personalized vs. non-personalized ads: in regions requiring consent (such as the EEA and UK), Google will show non-personalized ads unless you consent to personalization via Google’s consent flow. You can change that choice at any time.
• Manage personalization any time in Google Ad Settings (https://adssettings.google.com) and learn how Google uses data from partner sites (https://policies.google.com/technologies/partner-sites). You can also consult Google’s Privacy & Terms (https://policies.google.com/privacy).
• Our ads.txt file at /ads.txt lists the sellers authorized to sell our inventory, as required for AdSense authorization. It contains only the publisher line Google issues after approval.

Ads never influence the speed readout and never receive location. An ad appearing next to content is not an endorsement of the advertised product.

Third parties we involve — and why

I limit third parties to what is needed to deliver fonts, understand pageviews, and (optionally) fund hosting with ads. All are constrained by the Content Security Policy in public/_headers:

• Google Fonts (fonts.googleapis.com / fonts.gstatic.com): provides Inter and JetBrains Mono under Google’s terms so numbers stay tabular and readable. Fetching fonts contacts Google’s servers with standard request metadata (IP, User-Agent) under Google’s privacy handling — no coordinates are sent.
• Plausible Analytics (plausible.io): cookie-less pageview counting described above.
• Google Analytics (googletagmanager.com / google-analytics.com): GA4 pageview counting described above, loaded lazily to protect performance.
• Google AdSense (pagead2.googlesyndication.com, only when enabled): advertising described above. Until you see real ads, no request is made.

No social widgets, fingerprinting scripts, or data brokers run on this site. If I add or remove a third party in the future, I will update this section and the Last updated date.

Legal bases and your rights (GDPR / UK GDPR / CCPA)

Because this site stores no location trail and sells no personal information, most data-rights requests concern only analytics identifiers or emails you sent. Still, I respect all applicable rights. For visitors in the EEA, UK, and Switzerland, the legal bases are: consent for optional cookies and personalized ads where required, and legitimate interests for strictly necessary, aggregated, privacy-respecting measurement of which pages work. For California residents, I do not sell or share personal information as defined by the CCPA/CPRA, and I do not knowingly share GPS data with anyone because I never receive it.

• Access, correction, deletion: email hello@gpsspeedometer.bond and I will explain what (if anything) I hold about you — typically only your email correspondence — and act on a verifiable request.
• Opt out / object: block analytics or ads cookies in your browser or content blocker, use Google Ad Settings to opt out of personalization, revoke location permission in browser Site Settings, or clear localStorage. The tool remains usable.
• Non-discrimination: exercising privacy rights will never degrade your access to the free tool or change its price (it is free for everyone).
• Verification: to protect against impersonation, I may ask you to confirm control of the email address you wrote from before acting on a request about correspondence.

Data retention, security, and international transfers

Location: retained only in volatile memory for the active tab session and discarded on close, reload, or reset — effectively zero retention. Preferences: retained on your device until you clear them. Analytics: aggregated counts retained by the analytics provider under its terms (Plausible aggregated stats; GA4 per Google’s retention settings) with no coordinates attached. Emails you send are retained in the mailbox only as long as needed to answer and maintain a record of the fix or suggestion. Security: the site is served over HTTPS with HSTS, hardened headers (Content-Security-Policy, Referrer-Policy, X-Content-Type-Options), and static hosting so there is no application database of locations to breach. No method is perfectly secure, but the strongest protection here is minimization — the most sensitive data never leaves your device. Where providers process data outside your country (for example, analytics or fonts infrastructure), standard request metadata may travel under those providers’ safeguards; your GPS data does not travel at all.

Children's privacy

This site is a general-purpose utility not directed to children under 13, and I do not knowingly collect personal information from children. Because location never leaves the device and no account exists, there is no child profile to create even if a child uses the tool with a parent’s permission. If you believe a child has emailed personal information unnecessarily, contact me at hello@gpsspeedometer.bond and I will delete that correspondence on request.

Your controls — practical steps

You are in control at every layer:

• Location: allow, deny, or revoke in the browser or OS permission dialog and in Site Settings. Denying simply shows help — nothing is collected either way.
• Analytics: block plausible.io, googletagmanager.com, or google-analytics.com in a content blocker, enable Do Not Track-friendly settings, or disable cookies — the speedometer still works.
• Ads: manage personalization in Google Ad Settings; use your browser’s ad-privacy controls where available.
• Preferences: clear localStorage for gpsspeedometer.bond to reset theme and unit choices.
• Correspondence: email me to ask what I hold about you or to request deletion of an email thread.

Changes to this policy and how to contact us

I may update this policy to reflect tool changes, analytics or ads configuration, or legal clarifications. When I do, I will change the Last updated date above and, for material changes, add a brief note here describing what changed. Continued use after an update means you accept the revised policy. Questions, concerns, or requests? Email Bhagya Masalawala at hello@gpsspeedometer.bond via the Contact Us page. I read every message and aim to reply within a few days. If you feel a concern is unresolved, you may contact your local data-protection authority.