File: README.md

package info (click to toggle)
chromium 138.0.7204.183-1~deb12u1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm-proposed-updates
  • size: 6,080,960 kB
  • sloc: cpp: 34,937,079; ansic: 7,176,967; javascript: 4,110,704; python: 1,419,954; asm: 946,768; xml: 739,971; pascal: 187,324; sh: 89,623; perl: 88,663; objc: 79,944; sql: 50,304; cs: 41,786; fortran: 24,137; makefile: 21,811; php: 13,980; tcl: 13,166; yacc: 8,925; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (52 lines) | stat: -rw-r--r-- 2,381 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
# Bounce Tracking Mitigations (BTM)

This directory contains the code for Chromium's Bounce Tracking Mitigation (BTM)
feature.
BTM aims to mitigate the privacy impact of "bounce tracking," a technique used
to track users across websites without relying on third-party cookies.

## What is bounce tracking?

Bounce tracking involves redirecting users through a tracker website, often
without their knowledge or interaction.
This allows the tracker to set or access first-party cookies, effectively
circumventing third-party cookie restrictions and user privacy preferences.

## How does BTM work?

BTM detects potential bounce tracking by analyzing website behavior, including:

- Short dwell times on a website before redirecting.
- Programmatic redirects (as opposed to user-initiated ones).
- Writing to storage (cookies, etc.) before redirecting.

If BTM determines that a website is likely involved in bounce tracking and
there's no indication of legitimate user interaction with the site, it
automatically deletes the site's storage (eTLD+1) after a brief grace period.

### Goals of BTM

- **Reduce cross-site tracking:** Limit the ability of bounce trackers to
  identify and track users across different contexts.
- **Protect user privacy:** Prevent bounce tracking from circumventing
  third-party cookie restrictions.
- **Maintain compatibility:** Avoid disrupting legitimate use cases like
  federated logins and payment flows that rely on redirects.
- **Adaptability:** Mitigate tracking by short-lived domains that may evade
  traditional blocklist-based approaches.

### Non-Goals

- **Replacing third-party cookie blocking:** BTM is primarily designed for
  environments where third-party cookies are already restricted.
- **Mitigating tracking by sites with significant first-party activity:** BTM
  focuses on incidental parties (sites without meaningful user interaction) and
  may not be effective against sites with substantial first-party engagement.

## Further Reading

- BTM Spec: https://privacycg.github.io/nav-tracking-mitigations/#bounce-tracking-mitigations
- BTM Explainer: https://github.com/privacycg/nav-tracking-mitigations/blob/main/bounce-tracking-explainer.md
- Chrome Status Listings:
  - Original BTM Feature: https://chromestatus.com/feature/5705149616488448
  - Stateless Bounce Extension: https://chromestatus.com/feature/6299570819301376