# Security at Unforged

> Unforged is hosted in the region of your choice. Documents are used only to run your checks, never for training, and are deleted 24 hours after the check by default; results are kept as long as you choose.

Source: https://unforged.ai/security

**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.

## What we already do

- [Single sign-on and roles](https://unforged.ai/security#access)
- [Content security policy that blocks injected scripts](https://unforged.ai/security#csp)
- [Sessions in encrypted HttpOnly cookies](https://unforged.ai/security#sign-in)
- [API keys stored as argon2id hashes](https://unforged.ai/security#keys)
- [Row-level security per organisation](https://unforged.ai/security#isolation)
- [Append-only audit log kept 400 days](https://unforged.ai/security#isolation)
- [Responsible disclosure and security.txt](https://unforged.ai/security#report)

## Where it runs

- 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

- **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.

## 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.

## Building and running it

- 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

Uploads are deleted 24 hours after the check, by default. Results are kept for your history-retention period: 90 days by default, or anything from 30 minutes to 10 years, or indefinitely. When your account closes we delete your organisation's records (settings, keys and check history). Stored files - documents, reference images and result files - are deleted when you ask us to (email support@unforged.ai), unless law requires us to keep them.

## Policies and documents

Our public policies will appear here once they're approved. Until then, ask us for the questionnaire pack.

## Commitments

- Your documents are never used to train anything.
- Your data stays in the region of your choice.
- Found a vulnerability? [Report it responsibly](https://unforged.ai/security/disclosure).
