vouchinkStart free

Compliance, in full, on every plan

We don't charge twice
for the law.

Every signature on vouch.ink — the free ones too — ships with the same ESIGN- and UETA-compliant evidence package. No "premium" audit tier. No "enterprise" hash chain. No paywall on the legal record.

A product of Novan LLC. Used by The Mindful Landlord.

What every signature ships with

Eleven things competitors gate.
All eleven, every plan, here.

01

Intent

Affirmative consent, captured per signer.

Each signer affirmatively clicks "I agree to sign electronically" before they ever touch a field. The consent event is timestamped, IP-stamped, and bound into the audit chain — separate from the signature itself.

ESIGN § 7001(c) · UETA § 5(b)

02

Attribution

IP, user-agent, and email-link binding on every action.

View, consent, field-completion, and final signing each capture the requester IP, browser user-agent, and the unique signed-link token that proves the action came from the invited mailbox.

UETA § 9 · ESIGN § 7006(5)

03

Tamper-evidence

SHA-256 hash chain, append-only.

Every audit row stores the SHA-256 of the previous row plus its own payload. Modifying any historical event invalidates every hash that follows. PostgreSQL triggers reject UPDATE and DELETE on the audit log table.

FRE 901(b)(9) · 902(13)

04

Document integrity

PDF SHA-256 hash, stored three ways.

When a document is finalized, the SHA-256 of the resulting PDF is written to the database, embedded in the audit chain, and printed on the Certificate of Completion. All three must match for the document to verify.

FRE 901(b)(4) · 1001(d)

05

Server-side time

Authoritative timestamps, never client-trusted.

Every audit event is timestamped on the server in UTC. We never accept a timestamp the client claims. The Certificate of Completion shows times in both UTC and the server-resolved local zone of each signer.

Standard authenticity practice for e-records

06

Per-page identity

Document ID stamped on every signed page.

Each page of the signed PDF carries the document ID, a short hash, and the page number in the bottom-right footer — so a printed page in a binder still ties back to the digital record.

Best practice for binder evidence

07

Certificate of Completion

Cover letter auto-attached.

Every finalized document has a multi-page Certificate of Completion appended: parties, timestamps, hash, IP per signer, and the full event history with chain integrity check.

Standard cover-letter practice for e-records

08

Retention & access

Originals retained, downloadable any time.

Both the original uploaded PDF and the signed PDF are retained in tamper-evident storage. Either party can request a copy. The Certificate of Completion is regenerable from the audit log if lost.

ESIGN § 7001(d) · UETA § 12

09

Withdrawal of consent

Decline path preserved on every document.

A signer can decline at any point before all signatures are gathered. The decline is captured as its own audit event — the document moves to "declined" status and cannot be re-sent without sender action.

ESIGN § 7001(c)(1)(B)(iii)

10

Hardware & software

No special tools required for the signer.

Per ESIGN § 7001(c), the signer must be able to access the document with reasonable hardware and software. We render in any modern browser — no app install, no plugin, no PDF reader required.

ESIGN § 7001(c)(1)(C)

11

Public chain verification

You can verify the chain by hand.

The audit-trail PDF lists every event hash in plain text. Anyone with the document and a SHA-256 utility can recompute the chain end-to-end. We have nothing proprietary in the verification path.

Independent verifiability — best practice

What others charge for

Compliance isn't a tier.

Every competitor in the e-sign market puts the legal record itself behind a higher plan. Here's what that looks like — and what we do instead.

CapabilityIndustry normvouch.ink
Audit trail PDFMid-tier or higher (typically $25+/mo)Free plan, full detail
Tamper-evident hash chainEnterprise-only on most platformsEvery plan, verifiable by you
IP and user-agent captureOften labelled "advanced authentication" — paidDefault on every signature
Certificate of CompletionAvailable — but PDFs of audit data start at higher tiersAuto-appended to every finalized PDF
Document expirationSometimes paywalled; often only "Business+"Configurable on every plan
Reusable templatesLimited templates on lower tiers (3–5)Every plan has templates; tiers gate count
Per-page document-ID stampingRare; usually a setting buried in adminOn by default, every plan
API accessAlways paid, usually a separate add-onTeam plan ($24/user/mo) — same trail format
Number of recipients per envelopeOften capped on lower tiersUncapped on every plan

