LeadProof
Consent certification · patent-pending method

Prove what a consumer was shown
and did at the moment of consent.

When a TCPA complaint or a buyer dispute lands on a lead, a screenshot won’t hold up. LeadProof seals each consent event into a tamper-evident, independently-verifiable certificate — court-ready proof that travels with the lead.

No session replaySHA-256 hash chainRFC-3161 timestampIndependently verifiable
Get startedRead the API docs

How it works

01
Capture
Drop one script tag before </body> on your consent form. On submit, LeadProof records the exact consent language shown, the disclosures it links to, and behavioral + anti-fraud signals — and stamps a certificate ID onto the lead.
02
Seal
The record is reduced to a cryptographic integrity hash and anchored with an RFC-3161 trusted timestamp, so it is fixed to a moment in time and any later alteration is detectable.
03
Prove
Claim, verify, or defend a lead anytime. Generate a court-ready evidence package — one sealed PDF, one compound SHA-256 — independently verifiable without access to LeadProof.
Every capture is scored and tiered:Certifiedscore 85+Verifiedscore 70+Standardscore 55+

What you get

Automated compliance checks
Confirm rules run on every claim — 1:1 named consent, checkbox placement, phone/SMS disclosure, and your own custom checks — with no buyer action required.
Every lead carries its proof
A certificate ID rides with each lead. Buyers you sell to can claim it and independently verify the consent behind it.
Court-ready evidence package
One sealed PDF, one compound SHA-256 across every component, verifiable without access to LeadProof — with a cryptographically signed attestation when you need one.
A trust score you can price on
Each capture is scored from bot, behavioral, and page signals into a tier — Certified, Verified, or Standard.
Drift monitoring
Re-fetch a source later and see, side by side, whether the consent or disclosure language has materially changed since capture.
Disclosure archival
The documents your consent links to are fetched, archived, and hashed in a multi-layer chain — the full context, not just the checkbox.
Privacy by design
No session replay. Phone and email are one-way hashed at capture — we seal evidence, not personal profiles.
Form and call, one platform
Certify web-form and call consent through a single API and portal, priced by usage in credits.

Certify your first lead today.

Usage-based pricing in credits. No long-term commitment.

Get startedSee pricing