An audit trail you can check, not just trust.
Many insurers, banks and law firms only allow e-signature tools with a strong audit trail. SealProof was built to go further: every record is sealed, independently timestamped, publicly anchored and verifiable without us.
What an approved-vendor review looks for, answered.
These are the questions carriers, banks and firms put to an e-signature provider before approving it. Here's how SealProof answers each one.
Is the signature legally valid?
SealProof is designed around the U.S. ESIGN Act and UETA. It records each signer's consent in the exact words they saw, and shows consumers an electronic record and signature disclosure they can download. The signed PDF is a complete record anyone can keep and print.
Will the record hold up in a dispute?
Every view, code, signature and change is logged with time, IP address and device. The log sits in a Certificate of Completion sealed inside the PDF, so the evidence travels with the document.
How do you know who signed?
Choose per signer: a unique link, a one-time code by email (the link locks after 5 wrong tries), an access code you give by phone, a photo ID and live selfie check, or in-person signing. The certificate records which checks were used and passed.
Could anyone change it afterwards, even you?
No. The audit trail is hash-chained and the database refuses edits. The finished PDF is sealed with a key kept in AWS KMS hardware and timestamped by an independent authority. The seal is then anchored in a public log that's stamped into Bitcoin. Changing one byte breaks verification.
Who can see our clients' information?
Only the people involved. Documents are encrypted in the browser before upload, and we never store a key that opens them. Teams can require two-step sign-in and single sign-on, limit access to office networks, and see a security change log that can't be edited.
What if SealProof disappears?
Your records don't depend on us. A sealed PDF and its proof bundle verify with our open-source tool, offline, using our published key, the timestamp authority's certificate and Bitcoin. You can download everything at any time, by hand or through the API.
Everything you'd expect, and evidence others don't keep.
What a typical e-signature platform records, next to SealProof. We've included the one place we're behind.
| Evidence | Typical e-signature platform | SealProof |
|---|---|---|
| Signer name, email, IP address, device and timestamps | ✓ Standard | ✓ Every event |
| Consent to sign electronically | ✓ Standard | ✓ Exact wording recorded, per language |
| Consumer disclosure (ESIGN) | ✓ Commonly offered | ✓ Standard or your own text, and a fingerprint of the version each signer accepted |
| Document fingerprint (hash) | ✓ Common | ✓ SHA-256 of the original and the final PDF |
| Tamper-evident seal on the final document | ✓ Standard | ✓ Ed25519 seal; key in AWS KMS hardware |
| Independent trusted timestamp on every document | ~ Varies by product | ✓ RFC 3161, from an independent authority |
| Audit trail that can't be edited, even by the vendor | ~ Held in the vendor's system | ✓ Hash-chained; the database rejects edits and deletes |
| Public, append-only record of when each seal existed | — Not typically offered | ✓ SealProof Anchor, timestamped into Bitcoin |
| Free verification by anyone, with an offline open-source tool | ~ PDF signature check in a PDF reader | ✓ sealproof.io/verify and an open command-line verifier |
| Vendor can't read your documents (end-to-end encryption) | — Encrypted at rest, readable by the service | ✓ Encrypted in the browser; we can't read them |
| What the sender prefilled vs. what the signer entered | ~ Varies | ✓ Each field marked kept or changed |
| Photo ID and live selfie check | ~ Usually a paid add-on | ✓ Included allowance on Solo, Team and Business |
| PDF digital signature validated in Adobe Acrobat | ✓ Common | — Coming soon. Verify at sealproof.io/verify |
“Typical” reflects publicly documented features of widely used e-signature services. Features vary by product and plan, so check your current provider's documentation.
Check any SealProof document yourself, without us.
Verification doesn't depend on our servers or our word. Anyone can do it, free.
- Drop the PDF on sealproof.io/verify. Its fingerprint is computed in your browser, and the file is never uploaded.
- Or verify offline with our open-source command-line tool, the proof bundle and our published key.
- Check the timestamp against the independent authority's certificate. OpenSSL can read it.
- Check the anchor. The public log and its Bitcoin timestamps can be checked with the standard OpenTimestamps client.
The exact cryptography, and what each guarantee rests on, is on The math behind SealProof.
Insurance agency whose carrier asks for DocuSign or Adobe? See SealProof for carriers.
For security questionnaires.
Our policy lists approved e-signature tools. Can SealProof be added?
Do you have SOC 2 or ISO 27001?
Has SealProof had a penetration test?
Can SealProof staff read our documents?
Where is data stored?
How long are records kept, and can we export them?
Can we require two-step sign-in, SSO or office-only access?
Can Adobe Acrobat validate SealProof documents?
Can we use SealProof for health information?
Everything your review needs, in one PDF.
Tell us who's reviewing and we'll email an access code for the download, usually within one business day.
- Completed security questionnaire (CSA CAIQ-Lite)
- Security architecture and data flow
- Controls mapped to GLBA, NAIC and NYDFS questions
- Sample Certificate of Completion and verification steps
- Subprocessors, retention and incident response
Have your own questionnaire? Mention it below and we'll complete it too.