Changes

#FLoC runs in the user's browser, doing the hard work of analytics on the user's device, and then broadcasting the results. Not only are the visitor's interests being captured and distributed, but it is being done by the user's own browser, without the user's explicit consent.

#FLoC runs in the user's browser, doing the hard work of analytics on the user's device, and then broadcasting the results. Not only are the visitor's interests being captured and distributed, but it is being done by the user's own browser, without the user's explicit consent.

#This user data is freely available to every website the browser visits, whether directly (browsing to that site), or indirectly (iframed content, 3rd party scripts, CNAME trackers, etc.) even if they have no prior knowledge about that visitor, and do not otherwise engage in tracking.

#This user data is freely available to every website the browser visits, whether directly (browsing to that site), or indirectly (iframed content, 3rd party scripts, CNAME trackers, etc.) even if they have no prior knowledge about that visitor, and do not otherwise engage in tracking.

#Fingerprinting data points

#A common problem for user privacy has been browser fingerprinting, which is the practice of taking many data points about a browser (when by themselves are not useful), and using the collection of those data points to get as close as possible to uniquely identifying a user (without needing cookies). For example, browser language, screen size, browser version, OS version, whether DNT is enabled, which addons are installed, etc. Although FLoC IDs can change over time, they will still add new data points for browser fingerprinting.

#is 1k really enough?

#Google plans to manually re-balance cohorts (groups) to make sure that they have at least about 1000 users. This is intended to obscure each person's identity within the group. The concern that many people have is that as a user is added to numerous cohorts, they may end up with a unique combination of cohort IDs, resulting in them being individually identified.

#3rd party trackers will still track

#Third-party tracking is a booming business. Although user awareness has begun to push back against it in recent years, it seems unlikely to many that third-party tracks will all just show down their businesses as soon as FLoC is implemented. As web browsers have started putting more restrictions on such behavior, third-party trackers have only become more creative in their methods of tracking. It is reasonable to assume that with the implementation of FLoC, trackers will simply integrate the FLoC-declared user interests into their user profiles (thus benefiting from the web browser's own knowledge of the user), and continue tracking in ever-evolving ways.

#anti-trust?

#FLoC does not consolidate advertising profiles to Google specifically (although Google users will inadvertently begin sharing more data with Google), but this technology does make an effort to drive third-party trackers out of business, and force everyone to base their online advertising on the data that Google's FLoC provides. While some might see this a a good thing, it could also be seen as an anti-trust violation, since Google is using its position in the browser market to consolidate power to themselves while actively fighting third parties who have the same objective.

==References==

==References==