Skip to content
Security and trust

Security built around independence

The evidence is only as good as the separation between your systems, ours, and the keys that seal it.

Separate keys, separate ledger

AWS KMS, separate account

Keys outside the database

  • Sealing keys are non-exportable in AWS KMS in a separate account.
  • They are accessed through short-lived OIDC credentials.
Append-only

Tamper-evident ledger

  • Application roles cannot update or delete ledger entries.
  • Write-once copies use S3 Object Lock in compliance mode.
  • Signed checkpoints and external anchors make rewritten history detectable.

Access

01

Transport

TLS 1.2 or later everywhere.

02

Encryption

Encryption at rest, plus application-layer encryption for personal evidence fields.

03

Sign-in and roles

Multi-factor authentication required for owners and admins. Five roles.

04

API keys

API keys hashed at rest and shown once.

05

Audit log

Every dashboard action written to an audit log.

06

Staff access

Staff access to customer evidence requires a ticket, is time-boxed, and appears in your audit log.

Program, attestations, and infrastructure

Program

  • Annual external penetration test
  • Vulnerability disclosure policy and security.txt
  • Public subprocessor list
  • Versioned system description

When we act as your processor, we notify you without undue delay after becoming aware of a personal-data breach, as described in our DPA (GDPR Article 33).

In progress

SOC 2

Our SOC 2 program is in progress.

Enterprise security documents

Built on

Vercel and Supabase run the application and have their own SOC 2 Type 2 attestations.

AWS provides key management and write-once storage.

Build the signing flow yourself. Leave the record to us.

Free plan: 10 live signatures a month and a full test mode. No card required.

Working with an AI tool? This page is also available as Markdown: /security.md