You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: