Preference signals
Reads Global Privacy Control and Do Not Track if they are exposed to JavaScript. These express a preference but do not themselves block every tracker.
Privacy signal inventory
Browser Privacy Test: See What Your Browser Reveals
This browser privacy test inventories information that a website can read in the current session. It checks privacy preference signals, browser and screen attributes, selected fingerprint outputs and the network metadata visible to BrowserCheck.
Privacy is not a single pass/fail state. A browser may block third-party cookies while still exposing screen or rendering values; another may send GPC while allowing site storage. The live panel separates these observations instead of combining them into an arbitrary anonymity score.
Your browser privacy signals
Review each exposed value independently. Missing data can mean protection, unsupported APIs or a blocked test.
- Global Privacy Control
- Unspecified
- Do Not Track
- Unspecified
- Cookies
- Disabled
- Canvas output
- Loading...
- Public IP
- Loading...
Copied and printed output omits IP addresses, the full User Agent, exact versions, fingerprint hashes, and precise location.
Privacy signals included
Browser storage clue
Reads navigator.cookieEnabled. The value does not reveal every third-party-cookie, partitioning or per-site exception policy.
Fingerprint surface
Computes local Canvas, WebGL, audio and layout hashes and samples a fixed font list to demonstrate readable inputs without estimating population rarity.
Request metadata
Shows the IP and approximate location metadata already visible to this site's Cloudflare request, without calling third-party IP lookup APIs from the browser.
Privacy results in context
GPC is a request, not a blocker
GPC communicates an opt-out preference. Its legal effect depends on jurisdiction, and technical compliance depends on the receiving site.
Fingerprint visibility is not measured uniqueness
A readable hash shows that a rendering surface is available. Determining rarity requires a representative comparison dataset that this test does not collect.
Unavailable needs investigation
An unavailable signal may be intentionally blocked, unsupported or interrupted. BrowserCheck leaves it unavailable rather than labeling it safe.
Privacy questions outside this test
- It does not observe every network request made by extensions, service workers, other tabs or installed applications.
- It does not verify whether every website honors GPC, DNT, consent choices or data-deletion requests.
- It does not prove anonymity, prevent fingerprinting or measure uniqueness across the web population.
- It does not inspect browser history, passwords, private files or extension contents.
Improve browser privacy deliberately
- 1Enable the browser's built-in tracking protection and review third-party-cookie settings.
- 2Enable GPC where available if it matches your preference, then understand that sites still need to honor it.
- 3Remove unnecessary extensions and site permissions instead of stacking many overlapping add-ons.
- 4Use the fingerprint and leak reports to investigate specific exposed surfaces without treating them as a universal score.
Browser privacy test FAQ
Is Do Not Track the same as Global Privacy Control?
No. Both communicate preferences, but GPC is designed around requests not to sell or share data, while DNT is an older general tracking preference. Recognition and legal treatment differ.
Does disabling cookies make me anonymous?
No. It can break site sessions and does not remove IP, browser attributes, local storage alternatives or fingerprinting surfaces.
Are my fingerprint hashes uploaded?
BrowserCheck computes and displays these hashes in the page. The site's analytics events do not include raw fingerprint hashes.
Investigate the exposed surface
Open the fingerprint report for rendering signals or the leak test for the WebRTC/request-IP comparison.