Can I use the same privacy policy for Chrome and Firefox?

Yes, if both builds collect the same data. Make sure the Chrome Privacy tab and the Firefox manifest declarations match the policy.

Does my add-on need consent to send data?

For personal data, yes: Mozilla’s policy makes it opt-in, with a clear description first.

Mozilla Add-ons (AMO) · Platform guide

Privacy policy for Firefox add-ons (AMO)

Firefox add-ons on addons.mozilla.org must be honest about data collection. For Firefox 140+, Mozilla requires you to state data collection practices in the manifest using its taxonomy; older-compatible add-ons must give users a clear control right after install. Personal data is opt-in, and your privacy policy should describe the same practices.

§ 1

What Mozilla Add-ons (AMO) requires

Add-on Policies — 6.2.1 Data collection (Firefox 140+)

“It must accurately state the data collection practices in the extension manifest, including when it does not collect data, in line with the Firefox add-on data classification taxonomy”

Source: extensionworkshop.com verified 2026-10-30

1.1Older Firefox versions: control after install. 6.2.2: “The user must be provided with a clear way to control the add-on’s data transmission immediately after installation of the add-on.” Source: extensionworkshop.com

1.2Personal data is opt-in. 6.2.2.1: “Before an add-on may transmit personal information, it must clearly describe, and the user must affirmatively consent”. Mozilla lists names, email addresses, search terms and browsing activity as examples. Source: extensionworkshop.com

1.3Firefox built-in consent. Mozilla documents a built-in data collection consent experience that reads the data_collection_permissions you declare in manifest.json. Source: extensionworkshop.com

§ 2

What common SDKs collect

SDK / API	Data it collects	Source
WebExtension APIs (examples)	Browsing activity (tabs, history, webRequest) Search terms Cookies Names and email addresses entered by the user	Source: extensionworkshop.com

Everything in this table must appear in your policy if the SDK ships in your build.

§ 3

Where to put the URL

3.1AMO Developer Hub → your add-on → Edit product page → Privacy policy.
3.2Declare data_collection_permissions in manifest.json to match the policy.
3.3Link the policy from your add-on’s options page.

§ 4

Sample clause

§ 4.1 · Browsing data

The add-on reads the address of the current tab only when you click its toolbar button, to look up the page. It does not send your browsing history to us. If you turn on Sync in Options, we store your saved items and email address on our server until you delete them.

Illustrative wording. Your generated policy is written from your own answers.

§ 5

Questions

Can I use the same privacy policy for Chrome and Firefox?: Yes, if both builds collect the same data. Make sure the Chrome Privacy tab and the Firefox manifest declarations match the policy.
Does my add-on need consent to send data?: For personal data, yes: Mozilla’s policy makes it opt-in, with a clear description first.