Privacy Policy
Last updated: October 16, 2026 (edits that use a document's sources, and reading pages that need JavaScript)
Thirdraft ("we", "us") is a Chrome extension and web app that rewrites text in your own writing voice. To do that it has to read your writing, so this policy sets out exactly what we collect, where it goes, and how to delete it. It covers the extension, the web app at thirdraft.com/app, and this website.
1. What we collect
Your account
- Email address, used to sign in (with a one-time code or with Google) and to contact you about your account.
- Signing in with Google. Google shares your email address, name and profile picture with our sign-in provider (Supabase). We use only the email address.
- Guest sessions. If you use the web app without signing in, we may create an anonymous session with no email attached, only so your free rewrites can be counted.
Your writing samples
Samples are pieces of your own writing that Thirdraft learns your voice from. If you're signed in, they're saved to your account so the same voice works in the extension and on the web. A sample is saved when you:
- paste or upload writing as a sample;
- import documents from Google Docs or pages from Confluence (see below);
- accept a rewrite (the accepted text becomes a new sample); or
- turn on Learn from my Gmail. This is off by default and asks for Chrome's permission first. When it's on, the extension saves the text of emails you send, from your Sent mail. It skips messages from other people in the same thread.
If you use the web app without an account, your samples stay in that browser tab and are gone when you refresh. We don't store them. If you then sign in with Google, the tab holds them for the trip to Google and back, so they can move into your new account.
Importing from Google Docs
On the website you can import writing samples from Google Docs. Google asks you to allow Thirdraft to see "only the specific Google Drive files you use with this app," then shows Google's own file picker. Thirdraft can read only the documents you pick there, nothing else in your Drive. Your browser downloads each picked document as plain text and splits it into samples, which are saved to your account like any sample you paste. The Google access token stays in your browser: it's never sent to our server, and we don't keep ongoing access. We don't store document names or anything else from your Drive.
Thirdraft's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Text imported from Google Docs is used only to learn your voice for your own rewrites. It is never used to train AI models, never shown to anyone else, and never used for advertising. You can delete imported samples at any time, and you can remove Thirdraft's access in your Google Account settings.
Importing from Confluence
If you're signed in, you can import writing samples from Confluence. Atlassian asks you to let Thirdraft search and read Confluence content you can see. Our server then lists the pages you created (titles and spaces only) so you can choose which to import, and reads only the pages you tick. Their text is split into samples and saved to your account like any sample you paste; images, code blocks and other embedded content are left out. The access Atlassian gives us is held in our server's memory for at most 10 minutes and thrown away after the import. It is never stored in our database or logs, and we don't keep page titles or anything else from Confluence. Imported text is used only to learn your voice for your own rewrites, never to train AI models and never for advertising. You can delete imported samples at any time, and remove Thirdraft's access in your Atlassian account settings (Connected apps).
Documents in the editor
If you use the editor (thirdraft.com/editor), the documents you write or bring in there are saved to your account so you can come back to them. They're kept until you delete them, and deleting a document deletes it from our database. When you edit part of a document, the part you selected, the paragraph before and after it, and your instruction are sent to our AI provider (Anthropic) the same way as a rewrite, and not stored there. Documents are never used to train AI models, and never shown to anyone else.
You can also add sources to a document: text you paste, files you upload, or a web page you link to. A linked page is fetched by our server, which keeps only the page's text and its address. If a page builds its text with JavaScript, so our server finds nothing to read, we send just the page's address (without tracking parameters) to Jina AI's Reader, which loads the page and returns its text. Nothing you've written is sent to Jina AI. Sources are stored with their document and deleted when you remove them or delete the document. So that edits can use your sources, we split each one into passages and send them to Voyage AI to make embeddings (see below), which are stored with the source and deleted with it.
Text you rewrite
When you ask for a rewrite, the text you selected is sent to our server along with your samples. Our server passes it to our AI provider (Anthropic) to write the rewrite and sends the result back to you. We don't store the text you rewrite unless you accept the rewrite, which saves it as a sample. Anthropic's own handling is described in section 4.
Picking your most relevant samples. To choose which of your samples best fit what you're writing, we send each sample you save, and the text you rewrite, to Voyage AI. It turns the text into an embedding: a list of numbers that captures its meaning, without the words themselves. We store the embedding with its sample, along with two labels for the kind of writing and who it's for, picked by Anthropic's model. Deleting a sample deletes its embedding and labels. Voyage AI doesn't use your writing to train models and deletes it as soon as the embedding is made.
AI agents you connect
You can connect an AI agent (such as the Claude app, Claude Code or Cursor) to your account in two ways: by signing in to Thirdraft from the agent and clicking Allow, or with an API key you create under "Connect an agent". When you sign in, our sign-in provider (Supabase) gives that agent an access token for your account; you can disconnect it at any time in the agent's settings. Either way, the agent can send text to Thirdraft for a rewrite in your voice, and add writing samples to your account. Text sent for a rewrite is handled exactly like text you rewrite yourself: sent to Anthropic to write the rewrite, and not stored. Agent rewrites are never saved as samples. Samples an agent adds are labelled "via agent" so you can review and delete them. We store only a scrambled (hashed) copy of each key, and the date it was last used. You can revoke a key at any time, and nothing from agents is sent to Meta.
Payments
Payments are handled by Stripe. We never see or store your card number. We keep your Stripe customer ID, your subscription status, which plan you're on (Personal or Pro) and your renewal date, so we know your plan and limits.
Usage and technical data
- Free-plan usage: a count of how many free rewrites you've used this week.
- Product events: a few events, linked to your account ID and never to your text: a rewrite succeeded, you reached the free limit, you started checkout, and how you rated a rewrite (馃憤 or 馃憥, with an optional reason, and which of your samples it used). We use them to understand how Thirdraft is used.
- Website analytics: page views on thirdraft.com, and whether you joined the waitlist. In the web app, also when you sign up, add samples (how many, and whether you pasted, uploaded, imported from Google Docs or Confluence, or accepted them), how an upload or import ended (for example, finished or cancelled, never file names or document titles) and start a rewrite (the draft's rough length, such as "500 to 2,000 characters", and how many samples you have), never the text itself. Once you sign in, these are linked to your account and its email address. Our analytics tool (PostHog) uses a cookie or browser storage to tell visits apart.
- Session recordings: on our homepage, pricing page and API page, PostHog records how visitors use the page (clicks, scrolling and mouse movement) so we can see where it's confusing. Anything you type, including a draft you paste into the homepage, is masked, so recordings show blocks instead of your words. In the web app, every piece of text on the page is masked too, including your drafts, rewrites and samples, so recordings there show only the layout, clicks and scrolling. Recordings never run on the feedback page, and never in the Chrome extension. You can turn them off with Privacy choices (Opt out), and a Global Privacy Control signal turns them off automatically.
- Error reports: if our server hits an error, a report goes to Sentry. We remove the request contents, which is where your writing would be, before it's sent.
- Server logs: our server logs the type of each request (for example "rewrite") and the site it came from. It never logs your text. Our hosting providers may also record IP addresses as part of running their networks.
- Waitlist: if you joined the launch waitlist before the extension came out, your email address. The waitlist is now closed.
Advertising measurement (Meta)
Unless you opt out, we use Meta Pixel and Meta's Conversions API on thirdraft.com to measure how our ads on Facebook and Instagram perform. We share with Meta that you viewed a page on our website, joined the waitlist, clicked through to our Chrome Web Store listing, created an account on the website, or started a paid plan. With that we send technical data: your IP address, browser type, the page address, and Meta's own cookie identifiers. For account and payment events we also send your email address and account ID, hashed (turned into a code that can't be read back) before they leave our server, and for payments the plan price.
- Never your writing. We never send Meta your samples, the text you rewrite, rewrites, or what we've learned about your writing style.
- You can opt out. Use Privacy choices, at the bottom of every page, and nothing is sent to Meta from that browser, and no session recordings are made. If your browser sends a Global Privacy Control signal, we treat it as an opt-out automatically.
- Never from the Chrome extension. We don't use any data from the extension, or from accounts and payments started in it, for advertising.
2. The Chrome extension
- Reading pages. The extension can run on the pages you visit so that "Rewrite in my voice" works wherever you type. It reads the text you've selected only when you choose to rewrite it, and it writes the rewrite back into the page only when you click Accept. It doesn't record which sites you visit.
- Gmail. Access to mail.google.com is an optional permission, requested only when you turn on Learn from my Gmail. You can turn it off in the extension's settings at any time.
- AI chat sites. The extension never learns from AI chat sites such as ChatGPT or Claude, so it picks up your voice and not a chatbot's.
- Stored in your browser: your sign-in session, a copy of your samples, the style notes generated from them, and your settings. Signing out removes your samples and plan details from that browser.
- Permissions used: storage (the items above), sidePanel (the Thirdraft panel), contextMenus (the right-click "Rewrite in my voice" item), identity (the Google sign-in window), and optional access to mail.google.com.
3. How we use it, and what we don't do
We use the information above only to:
- provide Thirdraft: write rewrites in your voice and keep your samples in your account;
- run your account and subscription;
- answer you when you contact us;
- keep the service reliable and secure, and understand how it's used; and
- meet legal obligations.
We don't:
- sell your data, or share it for advertising beyond the ad measurement described in section 1, which you can opt out of;
- use your writing to train AI models, or allow our providers to;
- show your samples to anyone else; or
- use or transfer your data for any purpose unrelated to Thirdraft, including to determine creditworthiness or for lending.
We follow the Chrome Web Store User Data Policy, including its Limited Use requirements.
4. Service providers
We use these companies to run Thirdraft. Each gets only what it needs for its part of the service.
| Provider | What it does | What it handles |
|---|---|---|
| Anthropic | Writes the rewrites | The text you rewrite and your samples, per request. Anthropic doesn't train on data sent through its API and deletes it within 30 days, unless it's flagged for breaking Anthropic's usage policy. |
| Jina AI (Reader) | Reads linked pages that need JavaScript | Only the address of a page you add as a source, when our server can't read it. Never your writing. |
| Voyage AI | Picks your most relevant samples and source passages | Your samples, the text you rewrite or edit, and your documents' sources, per request, to make embeddings. Voyage AI doesn't train on this data and deletes it once the embedding is made. |
| Supabase | Database and sign-in | Your email, samples (with their embeddings and labels), usage count and subscription status |
| Fly.io | Hosts our server | Requests passing through, including text being rewritten |
| Vercel | Hosts this website and the web app | Standard web request data |
| Stripe | Payments | Your payment details and billing email |
| Resend | Sends sign-in codes | Your email address |
| PostHog | Analytics and session recordings | Page views, the product events above, and session recordings on our homepage, pricing and API pages (typing masked) and in the web app (all text masked); your account id and email once you sign in |
| Sentry | Error reports | Error details, with request contents removed |
| Meta | Ad measurement (unless you opt out) | Page views and the events in section 1, your IP address and browser details, Meta cookie IDs, and for account and payment events your hashed email and account ID. Never your writing. |
| ImprovMX | Forwards email to our support inbox | Messages you send us |
We may also disclose information if the law requires it, or as part of a merger or sale of Thirdraft. In a sale, this policy would continue to apply to your data.
5. Keeping and deleting your data
- Samples stay in your account until you delete them. You can delete one, all samples from Gmail, or all of them at once, from the extension's settings or the web app. Deleting removes them from your account, not just from that device.
- Your whole account: email support@thirdraft.com from the address you sign in with. We'll delete your account, samples and usage data within 30 days. Records we're legally required to keep, such as payment records held by Stripe, are the exception.
- Text you rewrite isn't stored by us at all (see section 1).
6. Your rights
Depending on where you live, including under the GDPR and California's CCPA, you may have the right to access, correct, delete or export your personal data, and to object to or restrict how we use it. Email support@thirdraft.com and we'll respond within 30 days. We won't treat you differently for using these rights.
Do not sell or share my personal information. We don't sell personal data. Sharing with Meta for ad measurement counts as "sharing" under some US state laws. To opt out, use Privacy choices and choose Opt out, turn on Global Privacy Control in your browser, or email us. You can also manage ads in your Facebook and Instagram settings.
7. Security
Data travels over HTTPS. Your samples and account data sit in a database that only our server can reach, and every request is limited to your own account. The keys to our AI provider, database and payments live only on our server, never in the extension or the website. No system is perfectly secure, but we'll tell you promptly if a breach affects your data.
8. International users
Thirdraft is run from the United States, and our providers process data in the United States and other countries. By using Thirdraft, you understand your data will be processed there.
9. Children
Thirdraft isn't meant for children under 13, and we don't knowingly collect their data. If you think a child has given us personal information, contact us and we'll delete it.
10. Changes to this policy
If we change this policy, we'll update the date at the top. If a change is significant, we'll also email account holders before it takes effect.
11. Contact
Questions or requests: support@thirdraft.com