Recorded on every signature
- Signer identity
- Authentication method
- Consent timestamp
- Explicit intent
- Document version
- SHA-256 at signing
- Server time (UTC)
- Source IP
- Browser & device
- Field completion
- Chain checkpoint
How it works
Three steps, and an evidence record at the end of them.
Upload and prepare
Drop in a PDF. Add your signers and drag their signature, date and text fields onto the page.
Send
Each signer gets their own private, expiring link. Nothing is guessable and nothing is reusable.
Verify
Anyone can check a finished document against its audit trail. No account needed.
Everything a signing workflow needs
From upload to a sealed, verifiable record.
Prepare in the browser
Drag signature, initials, date, text and checkbox fields onto any PDF. Coordinates are normalised, so a field lands in the same place on every screen.
Sequential or parallel
Route to signers one at a time or all at once, with CC recipients who receive the finished copy.
Verified signers
A signer opens a link sent to their address and enters a one-time code delivered to it — proving mailbox control at signing time.
Consent and intent
Versioned e-signature consent is presented and recorded. A signature is only created by a deliberate action.
Reminders and expiry
Automatic reminders on your cadence, and real expiry that revokes outstanding links.
Certificate of completion
Every finished transaction produces a sealed PDF and an evidence report with signer details, timestamps and hashes.
Verification that actually recomputes
“Verified” should mean something was recalculated, not that a boolean was read out of a table. Signet does the former, and reports exactly which check failed when one does.
- 256-bit
- SHA-256 over every version and event
- 100%
- of audit events hash-chained and append-only
- 0
- accounts needed to verify a document
- Ed25519
- signed checkpoints over the audit chain
Append-only audit trail
Every significant event is written once and never updated — modification is refused by the database itself, not merely avoided by the application.
Hash-chained history
Each event’s hash covers the hash of the event before it, so altering one entry breaks every link after it. An edit cannot be hidden, only relocated.
Server-authoritative record
Timestamps, document identity and completion status are decided server-side. A browser submits an action; the server alone decides what that action means.
Document binding
A signature is bound to the exact document version the signer’s browser rendered. If the hashes disagree, the signature is refused rather than quietly attached.
Two plans. One price each.
Both include unlimited documents and the complete evidence trail. Cancel any time.
Every plan includes the full audit trail and certificate of completion.
Questions worth asking
Including the ones most e-signature vendors would rather answer vaguely.
Is an electronic signature legally binding?
In the United States, the ESIGN Act and state adoptions of UETA establish that a signature is not invalid merely because it is electronic. That is a floor, not a guarantee: whether a particular signature holds depends on the transaction, the jurisdiction, and whether you can show who signed, that they intended to, and that the document has not changed since. Signet is built to preserve exactly that evidence. It cannot promise enforceability in every jurisdiction or for every document type, and nothing here is legal advice.
What makes the audit trail tamper-evident?
Every event is written once and never updated, and each event’s SHA-256 hash covers the hash of the event before it. Change one entry and every link after it breaks, so an edit cannot be hidden — it can only be moved. Because a hash chain alone would not stop someone able to rewrite the entire table, chain heads are periodically signed with an Ed25519 key held outside the database. Verification recomputes those hashes from the stored bytes rather than reading a stored “valid” flag.
Do signers need an account?
No. A signer opens the private link sent to their address, confirms a one-time code delivered to that address, and signs. Anyone checking a finished document against its audit trail does not need an account either — the verification page is public and shows integrity results only, never document contents or field values.
What happens when someone declines?
Declining is a first-class outcome, not a dead end. The signer gives a reason, the document moves to declined, and every outstanding link for it is revoked so nobody further down the routing order can sign into a transaction that is already over. The decline, its reason and its timestamp are recorded in the audit trail like any other event — a declined document still produces a complete, verifiable record.
Can I use this for real estate or healthcare documents?
Sometimes, and it depends on rules Signet has no visibility into. Sector regimes — state real-estate and notarisation requirements, HIPAA, lender and title-company policy — impose obligations on your process, your identity checks and your retention, not just on your software. Signet gives you strong technical controls and a complete evidence record; it does not certify your transaction as compliant. Take advice for the document types you actually send.
Can I cancel?
Yes, at any time, and the subscription runs to the end of the period you have already paid for rather than stopping mid-month. There is no cancellation fee and no notice period. Your completed documents, certificates of completion and audit trails stay downloadable while the account is open, so you can take your records with you before you go.