Data Policy & Telemetry Handling

Last Reviewed: October 8, 2026

This policy describes the current application implementation and the production Cloudflare configuration checked on that date. Hosting-provider request processing, browser-local records and optional database storage are distinct.

1. Measurements and Request Data

The browser measures download and upload throughput, latency and jitter, and displays loaded-latency diagnostics where available. Cloudflare processes your IP address to deliver requests. The IP-information endpoint returns IP, approximate city/country and ISP information to the browser where available. The API uses the connecting IP for transient rate-limit checks; this is not an IP-hashing pipeline.

2. Server-Side Database Storage

No database persistence is configured in the checked production Pages settings. The results API can optionally write a transaction ID, timestamp, download speed, upload speed, ping, jitter and ISP text to Supabase when the required bindings are enabled. That record does not include a raw or hashed IP address, account ID, browser history or browsing content.

With those bindings absent, the results response reports that database logging did not occur. Hosting-provider logs and temporary request processing remain separate and are governed by Cloudflare's service settings and Privacy Policy. Enabling persistence later requires reviewing the actual processor, storage fields and retention controls first.

3. Local History and Sharing

The vv-history localStorage entry keeps up to ten recent results on your browser: download, upload, ping, timestamp and a bufferbloat grade when available. You can remove these through Clear History or your browser's site-data settings. Records have no automatic time-based expiry in the current implementation.

Share links encode result measurements and, when included, ISP information in URL parameters. Anyone with the link can read those values. There is no server-side result-token store or automatic link-expiry mechanism. Browser history, recipients and hosting request logs may retain copied URLs. Share only information you intend to make available.

4. Newsletter and ISP Index

The newsletter endpoint is unavailable while database bindings are absent. If enabled later, it can store an email address, subscription ID and creation time; the current API does not implement double opt-in verification or an automated deletion schedule.

The ISP Index uses a separately supplied provider dataset. The current production configuration does not generate that dataset from newly submitted test records. Refer to the Index's methodology and disclosures; its figures are not proof of an active results-collection pipeline.

5. Your Controls and Requests

You can export current test results as JSON or CSV, clear local history, and manage optional analytics/advertising through Cookie Preferences. The application does not require a user account for a speed test. We do not sell individual test records or IP addresses.

For data questions or requests, contact [email protected] or use the Contact page. Rights and request handling are described in the Privacy Policy.