Privacy
Klyrix/speed keeps nothing about you on its servers: not your results, not your IP address, not your location. The site sets no cookies of its own and runs no analytics, ads or third-party scripts.
What the page shows you
- Your IP address, approximate location, provider and ASN. They come from how Cloudflare sees your request. The location is the city or region, with coordinates rounded to about 11 km before they leave Cloudflare’s server. This answer goes only to you, is marked as not cacheable and is not written anywhere.
- Your device and connection type. The page reads them in your browser. They are never sent to us.
What happens during a test
- Your browser downloads files of random data, uploads random data (dropped as soon as it arrives) and sends small ping requests.
- The result is calculated in your browser. It is not sent to us or shared with anyone.
- Your browser keeps your last 30 results (time, server and measured values, no IP address) and your speed unit in its own storage on this device, so you can compare tests; they never leave it, and you can clear them in Settings or by clearing this site’s data.
Cloudflare
The site itself runs on Cloudflare, which handles every request for the page, including your IP address, to deliver the site and protect it. Its security features, such as rate limits, use your IP address briefly to stop abuse. Cloudflare’s own privacy policy applies to that processing. Cloudflare is also the fallback test target when none of our own servers is close enough to you, and on a very fast line it can be one more source alongside them.
The server status in the page’s footer comes from a public file at pub.klyrix.network (on the test copy, pub-staging.klyrix.network), which we keep in Cloudflare’s file storage. It holds only server counts and city names, nothing about you; your browser fetches it like any other part of this site, so that request too reaches Cloudflare with your IP address.
The site’s own code on Cloudflare writes no logs and records no IP addresses. Cloudflare keeps aggregate usage figures, such as request counts, which we use to keep the service within its limits.
The public test copy is different. On staging.klyrix-speed.com, the test copy of this site, Cloudflare’s request logs also keep each visitor’s IP address and approximate location, for as long as Cloudflare retains them. The live site does not.
Our own test servers
A test runs against test servers we rent whenever one of them is close enough to you: it has to answer within 40 ms and be no more than 10 ms slower than Cloudflare. Otherwise the test runs on Cloudflare instead. Your browser sends your IP address to the servers it uses, as it does to any website you open. On a fast line the test uses several servers at the same time, since one server cannot fill a very fast connection; those servers can be in other countries, and Cloudflare can be one of the sources as well.
Before the test picks one, your browser sends a few tiny requests to every server it was offered to see which answers fastest, so your IP address reaches all of them even when the test ends up using only one.
Which servers you are offered, and in which order, is worked out from your approximate location as Cloudflare reports it. That value is used to sort the list while the answer is being written and is stored nowhere.
Our test servers keep no access logs and record no IP addresses: the program removes any address from its own error messages before they are written down. On each server we keep a running total of bytes, for the provider’s traffic allowance, and operating counters for the whole machine — processor and memory load, network bytes and similar totals — in 10-second steps for seven days, so we can see when a server is unwell. Our back office keeps the same counters in coarser steps: per minute for a week, per five minutes for 90 days, and hourly and daily totals after that. How many tests a server ran, and how fast they went, is kept only as hourly totals for the whole server; an hour with fewer than five tests is shown as “fewer than 5”. None of these records holds an IP address, a cookie or a row for a single test. No cookies are set, either way. What a server receives with each request is a signed ticket that names only the server, a random test number, a time window and a byte allowance — nothing about you. Downloads are random data; uploads are random data your browser makes up, and the server throws them away as they arrive.
All our test servers are rented from Gcore, which runs the network around them and may keep the traffic records the law of each country requires; Gcore’s own privacy policy applies to those.
These are the places where our test servers stand, with their provider and the number of servers in each. Every server is listed here before it serves any test.
- Baku, AzerbaijanGYD · Gcore · 2 servers
- Helsinki, FinlandHEL · Gcore · 2 servers
- Paris, FranceCDG · Gcore · 2 servers
- Frankfurt, GermanyFRA · Gcore · 2 servers
- Tokyo, JapanNRT · Gcore · 2 servers
- Luxembourg, LuxembourgLUX · Gcore · 4 servers
- Amsterdam, NetherlandsAMS · Gcore · 2 servers
- Warsaw, PolandWAW · Gcore · 2 servers
- Sines, PortugalLIS · Gcore · 3 servers
- Istanbul, TürkiyeIST · Gcore · 2 servers
- Dubai, United Arab EmiratesDXB · Gcore · 2 servers
- Chester, United KingdomMAN · Gcore · 2 servers
- London, United KingdomLHR · Gcore · 4 servers
Your choices
We hold nothing about you to delete: what our servers keep are the machines’ own counters, never a record of you or your test. Your recent results are in your own browser: clear them in Settings, or clear this site’s data in your browser.
Contact
Responsible for this site: [to be added]
Contact: [to be added]