Simple browser automation.
Updated Google’s FLoC (Federated Learning of Cohorts) mechanism for ad personalisation, currently being trialled in the Chrome browser, has been rejected as privacy-invasive tracking by other browser makers including Vivaldi and Brave.
FLoC is part of what Google calls the Privacy Sandbox initiative, a proposal to “support business models that fund the open web in the absence of tracking mechanisms like third-party cookies,” according to now-retired Chrome engineering director Justin Schuh and product manager Marshall Vale in January.
Third-party cookies are widely used (or abused) for tracking users across the web, and are increasingly likely to be blocked. Google is determined to preserve its ability to target and personalise advertising and claims the Privacy Sandbox APIs “enable use cases such as ad selection and conversion measurement, without revealing individual private and personal information.”
Diagram of how FLoC works via web.dev/floc/ (click to enlarge) Licensed under CC 4.0
The idea of FLoC is that each web browser has a cohort ID which groups it with other browsers that have a similar browsing history. Google runs a FLoC service that defines the cohorts and sends data to the browser. The cohort ID is then calculated by the browser. The browser does not send its history to the FLoC service.
Websites can query the browser for its cohort ID and select advertising accordingly. Advertising networks – such as Google’s own – are expected to record data such as “a browser from cohort 1354 showed interest in hiking boots.” It is profiling, but of groups rather than individuals.
FloC is controversial. Last month the Electronic Frontier Foundation (EFF) declared it “a terrible idea” and said that “the technology will avoid the privacy risks of third-party cookies, but it will create new ones in the process.” The EFF also noted that having behavioural ads at all is an issue and that FLoC may exacerbate problems such as “discrimination and predatory targeting.” One might imagine cohorts that identify users as looking for help with debt, for example.
- Google’s ‘privacy-first’ ad tech FLoC squawks when Chrome goes Incognito, says expert. Web giant disagrees
- EFF urges Google to ground its FLoC: ‘Pro-privacy’ third-party cookie replacement not actually great for privacy
- In a trial run, Google Chrome to corral netizens into groups for tailored web ads rather than target individuals
Browser maker concerns
He added that FLoC would expose personal data in new ways. “You might visit a website that relates to a highly personal subject that may or may not use FLoC ads, and now every other site that you visit gets told your FLoC ID, which shows that you have visited that specific kind of site,” he said.
These risks could go beyond embarrassment to have “serious implications for society” if used by authoritarian governments. “A dictatorship may be able to work out that dissenters often seem to have one of the same five FLoC IDs. Now anyone who visits a nationally controlled website with that ID could be at risk,” he added. “We will not support the FLoC API and plan to disable it, no matter how it is implemented.”
Two days ago, Brave CEO Brendan Eich and senior privacy researcher Peter Snyder also voiced their objection to FLoC. “Brave has removed FLoC in the Nightly version of both Brave for desktop and Android. The privacy-affecting aspects of FLoC have never been enabled in Brave releases; the additional implementation details of FLoC will be removed from all Brave releases with this week’s stable release,” they said.
According to Eich and Snyder, “FLoC tells sites about your browsing history in a new way that browsers categorically do not today.”
They dispute the claim that cohorts protect privacy because each cohort has thousands of users – a method called k-anonymity. “Any useful concept of privacy should include some concept of ‘don’t tell others things you know about me, without my permission’,” they said.
FLoC tells sites about your browsing history in a new way that browsers categorically do not today
As for Mozilla, their spokesperson told us: “We are currently evaluating many of the privacy preserving advertising proposals, including those put forward by Google, but have no current plans to implement any of them at this time.”
We don’t buy into the assumption that the industry needs billions of data points about people, that are collected and shared without their understanding, to serve relevant advertising. Advertising and privacy can co-exist. And the advertising industry can operate differently than it has in past years.”
Yesterday Google mathematician Michael Kleber, on the Chrome team, claimed that “FLoC is not useful for tracking. There are thousands of people with the same FLoC, so someone trying to use it to track you would end up seeing a huge amount of not-you mixed in with a very small amount of you.”
Apple WebKit Security Engineer John Wilander disputed Kleber’s claim, saying that “the user’s cohort will not be partitioned per first party site so multiple sites can observe the cohort ID in sync as it changes week after week. A hash of the cohorts seen so far will likely get more and more unique as the weeks go by… to take this to the crowd metaphor: Before the pandemic and some time back, I attended a Mew concert, a Ghost concert, Disney on Ice, and a Def Leppard concert. At each of those events I was part of a large crowd. But I bet you I was the only one to attend all four.”
Although Google’s Schuh said the web giant was encouraging feedback on the privacy sandbox proposals, including FLoC, which are listed on GitHub here, the company appears to be full steam ahead on implementation.
In Chrome 89, the current version, FLoC was implemented as an “origin trial,” meaning that websites and advertisers can apply to start using it on an experimental basis. “We hope that during the Origin Trial, the ad tech community will collectively figure out which tasks are well served by the FLoC approach,” said Kleber.
The EFF noted that while websites and advertisers could opt in, users were not asked permission. “A small portion of Chrome users – still likely millions of people – will be (or have been) assigned to test the new technology,” it said. Security site Malwarebytes said: “Chrome users had no choice in whether they were included in the FLoC trial, they received no individualized notification, and, currently, they have no option to specifically opt-out.”
Last week the W3C Technical Architecture Group (TAG) stated that First Party Sets, another part of the privacy sandbox proposals, are “harmful to the web in its current form” and also warned against browser vendors working on or implementing additional features that depend on them.
The suspicion is that Google may rely on its Chrome market share – around 65 per cent, according to Statcounter, followed by Safari at 19 per cent, and all others with tiny percentages – as being sufficient that it will not wait to achieve consensus but simply go ahead on its own.
Google User Trust Product Manager Chetna Bindra describes here how the privacy sandbox will enable Google to continue with targeted advertising, ad tech bidding and conversion measurement because “advertising is essential to keeping the web open for everyone.”
Does advertising have to include tracking, though? Privacy search engine DuckDuckGo said that tracking is not necessary in order to advertise successfully. “When you search on DuckDuckGo, we can show you an ad based on the keywords you type in. That’s it. And it works.” It added that “FLoC IDs will also be accessible by third-party trackers lurking on websites” and is offering a Chrome extension to block FLoC.
Niche privacy-focused vendors like Brave and DuckDuckGo base their appeal on being more private than Google so there is self-interest in their complaints. That said, it is obvious that Google has not achieved cross-industry consensus with its Privacy Sandbox proposals. Less obvious is the extent to which it intends to respond.
We have asked Microsoft about its plans for FLoC in Edge and will update with any information received. We have also asked Google for comment on how it is responding to feedback. ®
Updated to add
A Google spokesperson has been in touch to clarify how Chrome users can, for now, avoid the FLoC trial:
The Privacy Sandbox proposals are developed as part of a collaborative, open-source effort and we welcome feedback as we continue working with the W3C and broader web community to find solutions that improve privacy while maintaining a healthy ecosystem.
We believe that FLoC improves user privacy while still supporting the relevant advertising that’s fundamental to maintain a free and open web. FLoC is based on large anonymous groups, not tracking individuals across the web as third-party cookies do today.
If a user has chosen to block third-party cookies with the current version of Chrome, they won’t be included in the FLoC origin trial, and this month, we’ll introduce a control in Chrome Settings that users can use to opt out of inclusion in FLoC and other Privacy Sandbox proposals while they’re in trials.
Browser automation without code.