From 85b0dddaba24af4f447ee4e96f8a219e06466817 Mon Sep 17 00:00:00 2001 From: Ben Kelly Date: Thu, 27 Jul 2023 11:39:49 -0400 Subject: [PATCH] Add links to the specification and developer documentation for MVP Chrome behavior. (#59) --- bounce-tracking-explainer.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/bounce-tracking-explainer.md b/bounce-tracking-explainer.md index 2afc0dd..d4e1e86 100644 --- a/bounce-tracking-explainer.md +++ b/bounce-tracking-explainer.md @@ -27,6 +27,8 @@ Safari, Firefox, and Brave have already shipped various bounce tracking mitigati # API / Browser Behavior +***NOTE**: This section contains early discussion of possible ways to mitigate bounce tracking. In developing Chrome's MVP implementation, however, we have settled on a more precise definition. This is fully defined in the [specification](https://privacycg.github.io/nav-tracking-mitigations/#bounce-tracking-mitigations) and also described in more accessible terms in [developer documentation](https://developer.chrome.com/docs/privacy-sandbox/bounce-tracking-mitigations/#how-it-works). Please see these sources for an up-to-date description of bounce tracking mitigations.* + This proposal does not have any additional API surface, but instead changes the behavior of the browser. At a high level the proposal is for the browser to automatically delete storage for a site (eTLD+1) when both of the following are true: