Privacy sandbox enrollment
To access certain privacy sandbox features, browsers require developers to complete an enrollment process.
Enrollment provides a mechanism to verify the entities that call privacy sandbox features, and to gather the developer-specific data needed to properly configure and use them. The enrollment process adds an additional layer of protections on top of the structural restrictions enforced within each feature by adding transparency to who is collecting data, and mitigating attempts to misuse features to gather more data than intended.
The intention is for information about each company that completes enrollment to be made public, to provide auditable transparency.
Features requiring enrollment
The following features require enrollment to be usable:
- Attribution Reporting API
- Fenced Frame API
- Protected Audience API
- Shared Storage API
- Topics API
The documentation of each feature includes more details on exactly which sub-features will fail if enrollment is not completed, and how.
Browser enrollment information
Chrome
- Instructions: Enroll for the Privacy Sandbox.
- Testing: You do not need to enroll to test privacy sandbox features locally. To allow local testing, enable the
chrome://flags/#privacy-sandbox-enrollment-overridesdeveloper flag.