Verify with BotShield.
Built on passkeys.

By architecture. The account is linked in a chain to an identity root the person already holds: Apple or Google attest the root, the root holds their BotShield ID, and the ID links the account on your platform. Each answer is a passkey ceremony on their own phone — the check that unlocks it never leaves it. What reaches you is a signed yes scoped to your company alone, keyed by an opaque ID. No name, no email, no document; nothing about them travels the chain.

A gate sent to one person, or an ask placed in front of them. Both land in the BotShield app on the phone they already hold and are answered with a passkey. Nothing is sent over a carrier, so there is nothing to forward, read aloud or intercept — and nothing to meter but the answer.

Every account that verifies carries one BotShield ID, and an ID links one account on your platform. A second account for the same person takes a second ID, which takes a real device, a real root and real time. We raise the cost; we never claim it is impossible.

No. Your sign-in stays exactly as it is. Open BotShield is one button behind it, a gate is a tag on a page, an Action is a passkey on one act. Nothing moves onto our rails.

Yes, on the acts you let it. A registered agent proposes; the person answers on their own device; a signed Proof of Resolution comes back before anything runs. None of the five tools can say yes, and the default is always no.

Five things, named: the BotShield ID (the person’s own root), an opaque ID per link, gate sign-ups as opaque keys against a deal, a count never a roster, and a verified number only where a gate asked for one. Gate verdicts are kept 90 days, then deleted.