Privacy

A privacy tool that collects your data would be a contradiction. Here is exactly what happens when you run an audit.

What we collect

Nothing on our servers. The audit runs in your browser. Results are computed locally and rendered locally. We do not run any analytics, tracking pixels, A/B tests, session replay, or remote logging.

Outbound requests

The page makes exactly two kinds of network calls:

• Static assets — HTML, CSS, JS, and the favicon. These are served from this domain and are required to render the page.
• IP geolocation — a single fetch to ipapi.co when you click "Run the audit", to look up the city / ISP for your IP. ipapi.co necessarily sees your IP (that's the whole point) and has its own privacy policy. If you block this request, the rest of the audit still runs — you just won't see geolocation data.

WebRTC, fingerprinting, etc.

The fingerprinting checks (canvas, WebGL, fonts, WebRTC) all execute and resolve inside your browser. The hashes and signatures we compute are shown to you and never leave your device.

Cookies

We don't set any. No first-party cookies, no third-party cookies, no localStorage, no fingerprint we use to recognise you between visits. Open your browser's storage inspector and confirm.

Verifying these claims

Open your browser's network tab (F12 → Network) and reload. You will see a small handful of requests for the page itself, plus one request to ipapi.co when you start the scan. That's the entire footprint.

Server logs

The static host serving this site retains standard HTTP access logs (IP, request path, timestamp, user-agent) for a short window for abuse / debugging purposes only. These logs are never associated with audit results — there are no audit results to associate them with.

Changes to this policy

If anything ever changes — say we add an optional account feature — this page will be updated and the change will be noted here. For now, last updated April 2026.

Contact

Concerns or questions: hello@browserinspector.net.