Privacy

Identity never travels.

An agent gets the least it needs. BotShield is independent of your company and of the agent: an agent carries a different ID at each company, never your customer’s identity, and BotShield never asks your customer for an ID.

FIDO Alliance memberFIDO Alliance member
Why the BotShield ID exists

Agents need something to bind to that is not the real identity. That is the BotShield ID.

The agent
Asks.The answer takes a passkey.
binds to
The BotShield ID
Pairwise, unique to your company.No other company sees the same one.
asks
The account holder
Answers with a passkey.On their own device.
The real identity stays here. BotShield never passes it to an agent.
With you
Your customer record.
With their account provider
The account.
On their phone
The passkey.

A phone number can be matched to a person. So BotShield never hands one to an agent, and keeps the number with no name beside it.

An independent yes

The party that wants a change shouldn’t be the one that says it was approved.

BotShield is separate from your company and from the agent, so the signed record stands on its own. BotShield never asks your customer for an ID.

Good practice · OWASP

“Limit access to sensitive data based on the principle of least privilege.”

And “require a human to approve high-impact actions before they are taken.” From OWASP’s 2025 list for applications built on language models. Source · Source  →

Two kinds of agent

Trusted by you. Verified by your customer.

Which agent is this?
A Trusted Agent.An agent you run, registered with its own key and the acts it may ask for.Live today
Is it a verified customer’s agent?
A customer’s agent.It belongs to a BotShield Verified customer. At each order, the BotShield Signal API answers verified, true or false.

Trusted Agents, on Agents Ask  →

BotShield Signal API · For agentic commerce

Know the agent belongs to a verified customer.

When an agent places an order, the wallet pays. One call to the BotShield Signal API tells you, fresh, whether the agent belongs to a BotShield Verified customer. The answer is verified, true or false, and nobody is asked.

The BotShield Signal API, in the docs  →The fields  →Poppy, in the docs  →

The wallet pays and you place the order; BotShield is not the checkout. It sits beside the payment rails (ChatGPT’s wallet, the Agentic Commerce Protocol, the Agent Payments Protocol, Visa’s Trusted Agent Protocol) and is not affiliated with or endorsed by any of them, or by the authors of Poppy.

What a BotShield ID stands on

What BotShield stores, named.

Stored

Five things.

The BotShield ID and the public half of its passkey.
Its bindings. Each company and each agent, and when.
Its history. Each ask answered.
One mobile number. Confirmed once with a texted code. Encrypted, with no name beside it. No company receives it from us.
The sign-in. An id from Apple or Google, and a one-way fingerprint of the email. The name and email they share are held for BotShield by our sign-in provider, as the privacy policy says.

Never stored

A document. A face. A location.

No government ID and no ID upload.
No Face ID data. It never leaves the device.
No location.

They answer with their passkey. None of it is for sale.

The account holder can remove any company or agent, and download or delete everything.

Questions

What is the difference between a Trusted Agent and a customer’s agent?
Who vouched for it. A Trusted Agent is one you run and registered, with its own key and the acts it may ask for. A customer’s agent belongs to a BotShield Verified customer, and the BotShield Signal API tells you at each order: verified, true or false. Your own support agent is the first. A customer’s own assistant is the second.
We already have agent identity from our identity provider. Is this the same?
They work together. Your identity provider tells your systems which agent is calling. BotShield shows your customer which agent is asking, tells you whether it belongs to a verified customer, and carries the account holder’s yes.
What does an agent hold about a customer?
A pairwise ID, never your customer’s identity. Your own agent carries a pairwise BotShield ID, unique to that agent. A customer’s own agent carries nothing that says who they are; at each order, the BotShield Signal API answers verified, true or false, and nobody is asked. Your company holds the pairwise BotShield ID it is bound to. No name, email address or phone number either way.
Which agents work today?
Your own agents, through the hosted MCP server, are live today.
Can the account holder end it?
Yes, from the BotShield app. They can remove any agent or company, and the next check answers false.

Give your agents something safe to bind to.

Verified customers, and the agents acting for them. Without identity traveling, or leaking to agents.

Start now

Sign in and take a sandbox key. The sandbox asks for nothing.

Get sandbox keys  →
Or have us reach out

Leave your work email. We usually reply the same day.