Privacy Policy
Payments and the account are not available yet. The sections about them below describe the prepared flow for a future launch.
In short: the texts of your AI chats are stored only in your browser. We do not sell data or share it for advertising, we use no trackers, and the extension collects no analytics. Our server receives only what the key and payments cannot work without. Below is exactly what, why, and how to delete it.
Who we are
The data controller and seller is seller details will be published before payments open, registration number at the same time, address: at the same time. For any data question, write to hello@chatsavo.com.
This policy covers the Chatsavo extension (Chrome, Edge, Yandex Browser, Opera, Brave, Arc, Vivaldi and Firefox) and the chatsavo.com website.
What stays only in your browser
| Data | Where it is stored |
|---|---|
| Texts and titles of chats the AI site's page loaded for you | Extension storage (IndexedDB) on your device |
| Folders and pinned chats (tags and prompts, once they arrive) | Same place |
| Search index | Same place |
| Panel settings, trial start date, license token | Extension storage (chrome.storage) |
This data never reaches us. The extension reads only the AI site responses with the chat list and chat content that the page itself already requested. It does not modify requests and never reads or forwards cookies, passwords, tokens or authorization headers of the AI sites.
Local data is not encrypted: anyone with access to your browser profile can read it. If other people use your computer, use a separate browser profile.
The trial start date is also copied to the browser's synced storage (chrome.storage.sync). If browser sync is on, the browser itself carries it (for example, through your Google account). We have no access to that copy.
What reaches our server and why
| Data | When | Why | How long we keep it |
|---|---|---|---|
| A random device ID (a UUID created at install, not linked to your identity), browser name, extension version | When you activate a key and when it is re-checked, about once a day | To verify the key and enforce the 5-device limit | While the key exists. You'll be able to unlink a device at any time — device management arrives together with payments |
| Your key | When issued after payment and on activation | To issue and verify the key | To verify the license, we store an HMAC-SHA256 of the key and its last 4 characters. When a new key is issued, we temporarily keep an encrypted copy to show it after payment, pass it to the extension and retry the key email if delivery fails. The copy is available for these purposes for 24 hours; after that it is no longer used and is deleted by the next daily cleanup. We do not store the plaintext key in our databases |
| A hash of the device ID and a salted hash of your network subnet | When the trial starts | To prevent unlimited trials. The IP address itself is not stored | 30 days |
| IP address | On any request to the server | Protection against brute force and abuse: the server counts requests per subnet hash | The IP is not recorded; hash-based counters are deleted after 2 days |
| Payment data: the provider's payment ID, plan, amount, currency, status, partner code (if any) | On payment | To issue and renew the key, handle refunds and keep accounting records | Technical fields of the provider's response: 180 days; the payment record itself: for the period required by accounting law |
AI site recognition rules are built into the extension; fixes ship as a new extension version. If a remote configuration is added in the future, it will be downloaded from our server as data with a plain HTTP request and no identifiers, and we will update this policy in advance.
Payments and e-mail
Ruble payments (YooKassa). The e-mail you enter at checkout goes to YooKassa (YooMoney NBCO LLC) for the fiscal receipt required by Russian Federal Law 54-FZ. After payment, we send your key to that address through Resend; if delivery temporarily fails, we may retry sending the same key within 24 hours of its issue. We do not store the e-mail of ruble buyers in our databases. The key is also shown on the page after payment and passed to the extension automatically. Card details are entered on YooKassa's side and we never receive them.
Dollar payments (Paddle) are coming later. Paddle acts as the seller (Merchant of Record) and processes payment data under its own policy. Paddle will give us your e-mail so we can send your key and let you sign in to your account; we keep it while you have a key and delete it on request, except records we must keep by law.
Your account (/account) uses a sign-in link sent by e-mail. If you sign in, we store your e-mail address and the sign-in session. The account is not yet available to ruble buyers. If you lose your key, contact support with the payment number from your YooKassa receipt.
Features that do not exist yet
We will update this policy before they launch.
- Sync between devices (Pro). Only you can turn it on. Data is encrypted in the browser with a key derived from your passphrase; the server stores only ciphertext it cannot read.
- AI summary when moving a conversation to another AI (Pro). Chat texts are stored only in your browser. They reach the server only when you click "AI summary" yourself: the text of that chat is then passed through our server to an AI provider to produce the summary and is not stored. We will show a separate consent window before the first use.
- Anonymous usage statistics. Not collected now. If added, only with your consent, off by default, with no texts, page URLs or personal data.
The chatsavo.com website
- We use Vercel Web Analytics, which counts visits without cookies and without identifiers that could recognize you.
- No third-party trackers, pixels or ads. See the cookie policy.
- The site's host (Vercel) processes IP addresses and browser data in technical logs to deliver pages and defend against attacks.
Who else processes data
We use vendors only to run the service and do not let them use data for their own purposes:
| Vendor | Role |
|---|---|
| Supabase Inc. | Database and server functions for licenses and payments |
| Vercel Inc. | Website hosting, anonymous visit statistics |
| Resend | Sending key e-mails |
| YooKassa (YooMoney NBCO LLC) | Ruble payments, 54-FZ receipts |
| Paddle.com Market Ltd | Dollar payments (when available), independent seller |
We do not sell data or use it for advertising. We disclose data to authorities only when the law requires it.
Legal bases
- Performance of a contract: checking your key, counting devices, payments, sending the key, refunds.
- Legitimate interest: preventing trial abuse and key brute-forcing, service security.
- Legal obligation: fiscal receipts, accounting.
- Consent: newsletters, messages sent through website forms. You can withdraw consent at any time.
Users in the EU and UK (GDPR)
You have the right to:
- access: learn what data we hold about you and get a copy;
- rectification of inaccurate data;
- erasure ("right to be forgotten"), except data we must keep by law;
- restriction of processing and to object to processing based on legitimate interest;
- portability: get your data in a machine-readable format. All local extension data can be downloaded as JSON at any time;
- withdraw consent at any time, without affecting the lawfulness of earlier processing;
- lodge a complaint with the data protection authority in your country.
Some vendors are located in the USA. Transfers outside the EU rely on the European Commission's Standard Contractual Clauses or other mechanisms provided by the GDPR. We respond to requests within one month. We make no automated decisions with legal effects on you.
Users in Russia (152-FZ)
In the prepared ruble-payment flow, the buyer’s email is not written to our database. YooKassa uses it for the receipt, and Resend uses it to deliver the key email, including retries after temporary failures. Data hosting regions and processing arrangements with vendors must be confirmed before payments open. You may request information about the processing of your data, its correction, blocking or destruction, withdraw consent, and appeal to Roskomnadzor or a court. Where consent is required, it is given in a separate document (in Russian). We respond within 10 business days, extendable by 5 business days with a stated reason.
How to delete your data
- Local data: in the extension, open Settings → Your data → Delete all data. You can click "Download everything (JSON)" first. Removing the extension also erases its local data. Chats on the AI sites themselves are not affected.
- A device: device management arrives together with payments; then you'll be able to unlink a device in the extension settings or in your account, and the activation record is deleted. Until then, write to hello@chatsavo.com.
- Everything else on the server: write to hello@chatsavo.com. We delete or anonymize the data within 30 days. Payment records we must keep by law are anonymized and deleted when the retention period ends.
Security
Connections to the server are encrypted (HTTPS). We store key hashes for license verification; temporary encrypted copies for key issue and delivery are described above. IP addresses are stored only as salted subnet hashes. Only server functions can access the database; internal data is not reachable from the browser. We report serious breaches to users and authorities within the deadlines set by law.
Children
The service is not intended for children under 14 (under 16 in the EU unless permitted by local law). We do not knowingly collect their data.
Changes to this policy
If we change what data we process, we will update the date at the top and announce it on the website and in the extension in advance. Earlier versions are available on request.