User:Shaver/AMO Extension Policy: Difference between revisions
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
* description of the extension must clearly indicate that such collection occurs | * description of the extension must clearly indicate that such collection occurs | ||
* description of the extension must include a link to the privacy policy for the organization/site to which the data is reported | * description of the extension must include a link to the privacy policy for the organization/site to which the data is reported | ||
Relevant AMO bugs: | |||
* {{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 | |||
=== EffectiveBrand toolbars === | === EffectiveBrand toolbars === | ||
Revision as of 14:07, 15 May 2006
Collection of user data
- description of the extension must clearly indicate that such collection occurs
- description of the extension must include a link to the privacy policy for the organization/site to which the data is reported
Relevant AMO bugs:
- 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
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.