HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
EFForg
dnt-guide
Learning & Reference2017–2022
EFForg / dnt-guide

dnt-guide

How to Implement DNT

3Distinct people
5Mentions
0Explicit recommenders
144GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

How to Implement DNT

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year5 dated mentions

Observed mentions: 2017-11-05 15:29:16 UTC to 2022-08-30 18:10:12 UTC.

01232017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC110
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC303
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101

What Hacker News says

5 sources
Can you give a few more details of what you mean? It's true that Do Not Track (DNT) is not a true standard in terms of implementation and intent and different folks mean different things when setting the DNT flag. However, when building DNT for EthicalAds and for Read the Docs, we followed the EFF's implementation guide for DNT[1]. This means a number things including: * We do not store personally identifying information when users are merely browsing a site with our ads. * We rotate our logs in less than 10 days * We do not set cookies on ad requests. We also don't use some non-cookie alternative. Obviously for publishers or advertisers, logging into our backend requires a login cookie. [1]: https://github.com/EFForg/dnt-guide
In Show HN: EthicalAds – Privacy-first ad network for developers
Props to Medium, because not only does it respect DNT, it pretty rigorously follows the advice about blocking third-party embeds if they don't respect it.[0] Medium is not always on my good side, and I think the site has some problems, but at least somebody working there does really care about privacy, and I regularly notice and appreciate their work. DuckDuckGo as well, but I would have a problem if they didn't respect DNT. Medium is the site where they really didn't have to care, but they did anyway. [0]: https://github.com/EFForg/dnt-guide#a-embedly
In Why Doesn't Google Comply with Do Not Track?
- Medium (https://medium.com/.well-known/dnt-policy.txt) - EFF (https://www.eff.org/.well-known/dnt-policy.txt) - Read the Docs (https://readthedocs.org/.well-known/dnt-policy.txt) Sites that implement DNT should respond to either /.well-known/dnt-policy.txt or /.well-known/dnt/ or both. Responding to /.well-known/dnt/ means a site has implemented the W3's Tracking Preference Expression (https://www.w3.org/TR/tracking-dnt/). This doesn't necessarily mean much as there's no agreed standard of what complying with DNT means. However, it typically implies that the site does something different for users with DNT enabled vs. disabled. Responding to /.well-known/dnt-policy.txt is typically stricter and means a site adhere's to the EFF's guidelines (https://github.com/EFForg/dnt-guide) for DNT. This has rules for how long data is retained, which
Read the rest
data can be retained, specifications around anonymizing data, and security precautions. Disclaimer: I worked on Read the Docs' DNT implementation.
In Why Doesn't Google Comply with Do Not Track?
> I'm sorry, but this is crap. I agree with your sentiment that on by default should be the standard. However, it isn't. The standard is specific and it says it should be off by default. The standard was designed to be completely toothless and the advertising industry still tried to water it down. There's no enforcement mechanism and nothing that says what it means to comply. If you want something with teeth, try the EFF's pseudo-standard for DNT: https://github.com/EFForg/dnt-guide
In Why Doesn't Google Comply with Do Not Track?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.