Nothing is uploaded, and you can verify that yourself.

Disconnect from the internet, then convert an export. The whole conversion completes — inspection, rendering, packaging, download — with no network connection at all.

That is not a trick of caching. It is the only possible behaviour of a program that does its work on your machine, and it is impossible for a program that does not. A tool that needed your conversations on a server could not finish that test, and no amount of reassuring copy on a page like this one can substitute for running it.

Everything below is just a description of why the test passes.

The converter finishes loading before you choose a file. From the moment you drop an export in, parsing, rendering and packaging all happen inside a Web Worker in your own browser — the same place the page you are reading is running.

The converter route carries no third-party scripts. Nothing is loaded from an analytics vendor, an ad network, a font CDN, or a session-recording service, because any one of them would be running code on the page where your conversations are open.

This site has exactly two server endpoints, and it is worth being precise about both:

• A health check. It reports that the site is up. It receives nothing and returns nothing about you.
• A licence check. When you press Unlock, your licence key — and nothing else — goes to our server, which asks Dodo Payments, who issued the key, whether it is still valid. Your export is not part of that request and never has been. Attempts are counted against the requesting IP for a minute at a time so a stranger cannot hammer it.

Exports are not written to localStorage or IndexedDB. They exist in the worker for as long as you are working with them and nowhere else.

The Clear action releases the parsed export and its filename inside the worker and revokes the download URL. Closing or reloading the tab tears the worker down entirely. The only thing intentionally persisted is a licence key you have explicitly validated, so that you do not have to paste it in again.

If you arrive from checkout with a key in the address bar, it is read, saved, and then removed from the URL — a credential sitting in your browser history is a credential in your browser history.

These are the ones nobody asks about and which quietly matter:

• No conversation content in analytics or error reports. Diagnostics are codes, not text. A crash report that helpfully includes the message that caused it is a leak with a friendly name.
• No URL fetching for attachments or images. When an export references a file it does not contain, that gap is recorded rather than filled by reaching out to a remote server — which would tell that server what you are converting and when.
• CSV reports are written to defend against formula injection, so opening the skipped report in a spreadsheet cannot execute anything.

A privacy page that lists only reassurances is marketing. The honest limits:

• Visiting this site is still a visit. The pages are served over the internet, so the host serving them sees the request, as with any website. What it does not see is your export, because your export never goes near it.
• Browser extensions can read any page you open, including this one. If you have granted an extension access to every site, that access includes the tab your conversations are open in. This is a good argument for converting an export in a clean browser profile, and a better one against installing a chat-exporter extension in the first place.
• Once the archive is on your disk, it is a normal folder. It is readable by anything else on that machine and by whatever you sync it to. Choosing where it lands is your decision and we cannot make it for you.
• If you buy, Dodo Payments handles the transaction and sees what a merchant of record sees. They do not receive, and have no route to, anything from your export.