# Privacy sandbox

The Privacy Sandbox is an initiative led by Google to create web standards for websites to access user information without compromising privacy. Its core purpose is to facilitate online advertising by sharing a subset of user private information without the use of third-party cookies.$^{:39}$ The initiative includes a number of proposals, many of these proposals have bird-themed names which are changed once the corresponding feature reaches general availability. The technology include Topics API (formerly Federated Learning of Cohorts or FLoC), Protected Audience, Attribution Reporting, Private Aggregation, Shared Storage and Fenced Frames as well as other proposed technologies. The project was announced in August 2019.
On September 7, 2023, Google announced general availability of Privacy Sandbox APIs, naming explicitly Topics, Protected Audience, Attribution Reporting, Private Aggregation, Shared Storage and Fenced Frames, meaning these features were enabled for more than half of Google Chrome users. Privacy Sandbox features were also made available on Android around the same time.
The initiative has been described as anti-competitive and has generated an antitrust response due to concerns that the introduced proposals limit tracking through traditional methods and push advertisers to use Google as a middleman in order to show advertisements.

## Model

Proposals in the Privacy Sandbox follow the idea of k-anonymity and are based on advertising to groups of people called cohorts instead of tracking individuals. They generally place the web browser in control of the user's privacy, moving some of the data collection and processing that facilitates advertising onto the user's device itself.$^{:41}$ There are three focuses within the Privacy Sandbox initiative: replacing the functionality of cross-site tracking, removing third-party cookies, and mitigating the risk of device fingerprinting.$^{:45}$

## Proposals

In January 2020, Google invited advertising technology companies to join the Improving Web Advertising Business Group (IWABG) of the World Wide Web Consortium (W3C) as a way to participate in the proposal process for the Privacy Sandbox.
Proposals :
| Proposal | Description | Status |
| Federated Learning of Cohorts (FLoC) | The Federated Learning of Cohorts algorithm analyzed users' online activity within the browser, and generates a "cohort ID" using the SimHash algorithm to group a given user with other users who access similar content.$^{:9}$ | Discontinued |
| TURTLEDOVE | TURTLEDOVE, which stands for "Two Uncorrelated Requests, Then Locally-Executed Decision On Victory",$^{:45}$ is a framework proposed by Google to serve ads through the browser.$^{:49}$ | Partially implemented |
| Private state tokens | Private state tokens will be able to be issued by websites to verify those browsers whose behavior denotes a real person rather than a bot or malicious attacker. Private state tokens are encrypted, so that an individual's identity is protected. | Implemented |
| Related Website Sets | Related Website Sets (formerly known as first-party sets) will allow domains that belong to the same entity, that have related sites with different domain names, to declare themselves, and be recognized, as a "related set." The exchange of information outside of a related website set is restricted to safeguard the privacy of users. | Implemented |
| CHIPS | CHIPS (Cookies Having Independent Partitioned State) takes into account that certain embedded services need to know a given user’s activity on a site to function. CHIPS are partitioned cookies that will inform browsers that the necessary cookie is allowed to function only between a particular site and another embedded site. | Implemented |
| Storage Partitioning | Storage Partitioning will isolate certain web platform APIs that are used for storage or communication when used by an embedded service on a given site.This will enhance web privacy while still allowing web compatibility with existing sites. | Implemented |
| Network State Partitioning | Network State Partitioning will partition a browser’s network resources to prevent these resources from being shared across first-party contexts. It requires each request to have an additional "network partition key" for resources to be reused and safeguards user privacy by disallowing access to shared resources and metadata learned from loading other sites. | Implemented |
| Federated Credential Management | Federated Credential Management is an API that will provide support for single sign-on designs that previously depended on third-party cookies. | Implemented |
| Client Hints | Client Hints API allows sites to request required information directly rather than via a User-Agent String, a significant surface vulnerable to passive fingerprinting, therefore reducing details that can be shared about a user online. | Implemented |
| User Agent reduction | User Agent reduction minimizes the information in a User-Agent String thereby reducing its vulnerability to passive fingerprinting. | Implemented |
| Privacy Budget | Privacy Budget aimed to limit fingerprinting by restricting the identifying information that a site is allowed to access. | Discontinued |
| HTTP Cache Partitioning | HTTP Cache Partitioning assigns cached resources with a 'network isolation key' along with the resource URL, composed of the top-level site and current-frame site. This prevents other websites from being able to infer details about the status of cached resources on a different website. | Implemented |
| IP Protection | IP Protection is a proposal that will hide a user’s IP address from third parties using double-hop anonymous proxy. | Proposed |
| DNS-over-HTTPS | The DNS-over-HTTPS protocol prevents attackers from observing the sites a user visits by encrypting Domain Name System (DNS) queries. | Implemented |
| Topics API | Topics API aims to provide the means for advertisers to show relevant content and ads by sharing interest-based categories, or 'topics', based on recent browsing history processed on the user device. | Implemented |
| Fenced Frames API | Fenced frames are an embedded frame type that is not permitted to communicate with a given host page, making it safe to access its unpartitioned storage as joining its identifier with the top site is impossible. Advertisements using FLEDGE-based APIs will only be allowed to be displayed within Fenced Frames. | Implemented |
| Attribution Reporting API | The Attribution Reporting API facilitates conversion tracking, for example, recording whenever a click on an ad or a view results in a purchase, while suppressing the ability to track users across multiple websites. | Implemented |
| Protected Audience API | Protected Audience API is designed for targeting of interested audiences, including through retargeting. It allows vendors selected for advertising to take an advertiser’s website data and to place users in interest groups specifically defined for a given advertiser, meaning that users can see tailored ads, with no infringement on their privacy. Prior to reaching global availability on August 17, 2023, the technology was known as "First Locally-Executed Decision over Groups Experiment", (FLEDGE). | Implemented |
| Private Aggregation | Private Aggregation API tracks some aggregated statistics across ad campaigns. | Implemented |

