Encryption
Traffic is protected with TLS 1.2+ and stored data is encrypted at rest with AES-256.
Signed documents can become legal evidence. We design the platform to protect their confidentiality, integrity and availability.
Traffic is protected with TLS 1.2+ and stored data is encrypted at rest with AES-256.
Completed PDFs use PAdES-compatible controls and RFC 3161 timestamps where configured, so later changes can be detected.
Relevant signing events retain timestamps, IP addresses, user-agent information and configured identity-verification events.
Production infrastructure and customer data are hosted in the European Union, with encrypted backups and isolated environments.
Organisation isolation, role-based permissions and session controls restrict who can view and send documents.
Workflows can add email access, one-time SMS codes and optional KYC checks before signing.
Compliance with a legal framework and third-party certification are different things. We publish the controls available today separately from certifications that remain on the roadmap.
See compliance and roadmapIf you believe you have found a vulnerability, contact our security team. Do not access or alter another customer’s data and give us reasonable time to investigate before publication.