I Tested 5 “Private” Browsers — Only One Didn’t Spy

Summary of the Video

The video tests five “privacy” browsers by measuring idle startup network traffic—that is, what each browser sends/contacts before any website visit, clicks, or typing. The creator argues that many privacy marketing claims are technically defensible but misleading once you look at real network behavior.

---

Testing Methodology (Core Technical Approach)

• Tool: Wireshark (packet capture / network protocol analyzer).
• Test setup:
  • A clean OS install on a dedicated test machine (no other apps).
  • Each browser launched and allowed to fully initialize.
  • The browser was then left idle for 15 minutes on the desktop.
• What was measured:
  • All external connections made during idle time.
  • Connections initiated by the browser itself (with no user interactions).
• Validation:
  • Captured server addresses were cross-referenced with:
    • publicly available server ownership databases,
    • independent privacy research,
    • and the browser’s own source code (when available).

Claim: This is presented as a “cleanest possible” test for verifying what a browser does without user actions, directly challenging marketing statements about “no tracking.”

---

Results by Browser (What the Traffic Indicates)

1) Brave

• Compared to marketing: Mostly consistent with Brave’s stated architecture, including:
  • update checking,
  • safe browsing database updates,
  • component verification.
• Main issue found: Brave connected to infrastructure associated with Brave Ads during idle startup—even when the tester had not enabled Brave Rewards / opted in.
• Nature of the issue:
  • Connections were described as limited and not behaving like traditional behavioral ad tracking,
  • but they still represent advertising-adjacent infrastructure a user might not expect from a browser chosen to escape ad surveillance.

2) Firefox

• Main issues found during idle startup:
  • Google Safe Browsing lookups (default behavior was described as documented/disclosed, but it contradicts some users’ expectations for a non-Google privacy browser).
  • Mozilla telemetry sending session initialization data by default.
  • Pocket checking for content even without the user enabling Pocket.
• Nuance: Firefox can become substantially more private when configured, but the default startup configuration made more external connections than privacy-focused users typically expect.

3) DuckDuckGo (Desktop Browser)

• Main finding: Connections to Microsoft Bing infrastructure during idle startup before any searches.
• Why this matters: DuckDuckGo uses Bing for search infrastructure, but the startup connections suggest maintaining/establishing Microsoft connectivity as part of background initialization—not only when a query is submitted.
• User-impact angle: For users choosing DuckDuckGo to reduce exposure to Microsoft data infrastructure, this was framed as a significant mismatch (including concerns tied to Windows 11).

4) Opera

• Most concerning outcome in the comparison:
  • Connections associated with advertising measurement and behavioral analytics platforms.
  • Traffic metadata indicating session initialization telemetry, including hardware fingerprinting signals.
  • Connections to infrastructure linked to Opera’s parent company (not detailed fully in the subtitles, but described as scrutinized by privacy researchers).
• VPN detail: Opera’s built-in VPN routes traffic through Opera’s own servers, meaning it doesn’t simply “hide from third parties”—it shifts traffic to Opera infrastructure with Opera data practices.

5) LibreWolf

• Finding: During the 15-minute idle test, LibreWolf showed only update checks to its own update servers.
• Not found (as claimed by the video):
  • no connections to Google,
  • no Mozilla telemetry,
  • no advertising-adjacent connections,
  • no fingerprinting signals,
  • no analytics-platform connections.
• Why it passed: LibreWolf is described as a Firefox-based browser configured specifically to remove/disable telemetry and Google-related behaviors, with stricter privacy defaults.

---

Overall Conclusions / Analysis Framing

• In 4 out of 5 cases, privacy marketing was described as being optimistically framed:
  • marketing claims weren’t necessarily outright lies,
  • but the network evidence suggests users would likely reject those behaviors if explained plainly.
• The creator argues the only reliable way to evaluate privacy claims is to observe what the software actually transmits at the network level, since policies/marketing language can be selective.

---

Practical Recommendations Mentioned (Configuration Steps)

• If using Brave:
  • disable Brave Rewards (if not using it),
  • block Brave advertising endpoints via system firewall.
• If using Firefox:
  • install uBlock Origin,
  • set privacy.resistFingerprinting in about:config,
  • disable telemetry in Privacy & Security settings.
• If using DuckDuckGo or Opera for privacy:
  • the video recommends switching to LibreWolf as a meaningful improvement based on the network results.
• Tradeoffs for LibreWolf:
  • stricter privacy defaults can break some sites (especially JS behavior),
  • requires more configuration to handle incompatible websites,
  • smaller userbase means fewer community troubleshooting resources,
  • update timing may lag Firefox briefly after security updates.

---

Guides Promised / Future Content

The creator says they will provide:

• a Wireshark setup guide, and
• specific configuration steps for each tested browser, so users can move them closer to the privacy behaviors implied by default marketing.

---

Main Speakers / Sources

• Main speaker: The video creator/tester (not named in the subtitles).
• Primary tool/source referenced: Wireshark (open-source network protocol analyzer).
• Browsers compared: Brave, Firefox, DuckDuckGo browser, Opera, LibreWolf.
• Related referenced systems/services: Brave Ads, Google Safe Browsing, Mozilla telemetry, Pocket, Bing, Opera’s VPN/analytics infrastructure.