## Privacy Sandbox for Android

For Android, Privacy Sandbox will use technology that operates without cross-app identifiers, such as Android/Google Advertising ID. SDK (Software Development Kit) Runtime will limit covert tracking and the collection of user data by way of a process for third-party code, e.g. used for advertising, that runs separately from a given app’s code.
For the measurement of digital ads, the Attribution Reporting API is intended to supersede current measurement methods with solutions not reliant on user-level tracking mechanisms.
In order to continue to show relevant ads and content on Android, Topics will present categories that are based on the use of apps on a user’s device and are selected only through a given device’s settings. To further supplement privacy on Android, FLEDGE will use “custom audiences” that are built by app developers based on interactions with their app, information that will be stored locally so that no individual identifiers are shared with external parties.

## Testing

On March 31, 2022, Google announced the start of a single origin trial, for the Topics, FLEDGE and Attribution Reporting APIs. It allows sites to run unified experiments across the APIs.
In October 2022 RTB House published its findings of actively testing FLEDGE by adding users to interest groups. Google and Criteo, also ran tests. The report highlighted that, while positive, the FLEDGE origin trials were limited in scope. It noted that a number of essential features of FLEDGE, specifically k-anonymity requirements, were not available for testing, and will require adjustments after industry feedback.
The scale of tests is increasing. Google Chrome aims to dedicate H1 of 2023 to developer testing, and make FLEDGE available for the entirety of Chrome users in H2 of 2023.
In November 2022 the Competition and Markets Authority released a report on Google’s quantitative testing of its Sandbox technologies that highlighted the importance of the industry adopting a common testing framework so that performance tests can be conducted more widely across multiple testing entities. Google is developing such a framework in cooperation with the CMA and is seeking to drive engagement with market participants on the design of testing between now and at least the beginning of General Availability in Q3 2023.

## Antitrust concerns

In January 2021, the Competition and Markets Authority (CMA) in the United Kingdom announced plans to investigate the Privacy Sandbox initiative, with a focus on its potential impacts on both publishers and users. In a statement, CMA chief executive Andrea Coscelli said that "Google’s Privacy Sandbox proposals will potentially have a very significant impact on publishers like newspapers and the digital advertising market," and that there were also "privacy concerns to consider."
CMA accepted legally binding commitments offered by Google concerning its proposals to remove third party cookies (TPCs) on Chrome and develop the Privacy Sandbox. The formal acceptance of these commitments by the CMA resulted in the closure of the investigation, with no decision on whether the Competition Act 1998 was infringed. CMA reported that Google was complying with its legally-binding commitments between July 2022 and September 2022.
In March 2021, 15 attorneys general of U.S. states and Puerto Rico amended an antitrust complaint filed the previous December; the updated complaint says that Google Chrome's phase-out of third-party cookies in 2022 will "disable the primary cookie-tracking technology almost all non-Google publishers currently use to track users and target ads. Then [...] Chrome, will offer [...] new and alternative tracking mechanisms [...] dubbed Privacy Sandbox. Overall, the changes are anticompetitive". The lawsuit suggests that the proposed changes in the Privacy Sandbox would effectively require advertisers to use Google as a middleman in order to advertise.