Privacy policy

AI Chat Clipper reads a conversation from an AI chat website and turns it into a document. This page describes every piece of data it touches to do that, where each piece goes, and how long it stays.

The short version: your conversations are converted inside your browser and go only where you send them. There is no AI Chat Clipper account, no server of ours that receives your chats, and no analytics of any kind.

What the extension reads

When you ask for an export — from the toolbar popup, or the button beside a single reply — AI Chat Clipper reads the conversation shown in that tab: the messages, code blocks, tables, formulas and images as they appear on the page.

It reads a page only when you act. It does not run in the background, does not watch pages you are not exporting, and does not read anything on sites outside the list of supported AI services.

What happens to a conversation

The conversation is converted in your browser and then goes to the destination you picked, and nowhere else:

• A file — saved to your computer through the browser's own download mechanism.
• The clipboard — as Markdown or rich text.
• A service you connected — Google Docs or Drive, Word Online, OneNote, Notion, or your own Nextcloud server. The document is sent from your browser directly to that service, using the account you signed in with.

We do not receive a copy in any of these cases. There is no yaiol server in the path between the chat page and your file or your chosen service.

While a conversation is being prepared, it is held in the browser's own extension storage on your device, and it is cleared when the export finishes.

What is stored on your device

All of it lives in your browser profile, under the extension's own storage. None of it is transmitted to us.

• Your settings — interface language, output format, fonts, maths rendering, and which AI sites you show, hide or reorder.
• Connection details for services you chose to link:
  • Microsoft — an access token, a refresh token, and the account name and email address, so Settings can show you which account is connected.
  • Notion — an access token, the workspace name and icon, and the page you selected as the destination.
  • Nextcloud — your server address, your username, and the app password you created for the extension.
  • Google — handled by Chrome itself through the browser's identity service; the extension asks Chrome for a token when it needs one.
• A short-lived technical value for Google NotebookLM. NotebookLM does not expose its conversation in a readable form, so exporting from it requires two per-session identifiers that the page sends to its own servers. The extension observes only that one address, keeps the values in memory for that tab, and never stores or transmits their content anywhere else.

You can remove all of it at any time: disconnect a service in Settings to delete its stored credentials, or uninstall the extension to delete everything at once.

What is stored on our server

Nothing.

There is no AI Chat Clipper account, no database of ours, and no server of ours that your conversations, your exported documents, your tokens or your settings ever reach. If you asked us for a copy of your data, we could not produce one — none exists.

One qualification, so that "nothing" is exact: the Notion sign-in described below passes through a small endpoint of ours, and that endpoint keeps nothing it handles. If a sign-in fails, it records a diagnostic line containing the error Notion returned — never a token, and never anything from a conversation.

The one thing that passes through our server

Connecting Notion — and only Notion — involves one request to api.yaiol.com.

Notion's sign-in requires a secret that identifies the application. A browser extension cannot hold such a secret safely, because anyone can read the code of an installed extension. So the final step of the Notion sign-in is completed by a small endpoint of ours, which holds that secret, exchanges your one-time sign-in code with Notion, and returns the result to your browser.

This is what Notion itself requires. Its authorization guide specifies that the exchange is authorised with the connection's client ID and secret, and says those values "should be protected and should never be included in source code or version control" — which is precisely what putting them inside a browser extension would do. See Notion's authorization guide.

That endpoint stores nothing. It keeps no token, no account details and no record of a successful sign-in; it writes a log line only when the exchange fails, containing the error returned by Notion. Google, Microsoft and Nextcloud sign-ins do not involve our server at all.

What we never do

• We do not collect, receive or store your conversations.
• We do not use analytics, telemetry, tracking, advertising or fingerprinting of any kind. The extension makes no measurement requests.
• We do not sell or transfer your data to third parties, and we do not use it for anything unrelated to exporting your conversations.
• There is no AI Chat Clipper account and no sign-up.

Children

AI Chat Clipper is a document tool for general audiences. It is not directed at children and collects nothing about age.

Changes to this policy

If the way the extension handles data changes, this page changes with it, and the date below is updated. Material changes will also be described in the release notes.

Contact

Questions about this policy, or about anything on this page: privacy@yaiol.com

Last updated: 2026-08-12