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

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:

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

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.

2. The Chrome extension

3. How we use it, and what we don't do

We use the information above only to:

We don't:

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.

ProviderWhat it doesWhat it handles
AnthropicWrites the rewritesThe 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 JavaScriptOnly the address of a page you add as a source, when our server can't read it. Never your writing.
Voyage AIPicks your most relevant samples and source passagesYour 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.
SupabaseDatabase and sign-inYour email, samples (with their embeddings and labels), usage count and subscription status
Fly.ioHosts our serverRequests passing through, including text being rewritten
VercelHosts this website and the web appStandard web request data
StripePaymentsYour payment details and billing email
ResendSends sign-in codesYour email address
PostHogAnalytics and session recordingsPage 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
SentryError reportsError details, with request contents removed
MetaAd 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.
ImprovMXForwards email to our support inboxMessages 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

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