Industry-norm column reflects publicly-listed plan structures of major e-sign vendors as of April 2026. Names omitted intentionally; the pattern is the point.

What we ship, plainly

The list, not the legal opinion.

  • ESIGN-compliant signing flow. Affirmative ESIGN § 7001(c) consent captured per signer before any field is touched, with the disclosure text version hashed into the audit log.
  • UETA-compliant intent + attribution. Each signer affirmatively clicks to sign; their IP, user-agent, and the unique signing-link token bind the action to a specific mailbox.
  • Hash-chained, append-only audit log. SHA-256 chain across all events; PostgreSQL triggers reject UPDATE and DELETE on the audit table.
  • Server-side timestamps. Every event timestamped on our server in UTC. Client-claimed times are never trusted.
  • SHA-256-sealed final PDF. The signed PDF's SHA-256 is stored in the document row, written into the audit chain, and printed on the Certificate of Completion. Three-way match required for verification.
  • Per-page document ID stamping. Every page of the signed PDF carries the document ID, a short hash, and the page number — printable evidence that ties to the digital record.
  • Certificate of Completion. Multi-page cover sheet with parties, timestamps, hashes, IP per signer, and full event history. Auto-appended to every finalized PDF.
  • Decline + withdrawal of consent path. Signers can decline at any point; the decline is captured as its own audit event and the document moves to declined status.
  • No special hardware/software for signers. Renders in any modern browser, no app install, no plugin.
  • Public chain verification. Anyone with the audit-trail PDF and a SHA-256 utility can recompute the chain end-to-end. Nothing proprietary in the verification path.

We're not lawyers and this isn't legal advice. We list what we capture; how a specific signature holds up depends on the document, the parties, and the jurisdiction.

How tamper-evidence works

Three SHA-256 chains.
Break one, break all three.

Chain 1

Audit log chain

Each row stores the SHA-256 of the previous row + its own canonicalized JSON payload. The very first event chains off a known genesis string per document.

this_hash = SHA-256(
  prev_hash
  + canonical_json(payload)
)

Chain 2

PDF integrity hash

When the final PDF is sealed, its SHA-256 is computed and stored in the document row, written into the audit chain as a "sealed" event, and printed on the Certificate of Completion.

signed_pdf_hash =
  SHA-256(final_pdf_bytes)

stored in:
  1. documents.signed_hash
  2. audit_log "sealed" event
  3. Certificate of Completion

Chain 3

Storage object hash

Supabase Storage independently records the object's ETag and content-hash. We compare against our stored value on every download — divergence triggers a chain-broken warning.

etag = storage.head(path)

assert etag.sha256
   == documents.signed_hash

Any modification to a single audit row, the PDF, or the storage object recomputes its own hash — and breaks every chain that follows. You can verify the entire chain from your dashboard with one click.

What we do gate

We tier on volume, branding, and API.
Never on the legal record.

Volume

Free and Pay-as-you-go cap at five documents per calendar month. Operator and Team are unlimited. Same audit trail on all four.

Branding

Operator and Team get your logo, your colors, your sender name on the signing page and the email. Free and PAYG sign on the vouch.ink page. The signature is the same; the wallpaper is different.

API & roles

The Team plan unlocks REST API access, multi-user organizations with role-based permissions, and webhook delivery for integration into your own systems. The audit trail those APIs return is identical to the one a free user gets in the dashboard.

Always free, every plan

ESIGN/UETA-compliant signing flow · hash-chained audit log · server-side timestamps · IP and user-agent capture · ESIGN § 7001(c) consumer consent · per-page document ID stamping · Certificate of Completion · SHA-256 PDF integrity hash · append-only database triggers · downloadable audit-trail PDF · public chain verification.

Plant the signature.
We grow the audit trail.

Five free documents a month. Full evidence package included. No credit card. Cancel by closing the tab.