Extension Privacy Checker
Free to linkEditorial links welcomeNo link schemes

Link to Extension Privacy Checker

Writing about extension permissions, privacy or version updates? Use a text link, an embeddable badge or a citation. Keep the anchor descriptive and link to the page that best matches your reader's question.

Text link

Link to the analyzer when your readers need to inspect a package. Link to the home page when you are introducing the tool.

<a href="https://extensionprivacychecker.example/en/analyzer">Extension Privacy Checker</a>

Suggested anchors: Extension Privacy Checker, browser extension analyzer, extension permission checker.

Badge embeds

Use a badge on a project page, documentation site or README. The badge links to the analyzer and uses descriptive alt text.

Extension Privacy Checker badgeExtension Privacy Checker light badge

HTML

<a href="https://extensionprivacychecker.example/en/analyzer" rel="noopener">
  <img src="https://extensionprivacychecker.example/badges/extension-privacy-checker.svg" alt="Extension Privacy Checker - free static analysis for browser extensions" width="300" height="64" loading="lazy">
</a>

Markdown

[![Extension Privacy Checker - free static analysis for browser extensions](https://extensionprivacychecker.example/badges/extension-privacy-checker.svg)](https://extensionprivacychecker.example/en/analyzer)

Markdown, light badge

[![Extension Privacy Checker - free static analysis for browser extensions](https://extensionprivacychecker.example/badges/extension-privacy-checker-dark.svg)](https://extensionprivacychecker.example/en/analyzer)

Citation

For articles, reports and academic work, cite the methodology page so readers can inspect the scoring rules and limits.

Extension Privacy Checker. (2026). Static analysis methodology for browser extensions. https://extensionprivacychecker.example/en/methodology

Do not describe a generated report as an official audit, certification or endorsement. The analyzer produces static indicators, not a malware verdict.

Suggested link targets

Match the link to the reader's intent instead of sending every link to the home page.

AnalyzerUpload a CRX, XPI, ZIP or manifest.json package.MethodologyScoring weights, detection rules and limits.Compare versionsDiff permissions, domains and findings.Privacy checker hubGuides on extension privacy.Permissions hubUnderstand API and host permissions.Guides indexHow-to, comparison and reference pages.

Linking guidelines

  • Use a descriptive anchor and link to a relevant page.
  • Do not imply that Extension Privacy Checker certified, approved or audited your extension.
  • No paid links, private blog networks, automated link drops or reciprocal-link requirements.
  • Disclose sponsored or affiliate relationships as required by your jurisdiction.

Frequently asked questions

Can I link to Extension Privacy Checker from my website?

Yes. You can link to the home page, the analyzer, the methodology page or a relevant guide. Use a descriptive anchor such as “Extension Privacy Checker” or “browser extension analyzer” rather than “click here”.

Can I use the badge on my extension's website or README?

Yes. The badge may be used on documentation, project pages and posts that reference the analyzer. Keep the alt text, link it to the analyzer, and do not imply that the site has certified or endorsed your extension.

Do you offer a data citation for research or journalism?

Yes. Cite the methodology page for scoring and detection details, and link to the analyzer for the tool itself. The citation formats on this page can be adapted for articles, reports and academic work.

Do you buy or exchange links?

No. We do not buy links, join link schemes or offer reciprocal-link requirements. Relevant editorial links, documentation links and directory listings are welcome.