Your signer never makes an account.
Send a PDF.
Get it back signed.
Place the fields where you want them, send one link, and your client signs in their browser. Every step is recorded in an audit trail you can check yourself, and the finished document carries a seal that breaks if anyone edits it.
Listed on G2.Read or write a review
Three steps, one link
01
Drop the PDF in
Your own file, exactly as you wrote it. We read the page sizes and rotations so a field lands where you put it, even on a rotated scan.
02
Place the fields
Drag a signature, initials, date or text box onto any page. Fields snap to each other, arrow keys nudge them, and undo works the way you expect.
03
Send one link
Your client opens it, confirms a code we email them, signs on their phone and downloads the sealed PDF. No account, no app.
Proof, not just a signature.
A signature is only worth what you can prove about it. Every event on an envelope carries the hash of the event before it, so the trail cannot be quietly rewritten. Delete one line and verification tells you which line, by number.
When the last person signs, we hash the finished PDF. That hash is the seal. Anyone holding the document can drop it on the verify page and check it, and the hashing runs in their browser, so the file never has to be uploaded to be trusted.
Check a document nowAudit trail
Chain intact · 7 events
Signing link opened
14:02:11 UTC9f2c41ab…7d0e
Identity confirmed by email code
14:02:44 UTCc7d38e10…41ba
Signature applied on page 6
14:03:09 UTC2ab90fd4…8c17
All recipients signed. Document sealed
14:03:09 UTCe05b7c2a…9f31
Integrity seal
e05b7c2a4f19d8b3c60a7e51f2d94ab8e05b7c2a4f19d8b3c60a7e51f2d949f31
What is in the box
- Signature capture
- Draw with a pressure-sensitive pen, type it in one of three hands, or upload a photo of a wet signature.
- Field types
- Signature, initials, date signed, free text and checkbox, any number per page.
- Multiple signers
- Sequential order, one link each, per-recipient colour coding in the editor.
- Identity check
- A six-digit code to the recipient's email before the document is shown to them.
- Audit trail
- Every event hash-chained to the one before it, with IP address and browser recorded.
- Integrity seal
- SHA-256 of the signed PDF, checkable in your own browser at any time.
- Certificate of completion
- A separate PDF you can download on its own, with the full trail in a paginated table.
- Mobile signing
- Built for a phone first, because that is where most signers open the link.
- Document size
- PDFs up to 25 MB and 60 pages, rotated scans included.
- How many signers
- Up to 20 on one document.
- Retention
- A sent document, its trail, its seal and its certificate are kept for as long as the account exists.
Questions people actually ask
Does my client need an account?
No. They get a link, confirm a six-digit code we email them, sign in the browser and they are done. There is no password to set and nothing to install.
Then how do you know who signed?
The link is unique to one recipient and the code goes to the email address you addressed it to. We record when the link was opened, when the code was confirmed, the IP address and the browser, and every one of those events is chained into the audit trail.
What stops someone editing the document afterwards?
When the last signature lands we hash the finished PDF and store that hash as the integrity seal. Change one byte and the hash no longer matches. You can check it yourself on the verify page, and the check runs in your browser, so the file never leaves your machine to be verified.
Can I see what happened, in order?
Yes. Every envelope has an audit trail where each event carries the hash of the one before it. Remove or edit an event and the chain breaks at a specific number. The same trail is typeset onto a Certificate of Completion, which downloads as its own PDF.
Where does my document live?
In Cloudflare R2 object storage, encrypted at rest, under our own account. Nobody at Sign Here opens it, and it is never sold, shared or used to train anything. Verifying a document does not need it either: the hashing runs in your browser, so checking a file uploads nothing.
Your next contract, signed today.
Drop a PDF in and you can have it out for signature in a minute.