Built for documents you cannot afford to leak.
What is in place today to protect your project, and how each control works.
Send us your security questionnaireIn place today. Running in production, right now.
Per-project logical isolation
One customer's data is never exposed to another, enforced in the data layer and covered by the test battery that runs on every change.
Encrypted in transit and at rest
Project documents and the extractions computed from them are encrypted on the wire and on disk.
Your documents are never used to train models
Not by us, and third parties are not permitted to train on them either.
Archie is not a document store
It retains the computed working extractions, not your source documents as a persistent library.
Deleted at the end of an engagement
Project data is deleted when the engagement ends, and the deletion is confirmed in writing.
Role-gated access, enforced at the API
A drafting role and an independent commissioner role. Only the commissioner can sign, and the API enforces it, not just the interface.
Signed means sealed
Signing renders the PDF, stores its cryptographic hash and locks the record at the database level. A revision becomes a new version.
Everything leaves a trail
Every engine run is logged with its inputs and results, and every review action records who, when and what.
A test battery on every change
Automated tests run on every change, including the graded accuracy battery.
Deployed. Live on the platform since 19 September 2026.
Deployed on 19 September 2026 and verified on the running system. Every item here is a control you have today.
Ask us for the deployment dateDeployed
Short-lived tokens bound to server-side sessions
Idle and absolute caps, with single-use refresh rotation.
Deployed
Multi-factor authentication
Standards-based one-time passwords. Live, enrolled per account from Settings.
Deployed
A tamper-evident audit log
An append-only hash chain, with a database trigger that refuses updates and deletes.
Deployed
A dedicated security suite in continuous integration
Authentication bypass, cross-tenant access, injection, headers, session and audit.
Deployed
An evidence pack generated from the running system
A statement of applicability, an access-control matrix and the test manifest, produced from the system itself.
The eight questions we get asked first.
Every control on this page is deployed and running today.
Put your questionnaire to usThey live in your workspace, logically isolated, encrypted in transit and at rest, and are used to produce your deliverables. They are never used to train models, ours or anyone else's. At the end of an engagement they are deleted, and the deletion is confirmed in writing.
Access is role-gated and enforced at the API. Engineering access to a workspace is for support and debugging only, it is logged like every other action, and we will name who holds it for your engagement.
Yes. Every engine run is logged with its inputs and results, and every review action records who, when and what. The trail is part of the deliverable.
It is rendered to PDF, hashed, and locked at the database level. If the underlying data changes afterwards, Archie raises a new revision rather than altering the signed record.
On managed cloud infrastructure. Ask us for the region and retention terms for your engagement and we will put them in writing as part of the agreement.
Models are used for interpretation and classification, never for arithmetic. Every engineering number is computed by a deterministic engine. We will confirm our model provider retention terms in writing as part of your security review.
Send them. Where the answer is no, we will say no and tell you what it would take.