Privacy
Collect, display, discard
| Data | Where | What happens |
|---|---|---|
| Public IP address | Server | Used to answer the request. Kept only in short-lived cache keys and rate-limit counters; not written to logs. |
| IP intelligence (location, ASN, ISP) | Server | Cached by IP for up to 6 hours to avoid repeated lookups. Contains no browser or request data. |
| Request headers | Server | Reflected back to you from an allowlist. Cookies and authorization headers are never shown or stored. |
| Browser fingerprint, canvas, WebGL, audio, fonts | Your browser | Computed and displayed locally. Never uploaded during a normal visit. |
| WebRTC public IP check | Your browser + STUN | Uses a public STUN server (stun.l.google.com) to discover a public-facing IP for comparison with the IP this site sees. No fingerprint data is sent to it — only the standard STUN handshake. |
| Verification duplicate-check hashes | Server (paid plans) | Keyed, site-scoped hashes only, kept for the integrating site's plan retention window so it can ask "seen before?". No raw values. Nothing on the Free plan. |
| Verification history | Server (Growth/Business) | Full result (browser, network including your real IP, classification) for past verifications, kept for the site's retention window so it can review them. Encrypted at rest (AES-256-GCM); decrypted only when the site's own authorized team views its own history. Nothing on the Free plan. |
| Returning-browser classification | Server (paid plans, when enabled) | Site-scoped keyed hashes and coarse buckets of browser signals, used to recognise a returning browser for that site only. No raw values. Deleted on the integrating site's request or when retention ends. |
| Optional stored identifier | The integrating site's storage | Only if that site enables it: a random ID in the site's own localStorage, sent with verification and stored here only as a keyed hash. |
| Last test summary | Your browser | Kept in localStorage for the Test again comparison. Clear it from the comparison panel or your browser settings. |
| Tab session ID | Your browser | Random value in sessionStorage, discarded when the tab closes. Never sent. |
| Cookies | Your browser | None on the public site. Signing in to the console sets a session cookie. |
Share results
Share results creates a text summary with a partially masked IP and hands it to your device’s share sheet or clipboard. Nothing is stored on the server. If saved report links are added in future, a snapshot will only be stored when you explicitly create one, it will expire automatically (default 7 days), and it will never contain proxy credentials.
Verification product
Sites that integrate our verification script send a browser fingerprint and receive your IP and network details on their own backend, through a short-lived encrypted token. Nothing is kept for sites on the Free plan. On a Growth or Business plan, the integrating site can review its own past verification results (browser, network and classification details, including your IP address) for its retention window. That history is encrypted at rest — AES-256-GCM, with a key only this deployment holds — and decrypted only when the integrating site's own authorized team views its own history; a stolen database backup reveals nothing. This is a reversible protection, not a one-way hash: unlike the values below, it can be decrypted by whoever holds the key, which today is us, on the integrating site's behalf. Separately, we keep a keyed hash of the device identifier, fingerprint and IP (not the values themselves, and never reversible by anyone, including us), scoped to that one site, so it can ask whether it has seen a device before; those hashes cannot be matched across different sites. When the site enables returning-browser recognition, we also keep site-scoped keyed hashes of browser signals so it can tell whether the same browser returns. The integrating site decides what to do with any of this, under its own privacy policy. For console accounts we store your name, email, sign-in method, sessions, projects, hashed API keys, allowed origins and daily usage counts. We also run this same verification on our own console's sign-in and sign-up pages, using a normal project on this deployment, so we can test it the way an integrating site would. It never blocks or delays signing in; results are kept for 30 days and visible only to console administrators.
Logs
Server logs are structured and record the request path, status, timing and a random request ID. Passwords, tokens, cookies, authorization headers and proxy credentials are redacted before anything is written.
Third parties
IP intelligence is resolved from locally hosted databases by default, so your IP is not sent to a third-party lookup service. The Tor exit list is downloaded periodically from the Tor Project; your IP is not sent to it. The fingerprinting library’s usage ping is disabled. The WebRTC public IP check (used to compare against the IP this site observes) performs a standard STUN handshake with a public Google STUN server; this reveals your public IP to that server the same way any WebRTC-based site would, but sends it no other data.