Announcing data collection consent changes for new Firefox extensions

As of November 3rd 2025, all new Firefox extensions will be required to specify if they collect or transmit personal data in their manifest.json file using the browser_specific_settings.gecko.data_collection_permissions key. This will apply to new extensions only, and not new versions of existing extensions. Extensions that do not collect or transmit any personal data are required to specify this by setting the none required data collection permission in this property.

This information will then be displayed to the user when they start to install the extension, alongside any permissions it requests.

Screenshot of example Firefox extension installation prompt showing data that the extension collects Screenshot of example Firefox extension installation prompt showing that the extension claims it collects no data

This information will also be displayed on the addons.mozilla.org page, if it is publicly listed, and in the Permissions and Data section of the Firefox about:addons page for that extension. If an extension supports versions of Firefox prior to 140 for Desktop, or 142 for Android, then the developer will need to continue to provide the user with a clear way to control the add-on’s data collection and transmission immediately after installation of the add-on.

Once any extension starts using these data_collection_permissions keys in a new version, it will need to continue using them for all subsequent versions. Extensions that do not have this property set correctly, and are required to use it, will be prevented from being submitted to addons.mozilla.org for signing with a message explaining why.

In the first half of 2026, Mozilla will require all extensions to adopt this framework. But don’t worry, we’ll give plenty of notice via the add-ons blog. We’re also developing some new features to ease this transition for both extension developers and users, which we will announce here.

2 comments on “Announcing data collection consent changes for new Firefox extensions”

Post a comment

  1. freaktechnik wrote on

    I’ve been trying to adopt this for my extensions. However, I’ve been struggling what kind of permissions polling a 3rd party would fall under. Obviously it is giving them information like the user’s IP or when they have Firefox open with the extension active (since that’s when the extension would poll), however technicalAndInteraction can only be optional so isn’t very useful for this.

    Reply

    1. Simeon Vincent wrote on

      @freaktechnik, does your extension include any other data with the request like query parameters, headerse, or a message body in a POST request? If not, you don’t even need to declare the technicalAndInteraction permission.

      Speaking of which, technicalAndInteraction is optional in the user can choose to disable it, but it is enabled by default. This permission is primarily meant for things like gathering metrics on feature usage in your extension.

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *