An update on Mozilla's terms of use for Firefox

Funding, Google, and Mozilla’s trajectory

  • Many argue Mozilla is in this position because it relied for years on a huge Google search deal instead of building sustainable, diversified revenue.
  • Some note Mozilla still has hundreds of millions in cash/investments and question why a browser with ~$500M/year historically “needs” to sell data at all.
  • Others counter that browser development is extremely expensive, Google’s antitrust issues threaten that revenue, and Mozilla must stockpile a war chest or collapse.

“We never sell your data” vs CCPA and actual practices

  • The key outrage: Mozilla dropped the “never sell your data” claim, then cited California’s very standard definition of “sale” that matches what users mean (sharing personal info for money/other value).
  • Many conclude Mozilla has in fact been selling user data via new‑tab ads and sponsored suggestions, just under legalistic rewording.
  • Defenders suggest some of what counts as a “sale” may be aggregated/deidentified metrics and not per‑user profiles; critics reply that aggregate ad metrics are still based on tracked user behavior.

New license language and “Firefox as a service”

  • The clause granting Mozilla a “nonexclusive, royalty‑free, worldwide license” over “content you input in Firefox” alarms many.
  • Core objection: a local browser vendor should not need any copyright license to data that never goes to Mozilla; that’s only necessary if Firefox is or will be sending user content to Mozilla/partners (e.g., AI, cloud features).
  • Some see it as boilerplate driven by lawyers; others see it as groundwork for broad future data/AI use and a re‑framing of Firefox as a “service,” conflicting with free‑software norms.

Telemetry, ads, and scope of data collection

  • Users dig into Mozilla’s privacy notice: new‑tab ads, sponsored suggestions, interaction metrics (views, clicks, positions), and some technical/location data can be shared with “partners,” often “de‑identified or aggregated.”
  • Supporters argue this is non‑personal, often on‑device, and tied to experiments like privacy‑preserving ad tech (OHTTP, acquired Anonym); critics say it is still behavioral tracking, and de‑identification is weak in practice.
  • Confusion persists on exactly which Firefox features trigger CCPA “sale” and whether opt‑outs truly stop all transmission.

Acceptable Use Policy and control

  • The now‑removed Acceptable Use Policy would have effectively banned common activities (viewing violent content, unsolicited communications, etc.) when applied to a browser binary; this was widely seen as incompatible with FOSS principles.
  • Mozilla’s framing that the AUP “caused confusion” is viewed by many as blame‑shifting rather than acknowledging a substantive misstep.

Alternatives, forks, and ecosystem risk

  • Many long‑time users report uninstalling Firefox or planning to: popular destinations include LibreWolf, Waterfox, various Gecko forks, Safari with blockers, and emerging engines like Ladybird and Servo.
  • Others warn that mass migration to forks weakens upstream Firefox and accelerates a Chromium monoculture, making the web more dependent on Google.
  • Some suggest the ideal would be a lean, community‑controlled Firefox (or Servo) focused solely on engine/browser, separate from Mozilla’s broader political and product agenda.

Business models, donations, and governance

  • A large faction argues Mozilla should offer a paid, telemetry‑free Firefox or clear product‑specific donation channels; they distrust donating today because money largely funds non‑browser initiatives and high executive pay.
  • Skeptics doubt enough users would pay to cover real costs and note that once source is open, free binaries will appear; others counter that a small paying “whale” base among ~200M users could easily fund a focused browser team.
  • Leadership is widely criticized for “mission drift,” political projects, and expensive acquisitions (Pocket, adtech startup Anonym) while Firefox lost market share and differentiation.

Legal risk vs user expectations

  • Some commenters accept that over‑broad US privacy laws and class‑action risk push lawyers to maximize protection with vague, expansive ToS language.
  • Others respond that Mozilla had a third option: genuinely stop collecting/selling data so that the legal definition of “sale” becomes irrelevant.
  • Overall sentiment: Mozilla’s explanations clarified that data‑sharing for commercial purposes is real, but did not restore trust; many now view Mozilla as just another ad‑funded vendor, not the privacy champion it once claimed to be.