This is a request for documentation. https://www.eff.org/dnt-policy says to include the policy verbatim under .well-known/dnt-policy.txt. Also, this repo contains a JSON file with hashes for the respective versions.
However, the text of the policy contains the sentence
This file will always be posted via HTTPS at https://example-domain.com/.well-known/dnt-policy.txt
to indicate this fact.
On reading the policy, it seems, that this sentence should be updated to contain the actual domain that issues the policy. In fact, that's how I did it on codepoints.net: https://codepoints.net/.well-known/dnt-policy.txt
Of course, any hashes will be different then. But apart from the above mentioned "verbatim" I found no note, if the file is indeed meant to be included just as downloaded from Github, or is a template (as https://example-domain.com/ suggests), that needs editing.
The intended way of embedding should be published at the FAQ at https://www.eff.org/dnt-policy, too.
This is a request for documentation. https://www.eff.org/dnt-policy says to include the policy verbatim under
.well-known/dnt-policy.txt. Also, this repo contains a JSON file with hashes for the respective versions.However, the text of the policy contains the sentence
On reading the policy, it seems, that this sentence should be updated to contain the actual domain that issues the policy. In fact, that's how I did it on codepoints.net: https://codepoints.net/.well-known/dnt-policy.txt
Of course, any hashes will be different then. But apart from the above mentioned "verbatim" I found no note, if the file is indeed meant to be included just as downloaded from Github, or is a template (as
https://example-domain.com/suggests), that needs editing.The intended way of embedding should be published at the FAQ at https://www.eff.org/dnt-policy, too.