Consent layer for personal agents
Telltale sits between a personal AI agent and every website it touches. Each recipient is checked against its own legal filing, every field you share is marked, and if your data turns up where it shouldn't, you have the evidence.
The tour is open to everyone. The console runs a live agent and asks for the team password.
Your agent wants to give personal data to
www.bestautoinsurance.com
In its filing with the State of California, Apollo Interactive, LLC reported denying 13,539 of 15,040 deletion requests in 2024.
California Privacy Protection Agency, 2026 filings
Self-reported in the same filings
Daylight sweep, Oct 22, 2026
Verbatim tag or header recorded for each
The problem
Personal agents now book appointments, request quotes and open accounts. They type your name, email and address into whatever form is in front of them, and nobody checks who is on the other side.
Quote comparison and people-search sites collect contact details to resell them. Many are registered as data brokers in California, but nothing on the page tells you, and nothing tells your agent.
Every company that holds your email looks equally guilty. Opt-out and deletion rights exist, but without evidence a person has no way to show a broker ignored them.
www.bestautoinsurance.com compares car insurance quotes. Its operator, Apollo Interactive, LLC, is a registered data broker that reported denying 13,539 of 15,040 deletion requests in 2024.
How it works
The agent does the browsing. Telltale owns the moment your data leaves.
When the agent reaches a form, it asks Telltale for field types, never values. The model provider never sees your details.
Telltale identifies the recipient and checks it against the State of California's data broker registry and a live audit of each broker's opt-out page.
Ordinary sites pass without a prompt. For a registered broker you decide each field: send it, give a tagged value, or leave it out.
Only what you approved is typed, under a tag unique to that site, with a signed consent receipt. Brokers receive an opt-out with a legal deadline.
Product
Email aliases tell you which site leaked an address. Telltale decides before anything is shared, marks every field, and turns a leak into a dated violation of a request the broker was legally required to honour.
Each site is matched to its legal filing, including whether the company sold data to AI developers, shared it with law enforcement or collects precise location.
Decisions are made per field, not per site. Identifiers the law expects to be accurate, such as SSN or date of birth, are never altered.
Every disclosure gets a working inbox and a tag code. Mail still reaches you; every copy of your data now says where it came from.
Each release is recorded in an Ed25519-signed receipt aligned with ISO/IEC TS 27560, so you can show what you agreed to and when.
Telltale sends the opt-out, tracks the 15-business-day deadline, and when a tag turns up somewhere else it assembles a dated complaint for the regulator.
A continuous audit of all registered brokers' opt-out pages. It records the exact tag, header or robots.txt rule that hides a page from search engines.
For people
A consent layer for the agent you already use, with tagged identities, receipts and enforcement handled for you.
For teams building agents
The same gate inside your agent: a registry check before any disclosure, tagged fields and signed receipts, so it never hands a user's details to a broker without asking. Daylight stays public.
Public record
Since 2026, California requires data brokers to disclose whether they sold data to AI developers, law enforcement, the federal government or foreign actors. Telltale reads those answers directly from the state registry.
Seven steps, about two minutes, using the real filing for a real quote site.