Privacy Policy

Last updated: September 28, 2026

AI Chat Exporter reads AI responses only when you choose to export them. This policy explains what information the extension processes, where it is sent, and how it is stored.

Information We Process

The extension reads and prepares selected conversation content locally in your browser. Depending on the export destination you choose, that content may then be sent to that destination:

• AI chat content — text, images, code blocks, tables, and math from responses on ChatGPT, Gemini, Claude, DeepSeek, and Perplexity that you explicitly choose to export. The extension reads this content from the page and prepares the export in your browser.
• Google account authentication — when you choose Google Drive, Chrome's identity API supplies an OAuth token used to create or update documents in your Drive. The extension requests only the drive.file scope, which limits API access to files created or opened by this extension.
• Notion credentials — if you configure Notion, the integration token and parent page ID you enter are stored in Chrome's local extension storage. The token is used to authenticate the page creation request you initiate.
• Obsidian settings — your optional vault name is stored in Chrome's local extension storage and is used when you choose to open an export in Obsidian.
• Other preferences — your export mode, destination, and recent Google Doc references are stored locally using Chrome's storage API.
• Image data — when an exported response contains images, the extension may request access to the image's source domain, fetch the image, and include it in destinations that support embedded images. Image data is processed for that export and is not stored on a developer-controlled server. The current Notion export does not upload response images.

How We Use Information

Information is used solely to provide the export functionality:

• Read the response or conversation you select on ChatGPT, Gemini, Claude, DeepSeek, or Perplexity.
• Google Drive: create a Google Doc in the extension's export folders, or append content to a document associated with a previous export.
• Notion: send the selected export content and title to the Notion API to create a page under the parent page you configured.
• Obsidian: pass the selected export content to the locally installed Obsidian app using its obsidian:// link handler.
• Local files: download a .docx or .md file to your device. These destinations do not require a Google account.
• Preserve supported formatting such as headings, lists, tables, code blocks, math, and images where supported by the destination. Google Docs exports include source and citation metadata.
• Remember your preferences and recent Google Doc references locally so the extension behaves consistently between sessions.

Permissions Explained

The extension requests the following permissions:

• identity — required for Google OAuth sign-in (only used when exporting to Google Drive).
• storage — required to remember your preferences locally in your browser.
• downloads — required to save exported files to your device when using the local .docx or Markdown .md destinations.
• contextMenus — required to provide the “Export to Docs” right-click command when you select text on a supported AI chat page (ChatGPT, Gemini, Claude, DeepSeek, Perplexity). This menu item does not appear on other websites.
• Access to chatgpt.com, claude.ai, gemini.google.com, chat.deepseek.com, and www.perplexity.ai — required to add export controls and read the response you choose to export.
• Access to googleapis.com and docs.googleapis.com — required to upload documents to Google Drive and to append text to existing Google Docs (used only when Drive is the selected destination).
• Access to api.notion.com — required to create a Notion page when Notion is the selected destination.
• Optional access to image CDN domains — used to fetch images included in an export. Chrome may ask for access to the image's domain when needed. If you decline, the export continues and the image is represented by a placeholder or source reference where supported.

Data Storage & Security

The extension has no developer-controlled backend and does not store exported content on a developer-owned server. Content extraction and document preparation happen in your browser. When you choose a cloud destination, the export is sent directly to that provider's API (Google Drive or Notion). When you choose Obsidian, the content is handed to the locally installed app. Local file exports are downloaded to your device.

The Google OAuth token is managed by Chrome's identity API and used to authenticate requests to Google. It is not sent to the extension developer. You can revoke the extension's Google access at any time by visiting Google Account permissions.

User preferences, the optional Notion integration token, the optional Obsidian vault name, and conversation-to-document mappings are stored locally via Chrome's storage API. The extension does not sync them to a developer-owned server.

Google API Limited Use Disclosure

AI Chat Exporter's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Specifically, the extension uses only the drive.file OAuth scope. Google API data is used solely to create or update documents that you explicitly export, and is not used for advertising or accessed by the extension developer.

Data Sharing

The extension does not sell or rent user data. When you initiate an export, content is transmitted only as needed for the destination and options you selected:

• Google services — when you authorize the extension to create or update a document in your Google Drive.
• Notion — when you choose Notion, the selected content and page title are sent to the Notion API using the integration token you configured.
• The Obsidian app on your device — when you choose Obsidian, the export content is passed to the app through the obsidian:// link handler.
• Image CDN domains — when an export contains images, the extension requests the image from its source domain if you grant the required access.
• Google Forms — if you choose to send feedback or product suggestions, or uninstall the extension, a Google Form may open. Any information you submit there is sent to Google Forms.

Analytics & Tracking

The extension does not include developer-operated analytics, telemetry, error reporting, or usage tracking. Export content leaves your browser only when required by the destination you choose, as described above.

Changes

This policy may be updated if the extension's functionality changes. Significant changes will be reflected in an updated "Last updated" date at the top of this page.

Contact

For questions, bug reports, or feature requests, please use the support tab on the Chrome Web Store listing, or open an issue on the project's GitHub repository at https://github.com/daniel-zeyuli.