# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/firefox-add-ons-privacy-policy-in-listing-details/
- Source: [extensionworkshop.com](https://extensionworkshop.com/documentation/develop/create-an-appealing-listing/)
- GrowthDex source hub: [Firefox Extension Workshop: Create an appealing listing](/sources/firefox-extension-workshop-create-an-appealing-listing-extensionworkshop/)
- Last checked: 2026-06-06T12:04:00Z
- Rarity: uncommon
- Budget: free
- Channels: Marketplaces, Trust, Conversion
- Stages: browser extensions, firefox add-ons, privacy policy, trust surface


## Why this can grow

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.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where firefox add-ons privacy policy in listing details can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Trust channel.
3. Use the evidence from extensionworkshop.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed 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.

## Adjacent tactics in the same lane

- [Firefox Add-ons name earns the slug](/growth-ideas/firefox-add-ons-name-earns-the-slug/) - same source, 1 shared channel, 2 shared stages
- [Firefox Add-ons no-surprises copy before install](/growth-ideas/firefox-add-ons-no-surprises-copy-before-install/) - 2 shared channels, 2 shared stages
- [Chrome Web Store summary hook in 132 characters](/growth-ideas/chrome-web-store-summary-hook-in-132-characters/) - 2 shared channels, 1 shared stage
- [Chrome Web Store five-screenshot install story](/growth-ideas/chrome-web-store-five-screenshot-install-story/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The Firefox Add-ons page should remove the surprise before install](/blog/the-firefox-add-ons-page-should-remove-the-surprise-before-install/) - marketplaces, SEO, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.