Skip to content
Metaspry
Install

Docs

Privacy

What Metaspry sends, where, and why.

The free Chrome extension is local-first. The audit, the previews, the JSON-LD parsing - all happen inside the browser.

What stays on your device

  • Every scan you run.
  • The 10-entry local history.
  • Pinned tags + theme + side-panel/popup mode preference.
  • Settings (audit thresholds, rule weights).

Stored via chrome.storage.local. Cleared when you uninstall the extension or clear extension storage.

What goes over the network

Three HTTP fetches per scan, each issued from your browser to the page’s own host:

  • GET /robots.txt
  • GET /sitemap.xml (and child sitemaps if it’s an index, up to 20)
  • GET /llms.txt

Plus image loads (og:image, twitter:image) when the Audit tab measures dimensions or Previews renders cards.

That’s it. No telemetry, no tracking, no analytics.

metaspry.com itself

The marketing site at metaspry.com (this site) optionally loads GoatCounter — a privacy-focused, no-cookie analytics tracker — only when PUBLIC_GOATCOUNTER_CODE is set at build time. It does not load by default.

The website does not set cookies. The newsletter form posts directly to Buttondown; no third-party scripts inject themselves into the page.

AI crawlers

The extension and the site explicitly allow AI crawlers (GPTBot, ClaudeBot, PerplexityBot) to index metaspry.com. That’s a positioning choice for the site itself - the Chrome extension doesn’t crawl anything and doesn’t expose your scan data to anyone.

Pro tier (paused)

Cloud-synced history, shareable scans, and bulk audit are on the public roadmap but not shipping yet. When they ship, this page will document exactly what each feature sends and where. Until then there is no auth layer, no Firestore writes, and no server-side state tied to any user.

Questions?

Email hello@metaspry.com with any privacy concerns.