Privacy
No account, no tracking, and no advertising cookies. Your results stay in your own browser; a copy of the measurements, carrying nothing that identifies you, is sent here so the rating scale can be calibrated against real devices.
Stored in your browser
Four things, all in this site's own localStorage, all readable only
by this site and only on this device. Clearing your browser's site data removes
every one of them.
- The device type you chose - phone, tablet, laptop or desktop. Written only when you tap one of the buttons. The detector's guess is never saved, because a guess is not a statement of fact and should not outlive the visit.
- Your completed runs, up to the last eight, so the comparison table has something to compare. These never leave your browser unless you copy a share link yourself - and a share link carries the measurements inside the link itself, not a key to a row on any server.
- Whether this browser has contributed a run - a marker, so that one device is counted once and a single phone run many times cannot become most of the scale. It is a date, not an identifier, it never leaves the device, and clearing your site data removes it like the rest.
Sent to this site's server
When a run finishes, these are posted and kept:
- the measurements - overall score, CPU score, average FPS, 1% low FPS, frame consistency, refresh rate and core count;
- the device type you chose;
- a coarse operating system name - one of Windows, macOS, Android, iOS or Linux, and nothing more specific;
- what the device detector guessed, how confident it was, and whether you corrected it;
- the measured core structure - the fastest worker's throughput and the spread between the fastest and slowest. These describe how the processor is built, not who owns it.
That last one exists so the detector can be judged on its record rather than on anyone's opinion of it. If it turns out to guess wrong often, it gets deleted.
The stored row has 15 columns and none of them identifies anybody: no name, no account, no device identifier, no advertising identifier, no cookie, no browser user-agent string, no graphics-card string, and no IP address. There is no column for any of those, so there is nothing to disclose, leak or hand over. That count is read from the schema itself when this page is built, so it cannot drift from the table it describes.
Your IP address is seen by the server, as it is by every website you visit. It is used for one thing - capping how many runs a single address can submit in a minute - and it is never stored. There is no column for it.
Why collect anything at all? The tier - Flagship down to DEAD TIER - currently rests on an estimate of what a strong device of each type scores. Once enough real runs of a device type exist, that estimate is replaced by where your device actually falls among them, and the guesswork disappears. That is the only thing this data is for. It is not sold, shared or used to build a profile, because there is nothing in it to build a profile from.
Every completed run is added, and there is no tick box. There used to be one. It arrived already ticked for every new visitor, so for almost everybody it changed nothing, and it was removed rather than left on screen as a control that decided almost nothing. What gets sent is exactly the list above.
One device is counted once, ever. A marker in your own browser records that this browser has contributed, and later runs from it are not added again - so a single phone run many times cannot become most of the scale. Those later runs still get their full result and their real tier; they simply do not vote twice. The marker is a date, it never leaves your device, and clearing your site data removes it.
To run the test without adding anything, open deadtier.com/?contribute=off. Nothing is posted, no marker is written, and the screen says "Off for this visit" so you can see it took effect - you still get your score and your tier. It lives in the address rather than in your browser's storage, which means it keeps working on a device where site data is cleared, and it can be bookmarked.
Sent to Google
Only when a written summary appears under your results. Producing one means sending the same measurements - the numbers and the device type, the same list as above and no more - to Google's Gemini API, which writes the plain-English paragraph. When that panel says the summary could not be loaded, nothing was sent. The measurements themselves never depend on this: they are made on your device before any request and shown whether or not it succeeds.
Advertising
No ads are served today and no advertising cookie is set.
If advertising is enabled later it will be Google AdSense, and visitors in the EEA and the UK will be shown Google's own certified consent message before any advertising cookie is set. That mechanism is operated by Google, not by this site; this site has no means of setting an advertising cookie on its own and does not.
What this site does not do
- No analytics of any kind - no page-view counter, no session recording, no heatmap.
- No third-party fonts or images, and no third-party script on these written pages. The one exception is on the test page itself: while a benchmark is running, a Cloudflare Turnstile check loads to confirm a real browser is producing the run, because the results are added to a public scale and anything else could post invented numbers to it. It is not an analytics tool and it is not used to track you between sites.
- No email address is collected, because there is nowhere to enter one.
- No cross-site tracking, and nothing that could support it.
Getting in touch
Questions about any of the above, or a request to have something removed: deadtiermail@gmail.com. Note that contributed runs carry nothing linking them to a person, so there is no way to find "your" rows in order to delete them - which is the same property that makes them safe to collect.
Last updated 16 September 2026.