E-signature built into the desk
Send a contract and your client signs from a private link in their email — no account, no password. Once it's signed, Gaden seals it with a certificate of execution: a hash-chained audit trail, their consent and IP address, and a fingerprint of every clause.
Placed exactly where you dropped it
Every signature, initial and date field is measured against the page it sits on, at the moment it's placed — not against the whole document stacked into one long scroll. Zoom in, scroll a fifteen-page contract, resize the window: the field stays exactly where you put it, on exactly the page you put it on.
What you get when it's signed
A signed PDF only shows you the outcome. The certificate of execution shows you how it got there: who signed, from where, when, and every step in between — chained together so the record can't be quietly edited after the fact. It can be embedded in the executed file, or kept as its own downloadable record.
SHA-256 chained to the entry before itNot just a signed PDF
A generic e-signature tool
Gaden's certificate of execution
No. Each signer gets a private signing link sent to their email, with an optional access code for an extra layer of verification. Only one link is live at a time, and you can reissue a fresh one if it's lost or expires.
It's the record of how a document was signed, separate from the signed document itself: the audit trail, the signer's consent and IP address, and a hash chain linking every event so the history can't be quietly rewritten. You can embed it in the executed file or download it on its own.
Gaden records the elements standard e-signature law generally relies on — signer identity, consent, a timestamp, and a tamper-evident audit trail. Whether a specific document or jurisdiction has additional requirements is a question for your own counsel; Gaden isn't a law firm.
Yes. Withdrawing asks you for a reason, and that reason is written permanently into the audit trail alongside everything else that happened to the document.
Each entry is hashed with SHA-256 over a canonical version of the event, with the previous entry's hash folded in before hashing. That chains every event to the one before it, so an edited or missing entry breaks the chain instead of disappearing quietly.
A signing link for them, a certificate for you.