Wow, this week has to be one of the worst for the people over at Mozilla. There has been tremendous backlash to the organization’s updated Terms of Use.
Maybe not has big of a deal to Mozilla’s Mr. Robot blunder or the announcement to drop Firefox’s custom extensions system for that of Chromium, but still.
To recap: Mozilla announced terms of use and an updated privacy notice for Firefox on Wednesday. These were worded in lawyer-speak and included the following sentence:
When you upload or input information through Firefox, you hereby grant us a nonexclusive, royalty-free, worldwide license to use that information to help you navigate, experience, and interact with online content as you indicate with your use of Firefox.
Tech sites wrote about it and users were up in arms over the wording. Mozilla tried to calm users in an update, stating that the new terms did not give it ownership over user data or the right to use it for anything, even things not mentioned in the privacy notice.
It appears to have helped little. Mozilla published a new statement yesterday saying that it has updated the wording in the new terms of use to make things clearer for users.
The new wording includes the following paragraph now:
You give Mozilla the rights necessary to operate Firefox. This includes processing your data as we describe in the Firefox Privacy Notice. It also includes a nonexclusive, royalty-free, worldwide license for the purpose of doing as you request with the content you input in Firefox. This does not give Mozilla any ownership in that content.
Mozilla says it has also removed the “reference to the Acceptable Use Policy” because it seemed “to be causing more confusion than clarity”.
The Privacy FAQ was updated as well to better provide information on terms like “sells” according to the update.
This is a fairly common statement. Google, for example, has a big section of its terms of service dedicated to the worldwide, non-exclusive, royalty-free license that users give it.
If you check the terms of other browsers, you probably encounter something similar.
Was it an overreaction? Even with all the explaining, it seems likely that Mozilla won’t convince everyone that it was.
What is your take on this? Do you use Firefox currently? Let everyone know in the comment section below.











