How to turn off Google's "privacy sandbox" ad tracking, and why you should

Original Article ↗ Hacker News Discussion ↗

Google’s new “Privacy Sandbox” ad technology in Chrome is seen by many as a rebranding of tracking rather than a genuine privacy improvement, because it moves profiling into the browser while preserving Google’s control over the ad ecosystem. Commenters weigh alternatives such as switching to Firefox or non-Chromium browsers, pushing for better regulation, and using tools to block or poison tracking data, while also debating whether an ad-funded web can ever align with user privacy and freedom. Dark-pattern consent prompts, regulatory constraints like GDPR and antitrust, and the tension between centralized tracking and a more decentralized, user-controlled internet emerge as central concerns.

Overall reaction to Google’s “Privacy Sandbox”

  • Many see the branding as misleading “doublespeak”: tracking is being reframed as “privacy.”
  • Some argue it still improves privacy vs legacy third‑party cookies, especially given Google’s antitrust constraints, but others say Safari/Firefox already block third‑party cookies by default, so this is worse than the existing non‑Chrome status quo.
  • Concern that combining browser and ad network roles makes Google “fox guarding the henhouse”; suggestion that Chrome should be separated from Google’s ad business.

How Privacy Sandbox / Topics API works (per thread)

  • Tracking logic is said to run locally in Chrome; sites get coarse “topics” (up to a few per epoch) instead of per‑site cookies.
  • Topic taxonomy has hundreds of categories; browser tracks only a small top set and returns at most one topic per epoch to a site.
  • There is built‑in “noise” (e.g., 5% random topics), but cited research suggests this can be bypassed when combined with other fingerprinting data.
  • Some mention that with Chrome sync and no custom passphrase, this local data might still end up on Google servers; defaults are unclear.

Dark patterns and consent

  • The “Got it” button is criticized as a dark pattern that silently opts users in.
  • In the EU, the dialog is reportedly clearer and more explicit, highlighting that Google knows the global version is manipulative.
  • Commenters call for stronger UX and consent regulations (e.g., GDPR‑style defaults and concise messages).

Alternatives to Chrome and browser monoculture

  • Strong push to uninstall Chrome and use non‑Chromium browsers (especially Firefox) to preserve engine diversity and reduce Google’s leverage.
  • Mixed experiences with Firefox: praised for privacy and extensions (notably uBlock Origin, containers, Focus on mobile), but criticized for hidden/awkward profile management, occasional site incompatibility, and slightly worse performance/features.
  • Some corporate environments mandate Chrome and block Firefox or its extensions, reinforcing Chrome dominance.

Advertising, “free internet,” and business models

  • Large debate on whether a “free” internet without tracking ads is feasible.
  • One side: ads funded early personal blogs and today’s big platforms; someone has to pay, and non‑tracking ads may earn too little.
  • Other side: pre‑ad web and donation‑funded sites (e.g., encyclopedias, forums) show alternatives; ads incentivize surveillance and low‑quality content.
  • Several note you can do non‑tracking ads or self‑host ads, but revenue trade‑offs and scalability are contested.

Broader privacy concerns and user strategies

  • Some argue browser choice is moot if hardware (Intel ME/AMD PSP) and mainstream OSes are untrustworthy; others push Linux as partial mitigation.
  • Suggestions include: using Firefox containers/profiles, privacy‑focused mobile browsers, data “poisoning” via random behavior, and throwaway emails/phone numbers to avoid identity‑linked profiling.
  • Skepticism that individual user actions can change much; some argue the real levers are regulation and developer/browser‑vendor choices, not end‑user settings.