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

Update Explainer to add new 6.4 (Consent to Track Notwithstanding a Universal GPC Signal) #88

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

j-br0
Copy link
Contributor

@j-br0 j-br0 commented Dec 4, 2024

Added new section 6.4 to address #80 on when separate consent to track can override GPC.

Added new section 6.4 to address Issue-80 on when separate consent to track can override GPC
Copy link
Contributor

@bvandersloot-mozilla bvandersloot-mozilla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Am improvement, particularly with the paragraph about bombarding users with consent prompts

Copy link
Member

@jyasskin jyasskin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would still be useful to also say something very short in the normative spec itself, but this is good text for the explainer.

@j-br0
Copy link
Contributor Author

j-br0 commented Dec 4, 2024

I think it would still be useful to also say something very short in the normative spec itself, but this is good text for the explainer.

Any recommendation on where that should be? Maybe a sentence or two in 5.3 (maybe in lieu of some of the existing language in the second half of that section which is largely duplicative of what's now in the explainer)?

@jyasskin
Copy link
Member

jyasskin commented Dec 4, 2024

It ought to be somewhere in the definition of the meaning of the Sec-GPC header. That's in 3.3:

The Sec-GPC header field is a mechanism for expressing the person's preference for a do-not-sell-or-share interaction in an HTTP request (for any request method).

which refers to section 2:

A do-not-sell-or-share interaction is an interaction with a website in which the 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-site ad targeting, except as permitted by law.

A possible change could be "... except as permitted by law or specifically arranged between the person and the website."?

@rinchen
Copy link
Member

rinchen commented Dec 5, 2024

These changes look good to me. I don't have any opinions on Jeffrey's comment but the suggested wording looks good to me.

Copy link
Member

@martinthomson martinthomson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

grammar is hard. "company requests" seemed a bit off to me.

explainer.md Outdated Show resolved Hide resolved
j-br0 and others added 2 commits January 8, 2025 14:44
Minor wording change as suggested by Martin Thompson

Co-authored-by: Martin Thomson <[email protected]>
Amended 5.3 to add reference to different jurisdictions having different rules for consent to override, and deleted extraneous legal analysis that is duplicative of the Explainer (Legal and Implementation Considerations guide).
@j-br0 j-br0 added the agenda+ Request to add this issue to the agenda of our next telcon or F2F label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agenda+ Request to add this issue to the agenda of our next telcon or F2F
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants