Privacy

Privacy dashboard

Run all checks in your browser, no data sent to our servers. See exactly what websites can learn about you.

Privacy score
…/ 100

Higher is better. Score reflects WebRTC IP exposure, fingerprint uniqueness signals, and Do Not Track / GPC.

Public IP

WebRTC leak test

Probing…

Browser fingerprint

Privacy signals

How to improve

  • • Use a reputable VPN to mask your public IP.
  • • Disable WebRTC in your browser or install a leak-blocking extension if you use a VPN.
  • • Enable Global Privacy Control in your browser settings.
  • • Use a privacy-respecting DNS resolver (e.g. 1.1.1.1, 9.9.9.9).

What this dashboard does

The Privacy Dashboard runs four orthogonal checks in your browser: your apparent public IP, a WebRTC leak probe, a browser fingerprint snapshot, and the state of privacy signals (Do Not Track and Global Privacy Control). It then combines them into a single 0–100 privacy score so you can see at a glance how exposed you are.

Why it matters

Most privacy advice ("use a VPN", "block cookies") only addresses one vector. Tracking and fraud-detection systems combine network-layer, browser-layer, and behavioural signals. Testing all of them in one place is the only honest way to evaluate your real exposure.

How to interpret your score

  • 80–100 (green) — strong baseline. No WebRTC leak, privacy signals enabled.
  • 60–79 (yellow) — usable but improvable. Likely missing GPC or leaking via cookies.
  • Below 60 (red) — actively exposing your real IP or fingerprint. Fix the WebRTC leak first.

Common use cases

  • Verify your VPN is not leaking your real IP via WebRTC.
  • Confirm a privacy-focused browser (Brave, Firefox + arkenfox, Tor) actually reduces exposure.
  • Validate that Global Privacy Control is being sent by your browser.
  • Compare desktop vs mobile vs incognito exposure for the same network.

Limitations

The dashboard cannot detect every fingerprint vector — canvas hashes, audio context, font enumeration, and battery API tells are out of scope. It also cannot evaluate DNS leakage beyond what your browser's resolver exposes. For deeper checks see the VPN leak test.

Methodology

Public IP is fetched from ipapi.co. WebRTC IPs come from standard RTCPeerConnection ICE candidates against Google's STUN server. Fingerprint values come from navigator andscreen. The score formula is documented inline; no data leaves your browser besides the IP API request. See full methodology and data sources.

Frequently asked

What is a WebRTC leak?
WebRTC is a peer-to-peer protocol baked into every modern browser. To establish a connection it discovers local and public IPs and exposes them to JavaScript — including, in some configurations, your real public IP even while a VPN is active.
Does a VPN make me anonymous?
No. A VPN hides your network-layer IP from the destination, but does nothing about browser fingerprinting, cookies, login state, or WebRTC. True anonymity requires Tor plus careful operational hygiene.
What is browser fingerprinting?
The practice of combining many low-entropy signals — fonts, timezone, GPU, screen, audio context — into a near-unique identifier. Sites can recognise you across visits without cookies.
What does the privacy score actually measure?
It's a heuristic: 100 minus penalties for WebRTC IP exposure (-30), Do Not Track / GPC disabled (-15), and third-party cookies enabled (-5). It signals risk, not absolute privacy.
Does enabling Do Not Track do anything?
DNT is advisory — most ad networks ignore it. Global Privacy Control (GPC) is legally binding in some jurisdictions (California, Colorado). Both are worth enabling.