User:Shaver/AMO Extension Policy: Difference between revisions

User:Shaver/AMO Extension Policy (view source)

Revision as of 22:18, 22 November 2006

370 bytes removed , 22 November 2006

→‎Collection of user data

Shaver

Confirmed users

455

edits

@@ Line 40: / Line 40: @@
 * description of the add-on must clearly indicate that such collection occurs
 * description of the add-on must include a link to the privacy policy for the organization/site to which the data is reported
+* the privacy policy must clearly indicate what data is collected, by whom, and what the data is used for, as well as who the user should contact for
+The privacy policy document should be clear and factual, and focus on what _is_ done with the data; it is not a marketing vehicle, and should not spend significant space describing what is _not_ done with the data.
 Relevant AMO bugs:
@@ Line 45: / Line 48: @@
 * {{bug|335707}} Permit developers to provide a link to a privacy policy for their extensions
 * {{bug|335708}} Display privacy policy link for extensions in listings
-== More detail: EffectiveBrand toolbars ==
-EffectiveBrand toolbars are only permitted if they meet both of the preceding requirements, *and* are based on version 1.0.1.13 (or later) of the EffectiveBrand code. Toolbars based on older versions of the EB code should be denied, with a comment indicating that the developer needs to update to use at least 1.0.1.13.  The version number of the extension (as from install.rdf) will match the toolbar code's version in virtually all cases, but if you want to check more closely:
-* The drop-down menu next to the toolbar logo has an "About" entry which will show the version number.
-* You can unzip the inner chrome/*.jar and look in about.xul and/or ebToolbarJS.js for the version strings.
 = Rating systems =