Privacy Audit
A line-by-line account of what this site reads, computes, displays — and what it never does with any of it.
The facts, verbatim
- Fingerprint results uploadedNo
- Fingerprint results storedNo
- Analyzer cookies createdNo
- Persistent browser storage usedNo
- Permissions requestedNo
- External fingerprint API usedNo
- Comparison baseline storageCurrent-page memory only
- Third-party advertising script (site funding)Yes — disclosed below
What the analyzer reads
When you click Start analysis, the page reads: pixel output from an image it draws itself (Canvas); graphics vendor, renderer, and capability values reported by the WebGL API (WebGL); numeric samples from a silent signal rendered by the Web Audio API (Audio); resolution, color depth, pixel ratio, and viewport values (Screen); and rendered text widths used to infer installed fonts (Fonts). Every one of these APIs is available to any web page without a permission prompt — that availability is the point this site demonstrates.
What happens to the data
Raw results are hashed with SHA-256 by your browser's built-in Web Crypto API and rendered into the result cards you see. That is the complete lifecycle. The page makes no network requests after loading its own HTML, CSS, and JavaScript files, so there is no request that could carry a result anywhere. There is no server-side component, no database, and no account system on this site at all.
The comparison baseline
The change-detection feature needs to remember your first run to compare against a second. It does so in an ordinary JavaScript variable inside the analyzer page — deliberately the most fragile storage that exists. The variable is destroyed when you refresh, navigate away, close the tab, or press Clear results. It is never written to localStorage, IndexedDB, sessionStorage, cookies, the Cache API, or any server.
What this site does not include
- No analytics or tracking pixels of its own. This site does not measure its visitors.
- One third-party script: advertising. To fund free hosting, pages load an ad script from Monetag. It is the only code on this site not written for this site, and it is not part of the analyzer. Like any script embedded in a page, it runs alongside the page's own code — so the strict guarantees on this page describe the analyzer's own code, not code shipped by the ad network, whose behavior is governed by its provider's policy (see the privacy policy, section 4). The analyzer itself still never transmits or stores your results.
- No external fingerprint API. Some fingerprint checkers send your data to a backend service for processing or population comparison. This one does not — which is also why it honestly cannot tell you a "uniqueness percentage," as explained in the FAQ.
- No persistent identifiers from this site's own code. Visit today and tomorrow, and this site's own code has no way to know it is the same browser. The advertising script may set cookies or similar identifiers under its provider's policy — a trade-off we disclose rather than hide.
How to verify this yourself
You do not have to take this page's word for it. Your browser's developer tools can show the network requests a page makes: the analyzer's own scripts make none, including during an analysis run, so any requests you see belong to the advertising script and go to its ad-serving domains — never carrying your test results, which the analyzer's code does not hand to anyone. The same tools show cookies and storage: this site's own code creates none. The formal policy language lives in the privacy policy.