Privacy policy.

The short version: thread. is a browser extension with no server. Your emails never pass through any computer we own. We built it that way on purpose.

This policy explains what data thread. has access to, what it does with that data, and what we don't do. If something is unclear, email hello@usethreademail.com and we'll try to clarify.

What thread. has access to

When thread. is running in Gmail or Outlook, it has access to the following, strictly to do its job:

• Email content currently displayed in your browser. When you click thread., it reads the subject, sender, recipient list, and message text of the email thread you have open. This is used to provide context for drafting replies.
• The OpenAI API key you provide. Stored in your browser's local storage (chrome.storage.local). It never leaves your browser except when used to authenticate requests to OpenAI's API.
• Your voice profile. If you set one up, the writing samples and style answers you enter are stored in your browser's local storage. Never uploaded.
• Saved templates and panel preferences. Templates you save, the position of the panel, and its size. Stored in local storage only.

What thread. transmits

When you hit send in the thread. panel, the following is sent directly from your browser to OpenAI's API (api.openai.com):

• Your prompt (what you typed)
• The email thread context (to help the AI draft accurately)
• Your voice profile, if one is set (to match your writing style)
• Your OpenAI API key (as the authentication header)

That request goes directly from your browser to OpenAI. It does not pass through any server controlled by us, because we do not operate one. OpenAI's handling of this data is governed by their own privacy policy, available at openai.com/policies/privacy-policy.

What thread. does NOT collect

We want to be explicit about this because most software makes the opposite claim.

• No analytics. We don't track how you use thread. — not clicks, not usage patterns, not feature adoption, nothing.
• No telemetry. thread. does not phone home. It makes exactly one kind of network request: to OpenAI's API, with your API key, when you request a draft.
• No accounts. There is no sign-up, no login, no user database.
• No servers. We do not have a backend. There is no computer we operate that could have your data on it, because we never designed one.
• No third parties. We do not integrate with analytics tools, error trackers, marketing platforms, or any third-party service other than OpenAI (which you are explicitly opting into by providing your API key).

Data retention and deletion

All data thread. touches lives in your browser's local storage. If you uninstall the extension, Chrome automatically deletes this storage. You can also manually clear it by going to Chrome's extension settings, finding thread., clicking "Remove," and confirming.

OpenAI may retain the prompts and responses exchanged through their API according to their policy. Check OpenAI's privacy policy for current details on their retention practices.

Required permissions

thread. requests the following browser permissions, each necessary for the specified purpose:

• Access to Gmail URLs (mail.google.com) — required to read and modify the Gmail interface where thread. appears.
• Access to Outlook URLs (outlook.live.com, outlook.office.com, outlook.office365.com, outlook.cloud.microsoft) — required to read and modify the Outlook web interface.
• Access to OpenAI API (api.openai.com) — required to send your prompts and receive AI drafts.
• Storage — required to save your API key, voice profile, templates, and panel position between sessions.

Children

thread. is not directed at children under 13. If you believe a child has provided us with personal information through thread., please contact us at hello@usethreademail.com — though as explained above, thread. does not collect personal information from anyone, including children.

Changes to this policy

If we update this policy, we'll update the "Last updated" date at the top and post the new version on this page. Because thread. has no user accounts, we can't email you about changes — so if you care, check back periodically or bookmark this page.

Your rights

Depending on where you live, you may have rights under privacy laws like GDPR (EU), CCPA (California), or similar frameworks — rights like access, deletion, correction, and portability. Because thread. doesn't collect or store any personal data on any server we operate, these rights are satisfied by default: there's nothing for us to access, delete, correct, or port.

For data OpenAI holds about your API usage, contact OpenAI directly via their privacy contact.