Peite

Privacy Policy

Effective date: September 30, 2026

This Privacy Policy explains how Peite ("Peite", "we", "us", or "our") collects, uses, stores, and shares information when you use the Peite Chrome extension and related services.

Peite is designed around a local-first privacy model. Most of what the extension collects — your browsing history, time-on-page information, and domain-control data — remains on your device by default. Two things change that: explicitly using an AI feature, and History Sync, which (once you connect an account) uploads your browsing history to the Peite service so it's available across your devices and survives the local 90-day retention limit — see "2. Our Privacy Approach" and "3.1 Browsing history" below for exactly when and how.

This Privacy Policy is intended to accurately describe the data practices of the Peite extension and to be consistent with the disclosures made in the Chrome Web Store and Microsoft Partner Center.

1. Who We Are

Peite is operated by:

UAB Peite
Vingrių g. 13-7, LT-01141 Vilnius
Company code: 307385007
peite.office@gmail.com

For privacy-related questions, please contact us at peite.office@gmail.com.

If Peite is offered to users in the European Economic Area, the entity identified above acts as the data controller for personal data that Peite processes on its own behalf, except where applicable law provides otherwise.

2. Our Privacy Approach

Peite is designed so that your ordinary browsing activity does not need to leave your browser. Unless you explicitly activate an AI feature, or have History Sync turned on:

History Sync is the one exception to "never leaves your browser." Connecting a Peite account for the first time on a given browser turns History Sync on automatically; while it's on, your browsing history is uploaded to the Peite service (see 3.1 below). You can turn this off at any time from the extension's stats page, and that choice is remembered even if you disconnect and reconnect later.

When you explicitly request an AI feature, the minimum information necessary to provide that feature may be transmitted to the Peite service and, where applicable, forwarded to our AI service provider.

3. What Data Peite Collects

3.1 Browsing history

Depending on the features you use, Peite may locally record:

This information is stored locally in your browser and automatically deleted after 90 days. It is used to provide Peite's statistics, history, insights, and export functionality.

If History Sync is on (the default from the moment you first connect an account on a given browser — see "10. Your Controls" to turn it off), the same history entries, plus the time spent on each page and a random per-browser device ID, are also uploaded to the Peite service's database roughly every 15 minutes and on manual "Sync now", where they are not subject to the 90-day local limit. If History Sync is off, browsing history is never transmitted as part of ordinary browsing.

3.2 Time-on-page information

Peite may locally record how long a page remains the focused or active browser tab. This information is associated with the relevant locally stored browsing-history entry. It is used to provide your personal statistics and browsing insights. It is transmitted to the Peite service only while History Sync is on, or if you explicitly request an AI feature that requires an aggregated browsing summary.

3.3 Domain lists

Peite may maintain local:

These determine whether particular domains are allowed, warned about, or blocked. Peite may periodically retrieve a public JSON file containing domain-list information from the Peite service. This request is read-only. Peite does not include your browsing history or other personal browsing information in that request.

3.4 Email address

If you register for Peite AI features, we collect your email address. Your email address is used to:

Your email address is not sold or provided to advertisers or data brokers. Your email address is not sent to Anthropic as part of AI requests.

3.5 Password

Where the current Peite registration system uses a generated password:

Passwords are used solely for authentication and account-related functionality.

3.6 Registration ID

Peite may generate a unique registration identifier associated with your account. The registration ID may be stored:

It is used to authenticate and rate-limit AI requests. The registration ID is not provided to Anthropic as an identifying account credential.

4. AI Features

Peite provides optional AI-powered features. These features are activated only when you explicitly request them. Depending on the feature, Peite may transmit the following information to the Peite service.

AI Safety Check

When you select "Check this page", Peite may transmit:

The information is collected for the purpose of performing the requested AI safety analysis. Peite does not intentionally collect:

The transmitted page information is not part of your ordinary Peite browsing history transmission.

AI Insights

