EFForg / EFForg/dnt-policy

DNT-policy is too permissive in certain cases

Open
#29 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
50
Forks
9
PR merge metrics
No merged PRs in 30d

Description

After being caught up in the net of being tracking services we posted the /.well-known/dnt-policy.txt and are perfectly fine with it for some services. However for other services we have a very simple policy. We do not track _ever_ unless there are specific technical reasons we need to. Of course we are in compliance with the posted policy, but having such a permissive policy seems to suggest that we are doing a lot less to protect users privacy than we are actually doing. We would suggest two additional policies in addition to the Do Not Track Compliance Policy.

# Do not track policy.
Outline:
We do not track you unless we have specific technical reasons.

This is the policy we would like to use.

# Do not track policy - strict.
Outline:
We do not track you.

We think this too strict and difficult to follow through in practice, but it should exist as an option.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the existing /.well-known/dnt-policy.txt and compare its language with the two proposed outlines in this issue. Add the non-tracking and strict policy variants where this repository publishes policy text, and consider the work done when both options are clearly documented and distinguishable.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.