The Privacy Sandbox
A series of proposals to satisfy cross-site use cases without third-party cookies or other tracking mechanisms.
Read the documentation
#Introduction
What's in it, how to get involved, and what it's for.
Short explanations of key concepts.
How we collaborate with stakeholders to discuss, test, and adopt privacy-preserving technologies.
Review Chrome platform status, resources, and feature release timelines.
#Prevent covert tracking
Proposals to prevent third-parties from fingerprinting or collecting unlimited sensitive data.
User-Agent reduction
Limit passively shared browser data to reduce the volume of sensitive information which leads to fingerprinting.
Test your sites and services against the reduced Chrome user-agent with regular expressions.
More proposals
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.
#Show relevant content
Proposals to encourage an engaging web with free access to information.
Topics
Learn how to work with the API, including how to use Chrome flags for testing.
Quick guide to implement and test the API. Access topics with JavaScript and share your feedback.
Updates and enhancements to the design and implementation of the API.
FLEDGE
A proposal for on-device auctions to serve custom audiences. Choose relevant ads from websites the user has previously visited without third-party tracking.
Improve FLEDGE auction latency with these best practices.
Quick guide to implement and test the API. Play with demo code and share your feedback.
#Measure digital ads
Proposals to collect accurate and useful measurement of digital ads, so you can get messages to the right people at the right time.
A proposal to measure ad conversions without cross-site third-party tracking.
Understand how each service connects end-to-end for Attribution Reporting.
A step-by-step guide to implement and test the API. Play with demo code and share your feedback.
A quick reference to how the proposal has changed to address community feedback.
#Strengthen privacy boundaries
Proposals to create and strengthen cross-site privacy. This means information collected on one site is not automatically shared with another site, unless the user explicitly consents.
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.
A proposal to manage how your page and embedded third-party iframes access to browser features.
A web platform API that allows users to login to websites with their federated accounts in a manner compatible with improvements to browser privacy.
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.
Securely embed content onto a page without sharing cross-site data.
Separate storage from communication APIs in third-party contexts to prevent certain types of side-channel cross-site tracking.
#Secure cross-site storage
Prevent fraud, run A/B testing, rotate creatives, and support other use cases, while protecting user privacy.
Separate storage from communication APIs in third-party contexts to prevent certain types of side-channel cross-site tracking.
Allow access to unpartitioned cross-site data in a secure environment.
Measure Shared Storage data and generate a noisy summary report.
#Fight spam and fraud
Proposals to separate invalid clicks and impressions from legitimate ones.
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.