Privacy
Last updated 14 September 2026.
This page describes what Sound More Human does with your account details and with the text you paste into it. It describes the software as it is built. Where something depends on how the operator of this deployment has configured it, the page says so rather than reassuring you.
What you give us
An email address and a password. Sign-in is handled by Supabase Auth, which is where the password is stored and checked; Sound More Human keeps your email address on your profile so the billing and support screens can tell accounts apart. Supabase also sends the confirmation and password-reset messages to that address.
Or, instead of a password, a sign-in provider. If you continue with Google, Apple or Microsoft, that company confirms who you are and tells Supabase Auth your email address and an account identifier, and may also send your name and profile picture. Supabase keeps what it receives with your login; Sound More Human copies only the email address onto your profile and does not use the rest. Apple may give a relay address in place of your real one if you ask it to. The provider’s own privacy policy covers what it records about the sign-in.
The text you paste for the rewrite. That is the whole of it — Sound More Human asks for nothing about you beyond an email address and a way to sign in.
Card details are not among them. Paying takes you to a checkout page hosted by Stripe, and the card number is entered there.
What happens to your text
It is sent to an AI model provider. Each rewrite sends your text, along with the rewriting instructions, to the provider that this deployment’s administrator configured. Sound More Human does not attach your email address or your account identifier to that request. What the provider then does with the text is governed by that provider’s own terms, not by this page.
That provider is Anthropic, and the model is Claude Sonnet 5. Your text reaches Anthropic through its API. Anthropic’s Commercial Terms of Service, which cover that kind of access, say Anthropic may not train its models on customer content. Separately, Anthropic’s privacy policy describes content that its systems flag as possibly breaking its usage policy being reviewed and used to improve that detection. So “not trained on” is not the same as “never read by anyone”, and we would rather say so than leave you to discover it.
Those are Anthropic’s commitments rather than ours, they can change without this page changing, and the two documents linked above are what actually govern them. If the answer matters to your work, read them rather than taking our summary for it.
It is stored so your history works. Your submission and the rewrite are saved as a row in our database, readable only by your account: row-level security in Postgres scopes every query to the signed-in user, and there is no policy that would let one account read another’s row. Sound More Human does not encrypt that text itself — it is ordinary text in the database, protected by that access rule and by whatever encryption at rest the database host applies. The one secret this application encrypts on its own is the administrator’s provider API key.
The free trial is not stored. If you try Sound More Human before creating an account, your text is sent to the model provider in the same way, but Sound More Human saves none of it: there is no account to save it under, and the trial writes nothing to our database. The rewrite exists only in your browser tab.
It is never sent to analytics. Autocapture is switched off, so no element you click reports its contents; session recording is off; and every event the app sends is filtered at runtime through a closed list of properties that holds word counts, durations, style names, plan names and error codes. A property carrying text cannot be added to that list without a code change and a failing test.
It is not written to our server logs. The logging helper drops any field named for submitted or rewritten text before a line is written, and the code that handles rewrites logs counts, identifiers and error codes rather than content.
Who handles it
Six services, and what each one actually receives.
- Supabase — database and sign-in
- Your email address, your password (stored and checked by Supabase Auth), and every rewrite you run, with the text you submitted and the text that came back.
- The configured AI model provider — produces the rewrite
- The text you submit and the instruction that accompanies it. Nothing that identifies you is sent with it.
- Stripe — subscription payments
- Your email address and your account identifier, plus the card details you enter on Stripe's own page. Stripe never receives the text you paste.
- PostHog — product analytics
- Event names, the allowlisted properties above, the page addresses you visit, and your account identifier once you are signed in. Its library also records the ordinary technical details of a request — browser, device type, IP address. It never receives your text and never receives your email address. If the operator has not configured PostHog, the app loads none of it and sends nothing.
- Upstash — rate limiting
- Identifiers only: your account identifier and the IP address the request arrived from, counted inside short windows so one account or one address cannot flood the service. For the free trial before signup, the IP address is counted for up to a day and the random trial identifier from your cookie for up to 30 days, so each browser gets one free rewrite. No text is ever sent to it, and counters expire on their own.
- Vercel — hosting
- Requests to the site, which it serves and routes; the server code that talks to everything above runs there.
How long we keep it
Rewrites stay until you delete them. In Settings you can instead have them removed automatically after 7, 30 or 90 days; keeping them is the default, and nothing is deleted unless you choose one of those.
That clean-up is a scheduled job that runs once a night, so it is not instant: a rewrite that has passed the date you set can still exist until the next run. Deleting a rewrite yourself removes the row immediately.
Your controls
- Delete any single saved rewrite from your history.
- Delete your entire history at once.
- Choose automatic deletion after 7, 30 or 90 days, or keep everything.
- Ask for your account to be removed. Sound More Human has no button for this yet, so write to the support address below; deleting the account deletes the rewrites stored under it.
Contact
Questions about any of the above, or a request to delete your account, go to 2259151@betaweb.org. Account deletion is handled by hand rather than by a button, so say clearly that deletion is what you want; a live subscription is cancelled first, and everything tied to the account goes with it.
If this page changes, the date at the top changes with it.