Privacy Sandbox
Was ist Privacy Sandbox?
Privacy SandboxGoogle's umbrella initiative for replacing third-party cookies and cross-site identifiers with privacy-preserving alternatives — Topics, Protected Audience (FLEDGE), Attribution Reporting, and on-device APIs — under heavy regulatory and competitor scrutiny.
Privacy Sandbox is Google's multi-year initiative, launched in 2019, to replace third-party cookies and other cross-site identifiers in Chrome and Android with a family of purpose-built, on-device, privacy-preserving APIs while keeping the ad-supported web economically viable. The web-side APIs include Topics (browser-derived interest categories), Protected Audience (FLEDGE, previously TURTLEDOVE — on-device remarketing auctions), Attribution Reporting (browser-mediated conversion measurement with noise), Shared Storage and Fenced Frames (cross-site state in a privacy-bounded form), and Trust Tokens / Private State Tokens. Android-side counterparts include Topics, Attribution Reporting, and SDK Runtime. The U.K.'s Competition and Markets Authority has supervised Privacy Sandbox since 2022, with Google committing to behavioral remedies; in July 2024 Google announced it would keep third-party cookies in Chrome with a new user-choice mechanism rather than deprecate them, while continuing Sandbox APIs alongside. For privacy and AppSec teams, Privacy Sandbox is a major architectural change that needs site-by-site impact assessment.
● Beispiele
- 01
An ad-tech vendor builds a FLEDGE-based remarketing prototype to compare reach and conversion against legacy cookie-based remarketing.
- 02
A publisher integrates the Attribution Reporting API and watches for the noise/budget characteristics that change downstream conversion-measurement pipelines.
● Häufige Fragen
Was ist Privacy Sandbox?
Google's umbrella initiative for replacing third-party cookies and cross-site identifiers with privacy-preserving alternatives — Topics, Protected Audience (FLEDGE), Attribution Reporting, and on-device APIs — under heavy regulatory and competitor scrutiny. Es gehört zur Kategorie Datenschutz der Cybersicherheit.
Was bedeutet Privacy Sandbox?
Google's umbrella initiative for replacing third-party cookies and cross-site identifiers with privacy-preserving alternatives — Topics, Protected Audience (FLEDGE), Attribution Reporting, and on-device APIs — under heavy regulatory and competitor scrutiny.
Wie funktioniert Privacy Sandbox?
Privacy Sandbox is Google's multi-year initiative, launched in 2019, to replace third-party cookies and other cross-site identifiers in Chrome and Android with a family of purpose-built, on-device, privacy-preserving APIs while keeping the ad-supported web economically viable. The web-side APIs include Topics (browser-derived interest categories), Protected Audience (FLEDGE, previously TURTLEDOVE — on-device remarketing auctions), Attribution Reporting (browser-mediated conversion measurement with noise), Shared Storage and Fenced Frames (cross-site state in a privacy-bounded form), and Trust Tokens / Private State Tokens. Android-side counterparts include Topics, Attribution Reporting, and SDK Runtime. The U.K.'s Competition and Markets Authority has supervised Privacy Sandbox since 2022, with Google committing to behavioral remedies; in July 2024 Google announced it would keep third-party cookies in Chrome with a new user-choice mechanism rather than deprecate them, while continuing Sandbox APIs alongside. For privacy and AppSec teams, Privacy Sandbox is a major architectural change that needs site-by-site impact assessment.
Wie schützt man sich gegen Privacy Sandbox?
Schutzmaßnahmen gegen Privacy Sandbox kombinieren typischerweise technische Kontrollen und operative Praktiken, wie in der Definition oben beschrieben.
Welche anderen Bezeichnungen gibt es für Privacy Sandbox?
Übliche alternative Bezeichnungen: Google Privacy Sandbox.
● Verwandte Begriffe
- privacy№ 1263
Drittanbieter-Cookie
Cookie, das von einer anderen Domain als der in der Adresszeile gesetzt wird und historisch zur seitenübergreifenden Verfolgung von Nutzern dient.
- privacy№ 1286
Topics API
A Privacy Sandbox API in Chrome and Android that derives a small set of high-level interest topics from the user's recent browsing locally on the device, exposing them to participating sites instead of cross-site tracking identifiers.
- privacy№ 088
Attribution Reporting API
A Privacy Sandbox API in Chrome and Android that lets advertisers measure ad conversions across sites without cross-site identifiers, using browser-mediated, noise-injected event-level or aggregated reports.
- privacy№ 143
Browser-Fingerprinting
Zustandsloses Tracking-Verfahren, das Nutzer durch Kombination von Browser-, Geräte- und Konfigurationsmerkmalen zu einer nahezu eindeutigen Signatur identifiziert.
- privacy№ 266
Seitenübergreifendes Tracking
Die Praxis, die Aktivität eines Nutzers über mehrere voneinander unabhängige Websites hinweg zu verknüpfen, um ein langlebiges Verhaltensprofil aufzubauen.
- privacy№ 233
Consent Management
Prozesse und Werkzeuge zur Erhebung, Dokumentation, Aktualisierung und Durchsetzung von Nutzerzustimmungen für die Verarbeitung personenbezogener Daten und das Setzen von Cookies gemäß Datenschutzrecht.