Chrome privacy exposure check
Chrome dominates browser market share — which cuts both ways for privacy. Find out what your Chrome installation reveals and whether you blend into the crowd.
Chrome and browser fingerprinting
Google Chrome is used by roughly two-thirds of internet users globally, which creates an unusual privacy dynamic. Because so many people use it, a Chrome fingerprint does less to uniquely identify any individual visitor than a rare browser would. This "crowd anonymity" partially offsets the fact that Chrome offers minimal built-in fingerprint protection.
Chrome exposes a rich set of fingerprinting signals: a detailed User-Agent string and the newer User-Agent Client Hints headers that reveal platform, architecture, full version list, and whether the device is mobile. The canvas API and WebGL return hardware-specific rendering output with no randomisation. JavaScript can query screen dimensions, color depth, device pixel ratio, timezone, language, CPU core count, and device memory — all without user permission.
Google has been phasing out third-party cookies through the Privacy Sandbox project, replacing them with on-device APIs like Topics and Protected Audience. These APIs are designed to serve ads without exposing individual browsing history to third parties. However, Privacy Sandbox does not address browser fingerprinting — the passive collection of technical signals remains fully available to any website.
Chrome's Incognito mode prevents cookies and history from persisting after the session, but all fingerprint signals remain intact during the session. For meaningful fingerprint protection in Chrome, extensions like uBlock Origin reduce the number of tracking scripts that run, and switching to a privacy-focused alternative like Firefox or Brave provides built-in protection that does not require configuration.
What we measure in your Chrome session
- User-Agent & Client Hints — full version list, platform, architecture bits
- HTTP headers — Accept-Language, Sec-Fetch-*, Sec-CH-UA headers
- Screen & display — resolution, color depth, pixel ratio
- System locale & timezone — Intl API, timezone offset consistency
- Canvas fingerprint — raw rendering output, noise detection
- WebGL — renderer string, vendor, extension list, parameter bundle
- Audio fingerprint — AudioContext processing characteristics
- Font detection — available system fonts via glyph metrics
- Hardware signals — CPU cores, device memory, connection type
- IP geolocation — country, region, ISP (local MaxMind lookup)
See your Chrome browser's real privacy score — live analysis, no account needed.
Check my Chrome scoreFrequently asked questions
Does Incognito mode protect against fingerprinting in Chrome?
No. Incognito mode prevents Chrome from saving your browsing history, cookies, and form data to disk after the window closes. It does not change any of the technical signals your browser sends during the session. Your canvas fingerprint, screen dimensions, User-Agent, and all other signals are identical in Incognito and normal windows.
Will Chrome's Privacy Sandbox stop fingerprinting?
Privacy Sandbox targets cookie-based cross-site tracking and replaces it with on-device interest classification. It does not restrict access to the JavaScript APIs used for fingerprinting (canvas, WebGL, screen, navigator properties). Google has proposed some fingerprinting mitigations as longer-term work, but none are deployed in standard Chrome at this time.
Is Chrome more private with extensions?
Extensions like uBlock Origin block the scripts that collect fingerprints before they run, which is the most practical protection available in Chrome. They don't randomise or spoof your signals, but they prevent tracking scripts from ever reading them. Combine a content-blocking extension with Chrome's built-in safety check (Settings → Privacy and security) for the best results within Chrome.