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

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. This site does not measure its visitors.
  • No third-party scripts. All JavaScript is served from this domain, and fonts come from your operating system rather than a remote font service.
  • 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 of any kind. Visit today and tomorrow, and this site has no way to know it is the same browser — fitting, for a site about exactly that risk.

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 (there should be none after the site's own files load, including during an analysis run) and the cookies and storage a site has created (there should be none from this site). The formal policy language lives in the privacy policy.

Related pages