We measure how your exact GPU and CPU behave and reduce it to one stable ID, with no cookie and no login.
A fingerprint is measured from hardware, so there is nothing stored for you to clear.
Your browser exposes how your hardware renders graphics and does floating-point math. Those quirks differ between machines and stay identical on yours, which is enough for a stable ID.
Private windows and "clear cookies" only wipe stored data. They don't change your GPU or CPU, so the fingerprint is identical the moment you reopen the page.
No. Nothing is written – no cookie, no login, no local storage. The ID is derived live from how your hardware behaves and then discarded. Reload and it is recomputed from scratch.
No. Private modes only clear stored data, not your GPU or CPU. The same ID appears in incognito, in private windows, and in most other browsers on this machine.
A VPN changes your IP address, not your device fingerprint. The ID here is built from hardware behavior, so it stays the same whether or not a VPN is on.
Privacy-focused browsers like Tor and hardened forks randomise some signals, and disabling WebGL takes one away, both at a cost to how pages render. Nothing removes fingerprinting entirely.
TrustSig reads the same hardware layer to tell people from bots, then scopes what it finds to one project. No challenge, no cookie, no id that travels.
Already in production
Publishing platforms, fintech and national charities across Europe already run TrustSig on their forms.