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
Keys outside the database
- Sealing keys are non-exportable in AWS KMS in a separate account.
- They are accessed through short-lived OIDC credentials.
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
Transport
TLS 1.2 or later everywhere.
Encryption
Encryption at rest, plus application-layer encryption for personal evidence fields.
Sign-in and roles
Multi-factor authentication required for owners and admins. Five roles.
API keys
API keys hashed at rest and shown once.
Audit log
Every dashboard action written to an audit log.
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).
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.