-
Notifications
You must be signed in to change notification settings - Fork 46
Align all descriptions of GPC to say it restricts sharing and targeting between different organizations. #104
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
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -101,7 +101,8 @@ | |||||
| <p> | ||||||
| This document defines a signal, transmitted over HTTP and through the DOM, that conveys a | ||||||
| person's request to websites and services to not sell or share their personal information with | ||||||
| third parties. This standard is intended to work with existing and upcoming legal frameworks | ||||||
| third parties, or to have their data used for cross-organization ad targeting. | ||||||
| This standard is intended to work with existing and upcoming legal frameworks | ||||||
| that render such requests enforceable. | ||||||
| </p> | ||||||
| </section> | ||||||
|
|
@@ -115,7 +116,7 @@ <h2>Introduction</h2> | |||||
| services. While this architecture can be used in the service of better Web experiences, | ||||||
| it can also be abused to violate privacy ([[?privacy-principles]]). While data can be shared | ||||||
| with service providers for limited operational purposes, it can also be shared with third | ||||||
| parties or used for behavioral targeting in ways that many users find objectionable. | ||||||
| parties or used for [=cross-organization ad targeting=] in ways that many users find objectionable. | ||||||
jyasskin marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
| </p> | ||||||
| <p> | ||||||
| Several different legal frameworks have been proposed or enacted by jurisdictions around | ||||||
|
|
@@ -144,8 +145,8 @@ <h2>Introduction</h2> | |||||
| difficulty of scaling user choices by providing a way to universally signal to all website | ||||||
| publishers, through an HTTP header | ||||||
| or the DOM, a person's assertion of their applicable rights to prevent the sale of their data, | ||||||
| the sharing of their data with third parties, and the use of their data for cross-site targeted | ||||||
| advertising. This signal allows users to take advantage of specific provisions in some of these | ||||||
| the sharing of their data with third parties, and the use of their data for [=cross-organization targeted | ||||||
| advertising=]. This signal allows users to take advantage of specific provisions in some of these | ||||||
jyasskin marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
| opt-out based laws, such as, for example, the provisions relating to "opt out preferences | ||||||
| signals" in the California Consumer Privacy Act. [[?CCPA-REGULATIONS]]. | ||||||
| </p> | ||||||
|
|
@@ -161,7 +162,7 @@ <h2>Definitions</h2> | |||||
| <p> | ||||||
| A <dfn>do-not-sell-or-share interaction</dfn> 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, | ||||||
| one the person intends to interact with, or to have their data used for [=cross-organization ad targeting=], | ||||||
|
||||||
| one the person intends to interact with, or to have their data used for [=cross-organization ad targeting=], | |
| one the person intends to interact with, or to have their data used for [=cross-site ad targeting=], |
s/organization/party/
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.
Your suggestion says "site" here, but I've switched it to "party".
Outdated
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.
An explicit mention that "organization" is something that varies by the jurisdiction could be useful.
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.
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.
Undoing this change. I think the implicit inclusion of ads stuff is best for the abstract.
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'm not sure about this change: @j-br0 and @AramZS seem to be arguing that cross-party ad targeting isn't just a kind of sharing (or else #102 would be acceptable), and if that's a common opinion, I think the abstract should mention both.
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.
It wasn't as clear to me that they were opposed from the discussion, but I may have missed it in the subtlety of performing vs facilitating cross party ad targeting. I agree that if the editors think it is useful to identify as an independent behavior to call out in the abstract that we should continue to do so and the diff you already have in this PR is good.