Effective date: September 16, 2026
This policy explains what data the Peite Chrome extension ("the extension," "we," "it") collects, how it's used, and who it's shared with. It's written to match exactly what's declared in the extension's Chrome Web Store listing and its manifest — if the two ever disagree, this document is out of date and should be updated before resubmission.
History, time-on-page, and domain-list data stay local to your own browser and are never sent anywhere. AI features work differently: they require registering with an email address, which is collected and stored — by us, on the Peite service that powers those features — and your requests to those features pass through that service on their way to Anthropic.
We do not sell or share your email with advertisers or data brokers, and Anthropic never receives your email at all — only the Peite service does.
| Data | What it is | Where it's stored | Sent anywhere? |
|---|---|---|---|
| Browsing history | Page URL, title, domain, and visit timestamp | Locally (browser storage) | No |
| Time-on-page | How long each page was the focused, active tab | Locally, attached to the matching history entry | No |
| Domain lists | Your synced whitelist/blacklist and any temporary domains you add | Locally | No (the sync itself is a read-only fetch of a public JSON file) |
| Email address | Given once, to register for AI features | Stored on the Peite service's database (not just locally) | Yes — to the Peite service, when you register. It also emails you a password (stored only as a salted hash). Not sent to Anthropic. |
| Password | A password generated at registration and emailed to you, proving you control that inbox; you can change it any time | Stored on the Peite service only as a salted hash, never in plain text | Emailed to you once (and again if you use Forgot password). Never sent to Anthropic. |
| Registration ID | A unique ID generated in exchange for your email; acts as your credential for AI requests | Locally, and on the Peite service's database (linked to your email) | Sent to the Peite service with every AI request. Not sent to Anthropic. |
| Page content (AI safety check) | Visible text, page title, meta description, form structure (never field values), and external link domains of the page you're on | Not stored — read only at the moment you click "Check this page," then discarded | Yes: to the Peite service, which forwards it to Anthropic, only when you click that button |
| Browsing summary (AI Insights) | An aggregated summary — time per domain, visit counts, time-of-day patterns — for your selected date range | Not stored separately — derived from local history at the moment you click "Analyze" | Yes: to the Peite service, which forwards it to Anthropic, only when you click that button |
Beyond your email address, we do not collect health information, financial or payment information, authentication credentials (passwords, form values), personal communications, or location data.
None of this data is used for advertising, analytics about you, or any purpose other than the feature you're actively using.
Session-only data (the currently-tracked tab's timer, temporary domain overrides, blacklist bypasses) is cleared automatically when your browser restarts.
In short: history, tabs, and
activeTab let it read and display your own browsing
data back to you; storage and alarms let
it save your data and run periodic tasks locally;
declarativeNetRequest and webNavigation
power the domain-blocking feature; scripting and the
content script power the optional page-safety-check feature; and
the host permissions allow the extension to reach the Peite service
(registration, AI features) and the public domain-list file it also
hosts. The extension itself never connects to Anthropic directly —
only the Peite service does, from its own server.
This extension is not directed at children and does not knowingly collect data from children.
Data stored locally is protected by Chrome's own extension storage sandboxing. Your registration ID functions as a bearer credential for AI requests — anyone with local access to your browser profile could, in principle, use it, the same as any other locally-stored credential. Server-side, we're responsible for securing the Peite service's Anthropic API key and its registrations database.
If what the extension collects or does changes, this document will be updated to match, along with the corresponding Chrome Web Store listing disclosures. Check the effective date above to see when it was last revised.
Questions about this policy or the extension's data practices can be raised via an issue on the project's GitHub repository.