Privacy Policy — Chat History Exporter

Last updated: 28 August 2026

Chat History Exporter does not collect, transmit, or store your data on any server. Everything it does happens inside your own browser, on your own computer. There is no account, no analytics, no telemetry, and no backend.

What the extension accesses

When you are on teams.live.com or teams.microsoft.com and you click Export, the extension reads the conversation that is already displayed on the page — sender names, message text, timestamps, and the names of shared files — and assembles them into a file.

It does not access any other website. It cannot run on any other website.

What it does with that data

It writes the assembled conversation to a file in your computer's Downloads folder, in the format you chose (JSON, HTML, or plain text). That file belongs to you and stays on your machine.

The extension makes no network requests of its own. It has no ability to send your conversation anywhere: it contains no code that opens a network connection, and it requests no permission that would allow one. It requests two Chrome permissions, downloads and offscreen, and neither of them permits a network connection. Both are explained in the table below.

What it stores

Two small bookmarks per conversation, in your browser's local storage for the Teams site, so that a repeat export can collect only what is new instead of starting over:

A watermark — one number, the identifier Teams gave the newest message your last export reached.
A resume bookmark — the date of the oldest message that export reached, the identifier of its newest message, the conversation's name with everything but letters and digits removed, and the time it was written.

Both are named after the same stripped-down conversation name, so that name appears in your own browser's storage. Neither holds message text, sender names, file links or sign-in tokens, and neither ever leaves your computer. You can clear both at any time by clearing site data for Teams; the only effect is that the next export starts from the beginning.

What it sends to us

Nothing. There is no "us" in a technical sense — no server, no database, no collection endpoint. The authors of this extension never see your conversations, and could not see them even if they wanted to.

Your responsibility for the exported file

The file the extension creates contains the full conversation, including anything the other participants wrote and the names of any files they shared. Treat it with the same care as the conversation itself: store it somewhere appropriate, and do not share it more widely than the participants would expect.

Permissions, explained

Permission	Why it is needed
`downloads`	To save the export file. A long conversation is saved in numbered parts, and without this permission Chrome blocks repeated saves from a page. It is also used to confirm the final file was written and to remove the extension's own part-files afterwards; it never touches a download the extension did not create.
`offscreen`	To turn the assembled text into a saveable file. The background worker Chrome gives an extension has no document of its own, so it cannot create the link a download needs. The extension opens a hidden, empty page solely to create that link, hands it to the download, and discards it. That page has no network access and receives nothing but the text being saved.
Access to `teams.live.com` and `teams.microsoft.com`	To read the conversation you asked to export. These are the only sites the extension is allowed to run on.

No other permission is requested.

Changes

If this policy changes, the updated version will be published at this same address, with a new date at the top.

Contact

Questions about this policy can be directed to the extension's publisher through the Chrome Web Store listing.