TCPA consent evidence
Capture the consent moment as it happens. On the form, on the call, in the thread.
eConsent records the consent event as it happens and signs it into a tamper-evident certificate you can defend with carriers, lead buyers, and regulators. Web forms, live calls, and AI voice agents all write to the same evidence record.
HMAC-SHA256 signed · 7-year S3 Object Lock retention · Export as PDF, JSON, or shareable URL
Engineered for evidence
Compliance teams don't need another dashboard.
They need a record built to withstand scrutiny.
Every claim below is a property of the record itself, not a policy we promise to follow.
- 01 Cryptographically signed Each certificate carries an HMAC-SHA256 signature over the consent and disclosure data. Alter a field and the signature stops matching.
- 02 Immutable for seven years Records land in S3 Object Lock under COMPLIANCE mode. Nobody deletes them early, including us.
- 03 Verified in milliseconds Consent and revocation checks answer fast enough to sit inline in a form submit or a dialer's pre-call path.
- 04 One record across channels A web form and a recorded call resolve to the same consumer and the same audit trail.
The platform
Capture, certify, verify, and defend.
Web capture, voice consent, verification checks, certificates, replay, revocation, and partner handoff, in one evidence layer.
Replay the consent event exactly as it happened.
Full form context, disclosure state, clicks, scroll, field input, traffic source, and device details, attached to the certificate.
A tamper-evident certificate for every lead.
Hash, retain, and export consent records with attribution, disclosure text, channel, replay, and revocation history.
- Certificate
- cert_8K29-F1A7
- Signature
- Verified
- Channels
- Web, Voice
Capture consent while the call is still happening.
Record verbal permission during a live call or an AI voice-agent conversation, then attach call metadata, the transcript marker, agent identity, and post-call evidence to the same certificate.
- Call state
- Consent captured
- Transcript marker
- 00:42
- Evidence
- Certificate linked
Verify consent before you engage.
Check a consumer's consent status in milliseconds with the Verification API. Confirm channel, disclosure, and revocation state before a call or form submission.
- Response time
- <100 ms
Revocation center
Opt-outs, suppression events, bulk revocations, and downstream partner notifications in one audit trail.
Inspector
See which fields get captured, masked, or ignored before a form goes live.
- Full name
- Captured
- Captured
- Date of birth
- Masked
Why eConsent
Consent doesn't only happen on a web form.
It happens on web forms, in live calls, and in AI agent conversations. Evidence that covers only one of those has a hole in it.
One platform, two channels
Web forms, live voice, and AI agents write to the same certificate, wallet, and audit trail.
Published, usage-based rates
Public per-certificate pricing. Subscribe once volume is predictable, and pay the same posted rate on overage.
Evidence built for discovery
Signed certificates, session replay, transcript markers, and Object Lock retention, exportable as a single packet.
One script tag, or the API
Drop in the tracker or call the API directly. Webhooks, verification endpoints, and documented payloads.
Operations
A working surface for compliance, not a folder of screenshots.
Review certificate volume, inspect properties, confirm API activity, and export records without moving between tools.
AI voice consent
The consent layer AI voice agents are missing.
Call centers and AI agents can verify consent before dialing, capture verbal permission during the call, and attach the proof to a certificate your team can export. Web-form-only certification leaves this entire channel undocumented.
- 01 Pre-call verification
Check consent, revocation state, source, and permitted channels before the dialer connects.
- 02 Verbal capture
Mark the moment permission is given in a live call or an AI voice-agent transcript.
- 03 Evidence packet
Attach call metadata, the transcript marker, certificate, replay, and audit trail.
Exposure check
What is the risk sitting in your current call volume?
A rough sizing, not legal advice. The point is that statutory damages scale with volume, so consent proof has to exist before outreach does.
- Monthly outreach
- 50,000
- Claims at 0.5%
- 250
- Statutory exposure
- $125k+
Start where you are
Which of these is you?
Where it sits
Between your lead sources and everyone who needs the proof.
eConsent captures consent at the source and delivers the record to the systems and people who have to answer for it.
Sources
Destinations
Implementation
Start with web capture. Add channels when you're ready.
The tracker starts recording consent events on the next page load. Verification, revocation, partner delivery, and routing are API and webhook calls you can add later.
<script
src="https://cdn.econsent.org/cdn/scraper.min.js"
data-company="YOUR_COMPANY_ID"
data-property="auto"
></script>