PrivacyScope — Privacy Policy

🔒

Short version: PrivacyScope does not collect, store, or transmit any personal data. All analysis runs locally on your device. Your extension list never leaves your browser.

What data we access

PrivacyScope reads your installed browser extensions using Chrome's built-in management API. This gives us access to each extension's name, version, permissions, and enabled/disabled status — the same information visible at chrome://extensions.

We do not access your browsing history, web page content, form data, passwords, cookies, files, or any other personal information.

How we use this data

Extension metadata is analyzed locally to produce a privacy risk score and plain-language flags. Results are stored in chrome.storage.local on your device only, so the popup can display them without re-scanning every time.

When you visit a Chrome Web Store extension detail page, PrivacyScope downloads that extension's package from Google's servers (clients2.google.com) to analyze its manifest before you install it. This request is made directly to Google — no intermediary server is involved.

Data we do NOT collect

No personal data. PrivacyScope does not collect names, email addresses, IP addresses, device identifiers, or any other information that could identify you.

No analytics or telemetry. PrivacyScope makes no analytics calls, telemetry requests, or usage tracking of any kind.

No data sharing. We do not sell, share, or transmit any data to any third party or server we operate.

No browsing history or page content. PrivacyScope holds zero host permissions for arbitrary websites and cannot read web page content from any site you visit.

External requests

The only external requests PrivacyScope makes are to Google's extension update servers:

clients2.google.com — Google's CRX download and update manifest server. Used to download extension packages for pre-install analysis when you browse the Chrome Web Store. This is the same server Chrome itself uses to install and update extensions.

clients2.googleusercontent.com, storage.googleapis.com, dl.google.com — Google CDN endpoints where CRX packages may be hosted. Requests are made only when you visit a Chrome Web Store extension detail page.

All other network activity is blocked by design — PrivacyScope requests no permissions to access any other host.

Local storage

PrivacyScope stores the following data locally in your browser using chrome.storage.local and chrome.storage.session:

Scan results (psResults, psSummary) — The most recent scan output. Stored so the popup can display results instantly without re-scanning. Cleared and replaced on each new scan.

Permission snapshot (psPermSnapshot) — A record of each extension's permissions from your last scan. Used only to detect when an extension has gained new permissions since your last scan.

Trusted extensions (psTrusted) — A list of extension IDs you have manually marked as trusted. Stored so trusted status persists between browser sessions.

CWS pre-install results (cws_tab_*) — Temporary scan results for extensions you are viewing on the Chrome Web Store. Stored in session storage only — automatically cleared when the tab is closed or the browser session ends.

None of this data leaves your device.

Permissions we request and why

management — Required to read the list of installed extensions and their declared permissions. This is the core function of PrivacyScope.

storage — Required to persist scan results, trusted extension IDs, and the permission snapshot between browser sessions.

webNavigation — Required to detect when you navigate to a Chrome Web Store extension detail page, so the pre-install badge can be shown.

Host permissions for Google servers — Required to download extension packages from Google's CRX distribution CDN for pre-install analysis. Without these, the CWS badge feature cannot function. These hosts are all operated by Google and serve no purpose other than CRX distribution.

Changes to this policy

If this privacy policy changes materially, the updated version will be included with the next extension update published to the Chrome Web Store. The "Last updated" date at the top of this page will reflect the most recent revision.

Contact

Questions about this privacy policy or PrivacyScope's data practices can be submitted via the Chrome Web Store support page for this extension.