Skip to content
Brief
Privacy Sandbox ceased operations on October 17, 2025

Privacy Sandbox

Privacy & IdentityProduct· part of Google

Aimed to enable privacy-preserving digital advertising by replacing third-party cookies with browser-native APIs that kept user data on-device, reducing cross-site tracking while theoretically preserving ad relevance and measurement.

Last updated Sep 26, 2026 by ATDb automated enrichment

Founded
2019
HQ
Mountain View, California, United States
Parent
Connections
2

At a glance

Stock
GOOGL
1corporate family

About

Google-controlled initiative that sought to define the post-cookie advertising standards for the open web, ultimately failing to achieve industry consensus or regulatory approval

Privacy Sandbox was a Google-led initiative launched in 2019 with the stated goal of phasing out third-party cookies in the Chrome browser and replacing them with a suite of privacy-preserving APIs that could still support digital advertising use cases. The program represented one of the most consequential and controversial efforts in AdTech history, as third-party cookies had been the foundational tracking mechanism for programmatic advertising for over two decades. Key technologies developed under the initiative included the Topics API (a replacement for interest-based targeting), the Protected Audience API (formerly FLEDGE, for remarketing and custom audiences), the Attribution Reporting API (for conversion measurement), and CHIPS (Cookies Having Independent Partitioned State), among others. The initiative faced sustained criticism from publishers, advertisers, ad tech vendors, and regulators throughout its lifespan. The UK's Competition and Markets Authority (CMA) opened an investigation into Privacy Sandbox in 2021, concerned that the deprecation of third-party cookies would entrench Google's dominance in digital advertising by forcing the ecosystem to rely on Google-controlled alternatives. This regulatory scrutiny led to multiple delays in Google's original timeline to deprecate third-party cookies, which was pushed back from 2022 to 2023, then to 2024, and ultimately abandoned entirely. In July 2024, Google announced it would not deprecate third-party cookies in Chrome after all, instead pursuing a user-choice model. Following the reversal on cookie deprecation, the Privacy Sandbox APIs lost their central rationale, and Google formally retired most of the initiative's core advertising technologies — including Topics and Protected Audience — on October 17, 2025. The program's legacy is complex: it accelerated industry-wide conversations about privacy, prompted significant investment in alternative identity solutions (such as first-party data strategies, universal IDs, and contextual targeting), and demonstrated the profound difficulty of simultaneously satisfying privacy advocates, regulators, publishers, and advertisers within a single technical framework.

Business model

Open-source / Standards Initiative

Target market

Enterprise

What they offer

  • Topics API

    Browser-based interest-based advertising API that inferred broad topic categories from browsing history on-device, replacing third-party cookie-based audience targeting. Retired October 2025.

  • Protected Audience API

    Formerly known as FLEDGE; enabled remarketing and custom audience targeting by running ad auctions within the browser without exposing user data to third parties. Retired October 2025.

  • Attribution Reporting API

    Privacy-preserving conversion measurement API designed to replace pixel-based tracking for ad attribution across sites.

  • CHIPS (Cookies Having Independent Partitioned State)

    Mechanism allowing cookies to be set in a third-party context but scoped to the top-level site, limiting cross-site tracking while preserving some embedded functionality.

  • Related Website Sets

    Formerly First-Party Sets; allowed organizations to declare groups of related domains that could share cookie access, supporting single sign-on and analytics across owned properties.

  • Private Aggregation API

    Enabled aggregated, noise-added reporting for cross-site data without exposing individual user-level signals.

  • Storage Access API

    Allowed embedded content to request access to unpartitioned cookies with user permission, providing a fallback for legitimate cross-site use cases.

Key features

On-device processing to keep user browsing data within the browserInterest-based cohort classification via Topics APIBrowser-native ad auction execution via Protected AudienceNoise-added aggregated measurement for privacy-safe attributionPartitioned cookie storage to limit cross-site trackingOpen development process via W3C and public GitHub repositories

Use cases

Interest-based audience targeting without third-party cookiesRemarketing and custom audience ad deliveryCross-site conversion measurement and attributionFrequency capping without cross-site identifiersFederated login and SSO across related domains

Customer segments

PublishersAdvertisersDemand-side platforms (DSPs)Supply-side platforms (SSPs)Ad measurement and verification vendorsBrowser developers and standards bodies

Tech & specs

Technology stack

Chromium browser engineWebAssembly (for Protected Audience auction logic)Differential privacy / noise-addition algorithmsW3C web standardsJavaScript APIsTrusted Execution Environments (TEEs)

Security & compliance

GDPR (design intent)CCPA (design intent)UK CMA regulatory oversight

Deployment

Browser-native (Chrome)

API

No

Corporate history
  1. 2019 · Founded
  2. 2025Shut down
Connection details

Explore further

2 views