- From: Lukasz Olejnik <notifications@github.com>
- Date: Thu, 09 Jan 2025 03:57:42 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 9 January 2025 11:57:46 UTC
> We understand that Protected Audience is a substitute mechanism to enable ad targeting, specifically where targeting is based on specific actions that someone took on other sites. This use case was previously supported by cross-site cookies. > > The TAG is supportive of efforts to improve web privacy, particularly the [withdrawal of cross-site cookies](https://www.w3.org/2001/tag/doc/web-without-3p-cookies/), > > We recognize that the web is not perfect. There are lots of ways that cross-site information still leaks, especially when it comes to navigation. But we do insist that new work [leaves the web in a better state than it was found](https://www.w3.org/TR/design-principles/#leave-the-web-better) - our goal as web platform developers acting in good faith is to patch these vulnerabilities, and not create new means of cross-site recognition. > > If Protected Audience exists to support ad targeting based on cross-site information, it has to ensure that it does not enable cross-site recognition. Out of curiosity, was your baseline considered a situation with third-party cookies on or off? What's the standard situation on the Web today? -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/723#issuecomment-2579976153 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/723/2579976153@github.com>
Received on Thursday, 9 January 2025 11:57:46 UTC