Google's FLoC flopped, boffins claim, because it failed to provide promised privacy
(2022/05/05)
- Reference: 1651732213
- News link: https://www.theregister.co.uk/2022/05/05/googles_floc_flopped_boffins_claim/
- Source link:
Computer scientists from MIT Media Lab have exhumed the corpse of Google's FLoC ad targeting scheme and found that it lacked its key advertised ingredient: privacy.
[1]FLoC stands for Federated Learning of Cohorts. It consists of [2]computer code designed to deliver interest-based ads without the privacy problems of current cookie-based ad technology.
"FLoC provides a privacy-preserving mechanism for interest-based ad selection," explains Sam Dutton, Google Chrome developer advocate, on Google's web.dev site.
[3]
It was to have been one of a number of technologies with bird-themed names within what Google optimistically calls " [4]The Privacy Sandbox " – an initiative "to create technologies that both protect people's privacy online and give companies and developers tools to build thriving digital businesses."
[5]
[6]
As an alternative to the current privacy hellscape – wherein websites and their embedded tracking scripts can identify visitors, know what websites they've visited, and serve them ads linked to all manner of personal characteristics and conditions – FLoC aimed to aggregate website visitors into numbered groups called cohorts. These cohorts corresponded to various interest categories derived from people's browsing histories, but without making those people identifiable or exposing their browsing histories.
In theory, websites implementing FLoC could send a visitor's cohort identification number to an ad server and fetch an ad likely to align with the visitor's past browsing behavior without being able to surmise the identity of the visitor.
[7]
How FLoC worked
But FLoC barely made it off the ground. Following its [8]initial code commit in August 2019, and its Chrome browser trial [9]in early 2021 , Google [10]allowed its experiment to expire without renewal in July 2021, in order to make unspecified changes. Then, in January 2022, Google dispersed FLoC and [11]replaced it with another interest-based ad scheme, also ostensibly privacy-preserving, called the [12]Topics API .
Undaunted by rival browser makers like Apple, Brave, and Mozilla, or advocacy groups like the [13]Electronic Frontier Foundation , who have questioned both Google's motives and its technology, Google keeps repeating the word "privacy" in connection with its still-experimental adtech stack.
[14]Google starts testing fenced frames to guard its Privacy Sandbox
[15]Google resumes shoveling stuff into its 'Privacy Sandbox'
[16]Google expands Privacy Sandbox to Android
[17]Google dumps interest-based ad system for another interest-based ad system
Yet in a recent [18]research paper titled "Privacy Limitations Of Interest-based Advertising On The Web: A Post-mortem Empirical Analysis Of Google's FLoC," MIT Media Lab doctoral students Alex Berke and Dan Calacci argue that FLoC failed to provide privacy, and put personal information at risk.
Privacy advocates expressed those concerns about FLoC when it was being tested. But Google never revealed how its tests went, leaving observers to wonder about the results. So Berke and Calacci decided to investigate.
[19]
The two academics set about implementing FLoC using available open source code. They computed cohorts – interest groups – for users based on a dataset of more than 90,000 devices from about 50,000 households across the US, complemented by demographic data from those households.
[20]Their analysis indicated that FLoC's critics were spot-on, and they speculate that FLoC's privacy problems were what led Google to trade FLoC for the Topics API.
"First, contrary to its core aims, FLoC enables the tracking of individual users across sites," the paper states. "We find that more than 95 percent of user devices are uniquely identifiable after only four weeks. We then show how these estimates are extremely conservative, and that this risk increases with the use of common device fingerprinting methods."
[21]
However, FLoC was not entirely without merit. The researchers note that while there's a relationship between sensitive user demographics like race and income and browsing behavior, the FLoC algorithm they tested did not group users into cohorts based on race or income. That counts for something.
Berke and Calacci argue that those developing this sort of technology should publish tools, sample datasets, and code – as they have done – to allow other researchers to test whatever claims are being made.
"Google canceled FLoC in favor of a new approach (Topics), which is a more privacy-preserving step in the direction towards advertising based on contextual content," the paper explains. "However, like FLoC, it is still premised on tracking users' browsing behaviors and future work will need to demonstrate that this new approach goes far enough to preserve user privacy." ®
Get our [22]Tech Resources
[1] https://web.dev/floc/
[2] https://github.com/WICG/floc
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/personaltech&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2YnOgTHiWSYAW0P0H3Rny-AAAAIU&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[4] https://privacysandbox.com/intl/en_us/
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/personaltech&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YnOgTHiWSYAW0P0H3Rny-AAAAIU&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/personaltech&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YnOgTHiWSYAW0P0H3Rny-AAAAIU&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[7] https://regmedia.co.uk/2021/04/14/floc.png
[8] https://github.com/WICG/floc/commit/87740765c1ef25a34d32bceaec87b6c2315b4dc0
[9] https://www.theregister.com/2021/01/25/google_targeted_advertising/
[10] https://www.theregister.com/2021/07/08/google_floc_changes/
[11] https://www.theregister.com/2022/01/26/google_floc_topics/
[12] https://developer.chrome.com/docs/privacy-sandbox/topics/
[13] https://www.theregister.com/2021/03/05/eff_google_floc/
[14] https://www.theregister.com/2022/05/03/google_fenced_frames/
[15] https://www.theregister.com/2022/03/29/google_privacy_sandbox/
[16] https://www.theregister.com/2022/02/17/google_privacy_sandbox/
[17] https://www.theregister.com/2022/01/26/google_floc_topics/
[18] https://arxiv.org/abs/2201.13402
[19] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/personaltech&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YnOgTHiWSYAW0P0H3Rny-AAAAIU&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[20] https://github.com/aberke/floc-analysis
[21] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/personaltech&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YnOgTHiWSYAW0P0H3Rny-AAAAIU&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[22] https://whitepapers.theregister.com/
[1]FLoC stands for Federated Learning of Cohorts. It consists of [2]computer code designed to deliver interest-based ads without the privacy problems of current cookie-based ad technology.
"FLoC provides a privacy-preserving mechanism for interest-based ad selection," explains Sam Dutton, Google Chrome developer advocate, on Google's web.dev site.
[3]
It was to have been one of a number of technologies with bird-themed names within what Google optimistically calls " [4]The Privacy Sandbox " – an initiative "to create technologies that both protect people's privacy online and give companies and developers tools to build thriving digital businesses."
[5]
[6]
As an alternative to the current privacy hellscape – wherein websites and their embedded tracking scripts can identify visitors, know what websites they've visited, and serve them ads linked to all manner of personal characteristics and conditions – FLoC aimed to aggregate website visitors into numbered groups called cohorts. These cohorts corresponded to various interest categories derived from people's browsing histories, but without making those people identifiable or exposing their browsing histories.
In theory, websites implementing FLoC could send a visitor's cohort identification number to an ad server and fetch an ad likely to align with the visitor's past browsing behavior without being able to surmise the identity of the visitor.
[7]
How FLoC worked
But FLoC barely made it off the ground. Following its [8]initial code commit in August 2019, and its Chrome browser trial [9]in early 2021 , Google [10]allowed its experiment to expire without renewal in July 2021, in order to make unspecified changes. Then, in January 2022, Google dispersed FLoC and [11]replaced it with another interest-based ad scheme, also ostensibly privacy-preserving, called the [12]Topics API .
Undaunted by rival browser makers like Apple, Brave, and Mozilla, or advocacy groups like the [13]Electronic Frontier Foundation , who have questioned both Google's motives and its technology, Google keeps repeating the word "privacy" in connection with its still-experimental adtech stack.
[14]Google starts testing fenced frames to guard its Privacy Sandbox
[15]Google resumes shoveling stuff into its 'Privacy Sandbox'
[16]Google expands Privacy Sandbox to Android
[17]Google dumps interest-based ad system for another interest-based ad system
Yet in a recent [18]research paper titled "Privacy Limitations Of Interest-based Advertising On The Web: A Post-mortem Empirical Analysis Of Google's FLoC," MIT Media Lab doctoral students Alex Berke and Dan Calacci argue that FLoC failed to provide privacy, and put personal information at risk.
Privacy advocates expressed those concerns about FLoC when it was being tested. But Google never revealed how its tests went, leaving observers to wonder about the results. So Berke and Calacci decided to investigate.
[19]
The two academics set about implementing FLoC using available open source code. They computed cohorts – interest groups – for users based on a dataset of more than 90,000 devices from about 50,000 households across the US, complemented by demographic data from those households.
[20]Their analysis indicated that FLoC's critics were spot-on, and they speculate that FLoC's privacy problems were what led Google to trade FLoC for the Topics API.
"First, contrary to its core aims, FLoC enables the tracking of individual users across sites," the paper states. "We find that more than 95 percent of user devices are uniquely identifiable after only four weeks. We then show how these estimates are extremely conservative, and that this risk increases with the use of common device fingerprinting methods."
[21]
However, FLoC was not entirely without merit. The researchers note that while there's a relationship between sensitive user demographics like race and income and browsing behavior, the FLoC algorithm they tested did not group users into cohorts based on race or income. That counts for something.
Berke and Calacci argue that those developing this sort of technology should publish tools, sample datasets, and code – as they have done – to allow other researchers to test whatever claims are being made.
"Google canceled FLoC in favor of a new approach (Topics), which is a more privacy-preserving step in the direction towards advertising based on contextual content," the paper explains. "However, like FLoC, it is still premised on tracking users' browsing behaviors and future work will need to demonstrate that this new approach goes far enough to preserve user privacy." ®
Get our [22]Tech Resources
[1] https://web.dev/floc/
[2] https://github.com/WICG/floc
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/personaltech&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2YnOgTHiWSYAW0P0H3Rny-AAAAIU&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[4] https://privacysandbox.com/intl/en_us/
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/personaltech&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YnOgTHiWSYAW0P0H3Rny-AAAAIU&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/personaltech&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YnOgTHiWSYAW0P0H3Rny-AAAAIU&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[7] https://regmedia.co.uk/2021/04/14/floc.png
[8] https://github.com/WICG/floc/commit/87740765c1ef25a34d32bceaec87b6c2315b4dc0
[9] https://www.theregister.com/2021/01/25/google_targeted_advertising/
[10] https://www.theregister.com/2021/07/08/google_floc_changes/
[11] https://www.theregister.com/2022/01/26/google_floc_topics/
[12] https://developer.chrome.com/docs/privacy-sandbox/topics/
[13] https://www.theregister.com/2021/03/05/eff_google_floc/
[14] https://www.theregister.com/2022/05/03/google_fenced_frames/
[15] https://www.theregister.com/2022/03/29/google_privacy_sandbox/
[16] https://www.theregister.com/2022/02/17/google_privacy_sandbox/
[17] https://www.theregister.com/2022/01/26/google_floc_topics/
[18] https://arxiv.org/abs/2201.13402
[19] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/personaltech&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YnOgTHiWSYAW0P0H3Rny-AAAAIU&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[20] https://github.com/aberke/floc-analysis
[21] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/personaltech&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YnOgTHiWSYAW0P0H3Rny-AAAAIU&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[22] https://whitepapers.theregister.com/
Real privacy solution
b0llchit
What if they simply stop tracking you? That would be a real privacy solution.
But I fear the data-holics could not cope with the withdrawal symptoms and might vanish by implosion. Hm, why should I fear this scenario?
Re: Real privacy solution
Neil Barnes
Well, there's always the remote possibility that you might get hit by the splatter. Could be untidy.
PPE, obvs. --->
Re: Real privacy solution
b0llchit
The splatter would be acceptable. The smell of decaying bodies and the exposed skeletons may be less enjoyable. But then, the smell will go away and we'll be free.
I graciously accept the time limited discomfort of splatter and smell.
[disposable coat will keep some of the spatter away]
"That counts for something"
Yeah. Google will get a nice gold star for the effort.
Meanwhile, I will continue to avoid using Chrome for anything but my gmail, and using Firefox+NoScript+uBlock Origin for my general surfing needs.
Ads ? They're useless, privacy-invading AND a security menace.