E-signature built into the desk

A signature isn't proof.
A certificate is.

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.

SHA-256 chained Every audit entry hashes the one before it, so a rewritten history breaks the chain.
Consent + IP Captured the instant a signer signs, written permanently into the record.
One certificate A separate, downloadable proof of exactly how the document was executed.

Placed exactly where you dropped it

Fields that don't drift when someone scrolls

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.

Measured per page, not per document Holds up on long contracts Same result at any zoom level
Field positionLocked to its page
Long contractsNo stretched or oversized fields
On scroll or resizeField does not move
Field typesSignature, initials, date, text

What you get when it's signed

The certificate is the proof, not just the checkmark

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.

Embedded or separate download Per-clause fingerprint Withdrawal reasons kept on record

Not just a signed PDF

A checkmark tells you it was signed. A certificate tells you how.

A generic e-signature tool

You get a signed file

  • A flat PDF with a signature image on it
  • No record of how the pieces were verified
  • Lives outside your desk, disconnected from the account
  • Nothing stops a page from being swapped after export

Gaden's certificate of execution

You get the file and its proof

  • Consent, identity and IP recorded at the moment of signing
  • Every clause fingerprinted and hashed on its own
  • A hash chain that breaks visibly if history is altered
  • Stays attached to the account it belongs to

What agencies ask before sending the first contract

Does my client need to create an account to sign?

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.

What exactly is a certificate of execution?

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.

Is this legally binding?

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.

Can I withdraw a signature request?

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.

How is the audit trail protected from being altered?

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.

Send the next contract with proof attached

A signing link for them, a certificate for you.