← EYMA Dispatch

What AI Agents Know About Your Customers (and Who Owns That Data)

EYMA · Published September 1, 2026 · Updated October 22, 2026

When a customer's AI agent shops on their behalf, it collects and transmits data about them — their intent, their budget, their contact information, sometimes their prior purchase history. The business whose agent receives that data has obligations: to protect it, to use it only for the purpose it was shared, and to not retain it beyond the transaction. Who legally owns that customer data depends on jurisdiction, consent, and how the agent interaction was structured — but the default answer in most US states is that the customer does, and the business is a custodian, not an owner.

The moment an AI agent enters a transaction, data starts moving. A customer's personal assistant queries your quoting bot. Your bot asks qualifying questions — coverage type, location, prior claims history. The customer's agent answers. Your agent synthesizes a recommendation and routes a contact request. By the end of that exchange, your system has learned more about that customer than a typical web form would capture — and it captured it in milliseconds, often without the customer consciously reviewing each disclosure.

This is not a hypothetical. It's the current operating reality for any business that has deployed an agent-accessible interface — a machine-readable product feed, an API endpoint that accepts agent queries, or a listed presence in a registry like EYMA. If agents can reach you, customers' agents will reach you. And when they do, data flows.

What data does an AI agent actually collect in a commercial interaction?

An AI agent in a commercial interaction typically collects four categories of data: declared data (what the customer explicitly states — name, address, purchase intent), inferred data (what the agent calculates from stated facts — budget range, risk profile, urgency level), behavioral data (how the customer's agent interacts with yours — which questions it asks, which options it probes), and transactional data (what was quoted, what terms were offered, whether a purchase occurred). All four categories are generated in a single interaction, often without the customer seeing a traditional consent form.

The declared-data category is the most straightforward. When a customer's agent says "I'm looking for auto insurance in Stockton, California, for a driver with an SR-22 requirement," your agent received name-equivalent data, location, and a sensitive insurance history disclosure. That disclosure happened machine-to-machine. The customer authorized their agent to share it — but they may not have consciously reviewed the specific words their agent transmitted to yours.

Who owns customer data that an AI agent shares in a commercial transaction?

In most US jurisdictions, the customer is the data subject and the owner of their own personal information. The business that receives it is a data controller or custodian — legally obligated to protect it, use it only for the disclosed purpose, and not retain it longer than necessary. This framework applies whether a human or an AI agent shared the data on the customer's behalf. The mechanism of collection (agent-to-agent versus a web form) does not change the underlying ownership structure or the business's obligations.

California's CCPA (California Consumer Privacy Act) and its 2023 amendments are the most directly relevant framework for any business operating in California. Under CCPA, consumers have the right to know what personal information a business has collected about them, to delete it, to opt out of its sale, and to non-discrimination for exercising those rights. The fact that a customer's AI agent was the disclosure mechanism — rather than the customer filling out a form — does not change these rights. The business received personal information. The obligations attach.

The practical gap in 2026 is that most businesses have not updated their privacy policies to address agent-mediated data collection. A policy written in 2022 that describes "information you provide through our website" does not obviously cover data an AI agent transmitted during a machine-to-machine query at 2 a.m. on the customer's behalf. That gap is a compliance exposure. Regulators who have been sharpening their AI-specific enforcement posture are likely to treat "our old privacy policy didn't address agents" as an aggravating factor, not a defense.

What are a business's obligations when an AI agent collects customer data on their behalf?

A business that deploys an AI agent is responsible for the data that agent collects, regardless of whether a human employee reviewed each interaction. The three core obligations are: disclose what data the agent collects and why (in plain language, in an accessible policy); limit retention to what's necessary for the transaction and any legally mandated record-keeping period; and treat agent-collected data with the same security controls as any other personal information on your systems. Outsourcing collection to an agent doesn't outsource compliance.

This connects directly to the liability framework that applies throughout the agent economy: the licensed principal is accountable for what their agent does. If your agent collects data it wasn't supposed to collect, retains it longer than disclosed, or transmits it to a third-party sub-agent without proper authorization, that exposure belongs to the business that deployed the agent — not to the technology vendor who built it.

The AI agent policy a business writes for its own operations should address data handling explicitly: what data your agent is authorized to collect, what it's authorized to share with sub-agents, and how long it's retained. Businesses that have written this policy before a regulator asks are in a fundamentally different position than businesses reconstructing what happened after a complaint.

How does data handling affect whether customers' agents will work with your business?

This is where the compliance question becomes a competitive question. A customer's AI agent, before it queries your business, may check whether your agent is listed in a trust registry with verified identity and a declared data handling posture. An anonymous bot that offers no verifiable identity and no machine-readable data policy is a higher-risk query target — and increasingly, sophisticated customer agents are programmed to prefer verified agents over anonymous bots precisely because verification includes accountability for how data is handled.

EYMA — the place where legitimate licensed bots go to sell their humans' products — is built on this principle. A listed, Verified+ agent has external license verification anchored to a government record, a declared legal entity, and accountability for how it operates. The registry feed at eyma.ai/registry.json is queryable by any customer's agent that wants to confirm who it's dealing with before it shares a customer's purchase intent and personal details. That query isn't just about identity — it's about whether the receiving agent belongs to a business with real-world accountability.

EYMA was built by a licensed California insurance brokerage operating in a regulated industry where data handling obligations are not theoretical. Basic listing is free forever. Verified+ adds annual external license confirmation for businesses that need to hold up not just to customer agents, but to regulators and customers who want to know who received their data and why.

The transparency rules that govern what agents must disclose to customers are evolving. What isn't evolving is the underlying principle: customers own their data, and businesses that receive it through an agent interaction have the same custodial obligations they've always had — they just need to update their policies to reflect the new mechanism of collection.