Your browser has already introduced itself.
Every site you open reads this without asking. Here is the same reading, shown to you.
Local collection requires JavaScript. The explanation below remains available without it.
How recognition works without cookies
A fingerprint is not stored on your device. It is assembled from what the browser answers.
- 01
Nothing is saved on your side
Clearing cookies leaves the fingerprint intact: the screen, fonts and graphics chip answer the same way tomorrow.
- 02
A VPN changes the address, the answers stay
The address becomes someone else’s, the fingerprint stays yours — and it stitches sessions together.
- 03
Sameness helps
The closer a browser is to a mass configuration, the less it stands out. Rare fonts and exotic settings work against you.
Terracotta marks the loud signals
Screen geometry, time zone, canvas and audio rendering, and the font list carry the most information. They are also the hardest to hide without breaking pages.
The report shows observed signals without an invented uniqueness percentage: answers overlap, and a browser may deliberately limit their precision.
Where does this data go
Nowhere. The page has no analytics and makes no network requests while collecting. Closing the tab erases the report.
Why the number changes between runs
Some signals depend on the window and on what the browser is willing to answer at the moment. Resizing the window or switching displays shifts the reading.
What actually reduces the fingerprint
A mainstream browser in its default configuration, a standard window size, the system font set, and built-in fingerprint protection where the browser offers it. Exotic extension combinations make you more recognisable, not less.
Recognition is one thing. Ownership is another.
Mail, files, knowledge and AI in a contour where the keys stay with you.