Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

geo hint missing privacy considerations #196

Open
npdoty opened this issue Apr 27, 2022 · 0 comments
Open

geo hint missing privacy considerations #196

npdoty opened this issue Apr 27, 2022 · 0 comments
Labels

Comments

@npdoty
Copy link

npdoty commented Apr 27, 2022

What are the privacy implications of adding back geolocation information, particularly when an IP proxy has removed the ability to infer it? (This initial issue won't have nearly every question or consideration, but could be a starting point.)

Honestly, it's been 18 years since an RFC was published on location privacy requirements (rfc 3693); our privacy expectations and legal compliance regimes have since increased.

Do we want to add sensitive information to HTTP headers without any description of limits on how that information can be used, or any enforceable policy statements from the requester about their compliance?

What are the risks of inferring more precise geolocation by observing/linking multiple geo hint locations over time? See rfc 6772, for example.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants