Privacy policy
Effective July 8, 2026 · applies to the peeq Chrome extension v0.5
The short version: peeq makes zero network requests. Nothing you do with peeq is collected, transmitted, sold, or shared — with us or with anyone. There are no accounts, no analytics, and no trackers.
What peeq accesses
When you click the peeq icon, the extension reads the current page's DOM to extract schema.org structured data (JSON-LD and Microdata). This happens locally, in your browser, only on the tab you clicked. The extracted data is shown to you and discarded when the popup closes. It is never sent anywhere.
Local history (optional)
peeq keeps an optional history of pages you've audited, stored only on your device via chrome.storage.local. It is designed around data minimization:
- Summaries only. Each entry stores a sanitized URL, timestamp, schema count, source counts, and the list of
@types — never the schema contents. - Sanitized before saving. Credentials, hashes, sensitive query parameters (tokens, sessions, emails, …) and tracking parameters (
utm_*,gclid, …) are stripped or redacted. - Never recorded: incognito tabs, private and internal hosts (localhost, loopback, private IP ranges,
.local), and non-http(s) pages. - Encrypted at rest with AES-GCM. Only ciphertext is written to disk.
- You are in control. Pause recording, remove single entries, or clear everything, at any time, from the history view.
History never leaves your device. It is not synced, backed up, or transmitted.
Permissions
| Permission | Why peeq needs it |
|---|---|
| activeTab | Read the current page's DOM when you click the icon — and only then. |
| scripting | Inject the extraction script into the active tab on click. No persistent content scripts. |
| storage | Store your theme preference and the optional, encrypted, device-only history. |
What peeq never does
- No network requests of any kind — no servers, no APIs, no CDNs.
- No analytics, telemetry, fingerprinting, or ads.
- No selling, sharing, or transferring of any data — there is nothing to sell.
- No remote code. Everything ships inside the extension package.
Changes
If a future version changes any of this — for example, optional paid features that call AI APIs — this policy will be updated first, the change will be prominently disclosed in the extension, and the free, offline core will keep working exactly as described here.
Contact
Questions or concerns? Email support@peeq.ing.