Understanding Google FLoC, Topics API, and Privacy Sandbox: What Changed

Google's Federated Learning of Cohorts (FLoC) was proposed as a replacement for third-party cookies in Chrome. The proposal met fierce resistance and was replaced with the Topics API as part of the Privacy Sandbox initiative.

What Was FLoC?

FLoC analyzed browsing history locally in Chrome and assigned users to cohorts of thousands with similar interests. Advertisers could then target cohorts rather than individuals.

Why FLoC Was Problematic

Fingerprinting Risk

A FLoC cohort ID combined with other browser information could potentially identify individuals.

Sensitive Category Exposure

Cohorts based on browsing patterns could reveal health conditions or political interests.

No User Consent

FLoC was enabled by default without meaningful consent.

Browser Industry Rejection

Mozilla, Apple, Brave, Vivaldi, and DuckDuckGo all refused to implement FLoC.

The Topics API Replacement

Chrome observes broad topics from recent browsing, selected from approximately 350 predefined categories. Topics are determined locally and stored for only 3 weeks. While addressing some FLoC concerns, privacy advocates argue it still enables tracking without consent.

What Website Owners Should Do

For Your Analytics

If your analytics tool works without cookies, it will continue working regardless of Privacy Sandbox changes.

For Your Privacy Posture

The safest approach is minimizing reliance on any single technology company's tracking infrastructure. Choose analytics and advertising tools that work with privacy rather than trying to work around it.

The Bigger Picture

Any system that attempts to enable targeted advertising while claiming to preserve privacy will face fundamental tensions. True privacy requires minimizing data collection, not finding cleverer ways to categorize people.