DuckDuckGo browser seemingly sends domains a user visits to DDG servers (github.com)

Article summary

The DuckDuckGo browser has been found to send the domains of visited websites to DuckDuckGo's servers, allegedly for favicon retrieval. This behavior has raised concerns about user privacy. The issue was reported on GitHub, where a discussion ensued about the implications of this behavior. DuckDuckGo staff responded, explaining that the service is private and does not collect personal information.

Main themes

• privacy concerns
• browser behavior
• search engine dependencies
• alternative search engines
• privacy-focused browsing
• backend usage
• user trust and loyalty
• data collection and anonymity

What commenters say

• The browser's behavior is a privacy concern, as it sends user visit data to DuckDuckGo's servers.
• Implementing favicon retrieval locally would be a better approach to maintain user privacy.
• Some users trust DuckDuckGo despite this issue, citing its benefits over other search engines and browsers.
• The use of a backend for a privacy-focused browser is questionable, with some arguing it is unnecessary.
• Alternative search engines and browsers, such as Qwant and Startpage, are suggested as options for those concerned about privacy.
• DuckDuckGo's dependency on external services, like Bing, is seen as a potential vulnerability in its business model.
• The trade-off between privacy and functionality is a key consideration in the development of privacy-focused browsers and search engines.
• Some commenters are skeptical of DuckDuckGo's claims about the anonymity of the data collected through its favicon service.