When you select "Analyze", Peite may generate an aggregated browsing summary from your locally stored history for the date range you select. This summary may include:

The underlying browsing history remains local unless separately transmitted by another explicitly requested feature. The aggregated summary is transmitted only when you explicitly request AI analysis.

5. How AI Requests Are Processed

AI requests are sent first to the Peite service. The Peite service acts as a technical intermediary between the extension and the external AI provider. The extension does not directly contain or expose the Peite service's Anthropic API key. Where an AI request requires Anthropic processing, the Peite service forwards the relevant request to Anthropic using the Peite service's server-side API credentials. Anthropic therefore receives the information necessary to process the particular AI request, but does not receive your Peite email address merely because that request is processed.

6. How We Use Your Data

We use information only for purposes connected with the Peite features you use. Specifically:

Local browsing information

Used to:

Email address

Used to:

Registration ID

Used to:

AI request data

Used to:

Peite does not use your browsing history or AI request data for behavioral advertising. Peite does not sell your browsing history. Peite does not sell your personal information. Peite does not use your browsing history to create advertising profiles.

7. Data Sharing

Peite may share information with the following categories of recipients.

Peite service

The Peite service receives:

The service processes this information to provide the requested Peite functionality.

Anthropic

Where an AI feature uses Anthropic's API, the relevant AI request is transmitted to Anthropic. Depending on the feature, this may include:

Anthropic does not receive your Peite email address as part of the normal AI request architecture described in this Privacy Policy. Anthropic's applicable API terms and privacy documentation govern Anthropic's processing and retention of API data. Anthropic currently states that, under its standard commercial API retention policy, API inputs and outputs are automatically deleted from its backend within 30 days, subject to stated exceptions and alternative arrangements such as Zero Data Retention.

Public domain-list file

Peite may periodically request a publicly available JSON file containing domain-list information. This request does not intentionally transmit your browsing history or personal browsing data.

Other third parties

We do not sell, rent, or otherwise disclose your email address, registration ID, browsing history, or AI request data to third parties for advertising, data brokerage, or behavioral profiling. We may disclose information where reasonably necessary:

8. Chrome Web Store Limited Use

Peite complies with the Chrome Web Store User Data Policy and its Limited Use requirements. Peite uses browser permissions and user data only to provide or improve the functionality described in the Peite Chrome Web Store listing and this Privacy Policy. Peite does not use personal or sensitive user data for:

Peite does not permit human review of user data except where reasonably necessary for security, legal compliance, or another exception permitted by applicable law and the Chrome Web Store policies. Google requires extensions handling user data to disclose collection, use, and sharing practices and to limit use and transfers to permitted purposes.

9. Data Retention

Local data

Browsing history, time-on-page data, and local domain-control information remain in your browser for up to 90 days (automatically deleted after that), or until:

whichever comes first. Session-only information, including temporary domain overrides and active-tab tracking information, may be cleared when the browser session ends or restarts.

History Sync data

Once uploaded, synced history is not subject to the 90-day local limit and persists on the Peite service until the account is deleted, a deletion request is processed, or you turn off History Sync — note that turning it off stops future uploads but does not retroactively delete what was already uploaded.

Registration information

Your email address and registration record remain on the Peite service until:

At launch, Peite may not provide a self-service account deletion endpoint. If so, users may request deletion by contacting peite.office@gmail.com. We will process valid deletion requests in accordance with applicable law and any mandatory retention requirements.

AI requests

Peite is designed not to maintain a permanent database of the page content or browsing summaries submitted for individual AI requests. Temporary technical processing data may exist for as long as reasonably necessary to:

Where Anthropic processes the request, Anthropic's applicable API retention terms also apply.

10. Your Controls

Peite provides controls that allow you to manage locally stored information.

Clear Data

The Clear Data function removes locally stored browsing history and duration information. It does not delete your Peite registration or any already-synced history from the Peite service.

History Sync toggle

