Keep Factually independent

Whether you agree or disagree with our analysis, these conversations matter for democracy. We don't take money from political groups - even a $5 donation helps us keep it that way.

Loading...Goal: 1,000 supporters
Loading...

Has DuckDuckGo faced any controversies regarding its no-tracking claims?

Checked on November 15, 2025
Disclaimer: Factually can make mistakes. Please verify important info or breaking news. Learn more.

Executive summary

DuckDuckGo has faced a notable privacy controversy stemming from 2022 reporting that its browser and apps allowed some Microsoft-owned tracking scripts to run due to a search/ads syndication agreement; DuckDuckGo acknowledged the exception and later moved to block those scripts [1] [2] [3]. The episode prompted security researchers and multiple outlets to question whether DuckDuckGo’s “we don’t track you” marketing matched its real-world behavior until the company changed its handling of Microsoft scripts [1] [4].

1. The discovery that started the uproar — researcher Zach Edwards’ audit

In May 2022 security researcher Zach Edwards audited DuckDuckGo’s Privacy Browser and reported that while the browser blocked trackers from Google and Facebook, certain Microsoft-placed scripts — for example on Microsoft-owned properties such as Bing and LinkedIn — were being allowed to load, exposing a gap between marketing and practice [1] [2].

2. DuckDuckGo’s public admission and its reason: a syndication agreement with Microsoft

DuckDuckGo founder and CEO Gabriel Weinberg publicly acknowledged the issue, explaining that a search syndication or ad partnership with Microsoft had created a carve-out that prevented DuckDuckGo from blocking some Microsoft-owned scripts in its apps and extensions [1] [2] [4].

3. Why critics said users were betrayed

Critics and privacy-minded users argued that the exception undercut DuckDuckGo’s core promise that it “never tracks you,” because the company’s marketing suggested comprehensive blocking of third‑party trackers; outlets and community threads framed the carve-out as a transparency failure that only came to light after independent analysis [5] [6] [7].

4. DuckDuckGo’s response and policy change — blocking Microsoft scripts

Within months DuckDuckGo amended its approach: it announced it had expanded its third‑party tracker blocking to include Microsoft-generated scripts across its mobile apps and browser extensions and planned similar changes for its desktop/beta browsers, saying it aimed for “more privacy and transparency” [3] [4] [5].

5. Technical nuance: what the exception actually meant for tracking

Reporting noted nuance: DuckDuckGo stated it didn’t associate personal identifiers with search queries and that Microsoft’s tracking in some contexts related to ad conversion measurement (e.g., bat.bing.com) rather than storing DuckDuckGo‑linked profiling data, while researchers highlighted that allowing scripts still created a realistic tracking pathway [2] [4].

6. How the episode fits into broader privacy trade-offs and business realities

Multiple sources frame the episode as an example of a tension between privacy branding and the practical business relationships search engines need (e.g., sourcing results and serving ads via partners). Outlets observed DuckDuckGo relied on Bing for results and advertising infrastructure, which complicates an absolutist “no exceptions” stance [3] [4] [5].

7. Follow-on coverage and assessment of DuckDuckGo’s standing

After DuckDuckGo changed its blocking behavior and increased transparency about tracker protections, subsequent coverage characterized the company as having corrected the specific issue; some commentators still use the event to counsel ongoing skepticism and note the importance of audits and disclosure for privacy claims [3] [8] [9].

8. What remained unclear or contested in reporting

Available sources do not mention long‑term technical proof that Microsoft profiled DuckDuckGo users via those scripts, nor do they provide evidence that DuckDuckGo deliberately sold user profiles; reporting instead centers on the presence of scripts, contractual carve-outs, and the potential for tracking unless blocked — leaving room for differing interpretations of severity [2] [4] [8].

9. Takeaway for users weighing DuckDuckGo’s privacy claims

The episode shows independent audits can reveal gaps between marketing and behavior; DuckDuckGo acknowledged the gap and later expanded protections to block Microsoft scripts, but privacy-conscious users should assess claims against documented practices and expect ongoing scrutiny of vendor partnerships and exceptions [1] [3] [4].

10. Broader lessons for privacy marketing and regulation

Journalistic and expert coverage of this controversy underscores that privacy promises are judged by technical reality and contractual detail — companies that market privacy must disclose exceptions and the business relationships that create them, and independent researchers play a key role in holding firms to those claims [1] [6] [5].

Want to dive deeper?
What evidence has been presented that DuckDuckGo's tracking protections can be bypassed?
Have privacy researchers or watchdogs formally criticized DuckDuckGo's no-tracking claims?
How does DuckDuckGo's tracker-blocking compare to Brave, Firefox, and privacy extensions like uBlock Origin?
Has DuckDuckGo had partnerships or business deals that raised conflicts with its privacy messaging?
What changes has DuckDuckGo made after past criticism to strengthen or clarify its privacy promises?