Privacy Policy

This speed test is built to need as little information about you as possible. This page explains exactly what happens when you run a test.

What we do not collect

You do not need an account, an email address or any personal details to use this internet speed test, and nothing you measure is stored or tied to you. This deployment does load Google Tag Manager on every page, so it is not analytics-free; what that means is set out under Analytics below.

There is one place where you can hand over information deliberately, and that is the comment box at the foot of each page. Nothing you type there is required to use any tool on this site. See Comments below.

What happens during a test

Running a test exchanges real data between your browser and the test server. The server therefore sees the same technical details any web server sees when you visit a site: your IP address, the requested URL, timestamps and your browser's user-agent string. This information is needed to deliver the response and to prevent abuse of the test endpoints.

The upload phase generates random data inside your browser and sends it to the server. That data is counted and immediately discarded. It is never written to disk, never logged and never inspected. It contains nothing from your device.

Results

Your results are calculated in your browser and shown on the page. They are not submitted anywhere and are gone as soon as you close or reload the tab.

Connection information

The connection information card shows only values your browser already exposes to any website: online status, an optional connection-type hint, your browser and platform, and the local time of the test. Nothing there is stored or transmitted, and the browser does not expose your Wi-Fi network name, password or signal strength to a web page.

Starlink connection check

The Starlink speed test page can tell you whether the connection you are testing looks like Starlink. It does that by asking the internet's phone book, not a data broker: the server makes one reverse DNS lookup of the address your request arrives from, because Starlink names its customer addresses under starlinkisp.net. No IP-intelligence service, no third-party API and no account is involved, and nothing leaves this server except that DNS query.

Your address is used for the lookup and as a key in a short-lived in-memory cache, so that reloading the page does not repeat it. Neither the address nor the name it resolves to is written to disk or to a log, and the cache is gone when the server restarts. The answer is sent only to you and is never cached by anything in between. Nothing the page measures depends on it, the check runs only when you start a test on that page or press the button yourself, and no other page on this site performs it.

Comments

Each page has a comment box. If you post a comment, this is what happens to it.

• What is stored: the name you type (or "Anonymous" if you leave it blank), the text of your comment, the page you posted it on, and the time.
• Your IP address is not stored. A salted, one-way hash of it is kept alongside the comment so repeated abuse can be blocked and duplicate submissions caught. The hash cannot be turned back into an address.
• No account, no email, no cookie. Commenting sets nothing on your device and asks for no way to contact you.
• Comments are public. Anyone who visits that page can read what you wrote, and search engines may index it. Do not post passwords, network names, addresses, phone numbers or anything else you would not put on a public noticeboard.
• Removal. Comments can be hidden or deleted by whoever runs this deployment. Because there are no accounts, there is no way to prove a comment is yours, so ask through the contact page and identify the comment by page and wording.
• Moderation. Suspected spam is held for review rather than published. The operator can also switch every comment to review-before-publishing.

Comment text is stored and displayed as plain text and is never interpreted as HTML or script, so a comment cannot affect anyone else's browser.

Analytics

Every page on this site loads Google Tag Manager (container GTM-NZCBG5HG). Tag Manager is a loader: it fetches a configuration from Google and runs whichever measurement tags that configuration contains. Google therefore receives your IP address as part of serving it, and any tag inside the container - Google Analytics being the usual one - can record which pages you visit, when, roughly where from, and what device and browser you use, and can set its own cookies on your device to recognise a returning visitor.

None of that touches what you measure. Speed test results, latency samples and the Starlink checks are still calculated in your browser and are still never submitted anywhere. Analytics sees page visits, not results.

The site’s Content-Security-Policy limits what the container can load: a tag that fetches from a host the policy does not list is blocked by your browser. If you are running this deployment, list here exactly which tags your container contains, whether any of them set cookies, and add a consent banner if the law where your visitors are requires one - GDPR and ePrivacy generally do. To remove analytics entirely, delete the Tag Manager lines from the page templates and the googletagmanager entries from the policy in server/server.js.

Server logs and retention

If the operator of this deployment keeps standard web-server access logs, those logs may contain IP addresses and request lines. Keep the retention period short. A few days is usually enough for troubleshooting and rate limiting. Document it here for your deployment.

The test server

Measuring an internet connection means moving data to and from a server that is actually on the internet. By default this site tests against Cloudflare's public speed-test endpoints, so the requests during a test go to Cloudflare rather than to this domain. Cloudflare therefore sees your IP address and the size and timing of those transfers, exactly as it would if you visited any site behind its network. Nothing identifying you is added by this page, and the only detail read back from the response is the name of the data centre that served the test, which is shown to you on the results page.

The site operator can change this. The bundled backend implements the same three endpoints, and switching the server in the configuration file makes every test request go to this domain instead. See the project README for how.

Third-party resources

The page loads the Bootstrap CSS and JavaScript files from the jsDelivr content delivery network, and Google Tag Manager from googletagmanager.com. Both see your IP address as part of serving those files, and Tag Manager is covered in more detail under Analytics. Everything else on the page is served from this domain. To remove the jsDelivr dependency, host the two Bootstrap files locally.

Changes

If this policy changes, the updated version will be published on this page.