Security you can show a judge.
Bond paperwork carries Social Security numbers, addresses, IDs and collateral details. Here is exactly how BondSigner keeps that information private and proves every signature is real.
Your documents
Encrypted at rest
PDFs and signature images are stored in Amazon S3 with server-side encryption. They are never public: every view or download uses a link that expires within an hour.
Tamper check on every file
Each document gets a SHA-256 fingerprint when it’s created and when it’s signed. If even one byte changes, the fingerprint no longer matches.
Access enforced by the database
Account data lives in Postgres with row-level security, so a team member can only reach the documents their organization and role allow.
The signing link
One private link per signer
Each link is unique, works only for that signer’s part of the packet, and stops working once the packet is voided. Change a signer’s email or phone and a new link replaces the old one.
Links that expire when you want
Set how long signing links stay valid for your whole agency, for a client company, or for a single packet.
Consent recorded before signing
Signers agree to do business electronically before they can sign, as the E-SIGN Act and UETA require, and that agreement is logged with the rest of their activity.
Proof of signing
A complete audit trail
Sending, opening, signing, declining and voiding are each recorded with a timestamp, IP address and browser.
Certificate of Completion
Attached to every completed packet: each signer, when they signed and from which IP address, plus the packet’s activity history.
Verification anyone can run
The certificate’s QR code opens a public page showing the signers, the timestamps and the document fingerprint, so a court or surety can confirm a copy is genuine without an account.
Your team and integrations
Roles and permissions
Give each member exactly the access they need, per section, across your agency and any sub-agencies or client companies. Sessions sign out after inactivity and expire after a maximum length.
Scoped API keys
An API key can be limited to a single client company, so one integration can never read another company’s packets.
Signed webhooks
Every webhook carries an HMAC signature made with a secret only you and BondSigner hold. Rotate it any time.
Verify a document
Scan the QR code on the last page of the signed packet, the Certificate of Completion. It opens that document’s verification page on bondsigner.com, showing who signed, when, and its SHA-256 fingerprint.
Check that the web address starts with bondsigner.com/verify. If the details don’t match the copy in front of you, or the page won’t open, contact us and we’ll look into it.
Found a security issue?
Email us with the details and steps to reproduce it. We read every report and reply.