Caseliq

Sign NDAs by QR code, in the room.

Security & Trust

Last updated: 5 November 2026

How a Caseliq signature is recorded

  • Attribution. The person you show the QR to confirms their email with a one-time code and types their full legal name to sign. Where their device supports it, they can also use its lock, such as a fingerprint or face, to make a WebAuthn signature over the exact document hash. That shows a key created on the device during signing was used; it doesn't identify the person or prove the make of device. The person who sets up the NDA signs from their signed-in account, by ticking a box.
  • Intent. Signing requires an explicit agreement checkbox, an identity attestation, and a clearly labelled signing action. The full agreement is one tap away. The exact consent wording shown is quoted on the certificate of completion.
  • Record. Every step — link opened, summary viewed, code verified, checkbox ticked, signature applied — is appended to a per-agreement hash chain with server-side UTC timestamps. Altering any historical entry breaks every hash after it.
  • Tamper evidence. The executed PDF's SHA-256 fingerprint is stored in a global hash chain and summarised daily in a Merkle root, which independent timestamp authorities (DigiCert and FreeTSA) sign. They receive only that hash, nothing about any agreement. It shows the records existed by that date. Anyone can check a PDF at /verify: the file is hashed in the browser and never uploaded.
  • Fairness. Plain-English summary first, and a decline button that stays on screen at every step of the signing flow. There's no visible countdown; the link closes 15 minutes after it's opened, and again 15 minutes after the email is confirmed, which we tell the signer up front.

What we deliberately do not claim

Caseliq signatures are simple electronic signatures. We do not claim advanced or qualified signatures under eIDAS, government identity verification, or notarisation. Email verification proves control of an inbox at a moment in time; authority to bind a company rests on the signer's attestation. Whether a signature is valid in a particular case is for a court.

Platform security

  • Signing links carry 256-bit tokens, stored only as hashes. Only the first device to open a link can sign.
  • One-time codes are salted-hashed, expire in 10 minutes, and lock out after repeated failures.
  • Executed documents live in private storage; downloads are authenticated.
  • Security headers, rate limiting, and no third-party scripts anywhere on the site.