Encryption
TLS 1.3 in transit and AES-256 at rest. Stored documents are isolated per account, and every read of one goes through the API inside a transaction scoped to your organisation — there are no shareable object URLs to leak.
Security & compliance
Everything your security reviewer will ask, on one page
Passports, payslips and bank statements. Where they live, who can reach them, how long they stay — and the questions we cannot answer with a yes.
Data processing agreementThe processor terms, the subprocessor list and the transfer mechanism, as a draft you can send to your counsel.Privacy policyWhat is held, why, who else processes it, and how long it stays — written against what the software does.Security questionnaireSend yours. Answers come back within one business day, with the questions we cannot yet answer marked as such.
Controls
What the system actually does
Each of these is a property of the software rather than a policy somebody agreed to follow.
Never used for training
Your documents and the values extracted from them never train any model, ours or a provider's. The model provider receives document content only in order to extract fields from it, and nothing is retained on our side beyond your own workspace.
Tenant isolation, in the database
Every table holding your data carries an organisation key and a row-level security policy, and requests run on a role that cannot read past it. Isolation is a property of the database rather than of a query somebody remembered to write correctly.
Deletion is immediate, and there is no retention clock
Nothing expires on its own: a document, a profile or a generated file stays until somebody removes it. When they do, the stored file is dropped along with the record. Automatic retention windows are a decision we have deliberately not made yet — ask, and it goes into the contract.
Access control
Email and password with per-organisation membership today; a member removed from an organisation loses access on their next request rather than at their next sign-in. SSO and SAML are scoped as part of an enterprise agreement rather than offered as a switch we have not built.
Analytics are off until you say otherwise
Product analytics only start after somebody accepts the banner, and what they record is which screens were reached — never a field value, a document's content, or a recording of the screen.
Subprocessors
Who else touches your data
The full list, with what each one is for. Which of them are active depends on how the deployment is configured; the data processing agreement is the authoritative version.
| Subprocessor | Purpose |
|---|---|
| Neon | The database holding profiles, extracted values and document metadata. |
| Vercel Blob | Object storage for uploaded documents and generated output. |
| Resend | Transactional email only — confirmation, password reset, and account notices. |
| The configured model provider | Receives document content in order to extract fields from it. Anthropic, Google or OpenAI, depending on the deployment, and reached either directly or through the Vercel AI Gateway. |
| PostHog | Product analytics, and only after you have consented. |
The awkward ones
What we cannot answer with a yes
A reviewer finds these anyway. Finding them after a page that did not mention them is what ends a procurement.
Need a signed DPA before you upload anything?
Send yours or use ours. Questionnaires are answered within one business day, with the questions that have no good answer yet marked as such.