Compliance & security

Legally sound in every market you sign in

Each agreement is checked against the rules of its governing jurisdiction before it is sent, and every step leaves verifiable evidence.

Jurisdictions

Compliance profiles

Choose the governing law and document type; the platform applies the right rules and refuses documents that cannot legally be signed electronically.

JurisdictionLegal frameworkDefault retentionGuardrails
United StatesESIGN Act, UETA7 years (10 for loan agreements)Wills, codicils and court documents are blocked; deeds are flagged for notarisation.
United KingdomElectronic Communications Act 2000, UK eIDAS, UK GDPR6 yearsWills are blocked; Land Registry transfers and lasting powers of attorney are flagged.
European UnioneIDAS (EU) 910/2014, eIDAS 2.0, GDPR10 yearsWills and property transfers are blocked; loan agreements require an advanced signature.
IndiaInformation Technology Act 2000, BSA 2023, DPDP Act 20238 yearsFirst Schedule exclusions (wills, powers of attorney, property sale, negotiable instruments) are blocked; loan agreements require Aadhaar eSign.

Signatures are simple electronic signatures (SES) with a platform seal by default. In India, Aadhaar eSign and DSC tokens provide advanced signatures through licensed partners; qualified signatures (eIDAS) are on the roadmap. This page is general information, not legal advice; check requirements for your specific documents.

Trust

How a signature becomes evidence

  1. Step 1

    Fingerprint

    Every uploaded document is hashed with SHA-256 and the hash is recorded in the audit trail.

  2. Step 2

    Policy

    The policy engine decides the signature level, signer checks, consent wording, retention and data region.

  3. Step 3

    Verify

    Each signer confirms their identity with a one-time code sent to their email before seeing the document.

  4. Step 4

    Seal

    The completed PDF is sealed with a PAdES digital signature. Only a hash of the content reaches the signing key.

  5. Step 5

    Timestamp

    An RFC 3161 timestamp from a trusted authority proves when the document was sealed.

  6. Step 6

    Store

    Sealed documents are written to object storage with a retention lock, so they cannot be overwritten.

Tamper-evident audit trail. Each event (sent, viewed, verified, consented, signed, sealed) includes the hash of the one before it. Changing, inserting or deleting any event breaks the chain, and the certificate of completion records the final hash.

Data residency

Your data stays in its legal zone

The platform runs as independent regional cells. Each cell holds its own customers' documents, keys and audit trails, and data does not move between cells.

  • Each jurisdiction maps to a home region (US, UK, EU, India), recorded on every agreement
  • Warnings when an agreement's data belongs in a different region
  • Dedicated cells and on-premises deployment for banks and governments (planned)
  • Customer-managed encryption keys on the roadmap

Security

Security controls

Defence in depth, from upload to archive.

  • Every upload is scanned for malware before it is accepted
  • Signature images are fully decoded and re-encoded to block malformed files
  • Signing links are cryptographically bound to one recipient; forged links are rejected
  • One-time codes expire after 10 minutes and lock after 5 wrong attempts
  • Organisations are strictly isolated from each other
  • API keys are stored hashed and can be revoked at any time; webhooks are HMAC-signed
  • Passwords are hashed with bcrypt; sessions are HTTP-only cookies
  • Single sign-on with OIDC, optional enforcement per domain, and SCIM de-provisioning
  • Roles limit who sees which agreements; admin actions are kept in an activity log
  • Embedding is limited to the websites each organisation allows
  • AI features are off until an organisation's admin turns them on

Certification roadmap

Certifications we are working towards

We will publish reports and certificates here as audits complete. None of these are held yet.

Information security
SOC 2 Type II, ISO 27001, 27017, 27018, 27701
Industry
PCI DSS, HIPAA, 21 CFR Part 11 validation pack
Government
FedRAMP, IRAP, C5, ENS, MeitY empanelment
Trust services
eIDAS conformity assessment; CCA eSign licence or licensed partner (India)
Accessibility
WCAG 2.2 AA, Section 508

Ready to get started?

Have a compliance question?

Tell us your jurisdictions and document types, and we will walk you through how they are handled.

  • Free 14-day trial
  • No credit card required
  • Cancel anytime