Privacy policy

• Account information: your email and authentication details (if you set a password, we store only a one-way hash of it, never the password itself), and an optional display name.
• Project content: the voice samples, source material, briefs, positioning answers, and drafts you create.
• Usage data: counts of pieces generated, plan and billing status, and basic technical and log data such as IP address, browser type, and timestamps, used to run and secure the service.
• Payment information: handled by our payment processor. We do not store full card numbers.

We do not ask for and do not want sensitive personal data; please do not paste it into your drafts or sources.

• Provide and operate the service, including generating and revising your drafts.
• Process payments and manage your subscription.
• Provide support and send service messages, such as sign-in links, receipts, and limit notices.
• Secure the service and prevent abuse.
• Improve the service using de-identified, aggregated usage data, never your content in identifiable form.
• Comply with legal obligations.

To generate and revise drafts, your project content is sent to Anthropic, the provider of the AI models that power the service, and processed to return your draft. Under Anthropic’s commercial API terms, this content is not used to train their models. We do not use your content or output to train any model, and we do not sell it.

Spelling, grammar, and style checking runs entirely inside your browser. That text is never sent to a server for checking; it stays on your device.

We do not sell your data. We do not use your writing to train models. We do not share your drafts with other users. We do not publish or claim ownership of what you write.

We use cookies and local storage to keep your session and your work, and PostHog for product analytics, to understand which features are used and where people get stuck. We track behavior (pages visited, features used), never the content you write: screen recording is turned off, and your drafts and briefs are never sent to analytics. We also use Meta’s advertising tools (the Meta pixel and Conversions API) to measure our ads and reach people who have visited unwrite; they receive technical signals and, when you take certain actions (signing up, starting checkout, generating your first piece, or subscribing), a hashed (irreversible) email or account id, never your writing. We also use Google Ads conversion measurement to see how our ads perform; it receives only technical conversion signals when you take those same actions, never your writing and no email or account id. We also use LinkedIn’s advertising tools (the LinkedIn Insight Tag) to measure our ads and reach people who have visited unwrite; it receives only technical signals, never your writing and no email or account id. All of this honors your choice: it does not run if you decline in the cookie notice, or if you enable “Do Not Track” or Global Privacy Control in your browser, which we honor. You can change your answer any time with “Cookie choices”, at the foot of this site and in Settings in the Studio; saying no stops the tags already running on the page. You can also email hello@unwrite.ai.

When you are signed in, your projects and voice profiles are stored in a hosted database (Neon, a managed Postgres service in a United States region) so you can sign in from anywhere, and are also cached in your browser’s local storage for speed. If you use unwrite without signing in, your work lives only in your browser’s local storage on that device until you create an account, at which point it is moved to your account. When you enter your email to create an account, the piece you are setting up is also saved to our database, keyed to that email, so it can be attached to your new account even if you finish signing up in a different browser or on another device. If you never finish signing up, that saved setup is deleted automatically within about three days.

We use a small set of vendors to operate, each receiving only what it needs to do its job:

• Anthropic, for AI processing.
• A cloud host (Vercel), for running the application.
• A database provider (Neon), for stored projects and account data.
• A code host (GitHub), for storing our encrypted nightly backups of that database, so the service can be recovered if the database is ever lost. The backups are encrypted before they leave our systems and are deleted after 90 days.
• A payment processor (Stripe), for subscriptions.
• An email provider (Resend), for sign-in links and receipts.
• An email-marketing provider (MailerLite), for the product-update and tips emails. Your email address is sent there to keep that list accurate, including when you turn those emails off or change plan, so it can hold a record that you are not to be emailed. Deleting your account erases it there.
• An authentication provider (Google), for signing in with a Google account.
• A rate-limiting service (Upstash), for protecting the service from abuse.
• Product analytics (PostHog), for understanding feature usage. Behavior only, never your writing.
• Advertising measurement (Meta / Facebook), for measuring our ads and reaching people who have visited unwrite. Technical signals, plus a hashed (irreversible) email or account id when you take certain actions (signing up, starting checkout, generating your first piece, or subscribing), never your writing; gated by your decline / Do Not Track choice.
• Advertising measurement (Google Ads), for measuring how our ads perform. Technical conversion signals only, never your writing and no email or account id; gated by your decline / Do Not Track choice.
• Advertising measurement (LinkedIn), for measuring our ads and reaching people who have visited unwrite. Technical signals only, never your writing and no email or account id; gated by your decline / Do Not Track choice.
• Error monitoring (Sentry), for capturing and fixing crashes.
• Team messaging (Slack), for routing support messages and waitlist signups to our team in real time. Only what you put in those forms; never your writing.

We share personal data only with the service providers above, when required by law or to protect rights and safety, and in connection with a business transfer such as a merger or acquisition, in which case this policy continues to apply. We never sell your personal data.

We keep your information for as long as your account is active or as needed to provide the service, then delete or de-identify it, except where the law requires longer retention, for example billing records.

When you delete your account, it is erased from our live database at once, including the notes, suggested edits, comments and locked passages on your pieces. What you shared with a team stays with the team: shared voices, saved setups and workspaces pass to one of its admins (if it has no other admin, they are erased too). Your pieces do not stay, even those filed in a shared workspace: they are erased with your account. Your reviews and comments on teammates’ pieces stay on those pieces. So do folders you made in a workspace a teammate shared, and passages you locked on pieces that have since moved to a teammate. We also keep encrypted backups of the database so the service can be recovered after an outage, and a deleted account can remain in those backups until they are deleted: our nightly backups are deleted after 90 days. Backups are used only for recovery. If we ever restore one, we first erase again every account deleted after that backup was taken. To make that possible we keep a minimal record of each deletion: the old account id, a one-way hash of the email address (never the address itself), and the time. Separately, when our staff act on an account, for example setting up a plan or deleting the account at your request, our internal audit log keeps a record of that action that identifies the account. For a deletion or reset, a move to the Free plan, an edit to a team’s size, name or reviewer limit, or credits granted to an email address, the record also includes the account’s email address.

Our providers may process data in the United States and other countries. Where required, we rely on appropriate safeguards for international data transfers.

We use reasonable technical and organizational measures to protect your information. No method of transmission or storage is perfectly secure, so we cannot guarantee absolute security.

Depending on where you live, you may have rights to access, correct, export, delete, or restrict the use of your personal data, and to object to certain processing. To exercise any of these, email hello@unwrite.ai.

EU and UK (GDPR): we process personal data on the lawful bases of performing our contract with you, your consent, our legitimate interests in operating and securing the service, and compliance with law. You may withdraw consent and lodge a complaint with your supervisory authority.

California (CCPA/CPRA): we do not sell or share your personal data as those terms are defined. You have the right to know what we collect, to delete it, to correct it, and not to be treated differently for exercising these rights.

unwrite is not directed to children under 13, or the minimum age in your country, and we do not knowingly collect their data.

If this policy changes in a way that affects how your work is handled, we will update the date above and, for material changes, notify account holders by email.

Questions about this policy, or a request to access, correct, export, or delete your data, can be sent to hello@unwrite.ai, or by mail to:

unwrite, Inc.
1111 Oakfield Dr, Ste 115 PMB 2880
Brandon, FL 33511
ATTN: C. Orlando