Chrome is getting Tracking Protection, but don’t get your hopes up

Created on November 12, 2023 at 10:37 am

Google ORG is in the process of switching on its euphemistically named Privacy Sandbox ORG in Chrome ORG , which, depending on who you ask, is either a step in the right direction, or, the first ORDINAL advertising system baked into a web browser. Next to that, Google ORG is also working on Tracking Protection ORG .


A new experimental flag is available in Chrome Canary ORG that moves the Third-Party ORG Cookies section in the Settings to a Tracking Protection section. Many users, those who have used other browsers such as Firefox ORG , know that these browsers support tracking protection features already.

Google Chrome’s ORG implementation, on the other hand, has little to do with these advanced protective features. For now, it is mostly a name change. A click on Tracking Protection ORG in Chrome ORG displays almost the same options as the Third-Party ORG Cookies section of the settings in Chrome ORG Stable.

There are some differences though. In Chrome Stable ORG , users could set the default third ORDINAL -party cookies behavior to "allow third ORDINAL -party cookies", "block third ORDINAL -party cookies in Incognito mode", or "Block third ORDINAL -party cookies".

Tracking Protection ORG changes this to the two CARDINAL options "Standard" and "Custom". Standard "limits third ORDINAL -party cookies" automatically and blocks third ORDINAL -party cookies in Incognito mode. Google ORG does not reveal the list of exceptions, but explains that users may add temporary exceptions.

Custom contains the option to block all third ORDINAL -party cookies and to send the "do not track" header. These need to be enabled.

The remaining options, preload pages, see all site data and permissions, and customized behaviors, on the Settings page are identical.

The experimental flag hints that it prepares the browser for the next step in Google ORG ‘s plan to deprecate third ORDINAL -party cookies in Google Chrome ORG .

Google ORG plans to disable third ORDINAL -party cookies for 1% PERCENT of the entire Chrome ORG traffic in January 2024 DATE with the release of Chrome 120 PRODUCT . The test excludes most Enterprise ORG end users, unless administrators set policies. Additional information on the planned deprecation is available on the Chrome Developer ORG website.

Old wine in new skins, or something new?

One CARDINAL reason for changing the name from Third-Party Cookies to Tracking Protection ORG may have to do with the deprecation of third ORDINAL -party cookies in Chrome ORG . When the browser stops supporting third ORDINAL -party cookies, it does not make sense to have a setting about Third-Party Cookies anymore in the browser.

Renaming it to Tracking Protection ORG and changing the available options makes sense in this regard. Chrome users who have hoped that Google ORG would implement improved privacy protections may be disappointed though, as it does not look as if this is going to be the case.

Chrome ORG is one of Google ORG ‘s mightiest weapons in advertising and the company will do anything in its power to keep it that way.

Using a different browser, such as Brave ORG , Vivaldi PERSON or Firefox ORG , is, from a privacy point of view, the better option.

Summary Article Name Chrome is getting Tracking Protection ORG , but don’t get your hopes up Description Google ORG is integration a Tracking Protection ORG feature into its Chrome ORG web browser. Find out why it is lacking when compared to other browsers. Author Martin Brinkmann PERSON Publisher Ghacks Technology News Logo


Connecting to Connected... Page load complete