What Is Do Not Track?

Do Not Track (DNT) was a browser header a visitor could enable to signal that they did not want to be tracked across different websites. It was widely implemented in browsers around a decade ago but never became a binding standard.

Current status

Most major platforms, including Google/YouTube, do not honour the DNT header, and most modern browsers have removed or deprecated the setting in favour of other privacy controls such as blocking third-party cookies outright or offering dedicated tracking-protection modes.

What actually helps instead

Rather than relying on DNT, site owners get more reliable privacy improvements from using the youtube-nocookie.com embed domain, deferring embeds behind a click-to-load pattern, and giving visitors an explicit cookie consent choice.

A brief history of Do Not Track

Do Not Track emerged in the early 2010s as a proposed industry standard: a simple HTTP header a browser could send, and websites would voluntarily agree to honour, signalling that a visitor did not want to be tracked across sites. It was implemented in the settings of every major browser at the time, but adoption on the receiving end never became mandatory or consistent, and most large platforms, including YouTube and Google’s other services, chose not to change their behaviour based on it.

A practical example of why it fell short

Because honouring Do Not Track was always voluntary, a visitor could enable the setting in their browser and see literally no change in a site’s tracking behaviour, since nothing legally or technically compelled a website to respond to the signal. This gap between “I requested privacy” and “I received it” is a large part of why Do Not Track is now considered a largely deprecated approach, with several browsers having removed the setting from their interface entirely in recent years.

Do Not Track vs. modern privacy controls

Where Do Not Track relied on voluntary cooperation, current privacy approaches tend to rely on technical enforcement instead: browsers blocking third-party cookies outright, dedicated tracking-protection modes, and legally mandated consent mechanisms like those required under the GDPR. For YouTube embeds specifically, using the youtube-nocookie.com domain achieves through direct technical means what Do Not Track always intended but could never reliably deliver through a voluntary signal.

If privacy is the goal, technical measures like the privacy-enhanced embed domain now offer a more dependable path than any voluntary browser signal ever did.

If you encounter older documentation recommending a Do Not Track header check as part of a privacy strategy, treat that advice as outdated; modern browsers increasingly no longer expose the setting at all, making it an unreliable foundation to build any compliance approach on today.

In practice, this means a privacy-conscious site owner today gets far more real benefit from reviewing embed domains and consent banners than from anything related to the old Do Not Track header, which has essentially no remaining practical relevance to embedded video specifically.

Frequently asked questions