Metricly Privacy Policy

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

This Privacy Policy explains how Metricly: PageSpeed, SEO & Pixel Audit (“Metricly”, “we”, “our”, “us”) handles information when you use the Chrome extension.

Metricly is a Manifest V3 extension for Google Chrome. It helps you audit the page you are viewing: PageSpeed / Lighthouse-style performance, tracking pixels, on-page SEO, and social link previews — in the Chrome side panel (opened from the toolbar icon).

This policy covers:

  • The Metricly extension installed in Chrome
  • The Metricly API proxy used to request PageSpeed Insights data (for example https://metriclyapi.sunuplab.com)

It does not govern Google’s services beyond what is technically required when PageSpeed Insights is called on your behalf.

Metricly is Chrome-only. There is no Firefox build.

To provide features you explicitly use, Metricly may process:

Data When Why
Active tab URL When you open the extension or run a scan To know which page to audit, scan for pixels, or read SEO / social preview metadata
Audit strategy (mobile / desktop) When you choose it or load a saved preference To run or cache the correct PageSpeed mode
Cached audit results (scores, metrics, issues, Agentic Browsing checklist, in-progress flags) Locally on your device To show results without re-fetching until you retest or clear data
Audit history (per site) When audits complete successfully Stored in browser localStorage to show past runs
Feedback prompt state (success count, whether prompt was shown) After successful audits To show an optional feedback dialog at most once after several audits

We do not operate Metricly accounts inside the extension, and we do not require sign-in for core features.

  • Pixels, SEO, and social preview scans read the active page locally via chrome.scripting. Extracted signals (including Open Graph and Twitter Card meta tags) are processed in the extension UI; they are not uploaded to Metricly servers. Preview images may be fetched by your browser directly from their source URLs when displayed.
  • Theme follows your system prefers-color-scheme setting. Metricly does not store a separate theme preference.

Metricly does not include usage analytics (no Google Analytics or similar telemetry in the extension). We do not sell data and do not use it for advertising profiles, data brokerage, profiling, or credit decisions.

We are not designed to collect:

  • Name, email, phone, or account credentials (except what you voluntarily send if you use an external feedback form)
  • Payment or financial data
  • Health data
  • Personal communications content
  • Precise geolocation
  • Full browsing history or keystrokes

Processed information is used only to:

  • Run audits and page scans you request
  • Show results and audit history in the extension
  • Cache audit state and remember mobile/desktop preference for usability
  • Optionally prompt for product feedback after several successful audits

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

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

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

For abuse prevention, the proxy may also process your client IP address (from Cloudflare request headers) in short-lived counters to enforce rate limits. Operational logs on the proxy (via Cloudflare Workers observability) may record request metadata such as page hostname, audit strategy, HTTP status, and timing — not your full browsing history.

Metricly does not intentionally send unrelated tab data, cookies from other sites, or your full browsing history to third parties.

If you choose Leave feedback, you are taken to a third-party form (Tally). That interaction is governed by Tally’s policy, not Metricly’s. No data is sent to Tally unless you open the link and submit the form yourself.

If the extension is built with VITE_METRICLY_WORKER_SECRET, that value authenticates to your proxy only. Treat it like a password; do not publish it in public repositories.

Storage What Where
chrome.storage.local Audit cache, mobile/desktop preference, feedback prompt flags Browser extension storage
localStorage Audit history list Browser local storage

Data remains until you clear extension/site storage, retest or clear cached audits, or uninstall the extension.

Permission Purpose
activeTab Access the tab you interact with to audit or scan it
tabs Keep the side panel aligned with the active tab and window while open
storage Save audit cache, strategy preference, and feedback prompt state
sidePanel Open Metricly in Chrome's side panel when you click the toolbar icon
scripting Inject short-lived scripts to detect pixels and read SEO / social preview metadata on the active page
Host permissions http://*/* and https://*/* to inject pixel and SEO scanners on pages you view; plus your PageSpeed proxy origin

Metricly does not download and execute remote JavaScript or WebAssembly as extension code. The executable extension is shipped in the 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: maksymbv@icloud.com

A copy of this policy may also be published on our website for convenience. If versions differ, prefer the copy bundled with or linked from the extension at the time you installed it.