Back to GrowthDex
Growth idea action plan

Firefox Add-ons privacy policy in listing details

Put the privacy policy text in the AMO listing details itself, not only on your own site, so the trust answer is present where the install decision gets made.

uncommon tacticfree budget

Why this can grow a startup

A privacy link that sends the buyer somewhere else creates one more place for trust to leak. Mozilla's listing guide recommends plain language and tells developers to include the privacy policy text in the listing details even if a copy exists elsewhere. That changes the economics of the install page. Instead of making the user leave the decision surface, the add-on answers the awkward question in place. Good extension pages reduce context switching. This is one of the simplest ways to do it.

Company example

Firefox Extension Workshop says developers should write privacy policies in plain language and include the text of the privacy policy and license agreement in the add-on's listing details even if copies are hosted elsewhere.

Source and metric

Source: Firefox Extension Workshop: Create an appealing listing

Mozilla recommends including the privacy-policy text directly in the listing details, not only as an external link.

MarketplacesTrustConversionbrowser extensionsfirefox add-onsprivacy policytrust surface
GrowthDex operator note

When to use it

Use this when Marketplaces, Trust, Conversion is relevant to browser extensions, firefox add-ons, privacy policy and you can run a bounded test with a free budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

Founder checklist

  1. Read Firefox Extension Workshop: Create an appealing listing and identify what is directly supported.
  2. Choose one channel context: Marketplaces, Trust, Conversion.
  3. Define the test around Mozilla recommends including the privacy-policy text directly in the listing details, not only as an external link..
  4. Set an owner, evidence window, and stop condition before launch.

Explore the context

Product-Led GrowthMarketplacesTrustConversion

Related tactics

Firefox Add-ons no-surprises copy before install

Write the listing so a user can tell what the add-on does and what data it sends before install, because Mozilla treats that plain disclosure as part of review and consent.

epicMarketplaces, Brand, Conversion

Chrome Web Store five-screenshot install story

Use the full five-screenshot allowance to show the setup, the core action, and the payoff so the listing starts onboarding before the user hits install.

uncommonMarketplaces, Onboarding, Conversion

Chrome Web Store summary hook in 132 characters

Write the 132-character summary as the buyer's first job-to-be-done sentence, because Chrome shows it on the homepage, category pages, and search results before the long description gets a chance.

uncommonMarketplaces, SEO, Conversion

Safari extension in-use screenshots, not title art

Show the extension working instead of leaning on splash art or login chrome, because Apple reviews screenshots as product proof rather than poster design.

uncommonMarketplaces, Brand, Conversion

Chrome Web Store single-purpose and permission justification

State one narrow job for the extension and justify each permission in the privacy tab so the install page answers the trust question before review or install friction appears.

rareMarketplaces, Security, Conversion

Chrome Web Store test instructions with credentials if needed

Fill the Test instructions tab with reviewer steps and credentials when the extension needs login or paid state, so approval depends on the real workflow instead of a locked door.

rareMarketplaces, QA, Conversion
Advisory bridge

Apply this with an operator

Choose product surfaces that compound distribution without hiding weak activation or retention.

Work with Ian