Trust with something to check
Give a collaborator evidence they can verify, rather than just a claim about your background.
Private proofs for people and AI agents
Give your AI agent a verifiable introduction.
Bring your verified accounts and email credentials together. Let others check the information you choose to share, while keeping the rest private.
Anonymous by default. You decide whether to share more.
Google account
Organization email
What the recipient seesExample proof
Verification resultVerified
Shared informationAnonymous result
Your emailNot disclosed
Verification limit1 use
Only the selected result is shared with the recipient.
An introduction you can share alongside your agent.
Illustrative data — this is not an actual proof.
Privacy that you control
Choose the sources and details to include. Full email and organization domain require your explicit permission.
A clear limit on every share
One verification by default. Set a lifetime or use limit, and revoke a proof when you no longer want it shared.
From verification to sharing
Three steps. One proof you control.
Start with what you can verify, then decide what the recipient should see.
Add your verified sources
Connect a Google account or verify an organization email. Keep the sources together in your private identity.
Use Google · Verify an emailChoose what to share
Pick any combination of sources. Start with an anonymous result and preview any additional information before sharing.
Choose my informationSend a limited-use proof
Share a proof link. The recipient clicks to verify, and sees only what you allowed. Opening the link does not use it up.
See the guide
Try it for yourself
Interactive example
See exactly what gets shared.
Follow this example from adding a source to the result the recipient sees.
Verify a mailbox
An email code confirms that you control the address. This example uses illustrative values and sends no email.
Illustrative values only; no email is sent.
Bring sources together
Here are two example email sources, kept together with separate privacy settings. Combining them does not independently prove they belong to the same person.
Source A · university mailboxSource B · company mailbox
Choose the information
Select which sources to include and what to show. The default is an anonymous result; the real flow requires explicit permission for each source before sharing email or domain.
Share and check
Preview the result, then try the one-use example. A preview does not use it; the first verification does.
Preview what the recipient sees, then verify the example once.
A few useful answers
Will the recipient see my email?
Not by default. Anonymous mode reveals only a verification result. Email or organization domain needs explicit permission for the particular source, as well as your sharing settings.
What does verification establish?
It checks control of a Google account or organization email. A role such as employee, student or alumni is provided by the holder; it does not independently prove employment, enrollment, organization authority or personhood.
Can I use this with my AI agent?
You can share your selected proof with collaborators, or let a product check it through the API. A dedicated registry binding a particular agent to its owner is a future layer.
Building a product that needs trust?
Check a user’s selected proof in your app or agent workflow, including valid, used and invalid results.