WebmasterID logoWebmasterID
Privacy & compliance

IP Protection in Chrome

IP Protection is a Chrome proposal to reduce cross-site tracking by hiding a user's IP address from certain third-party domains, initially in Incognito, by routing eligible requests through a two-hop proxy so no single party sees both identity and destination. This page explains the design at a high level and what it does and does not change for analytics.

Partially verified

What IP Protection does

The IP address is a stable signal that can be used to link a user across sites. IP Protection aims to limit that by routing connections to certain tracking-associated third-party domains through privacy proxies, so those domains see a proxy IP instead of the user's. A two-hop design is described so that no single proxy operator sees both who the user is and which site they are contacting.

Scope and limits

IP Protection is scoped: it affects eligible third-party requests, not first-party connections to the site the user is visiting, and it applies to users for whom the feature is active. It does not anonymise everything, and IP is only one of many possible signals. Because this is an evolving proposal, the exact domain coverage, rollout, and behaviour should be verified against Chrome's current documentation rather than assumed.

How it appears in analytics and logs

For users on IP Protection, third-party requests on the list may see a proxy IP rather than the user's real one, so coarse geo or network fields from those endpoints can shift.

Diagnostic use case

Understand that IP-derived signals (such as approximate geolocation) from some third parties may be degraded for protected users, so you do not over-read IP-based fields.

What WebmasterID can help detect

WebmasterID derives coarse geography from privacy-safe signals and does not store raw IP addresses, so its approach is unaffected by third-party IP masking.

Common mistakes

Privacy and accuracy notes

This page is educational and not legal advice. IP Protection is a Chrome feature proposal whose scope and availability can change; always check current Chrome and Privacy Sandbox documentation.

Related pages

Sources and verification notes

Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.