Signed. Sealed. Provable.
Every contract carries legally-attributable signatures and a cryptographic seal that reveals any change after the fact — not a promise, a proof.
Don’t take our word
Watch the seal break in real time
When all parties sign, we hash the final document. Edit one character below and the hash — and the verdict — changes instantly.
…
…
This is the real algorithm — SHA-256, computed in your browser right now.
Security posture
Standards-based e-signatures
Executed under E-SIGN, UETA and eIDAS SES. Every signer gives explicit consent before signing.
Signature evidence captured
Name, unique ID, timestamp, IP, device, method and consent — the set that makes a signature attributable.
Certificate of completion
A standalone audit page with every party’s evidence and the document’s cryptographic seal.
Tamper-evidence seal
A SHA-256 hash over the final content and every signature. Any change breaks it — as you just saw.
Append-only audit trail
Creation, edits, AI actions, reviews, access and signatures — with immutable version snapshots.
Encrypted on Google Cloud
Stored on Google Cloud / Firebase, encrypted in transit (TLS) and at rest, behind role-based rules.
How a signature becomes provable
Consent
Each party explicitly agrees to sign electronically.
Sign
Name, timestamp, IP, device and method are captured.
Seal
A SHA-256 hash is computed over content + signatures.
Verify
Anyone can re-check the seal and read the certificate.
Recognized legal frameworks
E-signatures on Coventract are executed to be valid across the GCC, wider MENA, the EU and the US.
Data processing & sub-processors
Core sub-processors are Google Cloud / Firebase (hosting, database, auth, storage) and Resend (transactional email). A Data Processing Agreement is available for business customers on request.
This page describes current platform capabilities and is not legal advice.