

Pages sites using a custom domain will not be impacted.Īs reported by BleepingComputer researcher Ax Sharma, this header is actually meant for website owners to pull the plug on Google’s FLoC tracking. Yesterday, GitHub revealed that they’re adding a HTTP header on all GitHub Pages sites.Īll GitHub Pages sites served from the github.io domain will now have a Permissions-Policy: interest-cohort=() header set. However, privacy-focused companies such as Brave, DuckDuckGo, Vivaldi, and others rejected Google’s call to implement FLoC in their own browsers as they believe the creation of a personally identifiable profile is exactly why user privacy advocates reject cookies on browsers and websites.


Last month, Google announced that it will introduce a new web technology – FLoC tracking (Federated Learning of Cohorts), that will eventually replace the practice of browsers and third-party websites storing user data (cookies).
