From 75417f5e3d32645859d94cec82255dc130ec4a2e Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 7 Apr 2024 18:55:34 +0200 Subject: Adding upstream version 2020.10.7. Signed-off-by: Daniel Baumann --- doc/yellowlist-criteria.md | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/yellowlist-criteria.md (limited to 'doc/yellowlist-criteria.md') diff --git a/doc/yellowlist-criteria.md b/doc/yellowlist-criteria.md new file mode 100644 index 0000000..c209328 --- /dev/null +++ b/doc/yellowlist-criteria.md @@ -0,0 +1,8 @@ +EFF maintains a Privacy Badger "yellowlist" of domains for which requests are allowed but Privacy Badger restricts access or availability of objectionable cookies and potentially other objectionable identifiers. + +Our objective in curating that list is to maximize user privacy while minimizing disruption to functionality that users expect from sites. The criteria we examine when considering possible yellowlist entries include (but are not limited to): + +* Was this in [Bau and Mayer's](https://jonathanmayer.org/papers_data/bau13.pdf) manually curated non-tracker list? +* Is this domain necessary for functionality the user expects from 1st party pages? +* Is the domain's privacy policy clear that it does not perform non-consensual tracking? +* Is there a reasonable self-hosted surrogate available that could replace the functionality of this domain (e.g. https://github.com/EFForg/privacybadgerchrome/issues/400). -- cgit v1.2.3