Introducing the Privacy Budget

on YouTube ↗10m

" summary

Proposal measures how much identifying information each web API leaks and uses that to limit sites that would cross a privacy threshold, with Chrome running a large-scale real-user study sampling 300+ APIs to measure per-API entropy, API correlations, and which API subsets sites actually use. The plan targets roughly a 32 bits threshold (initially higher to monitor breakage), enforces limits when sites exceed the budget, and keeps results privacy-preserving with data deleted after short period.

AI-written summary · about

" chapters (5)

1. 0:00Introduction and context
2. 2:31Understanding fingerprinting
3. 4:56The privacy budget concept
4. 6:49Research and data study
5. 8:57Next steps and resources

" related talks

• 29mPrivacy SandboxMarshall Vale, Ari Levenfeld · Bitkom Privacy Conference 2021
• 13mPreparing for a more private webMaud Nalpas · Google I/O 2021
• 31mPrivacy sandboxBarb Smith, Michael Kleber, Rowan Merewood, Kaustubha Govind · Google I/O 2021
• 16mOpen web standards with Privacy SandboxRowan Merewood · Google I/O 2022
• 24mBuilding the Privacy SandboxKaustubha Govind, Hadas Shahar, Ryan Fitzgibbon, Vinay Goel · Google I/O 2022
• 16mBalancing Privacy: Leveraging Privacy Budgets for Privacy-Enhancing TechnologiesJordan Brandt · PEPR '24
• 37mDelivering High Speed with Low RiskNishant Bajaria · Bridge Summit 2024
• 47mDesigning for User-Centered PrivacyVenetia Tay · UXSEA Summit 2019