Privacy Policy

Last updated: May 12, 2026

This policy explains what data Huminizer collects, why we collect it, how we use it, and how you can exercise your rights. We are committed to minimal data collection and a transparent retention policy.

1. Data We Collect

We collect only what is necessary to operate the Service:

  • Account data: Your email address and an optional display name. Your password is stored as an argon2id hash — we never store your plaintext password, and we cannot recover it.
  • Submitted text: The text you paste into the Service for rewriting, and the rewritten output we return to you.
  • Usage metadata: Timestamps of requests, character counts, model identifiers used for rewriting, detector score estimates, request and retry counts.
  • Billing data: We do not store your card number or banking details. Payment processing is handled by Stripe; we retain only a Stripe customer ID and the amounts charged.
  • Technical logs: Server-side logs with personally-identifying fields redacted or omitted (raw input text, email addresses, and authentication tokens are not written to logs).

2. How We Use Your Data

We use collected data only for the following purposes:

  • To operate the Service: run the humanization pipeline, store your request history, display your credit balance.
  • To prevent abuse: rate limiting, fraud detection, detection of multi-account circumvention.
  • To process payments: passing billing identifiers to Stripe or our backup processor.
  • To send transactional emails: account verification, password reset, purchase receipts, and material policy changes. Sent via Resend.
  • To improve the Service in aggregate: we may analyse anonymised, aggregated usage statistics. We do not train any language model on your submitted text or rewritten output.

3. Data Retention

Submitted text and rewritten output are retained for no more than 30 days from the date of submission. After this window, these fields are either permanently deleted from active storage or irreversibly anonymised. The 30-day default may be shortened in a future product setting that allows you to set your own retention window.

Account metadata (email address, account creation date, credit balance, payment history) is retained until you request deletion or close your account.

Billing records may be retained for up to 7 years where required by law (tax and financial compliance).

4. Your Rights

You have the following rights with respect to your personal data. These rights are available to all users and are specifically required under GDPR Article 17, the UK GDPR, and equivalent privacy laws in Canada, California (CCPA), and other jurisdictions:

  • Right to access: Request a copy of the personal data we hold about you.
  • Right to correction: Request that we correct inaccurate or incomplete data.
  • Right to deletion: Request that we delete your account and your submitted-text data. We will process deletion requests within 30 days. Submitted text and outputs are purged on the standard 30-day schedule regardless.
  • Right to data portability: Request an export of your account information and request history.
  • Right to object: Object to certain uses of your data (e.g., aggregate analysis).

To exercise any of these rights, email [Operator: insert privacy@yourdomain] or use the in-product account deletion endpoint (shipping in a later development phase). We will respond within 30 days.

5. Third-Party Processors

We share data with the following sub-processors only to the extent necessary for the Service to function:

| Processor | Purpose | Data shared | |-----------|---------|-------------| | Stripe | Payment processing | Stripe customer ID, payment amounts. We never receive or store card numbers. | | Paddle | Backup payment processor | Same as Stripe, used only if Stripe is unavailable. | | Resend | Transactional email | Your email address and the content of transactional messages. | | OpenAI | Text rewriting (primary) | Your submitted text is sent to OpenAI's API under a data-processing agreement. OpenAI does not train on inputs under its zero-data-retention API agreement. | | Anthropic | Text rewriting (fallback) | Your submitted text is sent to Anthropic's API under a similar agreement. Anthropic does not train on inputs under its commercial API terms. | | Vercel | Web hosting | Server logs (PII-redacted). | | Neon | Managed Postgres database | All account and request data stored in our database. Neon is SOC 2 Type II certified. | | Modal Labs | AI detector inference | Submitted text may be processed by open-source detector models hosted on Modal. No persistent storage by Modal. | | Upstash | Rate limiting | Per-IP and per-account request counters (no content). | | Sentry | Error monitoring | Redacted stack traces and breadcrumbs (no raw submitted text). |

We do not sell your data, share it with advertising networks, or share it with AI-detector vendors.

6. Cookies and Session Storage

We use a single HttpOnly, Secure, SameSite=Lax session cookie (huminizer.session_token) to keep you signed in. This cookie is set by our authentication system and contains only a session identifier. We do not use third-party analytics cookies, tracking pixels, or advertising cookies.

7. Children

The Service is not directed at users under 16 years of age (applicable in the European Union and United Kingdom) or under 13 years of age (United States). Do not create an account if you are below the applicable minimum age in your jurisdiction.

8. International Data Transfers

Your data may be processed in jurisdictions outside your home country (for example, the United States) by the sub-processors listed above. For transfers from the European Economic Area or United Kingdom to processors in the United States, we rely on Standard Contractual Clauses (SCCs) as the legal transfer mechanism where required by applicable law.

9. Security

We implement reasonable technical and organisational measures to protect your data, including encrypted connections (TLS), hashed passwords (argon2id), redacted logging, and access controls. No method of transmission or storage is completely secure; we cannot guarantee absolute security.

10. Changes to This Policy

We will announce material changes to this Privacy Policy by email or in-product notice before they take effect. Continued use of the Service after the effective date constitutes acceptance of the revised policy.

11. Contact

For privacy-related questions or to exercise your rights, email [Operator: insert privacy@yourdomain].

This policy was prepared as a starting-point template. The operator should review it with qualified legal counsel before public launch.