Skip to content

Commit

Permalink
Update link to refer to third-party cookie user choice
Browse files Browse the repository at this point in the history
  • Loading branch information
miketaylr committed Feb 26, 2025
1 parent a7afd66 commit d231d37
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Explainer-IP-Geolocation.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

## Context and Goals

Location can be a key identifier for understanding what content is relevant for users. As Chrome prepares to [deprecates third party cookies](https://privacysandbox.com/), the Chrome team wants to ensure that we are taking appropriate steps to improve privacy on the web while also maintaining key use cases. We have [shared our proposal](https://github.com/GoogleChrome/ip-protection) for masking IP addresses for certain third party domains on the web. This comes with additional implications, like how IP addresses are used to understand the location of [GitHub - GoogleChrome/ip-protection](https://github.com/GoogleChrome/ip-protection) web users. This document outlines our initial proposal for how IP Protection will implement IP geolocation mappings.
Location can be a key identifier for understanding what content is relevant for users. As Chrome prepares to [offer users an informed choice on third-party cookies](https://developers.google.com/privacy-sandbox/cookies/prepare/overview), the Chrome team wants to ensure that we are taking appropriate steps to improve privacy on the web while also maintaining key use cases. We have [shared our proposal](https://github.com/GoogleChrome/ip-protection) for masking IP addresses for certain third party domains on the web. This comes with additional implications, like how IP addresses are used to understand the location of [GitHub - GoogleChrome/ip-protection](https://github.com/GoogleChrome/ip-protection) web users. This document outlines our initial proposal for how IP Protection will implement IP geolocation mappings.

It’s worth noting that IP geolocation—with or without IP Protection—only provides approximate and coarse location information and that there are ways in which users can obfuscate this data. With this proposal, we aim to improve user privacy while maintaining most of the existing uses of IP geolocation as a coarse location signal. Addressing pre-existing accuracy issues of IP geolocation is not a goal and generally, this proposal will inherit the prior limitations of IP as a source of location information.

Expand Down

0 comments on commit d231d37

Please sign in to comment.