Exclude same site #109
Merged
Exclude same site #109
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Primarily just moved language up from previous Section 5 to replace the intro into Section 4. Section 5 largely duplicative but also contained the clear disclaimer about same-site tracking, so I thought it made sense to replace as the lead-in to the Legal Effects section.
j-br0
added a commit
that referenced
this pull request
Sep 16, 2025
Per earlier discussions, I'm merging this PR which we've already discussed, and have made additional edits in PR #109 to further address.
|
Thank you Justin, this looks good to me. |
Member
|
A lot of the terms in this document do not appear to be linked, including "site" or "same site". Is that intentional? |
Contributor
Author
|
@annevk I didn't think we needed to define "site" and we gave a concrete example in the Legal and Implementations Guide, but I'm certainly not opposed to adding more to be sufficiently precise. |
Member
|
I think I would either expect these to reference the existing definitions of "site" and "same site" (as defined in the HTML standard) or use different terms. |
jyasskin
reviewed
Nov 6, 2025
jyasskin
reviewed
Nov 6, 2025
every --> any per @jyasskin, clarifying GPC is not designed to invoke "every" possible right (as opposed to "any" possible right --- it is in fact designed to invoke at least some rights)
Co-authored-by: Jeffrey Yasskin <[email protected]>
SebastianZimmeck
approved these changes
Nov 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per the discussion on Issue #94, I've added (or in one case moved up) language to both the spec and the Legal and Implementation Considerations Guide to clarify that same-site tracking is outside the intended scope of GPC.
Preview | Diff