GlobeLatency Privacy: What Data Is Stored and Where
GlobeLatency needs no account. A completed Test sends your measured numbers and your IP address to the server so a report can be created. Map and Monitor readings, settings, custom destinations and history stay in your browser. Analytics and the chat widget load only after you interact with the page. You can clear everything by removing the site data in your browser.
On this page
Quick answer: GlobeLatency is designed to need as little personal data as possible. No account, no email, no install. The only things that leave your browser for GlobeLatency's own server are the results of a completed Test and your IP address, which are needed to create a report. Live Map and Monitor data stay on your device.
Where each kind of data lives
| Data | Where it lives | Sent to the server? |
|---|---|---|
| Test results of shared destinations (averages, best, worst, percentiles) | Server database after a completed test | Yes |
| Your IP address when you save a test | Server | Yes (it is part of the request) |
| Your selected destinations and template | Browser local storage | No |
| Settings (passes, interval, timeouts, thresholds) | Browser local storage | No |
| Custom destinations | Browser local storage | No |
| Test history list | Browser local storage | No (only the report itself is on the server) |
| Map and Monitor readings (last 60 per host) | Browser local storage | No |
| Cached server locations for the map | Browser local storage (3 days) | No |
The local storage keys all begin with gl2_, which makes them easy to recognise in your browser developer tools.
What happens when a test finishes
- Your browser has measured each destination by itself.
- It sends the per-destination results (for shared destinations only) to the server.
- The server creates a session code, stores the report and returns the shareable link.
- Each destination's average, lowest and highest are added to the daily world statistics, which is how the world comparison is built. See The world comparison explained.
A stopped test is not saved, and custom destinations are never sent. Anyone with the report link can read the report; the page asks search engines not to index it.
What the destination servers see
When your browser measures a destination, it makes an ordinary web request to that destination. The operator of that server can see your IP address, browser identification and the request, as they would for any website visit. This is inherent to measuring latency against real servers, and it is also why measuring against servers you do not own should be done politely. The request has a random query string, but no cookies or login information of yours are attached to cross-site no-cors requests in a way that exposes your accounts.
The IP address and your location
- Your IP is used for abuse control and network context.
- The map uses your public IP to place the You marker. It is looked up through geolocation services and is approximate.
- Your location on the map is never uploaded as part of Map or Monitor readings.
If you do not want your real IP involved, you can use a VPN, but that changes the latency you measure. See VPNs and latency.
Analytics and chat widget
To avoid slowing the page or disturbing measurements, analytics and the support chat widget are loaded only after your first interaction (a click, a key press, scroll) or after a few seconds. They are separate services with their own policies. The measurement engine does not depend on them.
Clearing your data
- Open your browser settings and find site data or cookies for
globelatency.com. - Remove the stored data. This resets selection, history, custom destinations, settings and cached locations.
- Reload the page. It starts fresh with the default template.
Private or incognito windows start empty and discard local storage when closed.
Worked example
You run a 5-pass test with 12 shared destinations and 2 custom hosts. The server stores a report with the 12 shared destinations only. Your two custom hosts and their numbers exist only on your screen and in your browser. You copy the link to your ISP support. They can see the 12 destinations, nothing about your custom hosts, and nothing from your Map history. The following week you leave Monitor open for an afternoon: none of those readings leave your device.
Common mistakes and myths
- "Anyone can see my live map." No; it is local only.
- "Report links are public listings." They are unlisted, not password protected.
- "Clearing history deletes my reports." Browser history clearing does not delete server reports.
What to do next
Read Saved reports and sharing for how links work, or Accuracy and limitations for what the numbers can and cannot tell you. When ready, run a test.
Frequently asked questions
Do I need an account to use GlobeLatency?
No. There is no signup or login. You open the page and start. Reports are identified only by a long random session code in the link.
Does the live map or monitor upload my data?
No. Map and Monitor readings, settings, cached locations and your custom destinations are kept in your browser local storage. They are not sent to the server. Only the measurement requests themselves go out to the destination servers.
What is sent when I finish a test?
The measured values for the shared destinations, the number of passes and your IP address are sent to the server to build the saved report and to contribute to the world statistics. Custom destinations are never sent.
Why does the site store my IP address?
Your IP address helps with abuse control and with showing network context such as your provider. It is part of how a test request reaches the server and is not shown to people who open your shared report link.
How do I delete my local data?
Clear the site data for globelatency.com in your browser settings. This removes your selection, settings, history, custom destinations and cached locations. Server-side reports cannot be deleted by you, because there are no accounts.
Does the site use cookies or tracking?
The site loads analytics and a support chat widget after your first interaction with the page. These are loaded late so they do not slow down measurement. The measurement tool itself works from local storage, not login cookies.