Privacy
Privacy notice
Written plainly, and deliberately short. This is a draft pending review by counsel; the substance describes how the product is actually built, and the wording will tighten before launch.
Updated
Status
This document is a draft
Text you check
What happens to the text you submit
When you run an assay, the text is normalised, hashed with SHA-256, and passed to the layers. What we write to our database is the hash, the word count, the language guess, the layer outcomes and the report. The text itself is not stored. Re-running the same text produces the same hash, which is how a report can be tied back to an input we never kept.
A workspace on the compliance tier can switch input retention on, because some audit regimes require the source to be retrievable. That switch is off unless someone deliberately turns it on, and turning it on is written to the audit log with the user and the timestamp.
The classifier layers run on third-party services. When a classifier runs, the text is sent to that processor over TLS for the duration of the request and is not retained by us. Which layers run is described on the accuracy page, and any change to them is recorded in the detector changelog.
Data
What we store, and for how long
| Data | Why | Retention |
|---|---|---|
| SHA-256 of the input | Ties a report to an input without keeping the input | For the life of the report |
| The report | History, exports, your audit trail | For the life of the workspace |
| Input text | Only when a workspace has switched retention on | Off by default; workspace-controlled when on |
| Account details | Sign-in, workspace membership, billing | For the life of the account |
| Credit ledger | Billing accuracy and dispute resolution | Kept as long as accounting rules require |
| Hashed IP address and day counter | Enforcing the free daily limit | Rolling, per UTC day |
| Request logs | Debugging and abuse handling | Short-lived, no request bodies |
Where
Where it runs, and who else is involved
The application, the database and the job queue run in Frankfurt, Germany. The processors we rely on are: our hosting and database provider; Cloudflare for DNS, TLS and the Turnstile anti-abuse challenge; Stripe for payments; the classifier providers named on the accuracy page; and a product analytics provider on EU infrastructure for aggregate usage on this marketing site. Analytics is not loaded at all when no key is configured, and it never receives the text you check.
Under the GDPR you can ask for access, correction, deletion, restriction, portability, or to object to processing. Write to the address in the footer and we will answer within a month. If you are not satisfied, you can complain to your national supervisory authority.