Privacy Policy
Last updated: November 22, 2026. This edition adds the advertising section: the site shows Google AdSense ads, and the policy now says how ad cookies work and how to opt out. Version 2.27 (November 5) records the country a shared benchmark run came from, for the flag on the leaderboard and, since 2.32, in the top scores: see Country below. Version 2.24 shares screen measurements automatically, without a banner, and moves the off switch to this page: see Switching it off and the changelog.
Screen tests run in your browser. When a test measures your screen, such as its refresh rate, resolution class or touch points, the result is added to anonymous public screen stats. Pixel findings are shared only if you answer the short question after the dead pixel test. The scored benchmark keeps its own sharing option. No identifiers or IP addresses are stored, and you can switch screen stats off on the privacy page.
What never leaves your device
Screen images, microphone audio, typed text and individual touch positions are never uploaded. The gradient and pattern tests, the effects gallery, and free-play and Classic benchmark runs stay on your device. Only the anonymous screen stats fields listed on this page are shared. The mic test analyzes audio, and its optional recording, only inside the tab, and discards the recording when you stop or leave.
The mic test opens your microphone only after you press Start and your browser has asked you. The audio is analyzed inside the tab; the optional five-second recording is held in memory and discarded when you stop, record again, or leave the page. No audio, level reading, or device name is sent to us or to anyone else, and nothing is written to storage.
Benchmark samples, 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 with each scene's raw maximum stable load (the workload number already shown on your results sheet), whether that scene hit its time cap, its measurement flags ("drift" for a device that slowed as it warmed, "unconfirmed" or "floor" for a level that couldn't be proven) how much slower the end-of-scene check ran than the start — a single ratio like 1.3 — and whether that scene's number came from its one automatic re-measurement, plus benchmark version, profile, and whether the run completed cleanly, throttled, or degraded. All of this describes the run, not you; every field is already on your results sheet
- Screen numbers: resolution in pixels, pixel ratio, refresh rate bucketed to common tiers (60 / 75 / 90 / 120 / 144 / 165+), and a display-pacing class — "fixed", "adaptive", or "unknown" — describing how the display returns frames, so scores from different display types can be compared fairly
- 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"
- Country: from version 2.27 (November 5, 2026), the country the run came from, as a two-letter code such as "DE". Your browser doesn't send it: our server takes it from Cloudflare, which works it out from the network the run arrives on, so a VPN or a work network can change it. The IP address itself is never stored. Only the 193 UN member states are recorded; a run from anywhere else is recorded with no country. Runs shared between version 2.2 and 2.27 carry no country at all
- Date: day precision only. We stopped recording site language in version 2.2.
These rows power the public hardware benchmarks — medians over groups of at least 30 samples — and the top-scores board on the performance test page, which lists the best recent fully-measured runs individually (complete, and from 2.9 also thermally-throttled runs, which the board marks as such) — at most one row per coarse hardware profile, so one device running again and again can't fill the board: a score, the same coarse families shown above, and from 2.32 the run's country as a flag. The leaderboard page shows the same rows to a depth of 200, for the last 30 days or all time, and for earlier benchmark versions as long as we still hold their samples, with each run's country shown as a flag. Since 2.33 the screen size and pixel ratio of these runs also give the most common resolutions on the screen stats page: counts only, once per machine, for groups of at least 30 machines. Nothing finer-grained than the field list is ever published, because nothing finer-grained exists.
Anonymous screen stats
When a screen test measures something, the result is added to the public screen stats automatically. The homepage device readout adds display parameters, the refresh rate test adds the settled refresh rate, and the touch screen test adds touch results. A pixel finding is sent only after you run the dead pixel test and answer what you found and which screen you tested. Nothing is guessed from an unanswered question. See the screen stats.
This is the complete field list. Every sample carries:
- Which test it came from, your device type as the page detects it (phone, tablet or desktop), the OS family (for example “Android”) and the browser family (for example “Chrome”, without a version number), plus the date, to the day, set by our server.
And, depending on the test:
- Refresh rate test: the measured refresh rate as shown (for example 120 Hz) and its tier (60, 75, 90, 120, 144 or 165+).
- Resolution checker and homepage readout: a screen size class (the long edge of the physical resolution in ranges, such as 1920 to 2559 pixels, never the exact resolution), the pixel ratio, the color depth, the color gamut (sRGB, P3 or Rec. 2020) and whether HDR is available.
- Dead pixel test: your answers to “What did you find?” (nothing, a dead, stuck or hot pixel, or not sure) and “What did you test?” (phone, tablet, laptop, monitor or TV), and the screen’s age in ranges if you answer that question. These are fixed choices; there is no text box.
- Touch screen test: the most touches you held at once on the grid; from the ghost touch test, the number of phantom touches, the test length and whether the phone was charging; and the touch sampling rate. Each is sent only if you ran that part.
Not collected: your IP address (used only in memory to limit request rates, never stored), your user agent, your exact resolution, your country or language, any identifier, or any free text.
Counts are refreshed every hour. The screen stats page shows a group only once it holds at least 30 samples, and unusual values in open-ended measurements with fewer than 5 samples are combined as “other”. Single samples are never published. Counts describe tests, not unique people or devices.
So the same screen is not counted again and again, your browser notes the day it last sent each kind of measurement and sends at most one per kind per day. That note holds only the date, and it never leaves your browser.
Raw samples are deleted after 24 months. The daily counts are kept.
Switching it off
Tick the box below and this browser stops sending screen stats. Every test keeps working exactly as before. The choice is saved in this browser only, so set it again in another browser or after clearing site data. Samples already sent stay in the counts, because nothing in them links back to you.
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, your screen stats choice, the day each kind of screen measurement was last sent, 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. The same applies to screen stats samples: raw rows for 24 months, daily counts indefinitely.
No selling, no sharing
We don't sell, rent, or share the dataset with anyone. What we publish is aggregates with minimum sample-size thresholds, plus a top-scores board and a leaderboard listing the best runs, one per coarse hardware profile — each shown exactly as coarse as the field list above: a score, hardware families shared by millions of devices, and a country. No published row contains anything to identify you with, because no stored row does.
Third parties
The site is served through Cloudflare, which processes requests the way any hosting provider does (their privacy policy applies 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 by Google'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.
The optional gallery soundtracks stream from areal.me, another site we operate, served through the same Cloudflare setup as this one. Nothing is fetched from it until you switch the music on in the effects gallery, and turning it on sends an ordinary file request — no cookies, no identifiers, nothing about you beyond what any download carries.
The site shows ads from Google AdSense. Google and other third-party vendors use cookies or similar identifiers to serve ads based on your visits to this site and to other sites; Google's use of advertising cookies lets it and its partners serve those ads to you. You can turn off personalized ads in Google's Ads Settings, and opt out of other vendors' advertising cookies at aboutads.info. Visitors from the EEA, the UK and Switzerland see Google's consent message and can choose before personalized ads are shown. How Google uses information from sites that show its ads is explained in Google's partner-sites page. We never pass your benchmark results or screen measurements to an ad network.
The optional comments connect to a third-party comment service when you open them, and posting requires a Google sign-in. Comments are kept apart from the anonymous benchmark dataset; don't post personal details you don't want to be public.
Changes
If this policy changes, the change is dated here and noted in the changelog. 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.