Security
Built for documents you cannot afford to leak.
Construction runs on commercially sensitive documents: contracts, specifications, drawings. Here is how Archie treats them. Everything on this page is practice, not promise.
Your documents stay yours
Project documents live in your workspace and are used to produce your deliverables. They are never used to train models, ours or anyone else's.
Authenticated access, two roles
Every request is authenticated with short-lived tokens. Builders draft and submit; only the independent commissioner can sign or reject. The API enforces this, not just the interface.
Signed means immutable
Signing renders the final PDF, stores its cryptographic hash, and locks the record at the database level. Edits to signed records are rejected, and revisions become new versions.
Everything leaves a trail
Every engine run is logged with its inputs and results. Every review action records who, when and what. Deliverables carry document control blocks and revision history.
Provenance on every value
Extracted values keep their source: document, page or cell, extraction method and confidence. A challenged number answers for itself.
Straight answers on data location
Data is hosted on managed cloud infrastructure. Ask us about hosting regions and retention for your project, and we will give you specifics rather than a badge wall.
Working with your team
Enterprise requirements, honestly framed.
We are early, and we will not pretend otherwise with a wall of certification logos. SSO integration is on the roadmap and the auth layer is built for it. If your project has specific security requirements, put them in front of us and we will show you exactly where we stand on each one.
Put your security questionnaire in front of us.
We would rather answer the hard questions before the pilot than after it.