Skip to content

Clarify scope of GPC #99

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify scope of GPC #99

wants to merge 1 commit into from

Conversation

j-br0
Copy link
Contributor

@j-br0 j-br0 commented Apr 15, 2025

This PR is designed to

(1) Clarify to regulators the scope of rights intended to be invoked by GPC and
(2) Clarify the spec does not prescribe user interface language --- implementers should describe a privacy feature or setting they want to provide users and decide based on that whether it is appropriate to send GPC.


Preview | Diff

Clarify what rights GPC is intended to invoke.
The GPC signal was designed to allow users to take advantage of legal rights to stop certain
sharing or processing of their data. As such, the sending and receipt of a GPC signal may
The GPC signal was designed to allow users to take advantage of legal rights to <i>stop certain
sharing or processing of their data</i>. As such, the sending and receipt of a GPC signal may
Copy link
Member

Choose a reason for hiding this comment

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

It's not clear what adding italics conveys here.

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

Successfully merging this pull request may close these issues.

2 participants