Skip to content

Wording choice MAY --> can#126

Merged
j-br0 merged 1 commit into
mainfrom
issue-35-may-can
Feb 3, 2026
Merged

Wording choice MAY --> can#126
j-br0 merged 1 commit into
mainfrom
issue-35-may-can

Conversation

@j-br0

@j-br0 j-br0 commented Dec 18, 2025

Copy link
Copy Markdown
Contributor

Per Issue #35 and discussion at WG call on 12/18, changing the word "MAY" to "can" in the following sentence to be factual instead of implying that we're granting optionality:

"In the absence of regulatory, legal, or other requirements, websites MAY interpret an expressed Global Privacy Control preference as they find most appropriate for the given person, particularly as considered in light of the person's privacy expectations, context, and cultural circumstances."


Preview | Diff

Per discussion at WG call on 12/18, changing the word "MAY" to "can" in the following sentence to be factual instead of implying that we're granting optionality: 

"In the absence of regulatory, legal, or other requirements, websites MAY interpret an expressed Global Privacy Control preference as they find most appropriate for the given person, particularly as considered in light of the person's privacy expectations, context, and cultural circumstances."
@SebastianZimmeck SebastianZimmeck self-requested a review December 18, 2025 21:08
@j-br0 j-br0 merged commit f269cf6 into main Feb 3, 2026
1 check passed
@j-br0 j-br0 mentioned this pull request Feb 3, 2026
@jyasskin jyasskin deleted the issue-35-may-can branch February 3, 2026 14:51
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