ARZEN
Menu

Trust center

What is in place today, described plainly.

How certificates are isolated, traced and processed, and the honest status of security certifications. Last updated 2026-10-25.

How a certificate is handled

Isolation
Each organization's certificates are separated by row-level security in the database, so one customer's queries cannot return another's rows.
Encryption
Connections use TLS. Stored data is encrypted at rest by our database and storage providers.
Fingerprint
Each uploaded file gets a SHA-256 hash, printed on every report generated from it.
Audit trail
Every upload, confirmation and export is written to an append-only log. Each entry carries a Unix timestamp and a hash chained to the previous entry, so an edit to history is detectable.
Reading vs. deciding
OCR and an extraction model read the values. Pass or fail is decided by fixed code against the limits shown, never by a model.
Human confirmation
Uncertain reads are marked for review. When a person confirms a value, the original reading is kept next to the confirmation, with who and when.

Certifications

Arzen holds no security certification today. Status changes here only with an auditor's report.

FrameworkStatusNote
SOC 2 Type IPlannedNo audit scheduled yet.
SOC 2 Type IIPlannedFollows Type I.
ISO/IEC 27001Not planned yet—
CMMCNot applicable at launchArzen does not accept CUI, drawings or CAD. See what Arzen does not do.

Subprocessors

Providers that process customer data on our behalf. List dated 2026-10-25.

ProviderPurposeRegion
SupabaseDatabase and sign-inUS region (set at launch)
RailwayApplication serversUS region (set at launch)
VercelWebsite hostingGlobal edge network
Cloudflare R2Storage of uploaded certificatesUS jurisdiction (set at launch)
Amazon Web Services (Textract)Optical character recognitionUS region (set at launch)
AnthropicExtraction of values into structured dataUnited States
StripeCard payments and invoicesUnited States

See also what Arzen does not do.