Discover and read the best of Twitter Threads about #PrivacySandbox
Most recents (2)
Thread explaining FLEDGE (formerly TURTLEDOVE).
Online advertising generates value for publishers, advertisers, & users. Now, Google & others are proposing alternatives that preserve this value while better protecting user privacy under the "Privacy Sandbox" proposals. 1/12
Online advertising generates value for publishers, advertisers, & users. Now, Google & others are proposing alternatives that preserve this value while better protecting user privacy under the "Privacy Sandbox" proposals. 1/12
The public discussion of #PrivacySandbox is dominated by #FLoC, but many tech solutions are required to satisfy advertising use cases while protecting privacy. In particular, #FLEDGE propose more fundamental & interesting changes to the status quo. 2/
The key to FLEDGE is to move user targeting information onto the *browser*, rather than broadcasting a cookie ID to the adtech ecosystem so advertisers can bid on ad opportunities based on what they know about that cookie ID. The prototypical FLEDGE use-case is retargeting. 3/
This whole conversation between Justin and Robin is incredibly frustrating to read, and reinforces my lack of trust in Google/Chrome around #privacy issues, particularly in relation to their #PrivacySandbox proposals.
A little bit of context first - this isn't just some argument between random dudes on the internet.
Justin was "Engineering Director on Chrome Security & Privacy" for the last 11+ years, retiring just under a month ago.
Justin was "Engineering Director on Chrome Security & Privacy" for the last 11+ years, retiring just under a month ago.
Justin's original assertion is that Chrome's privacy label on the Apple app store shows so much data being collected because the *sites* you visit via Chrome can collect that data, and all other browsers should be listing the same labels.
