Add-on Policies – Frequently Asked Questions
This is a preview of Frequently Asked Questions that will become effective on Aug 4, 2025.
This is a preview of Frequently Asked Questions that will become effective on Aug 4, 2025.
It means users should clearly understand what your add-on does before and after installation. The add-on's name and description must accurately reflect its functionality, and any unexpected features must be disclosed, opt-in, and clearly attributed to the primary function of the add-on.
Features unrelated to the add-on's primary function, such as altering the homepage, search engine, or new tab page, especially if not clearly indicated in the add-on's name or description.
The add-on must present a clear opt-in interface after installation, specifying the feature and its impact. Users must actively consent; default settings cannot enable these features.
Yes, but it should follow the format "<Add-on Name> for Firefox" and comply with Mozilla's Trademark Guidelines.
Yes. Add-ons must not violate Mozilla's Acceptable Use Policy, must disclose any required payments, and must not promote or install unrelated software or content.
Yes. Add-ons intended for internal or private groups can be listed on AMO.
Your add-on must function as described, pass functional and code reviews, and include testing information and credentials if necessary. Unrelated changes in updates can complicate the review process. More info, including default reviewer environment, can be found on the source code submission guidelines.
Yes, especially if your add-on contains minified, transpiled, or machine-generated code. Provide the original source code and build instructions. All dependencies must either be included in the source code package directly or downloaded only through the respective official package managers during the build process. Obfuscated code is not allowed.
Data transmission refers to any data that is collected, used, transferred, shared, or handled outside of the add-on or the local browser.
Transmitting search terms or browsing activity unrelated to the add-on's primary function, or any ancillary data not required for primary functionality, is prohibited.
Add-ons may provide user-initiated local backup features without requiring explicit user consent. For example, a bookmark add-on could allow a user to download an export of their bookmarks to their local filesystem. Sending this same export file to a remote server would require that the extension follow the Add-on Policies' Data Collection and Consent provisions.
A privacy policy is no longer required to be hosted on AMO. It is recommended that developers provide a link to their privacy policy on their AMO listing page.
Personally identifying information may only be collected after receiving explicit consent from the user. For more information on how different types of data are classified, see Add-ons Data Collection Taxonomy.
Add-ons must safely manage data and interactions with the browser, web, and OS. Add-ons must be secure, well-maintained, and performant.
Add-ons may be blocked if they:
Mozilla may attempt to contact you to address issues before blocking. However, in cases of intentional or severe violations, blocking may occur without prior notice.
Publish
Publish
Publish