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.
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.
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.
Source-reported evidence
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.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
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.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Marketplaces and Trust, using evidence from Firefox Extension Workshop: Create an appealing listing as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.