Request signatures on a PDF — the document never sits on a server in the clear

E-signature services work by holding your contract. Bindery does not: you place signature, initials, date and name fields for each recipient, the file is sealed in your browser with a fresh AES-256 key, and every signer gets a link that carries the key in its fragment plus a private token. They sign on their own device, the file is re-sealed with the same key, and Bindery’s broker only ever stores ciphertext, token hashes and SHA-256 hashes of each version.

Sign in any order or one after another. When the last signer finishes, an audit page listing every step and hash is appended and the file is certified with a cryptographic signature and an RFC 3161 trusted timestamp. A status page shows progress; nothing is emailed — you send the links yourself. Bindery runs entirely in your browser — your file is never uploaded, so there is nothing to delete from a server afterwards.

How it works

1. Drop the PDF and open Request signatures; add recipients and click the page to place their fields
2. Create the signing links — the file is sealed on your device and uploaded as ciphertext
3. Send each link; signers draw or type their signature on their own device

Questions people ask

What does Bindery store?

The sealed package, hashed link tokens, the field positions, and a log of times and SHA-256 hashes. Never the key, never the document.

Is the signature legally binding?

The completed file carries each signer’s drawn signature, a hash-chained audit page and a certification with a trusted timestamp — the same evidence trail electronic-signature laws describe. Whether that suffices depends on your jurisdiction and document type.

Do signers need an account?

No. Only the person creating the request signs in; signers open the link in any browser.

More Bindery tools