The Privacy Sandbox

What's in it, what's it for, and how to get involved.

How we collaborate with stakeholders to discuss, test, and adopt privacy-preserving technologies.

Information and resources for online and in-person events.

Run unified experiments across Attribution Reporting, FLEDGE, Topics, Fenced Frames, and Shared Storage.

Review Chrome platform status, resources, and feature release timelines.

Where and how to provide feedback for Privacy Sandbox proposals throughout the development process.

First-Party Sets (FPS) is a way for a company to declare relationships among sites, so that browsers allow limited third-party cookie access for specific purposes.

Evolving First-Party Sets to advance privacy for users and web interoperability for developers.

Allow developers to opt-in a cookie to "partitioned" storage, with a separate cookie jar per top-level site. Partitioned cookies can be set by a third-party service, but only read within the context of the top-level site where they were initially set.

Securely embed content onto a page without sharing cross-site data.

A proposal to improve user privacy by protecting their IP address from being used for tracking.

A proposal to limit the amount of individual user data exposed to sites to prevent covert tracking.

Reduce or eliminate the ability of bounce tracking to recognize people across contexts.

Look closer at the future of the advertising ecosystem.

Deploy and manage this service to produce summary reports for the Attribution Reporting API or the Private Aggregation API.

Measure data aggregated across users with the Attribution Reporting API and the Private Aggregation API.

An API to convey a limited amount of information from one browsing context to another (for example, across sites) to help combat fraud, without passive tracking.