Introducing a terms of use and updated privacy notice for Firefox

New Terms of Use & License to User Input

• The central flashpoint is the clause: when users “upload or input information through Firefox,” they grant Mozilla a non‑exclusive, royalty-free, worldwide license to use it “to help you navigate, experience, and interact with online content.”
• Many interpret this as Mozilla giving itself rights over everything typed or uploaded via Firefox (emails, banking, passwords), rendering it unsuitable for sensitive or regulated data (HIPAA, FERPA, GDPR).
• Others note it’s a license, not ownership, and argue it’s boilerplate to cover things like sync, search suggestions, and other Mozilla-mediated features—but critics say the scope is far too broad and ambiguous.

Privacy Notice Changes & Data Sharing

• Users highlight diffs between old and new privacy pages: new language about sharing data with “marketing partners,” tracking referrals, and sending usage data from pre-installed Firefox.
• A previous FAQ promise—“Does Firefox sell your personal data? Nope. Never have, never will.”—was removed and replaced by softer wording: Mozilla doesn’t sell data “in the way most people think,” but does share de‑identified/aggregated data with partners to keep Firefox “commercially viable.”
• This, plus Mozilla’s acquisition of an ad-tech company (Anonym), is widely read as preparation for data monetization and ad expansion.

Acceptable Use Policy & “Firefox as a Service”

• ToS now says use of Firefox must follow Mozilla’s Acceptable Use Policy, which bans using Mozilla services to upload or grant access to graphic sexual or violent content, and to do “anything illegal.”
• Some read this literally as: no browsing porn, war footage, or engaging in civil disobedience via Firefox, and potentially siding with repressive laws.
• Others argue the AUP clearly targets hosted services (sync, VPN, Relay), not generic browser traffic, but the document itself blurs that line by coupling AUP to “use of Firefox.”

Legal / Open-Source Questions

• Confusion over how these ToS interact with the MPL: do they apply only to Mozilla-distributed, branded binaries, or also distro builds and forks?
• Some suggest rebranding and rebuilding (as distros and forks do) avoids the ToS; others question enforceability of “continued use = acceptance” against GPL/MPL principles.

User Reactions and Migration to Alternatives

• Many long-time users say this is a breaking of trust and announce switching to forks (LibreWolf, Waterfox, Floorp, Zen, IceCat, Mullvad Browser, Tor) or to non-Gecko options (Brave, Vivaldi, ungoogled Chromium, future Ladybird).
• Concerns are raised about trusting smaller forks, their long‑term viability if Firefox declines, and about Chromium monoculture.

Debate: Misreading vs Enshittification

• One camp: the outrage is a misreading of standard legalese; the license is constrained by “as you indicate with your use of Firefox” and by the Privacy Notice; it doesn’t authorize blanket spying or data sale.
• Opposing camp: legal text must be read defensively; vague “help you navigate/experience content” can justify ad targeting and AI training; simultaneous removal of “never sell” language and ad-tech moves suggest deliberate enshittification, not mere clarification.

Wider Concerns About Mozilla’s Direction and Funding

• Participants criticize Mozilla’s reliance on Google search money, high executive pay, side ventures (VPN, AI, activism), and expensive offices, arguing resources should focus on the browser.
• Some still see Firefox as the “least bad” and essential non-Chromium engine; others conclude that, once the privacy brand is compromised, its main differentiator is gone.