Your location stays on your device.

This is a static website. There is no application server, no database and no account system. That is not a policy choice we could quietly reverse — it is the architecture.

What happens to your GPS data

When you press Start, your browser asks for permission and then hands coordinates to the JavaScript running on your own device. Every calculation — speed, distance, averages, the route line — happens in that JavaScript, in your browser’s memory. None of it is transmitted. There is nowhere for it to be transmitted to.

What is stored locally

• Saved trips, in your browser’s IndexedDB database. Only pages from this domain, in this browser, on this device can read them.
• Preferences — your chosen speed unit, colour theme and acceleration best times — in local storage.
• Your analytics answer — whether you allowed measurement or refused it — in local storage. It is never sent anywhere; it exists so you are asked once rather than on every visit.

Clearing your browsing data deletes all of it permanently. There is no backup and we cannot recover it for you. Export anything you want to keep as GPX, CSV or JSON from the trips page.

Advertising

This site is paid for by advertising, served by Google AdSense. That is the entire business model: there is no paid tier, no subscription, and nothing about you is sold on.

To serve those ads, Google sets cookies and reads local storage on this domain. It uses them to decide which ad to show, to stop you seeing the same one repeatedly, and to measure whether anyone clicked. Depending on your consent and where you are, it may also use that data to personalise what you are shown. What Google collects, and the list of ad-technology providers it works with, are set out in Google’s advertising privacy notice.

If you are in the European Economic Area, the United Kingdom or Switzerland, you will be asked before any of that happens, and nothing requiring consent loads until you have given it. You can change or withdraw that answer at any time, and withdrawing is exactly as easy as giving.

What the advertising never receives

Your location. The coordinates the speedometer reads are handed to JavaScript on your own device and are never passed to the ad code, never attached to an ad request, and never leave the browser. This is enforced rather than promised: ads are displayed inside frames that this site explicitly forbids from requesting the location permission at all, and the coordinates never form part of any network request in the first place.

Nor do your saved trips, your acceleration best times, or your unit and theme preferences. None of those are readable by an advertiser.

Analytics

Where prior consent is required — the EEA, the UK and Switzerland — you are asked before anything loads, and nothing is requested from any Google domain until you answer: not a tag, not a cookieless ping, nothing at all. Everywhere else, Google Analytics and Cloudflare Web Analytics start with the page. You can switch them off at the bottom of this page, in either case, and the switch takes effect immediately.

Agree, and Google Analytics 4 counts the visit: which pages were opened, roughly which country from, which browser, and whether this browser had been here before. It sets its own cookies to recognise a returning visitor. It also records which controls were used, such as Start or a unit switch, in coarse buckets only: no speeds, no locations. What Google collects is set out in Google’s privacy policy.

Cloudflare Web Analytics counts the same visit, without cookies: which page was opened, which site linked to it, roughly which country from, which browser and device, and how quickly the page loaded. It stores nothing in your browser and cannot tell a returning visitor from a new one. What Cloudflare collects is set out in Cloudflare’s privacy policy.

Your answer is kept in your browser’s own storage and is never sent anywhere. Clear this site’s data and you will simply be asked again.

Third-party requests

Two. Ad requests go to Google’s ad-serving domains. Analytics requests go to Google’s and Cloudflare’s analytics domains, and only once you have agreed to them. Everything else the page needs — fonts, scripts, styles and icons — is served from this domain, and nothing else is fetched.

Hosting

The pages themselves still have to be delivered by someone, and that someone is Cloudflare. Like every web host, Cloudflare receives each request your browser makes — your IP address, the page you asked for, your browser’s user agent and the time — and keeps them briefly in ordinary server logs, for security and abuse prevention. Those logs are governed by Cloudflare’s privacy policy. We do not read them individually, nothing in them is tied to an identity, and they can never contain GPS data, because your coordinates are never part of a request in the first place.

Cloudflare may also set a security cookie of its own to tell browsers apart from bots. It carries no identifier for you and is used for neither analytics nor advertising. Beyond that cookie, the advertising cookies described above, and the analytics cookies you have agreed to, this site’s own code sets none.

Permissions we ask for

• Location — required; without it there is no speed to display.
• Screen wake lock — optional, only when you tick “Keep screen awake”. It prevents your display sleeping and nothing else.

You can revoke either at any time from your browser’s site settings, and the page will tell you plainly when a permission it needs has been withdrawn.

Changes

If this ever changes — if an account system were ever added — this page would say so before the change shipped. It said so before advertising shipped, and again before analytics, which is why you are reading these sections.

Questions

Ask anything about this policy at info@livespeedtracker.com — see the contact page. We hold no data about you to delete, because none of it ever reaches us; requests about what Google’s advertising collects go to Google, through the controls linked above. The terms and conditions cover the rest.