What we collect
When you run a test we record the resulting download / upload / latency / jitter values, the Cloudflare colo your traffic terminated in, the standard test mode, and a coarse device classification (Fixed or Mobile) derived from your User-Agent.
We do not store your raw IP address or raw User-Agent. Both are kept only as salted SHA-256 hashes via the hashIpFromHeaders and hashUserAgent helpers — the originals never reach our database. The hashes let us deduplicate abuse and reconstruct rough device class without storing identifiers we can reverse.
Where the test traffic goes
The measurement itself does not transit myping’s servers. The @cloudflare/speedtest SDK runs in your browser and exchanges binary payloads with speed.cloudflare.comover HTTPS. Download bytes, upload bytes, and ping samples are processed on Cloudflare’s edge — your IP, the colo your packets routed to, and the bandwidth/latency timings are visible to Cloudflare and governed by their privacy policy.
myping only sees what your browser posts back after the SDK finishes: the final speed numbers, the colo IATA, the standard test mode, and the request headers we hash on arrival.
Measurement Lab and the public BigQuery dataset
Per Cloudflare’s October 2025 announcement, Cloudflare aggregates measurement metadata from their speed-test infrastructure and publishes it to Measurement Lab’s open dataset on Google BigQuery. Because myping drives the same SDK against the same speed.cloudflare.comendpoints, every test run on this site contributes to that public dataset alongside Cloudflare’s own.
That dataset is open — researchers, regulators, ISPs, and the public can query it on BigQuery. The data published is the aggregate measurement record (timing, throughput, colo, geography); it is governed by Cloudflare’s and M-Lab’s respective privacy policies, not ours.
We do not separately upload, sell, or syndicate myping’s own anonymous result history beyond that pipeline. The hashed-IP, hashed-UA, visitor-cookie history described in the next section stays on our database.
Why we collect it
Hashed identifiers and aggregated test data power the global index, the per-result sharable pages, and your own anonymous history on this device. Personally identifiable details are not sold or shared in raw form because we never have them in raw form.
Cookies
We use cookies to remember your connection-class preference and to scope your anonymous result history to this device via an HttpOnly myping_visitor identifier. Aggregate site-usage cookies are non-essential and you can opt out of them at any time via the cookie banner.
Your rights
Depending on where you live, you may have the right to access, correct, or delete the personal information we hold about you. Because we store only salted hashes of your IP and User-Agent, deletion requests need either the visitor cookie ID or the public result IDs you want erased. To exercise these rights, contact privacy@myping.com.
More detail
The methodology page documents exactly how the test runs, what each field on a result means, and how the Cloudflare and Measurement Lab pipelines fit together end to end.
Contact
For privacy questions, email privacy@myping.com.
