Privacy
Draft. Last updated 17 November 2026.
Read to Post turns newsletter issues you choose into LinkedIn post drafts. This page explains what we collect, why, and who processes it.
What we collect
- Account: your email address, and your name and profile picture if you sign in with Google.
- Profile answers: your role, audience, tone, topics and any writing sample you add.
- Newsletters you import: the text of each issue, its title, publication name, sender and date. We do not keep the raw email file, attachments, recipient addresses or tracking links.
- Drafts: the drafts we prepare and any edits you save.
- Usage events: for example that you signed up, ran a draft, copied a draft or started checkout. We use these to run and improve the product.
- Payments: handled by Stripe. We store your Stripe customer and subscription identifiers and your plan status, never your card details.
Who processes it
- Supabase (database and sign-in) and Vercel (hosting).
- Our AI model provider. When you ask for drafts, the selected issue text, your profile answers and any take you add are sent to it to produce the drafts.
- Stripe, for payments.
- Google, if you sign in with Google, and for ad measurement on our public pages only. No ad or analytics script runs on pages that show your newsletters or drafts.
- Cloudflare, for receiving email, once forwarding addresses are enabled.
What we don’t do
- We don’t sell your data.
- We don’t read your inbox. You choose what to import.
- We don’t post anything on your behalf.
Deleting your data
Delete your account in Settings. Your profile, imported newsletters, drafts and usage records are deleted with it. Stripe keeps payment records as required by law.
Contact
Contact details will be added before launch.