Mozilla requires transparency regarding data collection
Briefly

Mozilla requires transparency regarding data collection
"Mozilla has announced that it will introduce new rules for Firefox extension developers starting November 3, 2025. From that date onwards, all new extensions submitted via addons.mozilla.org must explicitly state whether they collect or transmit personal data. This information must be included in the extension's manifest.json file via the new key browser_specific_settings.gecko.data_collection_permissions. According to Linuxiac, the measure is part of a broader privacy framework with which Mozilla aims to increase transparency towards users."
"When installing an extension, Firefox will now clearly show what data the extension collects, or whether no data is collected. This information appears next to the standard list of required permissions in the installation window. Mozilla displays the same information on the add-ons website, if the extension is publicly available there, and in the Permissions and Data section on the about:addons page in Firefox."
"The new requirement only applies to completely new extensions, not to updates of existing add-ons. However, developers who use the new key once must continue to include it in all subsequent versions. Extensions that do not fill in the field correctly cannot be submitted or signed until the error is corrected. For developers who support older versions of Firefox, it remains mandatory to provide users with a way to manage data collection immediately after installation."
Mozilla will require that all new Firefox extensions submitted to addons.mozilla.org from November 3, 2025 explicitly state whether they collect or transmit personal data in manifest.json via browser_specific_settings.gecko.data_collection_permissions. Extensions that do not collect personal data must use the value none. Firefox will display the declared data collection status during installation, on the add-ons site, and in about:addons Permissions and Data. The rule initially applies only to completely new extensions, but developers who use the key must keep it in later versions. Incorrect or missing values block submission and signing. In the first half of 2026 the requirement will extend to all extensions.
Read at Techzine Global
Unable to calculate read time
[
|
]