Intent to Prototype: Bounce Tracking Mitigations for dual-use sites

[Chromestatus]

Contact emails

sv...@chromium.org, ort...@chromium.org, l...@chromium.org, rtar...@chromium.org

Explainer

https://github.com/privacycg/nav-tracking-mitigations/blob/main/explainers/bounce-tracking-mitigations-for-dual-use-sites.md

Specification

None

Summary

Performs mitigations on URLs suspected of bounce tracking, even if the user has interacted with the URL’s site, possibly by blocking storage access or partitioning storage for those URLs.

Blink component

Privacy>NavTracking

Motivation

Bounce tracking mitigations (BTM) as currently implemented is applied at the site level, with an exemption for sites where the user has interacted with a page served by any of its URLs. As acknowledged in the original BTM explainer, this exception means that sites that many users interact with are not meaningfully prevented from doing bounce tracking at scale. We want to prototype bounce tracking mitigations at the URL level, to see if we can improve the coverage of bounce tracking we mitigate without breaking the web. Because bounce tracking looks technically similar to supported use cases like SSO, we want to expand incrementally.

Initial public proposal

https://github.com/privacycg/nav-tracking-mitigations/pull/100

TAG review

None

TAG review status

Pending

Risks

Interoperability and Compatibility

None

Gecko: No signal

WebKit: No signal

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

None

Debuggability

None

Is this feature fully tested by web-platform-tests?

No

Flag name on about://flags

None

Finch feature name

None

Non-finch justification

None

Requires code in //chrome?

False

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5422607224274944?gate=5966319415197696

This intent message was generated by Chrome Platform Status.