-
Notifications
You must be signed in to change notification settings - Fork 45
Clarifications and anchoring #108
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
base: main
Are you sure you want to change the base?
Conversation
index.html
Outdated
| person is requesting that their data not be sold to or shared with any party other than the | ||
| one the person intends to interact with, or to have their data used for cross-context ad targeting, | ||
| except as permitted by law. | ||
| except as permitted by law. In terms of the W3C's [[[privacy-principles]]], the person is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Requesting a single controller is not all that the person may be requesting or that the law promises. (In many cases a single large controller can perpetrate more cross-context privacy harms than several small ones, and laws requiring OOPSes do put some obligations on large multi-context controllers)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made changes there to clarify, let me know if it works.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New version looks much better, thank you
index.html
Outdated
| every website visited by the user. GPC is also not intended to limit a first party’s use of | ||
| personal information within the first-party context (such as a publisher targeting ads to a | ||
| every website visited by the user. GPC is also not intended to limit a <a data-link-type="dfn" href="https://www.w3.org/TR/privacy-principles/#dfn-first-party-0">first party</a>’s use of | ||
| personal information within the first-party <a data-link-type="dfn" href="https://www.w3.org/TR/privacy-principles/#dfn-context">context</a> (such as a publisher targeting ads to a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would "same context" be clearer than "first-party context" ? So:
GPC is also not intended to limit a first party’s use of personal information within the same context
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right, same context is clearer. See update.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you
| <h3>Other Jurisdictions and Privacy Rights</h3> | ||
| <p> | ||
| GPC could potentially be used to indicate rights in other jurisdictions as well. For example, the | ||
| GDPR potentially affords data subjects the right to limit the sharing of personal information under |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please don't mix semantic changes into a PR that mostly just adds links. It makes it hard to notice and vet the semantic changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's fair of course, but this isn't much of a semantic choice. "Potentially" is repeated two sentences in a row and the existence of this right isn't hypothetical by any measure. Happy to revert this change if you prefer but it's clear that this is a simple phrasing error.
This is a small and simple PR that updates GPC to be more anchored in the Privacy Principles now that they have been ratified (along with a couple of typos). This helps ensure a coherent use of privacy across the platform, as intended by the TAG.
(This PR references concepts that were unfortunately not exported correctly; this should be fixed in a few hours as xref republishes. Otherwise, I will make another fix.)
Preview | Diff