HumanizeWordPrivacy policy
Last updated 1 October 2026
Draft, pending legal review.
HumanizeWord is pre-launch. The operating entity and governing jurisdiction are not yet settled, and both are left explicit below rather than filled in with something untrue. This page accurately describes how the service behaves today; the legal framing around it is not final.
This describes what HumanizeWord collects, why, and how to get rid of it. The short version: we hold your email, your text, and your billing history.
Who is responsible
[Data controller and jurisdiction to be confirmed.] This determines which data-protection law governs the rest of this page, so we have left it explicit rather than guessing.
What we collect
- Account: your email address, name and avatar URL, from Google when you sign in. We never receive your Google password.
- Your text: what you submit and what we return, stored so you can read your own runs.
- Usage and billing: word counts, token counts, what each run cost us, what you were charged, deposits and ledger entries.
- Sessions: a session record with user agent and IP, used to let you sign out of a device and to spot credential theft.
- Operational logs: request metadata and errors. We exclude document text from logs.
We do not use advertising trackers and we do not sell personal data.
Your text
Rewriting sends the text you submit out for processing and returns a rewrite. Do not submit text you would not want processed that way. If the content is confidential, regulated, or contains other people's personal data, this service is not an appropriate place for it.
Other processors
- Cloud hosting and managed PostgreSQL, Redis and object storage.
- Google, for sign-in.
- CryptAPI, for deposits. It sees a blockchain address and transaction, not your identity or your text.
- An error-tracking service, which receives stack traces and request ids.
Cookies
Only what signing in requires: a short-lived access cookie, a longer-lived rotating refresh cookie scoped to the auth path, a CSRF cookie, and a non-sensitive hint cookie so the app knows a session exists without sending the refresh token on every request. No analytics or advertising cookies.
How long we keep things
- Run text: until you delete it. Delete any single run, or all of them, from Settings.
- Billing records: kept after text deletion, and retained for as long as accounting obligations require. Our ledger is append-only: entries are corrected by compensating entries, never rewritten.
- Sessions: until expiry or sign-out.
Your rights
Depending on where you live you may have rights to access, correct, export or erase your personal data, and to object to processing. Email [email protected] and we will act on it. Note the one limit above: we keep billing records after erasing text, because we are required to account for payments received.
Security
Traffic is encrypted in transit. Per-user inference credentials are encrypted at rest with AES-GCM. Sessions use rotating refresh tokens, and reuse of a rotated token invalidates the whole session on the assumption it leaked. API keys are stored only as hashes, which is why a new key is shown exactly once.
Children
The service is not intended for anyone under 16, and we do not knowingly collect their data.
Changes
Material changes will be announced in the app before they take effect.