Missing
The form fired, the lead landed, and the consent language never traveled with it. You have a phone number and a hope.
Built for lead gen, demand gen and AI agents
Fast automations.
Need brakes that Hold Up in Court
Your workflows text in seconds and your AI agents call back in four. ConsentVault proves every one of those contacts was agreed to, in the exact words, at the exact moment, sealed by someone outside your company.
Append-only by designOutside timestamp sealsNo row, no ring gateEvery stop, every channel
What one “no” costs
Per message. Not per person.
One workflow texts 2,000 people it cannot prove consent for. That is 2,000 × $500 = $1,000,000. One list, one bad Tuesday. And when a plaintiff says “I never agreed,” the burden of proof sits with the company that sent the message.
$500per call or text under the TCPA
$1,500per message if a court finds it willful
4 yearsthe federal window a plaintiff has to sue
1,052TCPA class actions in H1 2025, up from 539 a year earlier
$61 millionDish NetworkA vendor dialed Do Not Call numbers. The court found it willful and trebled the award. The vendor dialed; Dish paid.
$75.5 millionCapital One and three agenciesAutodialed and prerecorded calls to cell phones.
~$47 millionJiffy Lube franchiseeAbout 2.3 million marketing texts without written consent.
$1,994,123Colony Ridge DevelopmentMarketing texts to numbers on the Do Not Call Registry.
The problem
Four ways consent dies
Every team believes it has consent. Very few can prove it in the form a court accepts.
Mutable
Consent lives in an editable field. A rep, an import or a vendor changes it and nothing records that they did. In discovery, mutable reads as made up.
Mismatched
The person agreed to hear from one brand and a different brand called. Or the disclosure changed in March and nobody kept February’s version.
Muted
The person said stop, by text, voicemail, email or to a rep, and the system that dials never heard it.
If your consent proof is a screenshot someone took last week, you do not have consent proof. You have a screenshot.
The odometer problem
Your CRM checkbox is an odometer
Buying a used car, you never trust the odometer by itself. You trust the title history: every sale, the mileage written at that moment, stamped by a party with no stake in the number. ConsentVault is the title history.
The CRM checkbox
- One editable field
- Overwritten on every import
- No record of who changed it
- No copy of what the person saw
- Proves what the database says today
ConsentVault
- One sealed row per event
- Append-only, never overwritten
- Every change is a new row
- The exact disclosure, fingerprinted
- Proves what was true then, to a stranger
How it works
Five properties make a register outside
A register earns the word “outside” when it has all five. Four out of five is a nicer CRM.
Append-only
Nothing is updated or deleted. A correction is a new row that points at the old one, enforced in the database, not in a policy document.
Chained
Each row carries the fingerprint of the row before it. Change any old row and every link after it breaks.
Outside-sealed
The chain is signed by an RFC 3161 timestamp authority you do not control. Only a fingerprint leaves your systems, never the person.
Self-describing
Every seal names the exact fields it covered, so adding a column next year never makes old evidence read as tampered.
Re-verified daily
Every link and every seal is re-checked every day and fails loudly, by name, the same day. A seal nobody checks is a seal nobody can testify to.
Try it: click any block to edit its record, then watch what the chain says.
Chain verified. 5 events, every link matches, all 3 outside seals check.
The lifecycle
Capture. Seal. Gate.
Honor. Prove. Retain.
- 01
Capture
Write the event at the click, from the server. The exact disclosure is stored once, versioned, and fingerprinted on the row. Unchecked box by default, sellers named in plain words.
- 02
Seal
Each row is chained on insert and the chain is sealed by an outside timestamp authority on a schedule. Receipts are kept where a single admin cannot delete them.
- 03
Gate
Before any call, text, voicemail drop or AI conversation, the sender asks one question: is there an unrevoked consent for this person, this channel, this seller, right now?
- 04
Honor
Every place a person can say stop writes a revocation to the same register. Target minutes, not the ten business days the rule allows.
- 05
Prove
One person, one evidence pack: every event in order, the words behind each fingerprint, the seal receipts and every gate decision.
- 06
Retain
At least four years past the last contact. Third-party session certificates expire unless claimed; ConsentVault keeps your own copy.
AI agents
No row, no ring
A human rep makes one bad call. An AI agent makes four thousand before lunch. The gate sits in front of every agent you run.
- 1
Deny by default
The agent cannot start a conversation without a fresh gate decision naming the consent it relies on. If the register is unreachable, the answer is no. A gate that fails open is not a gate.
- 2
AI voice is its own scope
Consent to calls is not automatically consent to an AI voice. It is captured explicitly, named in the disclosure, and announced at the start of the call.
- 3
Agents read, never write, consent
An agent can record that a person said stop. It can never create or restore a consent. Grants come from capture, with their own credentials.
- 4
Every stop phrase, every channel
“Take me off your list.” “Don’t call me again.” Transcripts are scanned for revocation language and the stop is written before the call ends.
What attacks a consent pipeline with AI in it
Prompt injection through a form field
ControlForm fields are untrusted data; the model that reads them has no tool that can change consent.
Hallucinated consent
ControlConsent is a lookup in the register, never a model’s judgment of a friendly transcript.
PII sprawl
ControlKeyed fingerprints in the ledger; the raw number lives in one governed store.
Shadow tools
ControlA written data-tier rule for what may enter which AI tool, and an approved-processor list.
The rules keep moving
Store the words, the moment and the scope. Survive every rule change.
- Feb 2024
The FCC rules AI-generated voices are “artificial” voices. An AI voice agent calling for marketing needs prior express written consent.
- Jan 2025
The Eleventh Circuit vacates the one-to-one consent rule. The seller list on your form is still your evidence.
- Apr 11, 2025
Consumers can revoke by any reasonable means. STOP, QUIT, END, REVOKE, OPT OUT, CANCEL and UNSUBSCRIBE all count. Ten business days to honor.
- Jun 2025
McLaughlin v. McKesson: courts no longer owe deference to the FCC’s reading. Agency guidance is no longer a shield. Your evidence is.
- Sep 1, 2025
Texas SB 140 treats marketing texts as telephone solicitation and opens a private right of action.
- Oct 1, 2026New
The FCC replaces revoke-all. Informational messages can be opted out by category. Marketing got no relief: one opt-out stops all telemarketing, affiliates included.
One build, two exams
The same register is your ISO/IEC 42001 evidence
If your AI touches consumers, the consent register is a large share of what an AI management-system auditor asks for. Certification is a management-system audit, not a product badge: the auditor wants the rule, the owner, the evidence and the check that runs when nobody is looking.
Annex A areaWhat the auditor asksWhat the register shows
A.2 PoliciesIs there a written rule for how AI may contact people?The gate rule: no row, no ring, deny by default.
A.3 OrganizationWho owns it, and who can change it?Named owners for capture, gate and revocation; separate credentials for writing grants.
A.5 ImpactWhat happens to people if it goes wrong?Unwanted calls and ignored opt-outs; the gate and revocation path are the treatment.
A.6 Life cycleIs it tested and monitored?Daily re-verification, gate decision logs, revocation time tracked.
A.7 DataWhere did the data come from, and can you prove it?Provenance per event: words, moment, scope, source, outside seal.
A.8 TransparencyAre people told what is happening?The disclosure library and the AI-in-use announcement at call start.
A.9 UseIs AI used only for its intended purpose?Agents read consent and write stops, never grants.
A.10 Third partiesAre vendors and lead sellers controlled?Ten vendor questions, certificates and contract terms per source.
The 10-minute proof drill
Run it Monday. It beats any demo.
Pick one phone number you texted or dialed last month. Start a timer. Then answer these four:
Tick what you could produce in under ten minutes today.
Level 4GatedEvery dialer, texter and AI agent asks first. Evidence pack in under ten minutes.
Level 3SealedChained, outside-sealed, re-verified daily, seals name their columns.
Level 2LedgerAppend-only events, stops as rows, one register for every channel.
Level 1CaptureYou store the disclosure text and a timestamp at the click.
Level 0HopeConsent is a field. Nobody knows who can edit it.
You are at Level 0: Hope. ConsentVault is built to get you to Level 4.
Where ConsentVault fits
Buy the witnesses. Own the register.
Witness
Session certificates such as TrustedForm or Jornaya record the session as an independent witness. They are not your system of record. ConsentVault claims and keeps the copy you rely on.
Seal
RFC 3161 timestamp authorities sign a fingerprint of your chain. Pennies per seal, and the person’s data never leaves.
Register
The ledger, the gate and every stop path, owned by you, exportable by you, touching every system you send from. Never let the only copy of your evidence live in someone else’s account.
Your consent record is an odometer. If you can roll it back, so can the jury’s imagination.
For growth teams
Keep the speed. Lose the exposure.
- Every dialer, texter and AI agent checks one register first
- Stops from every channel land in minutes
- Bought leads arrive with their evidence, or not at all
For compliance and counsel
Evidence a stranger accepts.
- The exact words, moment and scope behind every contact
- Outside-sealed, append-only, re-verified daily
- One evidence pack per person, ready for a demand letter
Who builds it
Michael Soto
Fractional Chief AI Officer · The Innovative Native
Twenty years in growth marketing, now building the infrastructure underneath it. ConsentVault started as the consent register behind a real lead-gen operation, built after the hard way taught the five properties. One of those lessons: I added one column, and the next morning my own daily check called 203 sealed records tampered. Not one had changed. Every seal now names its columns. Nothing reads as tampered unless it was.
“There is a difference between using AI and having AI run your business. The difference is the evidence.”
Frequently asked
ConsentVault, explained
What is an outside consent register?
An append-only ledger of consent and revocation events, where each event is hash-chained to the one before it and sealed by an independent party, so the record can be verified by someone who does not trust the company that keeps it.
Is ConsentVault available today?
ConsentVault is in early access. The method runs today on a working consent register behind a real lead-gen operation; we are hardening it and packaging it for other teams now. Join early access and you will hear first when onboarding opens.
Does ConsentVault replace TrustedForm or Jornaya?
No. Session certificates are witnesses, and good ones. ConsentVault is the register: it keeps your own copy of what you rely on, adds every stop from every channel to the same chain, and gates every send against it.
Does personal data leave my systems for the seal?
No. Only a fingerprint (a SHA-256 hash) of the chain goes to the timestamp authority. The person’s phone number and email never leave.
What about AI voice agents?
AI voice is its own consent scope. The gate denies by default, agents can write stops but never grants, and every revocation phrase in a transcript is written to the register before the call ends.
How does this help with ISO/IEC 42001?
The register is documented evidence for policy, ownership, data provenance, monitoring and third-party control for one of your highest-risk AI uses. It supports an audit; it is not a certification.
Is this legal advice?
No. ConsentVault provides operations and direction behind decisions toward compliance. We are not legal counsel. Have your counsel review your disclosures and contact rules.
Early access
Stop proving consent with a checkbox. Start proving it with evidence.
Join early access for ConsentVault. You also get the free field guide: the event schema, the five properties, the 10-minute drill and a 30-day build plan.
The Outside Consent RegisterFree field guide, October 2026 edition. PDF, no email needed.