Privacy

Payloads sent to /compress are not written to a database, a log, a cache, or an error message. They exist in memory for the duration of the request and are discarded.

Our request log records a request id, the API key id, which path ran, and two byte counts. It does not record your text, and it does not record a hash of your text.

The one qualification worth stating plainly: on the prose path the response body contains extractive chunks of your input rather than offsets. Those chunks are returned to you and not retained by us, but the response is not offsets-only, and you should know that if you route sensitive prose through it.

Account data: the email address and name your sign-in provider gives us, and which organisations you belong to.

API keys: the public id prefix in plain text so a key can be looked up without scanning, and the secret only as a SHA-256 hash. We cannot recover a key secret, which is why a lost key must be rotated rather than retrieved.

Usage counters: per key and day, plus bounded content-free dimensions such as method, content type, decision, and query/preserve usage. We store request counts and byte totals, not payload or query text. These numbers are what your invoice and usage dashboard are built from.

Credit balance and the ledger of top-ups and debits against it.

Billing alert settings: the balance thresholds you want warned about, and an optional email address to send those warnings to instead of every owner and admin.

Resend, for transactional email — organisation invitations, low-balance credit alerts, and other account mail. They receive the recipient address and the message.

Our hosting and database providers, which run the API and store the account data described above.

We do not sell data, we do not share it with advertisers, and nothing you send is used to train anything. No LLM is called on your payload at any point. Prose compression does run a small classifier in our own process — it scores which sentences to keep and cannot generate text — and it is not trained on your data.

Account and organisation records are kept while the account exists, and deleted on request.

Usage counters are retained for billing and dispute resolution. They contain no content.

Payloads have no retention period because they are never written down.

You can request a copy of the account data we hold, ask for it to be corrected, or ask for the account and its data to be deleted. Write to the privacy address below and we will action it.

If you are in the UK or EU, the usual GDPR rights apply, including the right to complain to your supervisory authority.

Key secrets are stored as SHA-256 hashes and compared in constant time, so a timing difference cannot be used to guess one. Keys are looked up by their public prefix so there is no table scan and no timing oracle on the secret.

If you find a vulnerability, please report it to the security address below rather than filing a public issue. We will not pursue anyone acting in good faith.