Updates! privacySandboxEnabled’s deprecation in favor of more granular APIs

44 views

Skip to first unread message

unread,

Feb 2, 2023, 4:14:39 AM2/2/23

to chromium-...@chromium.org, Rohit Agarwal, Olesia Marukhno

Hi extension devs!

We will be deprecating chrome.privacy.privacySandboxEnabled in M111 and in its place we are introducing three new APIs to granularly control the individual privacy sandbox APIs namely Topics, Fledge, Attribution reporting and Private Aggregation:

By design, you would only be able to disable the new APIs, and any attempt to turn them “on” will produce a visible error.

We are planning to fully remove the chrome.privacy.privacySandboxEnabled from M113. Please note that during the migration period:

Enabling chrome.privacy.privacySandboxEnabled will CLEAR the new chrome.privacy.websites.{topics|fledge|adMeasurement}Enabled APIs because extensions aren’t allowed to enable them;
Disabling chrome.privacy.privacySandboxEnabled will also disable the new chrome.privacy.websites.{topics|fledge|adMeasurement}Enabled APIs;
Clearing chrome.privacy.privacySandboxEnabled will also clear the new chrome.privacy.websites.{topics|fledge|adMeasurement}Enabled APIs.

Lastly, look out for the deprecation issue in the Chrome Devtools Issues Tab if you use chrome.privacy.privacySandboxEnabled in your extensions from M111.

We look forward to continuing to provide Chrome users with transparent and easy-to-use privacy controls,