Privacy Policy

Last updated: August 23, 2026 — rewritten for 2.0; updated for 2.1's default-on sharing and again for 2.2, which stopped collecting country and language (see the changelog).

Short version: the screen tests run entirely in your browser and send nothing anywhere. The one thing this site can record is a single anonymous sample when you finish a scored benchmark run — and you're shown exactly what's in it, on screen, before the run starts, with a skip button right next to it.

What never leaves your device

The dead pixel test, gradient test, test patterns, device readout, and the effects gallery are local. No requests, no logging by us, no analytics scripts. Free-play and Classic benchmark runs don't submit anything either.

The one thing we collect, and when

When a scored Standard benchmark run completes, your browser sends one row to our stats service. Sharing is on by default: the start card that appears before every run shows a checked box and a live preview of the exact values your device would send — uncheck it and the run submits nothing, and that choice is remembered. This is the complete field list; nothing else is sent, ever:

• Benchmark result: total score, per-scene subscores, benchmark version, profile, and whether the run completed cleanly or degraded
• Screen numbers: resolution in pixels, pixel ratio, and refresh rate bucketed to common tiers (60 / 75 / 90 / 120 / 144 / 165+)
• Coarse hardware: OS family (e.g. "macOS"), browser family and major version (e.g. "Chrome 139"), GPU family normalized to a coarse label (e.g. "apple-m"), CPU cores and memory in buckets
• Device context: whether the device ran on battery or plugged in, its form factor (phone / tablet / desktop), and — on Android only — a coarse device family like "Galaxy S24" shared by millions of units; rare models are recorded as a brand bucket or "other", never as an exact model string, and other platforms record "none"
• Date: day precision only. We stopped recording country and site language entirely in version 2.2 — samples carry neither.

These rows power the public hardware benchmarks, which only ever show medians over groups of at least 30 samples.

What we will never collect

No IP addresses stored, no raw user-agent strings, no canvas or audio fingerprints, no stable device identifiers, no names, no emails, no precise timestamps, no free-text from your browser. There is no account system. Our own code sets no cookies; the only things it keeps in your browser's local storage are your own preferences (theme, your scores, your submit-or-skip choice, and which help cards you've dismissed), and they stay there. The one third-party service we use is described below.

Rate limiting

Our stats endpoint checks request rates by IP address to keep junk out of the dataset. The IP is used transiently for that check and is not written to the database or to logs we keep.

Retention

Raw samples are kept for 24 months, then deleted. Aggregated statistics (medians and percentiles per hardware family — never individual rows) are kept indefinitely and power the public stats pages.

No selling, no sharing

We don't sell, rent, or share the dataset with anyone. Published statistics are aggregates with minimum sample-size thresholds, so no single run is identifiable — not that a row contains anything to identify you with.

Third parties

The site is served through Cloudflare, which processes requests the way any hosting provider does (their privacy policyapplies to that).

We use Google Analytics 4 to understand aggregate site usage — which pages get visited, roughly where from, on what kinds of devices. It loads only after the page has finished rendering, and it may set cookies or similar identifiers governed byGoogle's privacy policy. We don't send it your benchmark results, and the anonymous stats dataset described above is completely separate from it. Blocking analytics with a content blocker breaks nothing on this site.

We run no advertising scripts.

Changes

If this policy changes, the change is dated here and noted in thechangelog. We won't quietly expand what's collected — a new field means a new consent card that says so.

Contact

Questions about any of this: admin at screentest.pro.