Privacy Sandbox for the Web provides open-source, privacy-enhancing technologies that empower businesses to thrive while respecting user privacy. By reducing reliance on various forms of tracking, we're building a web where companies can achieve their goals and peopleâs information stays private and secure.
Privacy Sandbox Timeline for the WebThe Privacy Sandbox proposals are in various stages of the development process. This timeline reflects when we expect new privacy-preserving APIs and other technologies to be ready in support of key use cases. Information may change and will be updated monthly.
The proposals are being developed in public forums, in collaboration with members of the industry. We also continue to work with the UK's Competition and Markets Authority in line with the commitments we offered for Privacy Sandbox for the web. We encourage participation through the many public feedback channels that inform development of the proposals. Stakeholders can also use this form to share feedback directly with Chrome.
Last Update: May 2025
Third-Party Cookies (3PC) and TestingOpt-in Testing with Labels Chrome will provide developers an experiment label for independent testing and simulation of third-party cookie deprecation.
1% 3PC Deprecation Chrome will deprecate third-party cookies for 1% of Chrome users globally.
Third-Party Cookie Phase Out * We envision proceeding with third-party cookie deprecation starting early 2025, subject to resolving any remaining concerns with the CMA.
Third-party cookies phases: Opt-in testing with labels: Q4 2023 through Q3 2024; 1% Third-party cookies deprecation: Q1 2024 through Q4 2024; Third-party cookies phase out: Q1 2025
* Subject to resolving any remaining concerns with the CMA.
Privacy Sandbox APIsDiscussion The technologies and their prototypes are discussed in forums such as GitHub or W3C groups. Some limited testing of solutions might happen at this stage to facilitate discussions.
Pre-Launch Testing The technologies for the use case are available for testing via Chrome origin trials or other pre-launch methods. Changes may be made based on testing results and ecosystem feedback.
General Availability The technologies for the use case are launched and available for 100% of Chrome traffic. Chrome expects refinements and optimizations as more companies test and use the APIs over time.
Fight spam and fraud on the web proposals phases: Testing period: Q1 2021 through the end of Q3 2022; Transition period, stage 1: Q4 2022 through the end of Q2 2023; Transition period, stage 2: Q3 2023.
Show relevant content and ads proposals phases: Discussion period: Q1 2021 through the end of Q4 2021; Testing period: Q1 2022 through the end of Q3 2022; Transition period, stage 1: Q4 2022 through the end of Q2 2023; Transition period, stage 2: Q3 2023
Measure digital ads proposals phases: Discussion period: Q1 2021 through the end of Q4 2021; Testing period: Q1 2022 through the end of Q3 2022; Transition period, stage 1: Q4 2022 through the end of Q2 2023; Transition period, stage 2: Q3 2023
Strengthen Cross-site Privacy Boundaries proposals phases: Discussion period: Q1 2021 through the end of Q1 2022; Testing period: Q2 2022 through the end of Q3 2022; Transition period, stage 1: Q4 2022 through the end of Q2 2023; Transition period, stage 2: Q3 2023.
The Privacy Sandbox initiative also includes efforts designed to limit covert tracking. These include proposals that address specific covert tracking techniques such as fingerprinting and network-level tracking.
Early Phases
Proposals go through an early incubation phase before moving into development.
In Development
These proposals are currently in development and/or being tested. Learn more about the implementation details of each proposal by clicking on the links below.
Topics API enables businesses to show relevant ads based on broad interest categories, like sports or travel, without relying on third-party cookies or individual tracking. The browser infers these interests, known as âtopics,â from recently visited sites without surfacing a personâs specific browsing information.
Protected Audience APIProtected Audience API helps businesses re-engage audiences who have previously shown interest in their products or services, without exposing their personal information. Companies can create anonymized custom audiences based on website visitorsâ on-site behavior. Marketers then bid to show relevant ads to re-engage these audiences, all without relying on individual tracking.
Read more about Protected Audience API
Attribution Reporting APIAttribution Reporting API allows businesses to measure ad campaign effectiveness, like understanding which ads led to purchases, without relying on third-party cookies or identifying people at an individual level. It provides reports that match ad interactions with conversions, delivering effective insights while respecting user privacy.
Read more about Attribution Reporting API
CHIPSCHIPS (Cookies Having Independent Partitioned State) maintains embedded site functionality by providing access to specific compartmentalized information, without enabling tracking.
Fenced FramesFenced Frames protects embedded content, as a replacement for an iframe, so it can't pass the embed data back to the site that embedded the fenced frame. The result is the data within the fenced frame is isolated, and no user activity is shared or stored.
FedCMFederated credentials allow people to sign in to various sites using their existing logins from Identity Providers, like social logins. This process enhances security and convenience for people while streamlining login management for businesses.
User-Agent Client HintsUser-Agent Client Hints API enables sites to request relevant information about a userâs browser to address certain use cases, rather than have it shared passively via the User-Agent header.
Read more about User-Agent Client Hints
User-Agent ReductionUser-Agent (UA) reduction is the effort to minimize the identifying information shared in the User-Agent string which may be used for passive fingerprinting.
Read more about User-Agent Reduction
DNS-over-HTTPSDNS-over-HTTPS is a protocol that encrypts Domain Name System (DNS) queries and responses by encoding them within HTTPS messages. This helps prevent attackers from sending users to phishing websites or observing what sites they visit.
Read more about DNS-over-HTTPS
IP ProtectionIP Protection is Privacy Sandboxâs proposal to hide IP addresses, in Chromeâs Incognito mode, from third-party sites known to track users.
Storage PartitioningStorage Partitioning will isolate some web platform APIs used for storage or communication if used by an embedded service on the site, i.e., in the third-party context. This helps maintain web compatibility with existing sites while enhancing privacy and security.
Read more about Storage Partitioning
Storage Access APIStorage Access API enables third parties to share information across sites only when user interaction and permission requirements are met, preventing unwanted tracking.
Read more about Storage Access API
Network State PartitioningNetwork State Partitioning reduces the sharing of network-related caches and state (i.e., shared DNS cache, socket reuse, etc.) in order to limit the ability to track users across first-party contexts.
Read more about Network State Partitioning
Bounce Tracking MitigationsBounce Tracking Mitigations reduce or eliminate the ability to track users via redirects as they navigate across the web.
Read more about Bounce Tracking Mitigations
Private State TokensPrivate State Tokens protect sites from bots and fraudulent traffic by using the browser to convey user trust signals, without revealing that personâs information.
Read more about Private State Tokens
FLoC APIFLoC was a Privacy Sandbox proposal designed to cluster people with similar browsing patterns into large groups, or "cohorts". This "safety in numbers" approach was designed to effectively blend any individuals into a crowd of people with similar interests. The development of FLoC stopped in 2021.
Privacy BudgetPrivacy Budget was a proposal that restricted the amount of identifying information that a site is allowed to access, in order to help prevent the user from being uniquely identifiable. The Privacy Budget is no longer an active proposal as of January 2024.
Industry Engagement Entry Point
Get your business readyRead case studies from companies helping to shape the future of online privacy, or learn more about the Privacy Sandbox technologies in our developer documentation.
Frequently Asked QuestionsNot necessarily. Chrome is focused on developing proposals that support key use cases. The set of proposals solving for a particular use case (for example, showing relevant content and ads) may change and evolve over time, with web community feedback and testing. The APIs shown on the timeline are based on current expectations and might change.
Origin trials are one method of testing new web technologies in Chrome. "OT" labels are shown when a Chrome origin trial has been publicly announced, is in progress, or has concluded. We will add new origin trials, and other forms of available testing, on the timeline as part of the monthly updates. Chrome's origin trial registration page provides information for origin trials that are live or starting soon.
While features are in development they are often made available behind one or more temporary flags (off by default) that can be used to enable and configure their behavior for local developer testing purposes. This may be as command line flags that need to be passed in when launching Chrome or as options in the chrome://flags browser interface.
Chrome works with a broad group of stakeholders throughout the web ecosystem â including web browsers, online publishers, ad tech companies, advertisers, developers, and users â to inform the design and implementation of Privacy Sandbox technologies. Additionally, Chrome continues to work with regulators, including the UK's Competition and Markets Authority in line with the commitments offered for Privacy Sandbox for the Web.
We want people to be aware of what's changing and how the changes offer more control over how your data is used in the ads you see. Some users may not be familiar with the term Privacy Sandbox, and âad privacyâ is a straightforward way to describe these controls.
All users will have robust controls, and can opt out of Privacy Sandbox relevance and measurement technologies at any point. You can learn more about controlling your ad privacy in Chrome here.
Sign up for Privacy Sandbox news and updates
Be the first to know about Privacy Sandbox developments with updates delivered straight to your inbox.
You will now receive monthly updates about Privacy Sandbox.
Something went wrong, please reload the page to try again.
I understand my personal data will be processed in accordance with Googleâs Privacy Policy.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3