Privacy Policy · SaveAI

The short version. SaveAI is local-first. Most export formats are produced inside your own browser. PDF export is rendered on our server by default — your conversation is uploaded for rendering — and you can switch PDF to local rendering in the extension settings. The only data we keep server-side is what's needed to run a sign-in: your email, your Google sign-in identifier, account timestamps, and the number of PDFs you've exported today (for capacity planning). Nothing else. We do not train models on your data. We do not sell data. We have no ads.

1. Scope

This policy covers the SaveAI browser extension (the "Extension"), the website at www.saveai.one (the "Website"), and the account and backend services we operate (the "Services"). Together we refer to these as "SaveAI".

2. Data the Extension stores locally

The Extension stores the following data on your device only, using Chrome's local storage and IndexedDB APIs:

Settings. Your interface language, reading theme, page width, font size, PDF page configuration (size, orientation, margins, image quality, page numbers, watermark), filename format, cache retention period, and other display preferences.
Captured conversations. When you choose to export a chat, the Extension writes a copy of that chat (title, messages, model name, source URL, timestamps) to your browser's IndexedDB so it appears in the side-panel archive. You can clear all archived chats at any time from the settings page.

Apart from the per-export usage event described in Section 5, none of this data is uploaded to our servers by the Extension itself.

3. Data the Extension does not collect

We do not collect the textual content of your AI conversations through the Extension.
We do not collect your name, email, phone, address, IP, or any other personal information through the Extension.
We do not record your browsing history.
We do not read or store any cookies, passwords, or credentials beyond what is technically required to call the AI site's own conversation API on your behalf (see Section 6).
We do not track which AI sites you visit; we only know that you used the Extension's export action (recorded per export as described in Section 5).

4. Data we store server-side (only when you use the Services)

When you choose to sign in on the Website, or submit a feedback or uninstall form, the Services may receive and store the following. Note: Word, Markdown, JSON, TXT and long-screenshot exports are generated locally in your browser and are never transmitted to us. PDF export is rendered on our server by default — the styled conversation HTML (including images) is sent to our server, rendered to a PDF, and served from a private, hard-to-guess download link. You can switch PDF to local rendering in the extension settings so that nothing is uploaded.

Account record. If you sign in with Google, we store your email address, the Google account identifier (a stable opaque string), your display name and avatar URL from your Google profile, and timestamps for account creation and last update. We never receive your Google password.
Daily PDF count. A counter of how many PDFs you've exported each day, used for capacity planning. The counter is keyed on your user ID and the calendar day in UTC. No payment or quota enforcement is performed against it.
Feedback and uninstall submissions. If you submit a feedback form (or the uninstall survey shown when you remove the Extension), we receive what you type in that form and any screenshot you choose to attach. We do not receive your conversation content through these forms. Word, Markdown, JSON, TXT and long-screenshot exports are generated entirely on your device. For PDF, by default the styled conversation HTML is sent to our server to be rendered (you can switch PDF to local rendering in the extension settings).
Notion connection. Only if you connect Notion: we store your Notion workspace access token and workspace name/ID so the Extension can export to your workspace. When you export a chat to Notion, its content (messages and images) is sent to Notion's API to create pages in your workspace, and inline images embedded in the chat are re-hosted to a public, hard-to-guess URL on our storage so Notion can fetch and display them.

What we do not store: payment information of any kind. SaveAI is completely free to use — every feature and every export format is free and unlimited — so there is nothing to charge for and no card details to store.

Share-link tool (Website): when you paste a public AI share link into the tool at /tools/share-to-pdf/, that URL is sent to our server. Our server fetches the public page, converts it and returns the result within the same request — the conversation itself is not stored. The one exception is PDF output, which has to be written to a file on our server so your browser can download it; that file is deleted automatically after 7 days, like every other PDF we render. We only fetch URLs that match a fixed list of supported sites, and we do not follow links found inside the fetched content.

5. Extension usage statistics (optional)