On by default the first time you connect an account on a given browser; you can turn uploading on or off at any time after that from the stats page, and your choice sticks even if you later disconnect and reconnect (this browser won't be silently re-enrolled). Turning it off stops future uploads but does not remove what was already uploaded — contact us to have already-synced history deleted.

Remove Account From Browser

The account Remove function removes the locally stored registration information from the browser. Removing local registration information does not automatically delete the corresponding server-side registration or synced history.

Temporary Domain Overrides

The Clear function can remove temporary domain permissions and blacklist bypasses.

Uninstall

Uninstalling Peite removes the extension's locally stored browser data, subject to Chrome's extension-storage behavior. Uninstalling does not automatically delete a server-side Peite registration.

11. Your GDPR Rights

If the GDPR or another applicable data-protection law applies to you, you may have rights including:

You may exercise applicable rights by contacting peite.office@gmail.com. We may need to verify your identity before completing certain requests.

You also have the right to lodge a complaint with the competent data-protection supervisory authority. For users in Lithuania, the relevant supervisory authority is the State Data Protection Inspectorate (Valstybinė duomenų apsaugos inspekcija).

12. Legal Bases for Processing

Where the GDPR applies, we rely on one or more of the following legal bases, depending on the specific processing activity:

Performance of a contract

We may process registration information where this is necessary to provide the Peite service you requested.

Consent

Where required, we may rely on your consent for a particular processing activity. You may withdraw consent at any time where processing is based on consent.

Legitimate interests

We may process limited information where necessary for legitimate interests such as:

Where we rely on legitimate interests, we consider and balance those interests against your rights and freedoms.

Legal obligation

We may process or retain information where required by applicable law.

13. Security

We use reasonable technical and organizational measures designed to protect information against unauthorized access, alteration, disclosure, or destruction. Data transmitted between the Peite extension and Peite servers is transmitted using encrypted connections such as HTTPS/TLS. Server-side credentials, including the Anthropic API key, are maintained on the Peite server and are not intentionally exposed to the extension. Locally stored registration credentials are protected by Chrome's extension storage environment. However, no electronic storage or transmission system can be guaranteed to be completely secure.

14. Chrome Extension Permissions

Peite requests browser permissions necessary for its functionality. Depending on the version of the extension, these may include:

history

Used to access browsing history so Peite can provide local browsing statistics and related functionality.

tabs and activeTab

Used to determine the currently active page and provide features relating to that page.

storage

Used to store Peite's local settings, history-related information, registration information, and other extension data.

alarms

Used to perform scheduled extension tasks (domain-list sync, History Sync uploads, local-history pruning).

declarativeNetRequest

Used to implement domain-blocking and domain-control functionality.

webNavigation

Used to monitor relevant navigation events required for Peite's functionality.

scripting

Used by the optional AI page-safety feature to inspect the current page when you explicitly request an analysis.

Host permissions

Used to communicate with the Peite service (sign-in, AI features, History Sync) and retrieve the public domain-list resource. Peite does not use these permissions to transmit your browsing history during ordinary browsing when History Sync is off. Chrome recommends requesting only the narrowest permissions necessary for an extension's functionality.

15. Children's Privacy

Peite is not directed to children. We do not knowingly collect personal information from children in circumstances where such collection is prohibited by applicable law. If you believe that a child has provided personal information to Peite, please contact us at peite.office@gmail.com.

16. International Data Transfers

Depending on the location of our service providers and infrastructure, personal data may be processed outside the European Economic Area. Where the GDPR applies, we will use appropriate safeguards for international transfers where required by applicable law.

17. Changes to This Privacy Policy

We may update this Privacy Policy when Peite's data practices, functionality, service providers, or legal requirements change. If a change materially affects how we collect, use, or share personal data, we will provide an appropriate notice where required by law. The effective date at the top of this policy indicates when it was most recently revised.

18. Contact

For questions, requests, or concerns about Peite's privacy practices, please contact:

UAB Peite
peite.office@gmail.com

You may also contact us through the official Peite project support channel: peite.office@gmail.com.