We count events, not people

LagScope is free, needs no account, and works because it collects almost nothing. This page is the complete list: what we count, what we store, and what we never see. Last updated 2026-07-25.

What we never collect

• No cookies. Not one. Preferences live in your browser’s local storage and never leave it.
• No accounts, no emails, no names. There is nothing to sign up for.
• No IP storage. Your IP is used in memory to route your test to the nearest node and rate-limit abuse, then forgotten. It is never written to disk.
• No cross-visit stitching. Analytics sessions live and die inside a single browser tab. Close the tab and the link is gone — we cannot and do not connect your visits.
• No third-party trackers, no ads. No pixels, no fingerprinting, no data brokers. Nothing to sell, because nothing identifying exists.

What the anonymous counters count

A single beacon endpoint (/ev) receives product events — things like “a test started”, “a test finished”, “a share sheet opened”, “a snapshot was created”. Each event carries a random per-tab ID that exists only in that tab’s session storage, plus coarse context (page, referrer bucket). The edge server keeps these in memory, computes aggregate funnel rows (“N starts → M finishes today”), and writes only those totals to disk. The per-tab IDs never touch disk. There is no way to go from a counter back to a person.

Test measurements

Your live measurements — latency samples, jitter, loss, score — are computed and displayed in your browser. Two explicit, user-initiated exceptions:

• Proof snapshots. When you generate a proof link or share card, the summary metrics (score, medians, spikes, tier — no IP, no identity) are stored so the link (/proof/<id>) works. Anyone with the link can view it; the id is random.
• Leaderboard opt-in. The ISP leaderboard exists only because some users explicitly choose to contribute anonymized aggregates — score, latency, loss per ISP. Opt-in, per session, revocable by simply not contributing.

The AI assistant surface (MCP)

LagScope exposes an MCP server (/mcp) so AI assistants like ChatGPT can run the test, explain concepts, and look up public data. It serves the same anonymous tool, the same public leaderboard aggregates, and snapshots fetched by id. It adds no new data collection: the widget runs the same browser-side test, and the assistant only sees a result if you run the test inside the chat.

Infrastructure

The site is served by three edge nodes (US, EU, BR) running our own Go binary. Standard server logs (request lines, no bodies) rotate on the host. TLS is handled per node; no analytics or advertising third party is in the path.

Changes to this policy

If this policy changes, the updated version lands on this page with a new “last updated” date. Material changes are called out on the page itself.

Questions or deletion requests for a snapshot you created: Discord or @lagscopeapp.