Technologies referred to in this README are scheduled for deprecation.
This repository will be archived and will no longer be updated.
See our Update on Plans for Privacy Sandbox Technologies.
Privacy Sandbox feature status provides more information about the status of individual APIs and platform features.
This GitHub repository contains proposals for the Privacy Sandbox's Protected Auction server-side infrastructure that supports the Privacy Sandbox's client-side APIs.
Protected Auction includes Protected Audience and Protected App Signals ad targeting products.
Important
This repository is for documentation only. For discussions, visit the WICG/protected-auction-services-discussion repository.
- Bidding and Auction services
- Self-serve guide
- Payload optimization
- System design
- Multi-Currency Support in Bidding and Auction services
- Multi seller auctions
- Reporting
- Chaffing
- Protected App Signals
- B&A and K-Anonymity integration
- B&A experiment support
- Cloud support
- Key/Value service trust model
- Key/Value service use cases
- Key/Value service user-defined functions (UDFs)
- Key/Value sharding
- K/V Server Instance Sizing Guide
- Key/Value service Cost
- Key/Value service hybrid mode
- Passing buyer signals from B&A to TEE KV for PA flow
- Production operation
- Debugging protected audience api services
- Monitoring protected audience api services
- Bidding and Auction services: Cost
- Protected App Signals cost
- Bidding and Auction Cost Estimation Tool
- Browser - Bidding and Auction services integration
- Android - Bidding and Auction services integration high level document
Additional explainers for Protected Audience API.
- Chrome FLEDGE proposal