Security Updated
Security, in depth.
Every claim on this page is backed by our code and infrastructure.
Certifications
Cyber Essentials certified on 28 October 2026, whole organisation. Cyber Essentials Plus is in progress; ISO 27001 and ISO 42001 are planned. A security questionnaire pack is available on request.
Verify our certificate →A cell-based deployment.
What a cell is
- Each cell is a complete, isolated copy of Unforged.
- Cells share only the code and the container images.
- Adding regions means more cells.
Around the cell
- Its own isolated cloud account
- In the region of your choice
- No root credentials
- Staff access through single sign-on, 8-hour sessions
- Every infrastructure action logged, kept 365 days
One check’s journey. From upload to verdict stamp.
-
Upload
- Sent over TLS.
- Validated before anything is written.
- Written create-only to your organisation’s bucket.
-
Queue
- The job waits in the database queue.
- Every row is fenced to your organisation by row-level security.
-
Check
- The check runs.
- Your documents are never used to train anything.
-
Result
- Recorded exactly once.
- Stamped with model, policy and API version.
- Images never go into the database.
-
Webhook
- Signed with HMAC-SHA256 and a timestamp.
- HTTPS only.
- Secrets encrypted at rest and rollable.
-
Your history
- Results kept for your retention period (90 days by default, you choose).
- References kept until you delete them.
- model
- nib v2.6
- policy
- default@1
- api version
- 2026-10-14
One document · upload to verdict stamp Example check
How your account is protected.
Sign-in
- Hosted sign-in: we never store your password.
- Sessions live in encrypted, HttpOnly, Secure, SameSite=Lax cookies.
- 30 days, sliding.
- A short-lived access token, refreshed automatically.
- Single sign-on and directory sync on plans that include them.
Keys
API keys
- Stored only as argon2id hashes
- Scoped to permissions
- Revocable instantly
- Last used shown
Client session tokens
- Up to 15 minutes
- One check
- One subject
Bucket keys
- At most two per organisation
- Secret shown once
Isolation
- Row-level security on every organisation table, so one organisation’s queries can’t read another’s rows.
- An append-only audit log, kept 400 days, covers:
- keys
- sessions
- policies
- webhooks
- references
- retention
- child-org access
- Acting in a child organisation is permission-gated and audited.
Access
Who can do what.
6 roles
32 permissions
Fine-grained, checked on every request.
| Permission | Owner | Admin | Member | Viewer | Auditor | Billing |
|---|---|---|---|---|---|---|
See org, members, usage org:read | Yes | Yes | Yes | Yes | Yes | Yes |
Invite/remove members, assign roles org:members:manage | Yes | Yes | — | — | — | — |
Admin Portal links: SSO, directory sync, role mapping org:sso:manage | Yes | Yes | — | — | — | — |
Create/revoke API keys (within own permissions) org:keys:manage | Yes | Yes | — | — | — | — |
Checkout, billing portal, plan org:billing:manage | Yes | — | — | — | — | Yes |
Retention, org-wide settings, the API version pin org:settings:manage | Yes | Yes | — | — | — | — |
Audit log org:audit:read | Yes | Yes | — | — | Yes | — |
Act in descendant orgs org:children:access | Yes | Yes | — | — | Yes | — |
Create/suspend child orgs org:children:manage | Yes | — | — | — | — | — |
Submit checks, sessions, live nib:checks:create | Yes | Yes | Yes | — | — | — |
Read checks and results nib:checks:read | Yes | Yes | Yes | Yes | Yes | — |
Read subjects/references metadata and thumbnails nib:subjects:read | Yes | Yes | Yes | Yes | Yes | — |
Enroll references, confirm-to-learn nib:references:write | Yes | Yes | Yes | — | — | — |
Delete references and subjects, unlearn nib:references:delete | Yes | Yes | — | — | — | — |
Policy, learning, templates, webhooks, bucket keys nib:settings:manage | Yes | Yes | — | — | — | — |
See filed records, folders and metadata folio:records:read | Yes | Yes | Yes | Yes | Yes | — |
Open and download documents (a reason is recorded) folio:documents:read | Yes | Yes | Yes | — | — | — |
Search record metadata and document text (audited) folio:documents:search | Yes | Yes | Yes | — | — | — |
File records, create folders, extend retention folio:records:write | Yes | Yes | Yes | — | — | — |
Request disposal and early deletion folio:records:delete | Yes | Yes | — | — | — | — |
Place and request release of legal holds folio:holds:manage | Yes | Yes | — | — | — | — |
Approve hold releases and early deletion (second person) folio:holds:approve | Yes | Yes | — | — | — | — |
Create exports, custody and integrity reports folio:exports:create | Yes | Yes | — | — | — | — |
Read the folio ledger folio:audit:read | Yes | Yes | — | — | Yes | — |
Retention classes, reason settings, protected folders, webhooks folio:settings:manage | Yes | Yes | — | — | — | — |
See packages, their signers and signed files sig:packages:read | Yes | Yes | Yes | Yes | Yes | — |
Create, send, correct and void packages sig:packages:send | Yes | Yes | Yes | — | — | — |
Sig settings: Folio filing and Nib checks sig:settings:manage | Yes | Yes | — | — | — | — |
Send documents to be checked for forgery loupe:checks:create | Yes | Yes | Yes | — | — | — |
See document checks and their findings loupe:checks:read | Yes | Yes | Yes | Yes | Yes | — |
Record the decision on a document check loupe:checks:review | Yes | Yes | Yes | — | — | — |
Loupe settings: webhooks loupe:settings:manage | Yes | Yes | — | — | — | — |
On plans with SSO, add your own roles and map your identity provider’s groups to them.
Permissions in the API docs →Building and running it safely.
-
A content security policy on every page
A fresh nonce on every page the server renders.
-
Deploys with short-lived credentials
No long-lived cloud keys.
-
Supply-chain checks
Dependencies are checked before every push and the infrastructure every night, and the build and deploy actions are pinned by commit.
-
Our own private registry
Container images with immutable tags, scanned on push.
-
Built from a pinned build definition
-
Alerts on failed work
-
Staff admin through a private tunnel
Every action recorded.
Retention and deletion. How long things live.
Uploaded documents are deleted 24 hours after the check, by default (a little longer while opt-in learning for it is still queued). Results are kept for your history-retention period (90 days by default, you choose).
Documents sent to Loupe stay with their result until your team has decided, and then for the same history-retention period. Anything marked as altered is kept while your account is open.
Leave cleanly
Close your account and we delete your settings, keys and check history. Stored files are deleted when you ask us to. Billing and audit records are kept.
Policies and documents. What we hold ourselves to.
Our public policies will appear here once they’re approved. Until then, ask us for the questionnaire pack.
Our commitments.
- Your documents are never used to train anything.
- Never sold.
- Your data stays in the region of your choice.
- Found a vulnerability? Report it responsibly, or read our security.txt.
- Need a security questionnaire filled in? Talk to us.