---
title: "Privacy and permissions"
description: "What each Chrome permission of Chat to Markdown is for, what stays on your computer, what reaches our server, and how to turn off usage events."
url: https://chattomarkdown.com/docs/1.0.0/privacy/
version: "1.0.0"
updated: 2026-11-04
---

# Privacy and permissions

> Your chats are read in your browser and written to your own folder; they never reach our server. Installing asks for no chat site: Chrome asks for each site when you turn its service on. Our server knows your email and plan only if you sign in for Pro, and a few anonymous usage events, which you can turn off in Settings → What to save.

Chat to Markdown works inside your browser. It reads your chats with the sign-in you already have on each chat site and writes them to a folder on your computer. This page explains every permission it asks Chrome for, what stays on your computer, and the few things that leave it. The full legal text is the [privacy policy](https://chattomarkdown.com/privacy/).

## What never leaves your computer

- **Your chats and their files.** Each chat is written as a Markdown file in the folder you chose, with its pictures and uploads next to it. They are never sent to us.
- **Earlier versions of each chat**, kept in a hidden `.chattomarkdown` folder inside your folder.
- **The list of saved chats**: chat ids, titles, file paths and update times, kept in the extension's storage in your browser so it knows what changed.
- **Your settings**, and Chrome's permission to write to your folder.
- **The sync log.** It says "Kept on this computer only" at its bottom. It leaves only if you copy or download it yourself.

The extension needs no password and no API key for any chat service. It never sees your chat passwords.

## Permissions Chrome asks for

### When you install

Installing asks for these permissions and for no chat site:

| Permission | What it is for |
|---|---|
| `storage` | Your settings, the list of saved chats and the sync state, in your browser. |
| `alarms` | Checking for new chats on your schedule, and refreshing your plan now and then. |
| `scripting` | When a chat site blocks a request from the background, asking again from inside an open tab of that site, the way the site's own page does. |
| `offscreen` | Writing files: the folder you chose is held by a small hidden page of the extension. |
| `identity` | Signing in with Google, and Google Drive once you connect it. |
| `webRequest` | Read only, and only on sites you allowed: the header Microsoft Copilot's page sends to its media service, so your Copilot uploads can be downloaded. |
| chattomarkdown.com | Noticing the "payment complete" page after you buy Pro, to turn Pro on at once. |

### When you turn a service on

Every chat service is off until you turn it on in the welcome page, the popup or **Settings → Chat services**. At that moment Chrome asks you to allow its site, together with the addresses where it keeps your pictures and uploads:

| Service | Chrome asks for |
|---|---|
| ChatGPT | chatgpt.com and OpenAI's file storage (oaiusercontent.com) |
| Claude | claude.ai, and claudeusercontent.com where its artifacts run |
| Perplexity | perplexity.ai and its file storage |
| Gemini | gemini.google.com and Google's image hosts (lh3.googleusercontent.com, lh3.google.com) |
| Microsoft Copilot | copilot.com and copilot.cloud.microsoft, its media service (asm.skype.com, or Teams' gateway for some work accounts) and designerapp.officeapps.live.com for pictures it made |
| Grok | grok.com, assets.grok.com and imagine-public.x.ai |
| DeepSeek | chat.deepseek.com and files.deepseeksvc.com |
| GitHub Copilot | github.com and Copilot's API hosts (api.individual, api.business and api.enterprise.githubcopilot.com), plus the hosts its uploads come from |

If you click **Deny**, the service stays off. Sometimes a service is on but its pictures need one more host; the popup and Settings then say **Pictures aren't saved yet** with a link to allow it.

> [!NOTE]
> Chrome can't allow just part of a site. For GitHub Copilot the permission covers all of github.com, but the Save button appears only on github.com/copilot.

### When you connect Notion, Google Drive or GitHub

Each asks for one more address when you connect it in Settings: api.notion.com, www.googleapis.com or api.github.com. Chats go from your browser straight there, never through our server.

- **Notion**: the API token you paste stays in the extension's storage and is sent only to Notion. The connection sees only the pages you give it.
- **Google Drive**: Google asks you to allow the `drive.file` permission, which lets the extension see only the files it made, nothing else in your Drive.
- **GitHub**: the token you paste stays in the extension's storage and is sent only to GitHub. Settings has you make a token that reaches one repository.

### Download as HTML

Saving a chat as an HTML file may ask for the exact sites its pictures come from, so the file can hold them. The extension never asks for all sites at once.

### See or remove what you allowed

Open `chrome://extensions`, click **Details** under Chat to Markdown, and look at **Site access**. If you remove a chat site there, that service turns off by itself. Turning a service off in Settings stops saving from it but doesn't remove Chrome's permission.

## What reaches our server

Our server is at api.chattomarkdown.com. The extension talks to it for these things only:

- **Your account, if you sign in for Pro.** We keep your email (and your name and picture if you use Google), your plan and its billing ids, when you last signed in, and when you first used Pro beyond the Free limit, because refunds depend on it. Free needs no account, so on Free we hold nothing that identifies you.
- **Prices and checkout.** Showing plans and starting a payment. Stripe handles the payment; we never see your card.
- **Usage events**, described below.

Details, retention and the companies that process data for us are in the [privacy policy](https://chattomarkdown.com/privacy/).

## Usage events

To see where people get stuck, the extension tells our server when certain steps happen:

- the welcome page opens, a folder is chosen, a service is turned on (which one), the first sync starts, setup is finished;
- Settings or the plans page opens (and why, for example the Free limit), a plan is clicked, a checkout starts;
- you sign in (with Google or email);
- the import page opens, reads an export, starts and finishes (which service, how many chats and files), and an offer to import a service's export is clicked.

Each event carries a random id made when you installed the extension and, if you are signed in, your account. Events never include chats, chat titles, or folder or file names. They are deleted after 180 days.

### Turn usage events off

1. **Open Settings** from the gear icon in the popup.
2. **Click What to save** in the sidebar and scroll to **Privacy**.
3. **Turn off Share usage events.** Nothing is sent from that moment.

It is on until you turn it off. Turning it off also leaves the random install id out of the page that opens when you uninstall.

## Hide secrets

If you paste API keys, tokens or passwords into chats, turn on **Hide secrets** in **Settings → What to save → Privacy**. Keys are replaced with a label such as `[hidden: OpenAI key]` before a chat is written to a file or copied. It recognises keys from OpenAI, Anthropic, Google, AWS, GitHub, GitLab, Slack and Stripe, private keys, and assignments like `password = …` when the value looks real (not a placeholder like `YOUR_API_KEY`). It also masks them in titles, so they don't end up in file names.

It is off by default and applies to chats saved from then on. Turn it on before your first sync so a secret is never written to disk. Read more in [Choose what to save](https://chattomarkdown.com/docs/1.0.0/what-to-save/).

## Other times data leaves your computer

- **The reader.** When you open a saved chat, pictures that are web links (not saved files) load from where they are hosted. Charts and widgets an AI made load the code libraries they need from public servers. They run in a sealed-off frame with no access to the extension or your files.
- **Report a problem.** This button appears in the popup when saving from a service stops working. It copies a report and opens an email to us with the extension and browser version, your settings, your folder's name and how each service is doing. Never chat titles or content. Nothing is sent until you press Send in your email app.
- **The sync log.** It stays on your computer. If you copy or download it to send to us, note that it contains chat titles and file paths; remove any you don't want to share.
- **Uninstalling.** Chrome opens a short page on our site that asks why. Answering is optional and anonymous. See [Uninstall and remove your data](https://chattomarkdown.com/docs/1.0.0/uninstall/#the-page-that-opens-when-you-uninstall).

## Your choices

- **Delete your account**: Settings → Account and plan → **Delete account**. See [Uninstall and remove your data](https://chattomarkdown.com/docs/1.0.0/uninstall/#delete-your-account).
- **Remove everything the extension keeps in your browser**: uninstall it. Your files stay in your folder.
- **Delete saved files**: they are ordinary files; delete them as you like. Version 1.0.1 adds **Settings → Start over**, which deletes them for you.
- **Questions**: write to us from the [contact page](https://chattomarkdown.com/contact/).

## Questions

### Do my chats go through your servers?

No. The extension reads your chats with the session you already have in this browser and writes them straight to your folder. Our server never receives your chats, their titles or file names.

### Why does Chrome ask for access to chatgpt.com and other sites?

To read your chats there with your own session. Every service is off until you turn it on, and Chrome asks for that site at that moment. The extension can reach only the sites you allowed.

### How do I turn off usage events?

Open Settings → What to save and turn off Share usage events. Nothing is sent from then on.
