Request signatures on a PDF — the document never sits on a server in the clear
Fields per signer, sealed on your device, signed on theirs; audit trail and trusted timestamp on completion.
Free: 3 jobs per UTC day, 25 MB per file. PDF exports include a visible Made with Bindery watermark. Pro exports clean PDFs.
Prefer the full studio? Open Request PDF signatures in the app →
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
- Drop the PDF and open Request signatures; add recipients and click the page to place their fields
- Create the signing links — the file is sealed on your device and uploaded as ciphertext
- Send each link; signers draw or type their signature on their own device
How a sealed signature request works
E-signature services work by holding your contract on their servers. Bindery does not. You place signature, initials, date and name fields for each recipient on a real render of the pages. The file is sealed in your browser with a fresh AES-256 key. Each signer receives a link that carries the key in its fragment plus a private token; they open it in any browser, draw or type their signature on their own device, and the file is re-sealed with the same key. Bindery’s broker stores ciphertext, hashed tokens, field positions, and a log of times and SHA-256 hashes — never the key, never the document in the clear.
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; you send the links yourself by whatever channel you trust.
Built for the common cases
- Order: sign in any order, or one after another.
- Access codes: require a code you share separately, so a forwarded link alone is not enough.
- Templates and bulk send: save field layouts for recurring documents and send the same document to many signers at once.
- Reminders and expiry: reminders open in your own mail app with the recipient’s link — nothing is sent by Bindery — and every request carries an expiry you set.
- Verification: anyone can check the completed file with Verify signatures on their device.
Free includes three requests a month; signing is always free and needs no account. Pro adds unlimited requests, templates, bulk send and access codes. The DocuSign comparison sets out where each approach fits.
Sealed requests versus e-signature services
| Request signatures | Bindery | Upload-based tools |
|---|---|---|
| Where the file is processed | In your browser tab, on your device | Uploaded to the service’s servers |
| Where the contract lives | Sealed on your device; the server holds ciphertext | On the service’s servers, readable |
| Evidence | Hash-chained audit page, certification, trusted timestamp | Audit trail held by the service |
| Signer account | None | Often required |
| What exists afterwards | The original and the new file, both on your device | A server copy until the retention window ends |
| Works offline | Yes, once the app has loaded | No |
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.
Is the completed document legally binding?
It carries each signer’s signature, an audit page of times and hashes, and a certification with a trusted timestamp — the evidence electronic-signature laws describe. Whether that is sufficient depends on your jurisdiction and document type; for documents that require a qualified signature, use a qualified provider.
What does a signer need?
The link, any modern browser and, if you set one, the access code. No account, no app.
How do I remind a signer?
From the status page. A reminder opens in your email app with that recipient’s own link already in it; Bindery sends nothing itself, so the channel is yours. Requests expire on the date you set when creating them.