You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/documentation/publish/add-on-policies-faq.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,7 +91,7 @@ Yes. Add-ons intended for internal or private groups can be listed on AMO.
91
91
92
92
### What are the key requirements when submitting an add-on?
93
93
94
-
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](https://extensionworkshop.com/documentation/publish/source-code-submission/).
94
+
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](/documentation/publish/source-code-submission/).
95
95
96
96
### Do I need to submit my source code?
97
97
@@ -113,23 +113,23 @@ Yes, especially if your add-on contains minified, transpiled, or machine-generat
113
113
114
114
### What is the definition of data transmission?
115
115
116
-
Data transmission refers to any data that is collected, used, transferred, shared, or handled outside of the add-on or the local browser.
116
+
Data transmission refers to any data that is collected, used, transferred, shared, or handled outside of the add-on or the local browser.
117
117
118
118
### What data transmission practices are prohibited?
119
119
120
120
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.
121
121
122
122
### What data transmission practices are permitted?
123
123
124
-
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](https://extensionworkshop.com/documentation/publish/add-on-policies-preview-2025-08/#data-collection-and-transmission-disclosure-and-control).
124
+
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](/documentation/publish/add-on-policies-preview-2025-08/#data-collection-and-transmission-disclosure-and-control).
125
125
126
126
### Do I have to host my privacy policy on addons.mozilla.org (AMO)?
127
127
128
-
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.
128
+
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.
129
129
130
130
### What data requires affirmative consent (opt-in)?
131
131
132
-
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](https://extensionworkshop.com/documentation/develop/firefox-builtin-data-consent/).
132
+
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](/documentation/develop/firefox-builtin-data-consent/).
133
133
134
134
{% endcapture %}
135
135
{% include modules/one-column.liquid,
@@ -153,10 +153,10 @@ Add-ons must safely manage data and interactions with the browser, web, and OS.
153
153
154
154
Add-ons may be blocked if they:
155
155
156
-
* Intentionally violate policies.
157
-
* Contain critical security vulnerabilities.
158
-
* Compromise user privacy.
159
-
* Circumvent user consent or control.
156
+
* Intentionally violate policies.
157
+
* Contain critical security vulnerabilities.
158
+
* Compromise user privacy.
159
+
* Circumvent user consent or control.
160
160
* Obfuscate or contain unreadable code.
161
161
162
162
### Will I be notified before my add-on is blocked?
0 commit comments