A simple zero-config plugin to opt-out of Google «Federated Learning of Cohorts» (FLoC).
Disable the tracking of your users with FLoC
Federated Learning of Cohorts (FLoC) is a replacement for third party cookies in chromium browsers like Chrome to target users with ads based on their interests. The proposed solution is better than using
third party cookies, but it still raises concerns in terms of privacy and data protection.
How does this plugin work?
This plugin tells your WordPress system to send a special header that disables FLoC on your website. There is no configuration needed besides installing the plugin.
If you are a developer, we encourage you to follow along or contribute to the development of this plugin on GitHub.
More about FLoC
- The Verge – What is FLoC on Chrome and why does it matter?
- Web.dev – What is Federated Learning of Cohorts (FLoC)?
- Adalytics.io – Who is sharing data with Google’s FLoC ad algorithm?
- Brave Browser – Why Brave disables FLoC
- The WICG Draft for FLoC
This plugin offers different methods implement the FLoC blocking HTTP header.
- None / Allow FLoC: This method does not provide an opt-out from FLoC.
- Simple / PHP: Works for most WordPress setups. Uses the «wp_headers» filter to provide the HTTP header.
- Apache / .htaccess: When you have to circumvent your cache. Only works on apache servers with the «mod_headers» module installed. Writes the HTTP header into the .htaccess file.
Compatibility with Cache Plugins
This plugin relies on the ability to deliver HTTP headers to the browser. Some Cache Plugins actively strip these HTTP headers and therefore invalidate the purpose of this plugin.
These cache plugins are known to be compatible with the Simple method:
- WP Super Cache – You have to activate the «Cache HTTP headers with page content.» checkbox in the Advanced Tab of the WP Super Cache Settings.
From within WordPress
- Visit ‘Plugins > Add New’
- Search for ‘Disable FLoC’
- Activate the plugin from your Plugins page.
- Upload the ‘Disable FLoC’ folder to the
- Activate ‘Disable FLoC’ through the ‘Plugins’ menu in WordPress
How do I check if it is working?
You can use the ‘Check FLoC’ link on the Plugins screen in your WordPress administration. Alternatively use an external tool to crawl your page. On example of such an external tool is the Uptrends HTTP response header check. With that tool you have to check if the «Permissions-Policy» header is present and if it contains the value «interest-cohort=()».
The plugin is active, but the header is not there.
The most common issues come with caching plugins, that are often stripping headers. Make sure that HTTP Headers get cached with your site in the configuration of your page cache.
Why should I install this plugin when I’m not using the Chrome browser?
The plugin does not only stop your browser from tracking with FLoC, but also the browsers from all of your users. So you’re not primarily installing the plugin for yourself, but for your users.
Colaboradores y desarrolladores
«Disable FLoC» es un software de código abierto. Las siguientes personas han colaborado con este plugin.Colaboradores
«Disable FLoC» ha sido traducido a 4 idiomas locales. Gracias a los traductores por sus contribuciones.
Traduce «Disable FLoC» a tu idioma.
¿Interesado en el desarrollo?
Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.
Registro de cambios
- Fixed a minor issue with a whitespace where it should not have been.
- Refactored the simple blocking method as suggested by @tjnowell in the FLoC discussion in make core.
- Added some proper settings found in the ‘Reading’ settings.
- Added help text to the ‘Reading’ page to explain these settings.
- Add the ‘apache’ method to disable FLoC in complicated hosting settings.
- Updated the asset art to better fit on social media.
- Resolved a deprecation for jQuery ‘click’. (thanks @backups)
- Added a method to check presence of the FLoC header. The «Check FLoC» Button on your plugins page in wp-admin should do that for you.
- Removed unneeded dependency.
- Added compatibility for WP Super Cache
- Initial release