After a successful export, the Extension sends one usage event to our own server (saveai.one) — never to any third party; the Google Analytics reporting described in earlier versions of this policy has been removed. An event contains: the export format, the action (save or copy), the surface that triggered it (in-page button, preview page or side panel), the chat title (which becomes the exported file's name) and the source site (e.g. chatgpt). As with any web request, our server also receives and stores the request time, your IP address and your browser's user-agent string. If you are signed in, the event is linked to your SaveAI account; otherwise it is stored without one.

We use these events solely to understand which features are used and to improve the product. They contain no conversation content and are never shared with or sold to anyone.

You can turn this reporting off at any time in the Extension's options (Settings → General → Usage statistics); when disabled, nothing is sent. On Firefox, the browser's own data-collection consent applies in addition. A local-only daily counter shown in the popup always stays on your device.

6. Communicating with supported AI sites

When you trigger an export on a supported AI site (ChatGPT, Claude, Gemini, NotebookLM, AI Studio, Grok, Perplexity, DeepSeek, Kimi, Microsoft Copilot, GitHub, Tencent Yuanbao, Doubao, Qwen), the Extension's content script reads the conversation directly from that site — either by reading the rendered page or by calling the site's own conversation API while you are signed in. The session cookie used for these requests is your own cookie that already exists in your browser; the Extension does not transmit it anywhere outside that AI site.

Word, Markdown, JSON, TXT and long-screenshot exports are generated entirely on your device. PDF export is rendered on our server by default: the styled conversation HTML (including images) is uploaded to our server, rendered to a PDF by headless Chromium, and served from a private, hard-to-guess download link. You can switch PDF to a local engine (produced in the browser with jsPDF) in the extension settings, in which case no conversation HTML is uploaded.

7. Cookies on the Website

The Website sets the following cookies when you sign in:

Authentication cookie — an HTTP-only, Secure, SameSite cookie holding a signed token that proves you are signed in. Lifetime: 30 days; refreshed on each request. Scope: the www.saveai.one domain.
OAuth state cookie — a short-lived cookie holding a CSRF token used during the Google sign-in flow; discarded immediately after sign-in.

The Website does not use third-party advertising cookies or cross-site tracking pixels. We do not embed Facebook pixels, TikTok pixels, or comparable trackers.

8. Third-party services

Google OAuth — when you sign in. We receive your email, name, avatar URL, and a stable Google account identifier. Governed by Google's privacy policy.
Notion — only if you connect it. What you export is sent to your own Notion workspace via Notion's official API, and images from your export are re-hosted from our storage so Notion can display them. Governed by Notion's privacy policy.
The supported AI sites themselves — calls go to those sites' own APIs using your browser session.

The Extension does not load remote code, contact any other servers, or embed third-party trackers in the popup, side panel, options page, or preview page.

9. International data transfer

Our servers are hosted in Tokyo, Japan. If you access the Services from another country, your data will be transferred to and processed in Japan. By using the Services you consent to this transfer.

10. Children's privacy

SaveAI is not directed at children under 13 and we do not knowingly collect data from such users. If you believe a child has signed up, contact us and we will delete the account.

11. Your rights

Depending on where you live you may have rights to access, correct, export, or delete the personal data we hold about you. To exercise any of these rights, email us from the address tied to your account; we'll respond within 30 days. The personal data we hold about an account-holder is the short list in Section 4 — so a deletion request is fast to honour.

12. Data retention & deletion

Extension data (settings, archive, client ID) — lives on your device. Uninstall the Extension to delete everything in one step. Archived chats can be wiped from the Extension's options page; retention period is also configurable there (1–60 days).
Account data — kept while the account is open. Email us to close the account and we will delete the account record and daily counters from the production database within seven days.
Notion connection — the stored Notion access token is kept until you disconnect Notion in the Extension (or revoke it in Notion), after which we delete it. Re-hosted export images are kept for as long as your Notion pages need them: Notion links to these images by their URL, so removing them would break the images in pages you already exported — for that reason they are not deleted on a timer, only deduplicated.
Export rendering — Word, Markdown, JSON, TXT and long-screenshot exports are generated locally in your browser, so their content is never sent to our servers. PDF export is rendered on our server by default: the conversation HTML is uploaded only to render the file, and the resulting PDF is stored on our server so you can download it, from a private, hard-to-guess link; switch PDF to local rendering to keep everything on your device. Feedback and uninstall-survey submissions (and any screenshot you attach) are retained only as long as needed to handle the report.

13. Changes to this policy

We may update this policy occasionally. Material changes will be announced in the Chrome Web Store listing and on this page, with the Effective date updated at the top. Continued use after the effective date constitutes acceptance.

14. Contact

Questions about this policy, requests to exercise data rights, or anything else privacy-related:

Email: [email protected]

Contact: reach us via our Feedback page

A bilingual (English + Chinese) version of the Extension-only privacy policy is also distributed with the Extension itself at install time. Where translations differ, this English version controls.