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

Clarify "targeted advertising" versus "cross-site targeted advertising"? #83

Open
michaelkleber opened this issue Nov 7, 2024 · 2 comments

Comments

@michaelkleber
Copy link

Section 5.6 says that GPC is explicitly not intended to prevent "a publisher targeting ads to a user on its website based on that user’s previous activity on that same site". But Sections 5.2 and 5.3 say that in Colorado and Connecticut, "the GPC signal will be intended to communicate a request to opt out of both the sale of their personal information and the use of their personal information for targeted advertising."

At face value I thought these were in conflict with one another. Per the side chat in today's meeting, perhaps I am mistaken, and 5.2/5.3 are only trying to refer to "cross-site targeted advertising" rather than all "targeted advertising".

If indeed the phrase "targeted advertising" is meant to always imply "cross-site", we should either explicitly say that, or use the full phrase each time. (I am personally nervous about explicitly saying that the "cross-site" part is implicit: we are discussion the specific details of many laws, and I wouldn't want us to accidentally mis-characterize some jurisdiction's law based on our adopting a non-universal conventional meaning for the phrase.)

@npdoty
Copy link
Contributor

npdoty commented Nov 21, 2024

Sounds like there may be agreement here on clarifying the terminology, and also that removing a lot of the legal implications language might decrease the potential conflicts here. Justin to propose a small change as needed.

@AramZS
Copy link
Member

AramZS commented Nov 21, 2024

In the PATWG's charter we talk about

Ways in which new features might enable inappropriate processing include (but are not limited to) enabling of cross-site or cross context recognition of users or enabling same-site or same-context recognition of users across the clearing of state.

is that maybe the type of language we want to specify here with the same supporting language?

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

No branches or pull requests

3 participants