Privacy Policy
Last updated: 5 November 2026
1. Who this policy applies to
This policy covers the AI Chat Archive browser extension (the "Extension") and the website at aichatarchive.app (the "Site"). We refer to both collectively as "the Service."
2. What the Extension collects from you
Nothing. The Extension does not transmit your conversations, attachments, exported files, or any content derived from them to any server we control. There is no analytics SDK, no error reporting, no usage telemetry, and no remote logging.
All export processing — reading conversations via claude.ai's API, rendering Markdown/HTML/PDF/JSON/TXT, bundling attachment bytes, zipping batch exports — happens locally in your browser.
3. Network requests the Extension makes
The Extension's network requests fall into the groups below: the chat providers' own APIs, file and image download hosts supplied by those providers, and Polar for license validation.
3.1 claude.ai
When you click an export action, the Extension reads your existing conversation(s) from claude.ai using the same session cookie your browser already uses to sign you in. This is the same API that Claude's own web app uses. We never see these requests or their responses — they go directly from your browser to Anthropic.
3.2 chatgpt.com
When you export a ChatGPT conversation, the Extension reads it from chatgpt.com the same way: using the session your browser is already logged into there. As with Claude, the conversation goes directly from that site to your browser — we never see it.
3.3 Provider-supplied file and image download hosts
Exports that include attachments or embedded images — including free single-chat exports that embed images in the HTML or PDF — also fetch the file and image bytes themselves. With Claude, those bytes come from Claude's own API and asset endpoints, requested with the same existing session the rest of the export uses (your browser sends its regular claude.ai cookie). ChatGPT reads files the same way from its own API, and may additionally respond with temporary signed download URLs on storage or CDN infrastructure the provider chooses; the Extension fetches those URLs without credentials, because the signature already authorizes the download. Either way the host is operated by the provider, can differ from file to file, and is not operated by us: the bytes travel from the provider to your browser and nowhere else.
3.4 api.polar.sh
When you activate a paid license, the Extension verifies your key against Polar's license API. Only the key string is sent — no conversation content, file content, or identifying information about you is included. The validation result is cached for a week, after which the Extension quietly revalidates the key; if the network is unavailable, paid features keep working through a grace window. We use Polar solely to issue and validate license keys; see Polar's privacy policy for their practices.
The Extension's manifest declares privileged host permissions for only three origins — claude.ai, chatgpt.com, and api.polar.sh. Those permissions are not a complete list of every host the Extension can fetch from, and they are not a firewall: just like an ordinary web page, the Extension's content scripts can make requests to other hosts when those hosts permit cross-origin access (CORS), which is how the file and image downloads described in section 3.3, including ChatGPT's signed URLs, reach the provider-chosen hosts. What the architecture guarantees is narrower and stronger than a host list: there is no AI Chat Archive server anywhere in these flows, and your chat content is never uploaded to us.
4. Storage on your device
The Extension stores your settings and license state using Chrome's chrome.storage.sync API:
- Your settings (export format preference, timestamp style, etc.)
- Your license key and its last validation result, if you have one
chrome.storage.sync is managed by Google's extension infrastructure. If you are signed into Chrome, this data is synchronized across devices via your Google account. We do not have access to this data. See Google's privacy policy for how they handle synced extension storage.
The Extension also uses chrome.storage.local for temporary export data. It never leaves your device:
- PDF hand-off payloads. For a PDF export, the full conversation is passed from the chat tab to the Extension's print page through a local storage key. The print page removes the payload from storage as soon as it has received it, before rendering. If an export is abandoned partway — for example because the tab closed — the leftover payload becomes eligible for removal after 15 minutes without activity and is swept the next time a PDF export starts.
- Export-resume checkpoints. Long batch and project exports save progress so an interrupted run can resume instead of starting over. The checkpoint is cleared when the export finishes. A checkpoint older than two weeks is removed the next time that export's progress is checked; there is no background timer, so an export you never resume again can leave its checkpoint beyond that point.
5. The Site (aichatarchive.app)
The Site is a static landing page hosted on Cloudflare. It does not set tracking cookies and does not load third-party fonts. To count visits, the Site uses Cloudflare Web Analytics: a small cookieless script (from static.cloudflareinsights.com) that reports aggregate visit statistics — pages viewed, referrer, browser and device type, country, and page-load timing — without cookies, fingerprinting, or any cross-site identifier. We see totals, never individual visitors. If you visit the Site, Cloudflare may also record standard server-log metadata (IP address, timestamp, User-Agent) for abuse prevention. All of this concerns the website only. When you use the Extension, your chat content is not uploaded to our servers; beyond the chat providers described in section 3, the only outgoing request is the license check to Polar, which sends your key alone.
Some blog posts include a YouTube video. Nothing loads from YouTube until you press play; the preview image is served by the Site. When you press play, the video loads from YouTube’s privacy-enhanced domain (youtube-nocookie.com), and YouTube’s privacy policy applies to that playback.
6. Payments
Purchases of paid features are handled by Polar, our Merchant of Record. When you buy a license, Polar collects your email address, payment details, and any other information required to complete the transaction and issue an invoice. Those details are collected and stored by Polar, not by us. We receive only the minimal information needed to issue your license key (primarily your email address, so we can send you the key). The checkout link also tags which browser the purchase came from (e.g. Chrome, Edge, Firefox, Safari) and whether you reached it through the extension or the website, so we can see which store drives sales; this is coarse, non-identifying information stored by Polar alongside the order, and we never use it to identify you.
For questions about how Polar handles your payment data, see Polar's privacy policy.
7. Account management
We do not operate a user account system. There is no login, no password, no profile. All post-purchase actions — viewing receipts, changing your payment method, canceling a subscription, requesting a refund — are performed through Polar's customer portal. Our Restore Purchase and Manage Purchase pages are static pages that deep-link you to that portal.
8. Third-party services we rely on
- Cloudflare — hosts the Site and its DNS, and provides the Site’s cookieless Web Analytics
- YouTube (Google) — plays the tutorial videos embedded in some blog posts, and only after you press play
- Polar — processes payments and issues license keys
- Google — distributes the Extension (Chrome Web Store) and runs
chrome.storage.sync - Anthropic (claude.ai) — hosts the conversations you choose to export; we interact with it only on your behalf, using your own session
9. Your rights under GDPR / CCPA / similar laws
Because we do not collect or store your personal information, most data-subject rights (access, deletion, portability, correction) don't have any data to act on for the Extension itself. If you want to exercise a right against our records — for example, to delete the email address we received when you purchased a license — contact us at support@aichatarchive.app and we will work with Polar to fulfill your request.
We do not sell or share your personal information within the meaning of the California Consumer Privacy Act (CCPA), the California Privacy Rights Act (CPRA), or any comparable law.
10. International users
AI Chat Archive is available globally. Export processing happens in your browser, and your chat content is not uploaded to our servers. The chat API requests and the file and image downloads described in section 3 are sent to the providers' own systems, whose locations we do not control, so we cannot make guarantees about where that traffic is routed. The only request involving us is license-key validation with Polar, which sends your key alone. Payment data you submit to Polar may be processed in the jurisdictions where Polar operates; see their policy for details.
11. Children's privacy
AI Chat Archive is not directed at children under 13. We do not knowingly collect personal information from children. Because we collect no personal information at all via the Extension, this exposure is minimal.
12. Changes to this policy
We may update this policy as the Service evolves. The "Last updated" date at the top of this page reflects the most recent revision. Material changes (for example, adding a new third-party service) will be announced on the Site and, where appropriate, inside the Extension.
13. Contact
Questions or requests about this policy: support@aichatarchive.app