Metricly — Page Speed & SEO Audit Privacy Policy

Effective date: May 13, 2026
Last updated: May 13, 2026

This Privacy Policy explains how Metricly — Page Speed & SEO Audit (“Metricly”, “we”, “our”, “us”) handles information when you use the browser extension.

Metricly is a Manifest V3 browser extension (for example Google Chrome and Mozilla Firefox) that helps you run PageSpeed / Lighthouse-style audits for the page you choose, from the extension popup.

This policy covers:

  • The Metricly extension installed in your browser
  • The Metricly proxy endpoint you configure (for example a Cloudflare Worker) used to request PageSpeed Insights data on your behalf

It does not govern Google’s or Mozilla’s own services beyond what is technically required when you use those platforms.

To provide the features you explicitly use, Metricly may process:

Data When Why
Active tab URL When you open the extension and run or resume an audit To know which page to analyze
Audit strategy (mobile / desktop) When you choose it or load saved preferences To run the correct audit mode
Cached audit state (scores, summaries, in-progress flags) Locally on your device To show results without re-fetching until you retest or clear data
Local audit history (per site, stored in the browser) When you run audits To show history inside the extension
UI preferences (for example theme) When you change settings To remember your choices between sessions
Light UI / session flags (for example feedback prompts) As needed for extension behavior To avoid repeating prompts inappropriately

We do not operate Metricly accounts inside the extension, and we do not require you to sign in to use core auditing features.

Metricly is not designed to collect, and we do not sell:

  • Name, email, phone, or account credentials (beyond what you voluntarily send us if you email support)
  • Payment or financial account data
  • Health data
  • Personal communications content
  • Precise geolocation
  • Keystrokes or full-page content outside what you send for an audit request

We do not use your data for advertising profiles, data brokerage, profiling, or credit decisions.

Processed information is used only to:

  • Run audits you request
  • Show results and history in the extension UI
  • Remember preferences and local cache for usability

When you run an audit, Metricly sends a minimal request to your configured Metricly proxy (the origin from VITE_PAGESPEED_WORKER_URL), typically including:

  • The page URL to audit
  • The strategy (mobile or desktop)
  • An Authorization header so your proxy can verify the client (see below)

That proxy may call Google PageSpeed Insights (https://www.googleapis.com/) and return the response to the extension. Google’s handling of requests is covered by Google’s policies, not this document.

Metricly does not intentionally send your full browsing history, cookies from other sites, or unrelated tab data to third parties—only what is needed for the user-initiated audit flow.

If you build or configure the extension with VITE_METRICLY_WORKER_SECRET, that value is used only to authenticate to your proxy. Treat it like a password: do not share it publicly or commit it to public repositories.

Metricly stores preferences, cache, and history locally in your browser (extension storage and other local storage the extension uses).

Data remains until you:

  • Clear site/extension storage in the browser
  • Remove cached entries (for example via retest / extension behavior)
  • Uninstall the extension

Metricly requests permissions only for documented functionality:

Permission Purpose
activeTab Read the active tab in context of your interaction to run an audit
tabs Keep the popup aligned with the active tab and window while it is open
storage Save preferences, cache, and small UI state
Host permissions In production: your proxy origin only. In development: may include localhost variants for local testing

Firefox: listing metadata may declare data_collection_permissions with required: ["none"] when applicable, meaning Metricly does not declare required collection of the listed sensitive categories beyond normal extension operation described here.

Metricly does not download and execute remote JavaScript or WebAssembly as extension code. The executable extension is shipped in the published package you install.

Metricly is not directed at children under 13, and we do not knowingly collect personal information from children.

We may update this policy. Material changes will be reflected by updating the Last updated date (and, when appropriate, the Effective date).

Privacy questions:

A copy of this policy may also be published on our website for convenience; if there is a conflict, the meaning should be the same—prefer the version bundled with the extension or linked from the extension at the time you installed it.