Privacy policy

This policy explains what data HumanizeWord collects, why we need it, and how to delete it. HumanizeWord, the operator of humanizeword.com, decides why and how this data is used.

What we collect

• Account: your email address, name, and the IP address used at signup. Google sign-in can also provide an avatar URL. We never receive your Google password. If you set a password, we store a hash of it, not the password itself.
• Rewrites: the draft you submit and the rewrite, so you can review them later.
• AI checks: the text of a check is used to produce the reading and is not saved as a document. The on-screen report expires after about an hour. The charge is kept in your billing history.
• Usage and billing: word and token counts, model costs, your charges, deposits, and transaction records.
• Sessions: your browser information and IP address, used to manage sign-ins and detect stolen credentials.
• 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

A rewrite is sent to third-party model providers through OpenRouter so they can produce the result. We do not use your text to train our own models. Those providers process the prompt under their own terms. 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.

An AI check runs on our systems. The text is held only long enough to produce the reading, and it is not sent to OpenRouter.

Who else processes data

Account and text data for the hosted service is stored in the United States, using managed PostgreSQL and Redis.

• OpenRouter and the model providers it routes a rewrite to. They receive the text of that rewrite. They do not receive AI checks.
• Google, when you use Google sign-in.
• Resend, the email provider for the hosted service. It receives your email address and the message, such as a verification or password-reset link.
• CryptAPI, for deposits. It sees a blockchain address and transaction, not your identity or your text.
• Error tracking, when it is turned on. It receives stack traces and request identifiers, not document text.

Cookies

We use cookies needed for sign-in: a short-lived access cookie, a rotating refresh cookie limited to authentication requests, a CSRF security cookie, and a non-sensitive cookie that indicates a session exists. This avoids sending the refresh token on every request. We use no analytics or advertising cookies.

How long we keep data

• Drafts and rewrites: until you delete them, or for 30 days, whichever comes first. Delete one draft and rewrite from its history page, or delete all saved text from Settings. The usage and billing record for that rewrite stays.
• AI checks: the text is not stored. The report expires after about an hour. The charge remains in billing.
• Billing records: kept after text deletion for as long as accounting obligations require. Corrections are added as new entries. Previous entries are not changed.
• Sessions: until expiry or sign-out. Expired sessions are deleted.

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 your request. There is no control in the app to delete an account. Billing records, and the account details needed to explain them, remain after text is deleted.

Security

Traffic is encrypted in transit. Each user’s model-provider credentials are encrypted at rest. Sessions use rotating refresh tokens. Reusing an old token ends the session because the token may have been stolen. API keys are stored as hashes, so each new key is shown only once.

Children

You must be at least 16 to create an account. We do not verify age. If we learn that we have collected personal data from someone under 16, we will delete it.

Changes

Material changes will be announced in the app before they take effect.

Contact

[email protected]