Effective 7 September 2026 · version 2026-09-07
Security
How documents and signatures are protected, in specific terms.
What is true today
| Area | Measure |
|---|---|
| Encryption in transit | TLS 1.2 or higher on every connection, HSTS enabled |
| Encryption at rest | All databases and file storage are encrypted at rest by the provider |
| File access | Files are never public. Every download uses a link that expires within 15 minutes and is issued only to a party entitled to that document at that moment |
| Signing links | 184-bit random tokens, unique per recipient, rotated when a document is resent, void once the document is complete, voided, or declined |
| Audit trail | Every event on a document is written to an append-only table the database will not let anyone update or delete, and each row is hash-chained to the previous one. A break in the chain is detectable |
| File integrity | Every uploaded and every signed file has a SHA-256 hash recorded and printed on the certificate of completion |
| Isolation | Every record belongs to a workspace; every read is scoped to the caller's workspace and role |
| Data region | European workspaces keep documents, signatures, and exports in the EU |
| Rate limiting | Signing, file, and billing endpoints are rate limited per address |
| Headers | Content sniffing disabled, framing denied, referrer suppressed on signing pages so tokens never leak |
| Secrets | Held in the hosting platform's encrypted configuration, never in code or logs |
| Backups | Point-in-time recovery on the database; restore is tested |
What is planned
SOC 2 Type 1, followed by Type 2; a public status page; advanced (PAdES) signatures with a hardware-backed key; qualified electronic signatures through a qualified trust service provider.
Reporting a vulnerability
Send details through the support form. We acknowledge within two working days, do not take action against good-faith research, and credit reporters who want it.