Urgent: Anthropic may introduce passport and selfie verification
The short version: Anthropic has sent privacy-policy update notices. Starting in July, some Claude users may be asked to verify their age or identity. For heavy Claude users, this means identity checks are no longer a theoretical possibility.
Anthropic is in the news again.
In recent days, many Claude users opened their email and found a message from Anthropic. The subject looked ordinary: a privacy-policy update notice. The surprising part was the wording that Anthropic may ask users to verify age or identity.
Screenshots of the email spread quickly on X, formerly Twitter, and the comments filled with concern.
According to the wording discussed by users, starting July 8 Claude may require identity verification in some cases.
Does this mean mandatory verification has arrived for Anthropic users? The answer is more nuanced.
Anthropic makes an official policy update
Around June 10, many users received emails about changes taking effect in July. The message said Anthropic may request age or identity confirmation as part of safety and compliance measures.
Some users received the notice on one account but not another. That suggests a staged rollout, regional difference, account-type difference, or A/B-style notification pattern.
Three changes stand out in the updated policy discussion.
1. Data sharing during multi-step tasks and integrations
As Claude becomes more agentic, it can perform complex multi-step tasks for users: planning trips, working with documents, connecting to third-party services, or coordinating data across tools such as Google Drive, Slack, and Notion.
That means data may no longer stay only inside Anthropic's environment. When users connect services or ask Claude to act on their behalf, information can move between the user, Anthropic, and third-party applications.
For ordinary users, the takeaway is simple: the more agentic the AI becomes, the wider the digital footprint can become.
2. The explosive point: identity verification
The most discussed clause is verification. Anthropic may ask users to confirm age or identity. In practice, this could involve a third-party verification provider, identity document checks, selfie checks, or similar flows.
This does not necessarily mean every user will be asked for a passport immediately. It does mean the policy gives Anthropic room to require verification when it believes the account, region, product, or use case requires it.
For users who rely on Claude daily, that is an operational risk. A workflow that depends on uninterrupted Claude access may be disrupted if an account suddenly needs verification.
3. Why AI agents make verification more likely
Claude is no longer only a chatbot. Claude Code, Claude Desktop, connectors, browser-related workflows, and agentic task execution all expand what the product can do on behalf of a user.
When a model can read files, interact with services, and execute multi-step instructions, platforms face stronger pressure around abuse prevention, age compliance, fraud prevention, and account accountability.
Identity verification is one response to that pressure.
What Persona has to do with it
Some reports connect the flow with Persona, a third-party identity verification provider. Persona-style verification commonly asks for a document, selfie, or other identity evidence, then returns a verification result to the platform.
For users, the practical question is not only "will Anthropic see my passport?" It is also:
- which provider processes the verification;
- what data is collected;
- how long it is retained;
- which regions are affected;
- what happens if verification fails;
- whether business and personal accounts are treated differently.
Those details matter more than the headline.
What users should do now
Do not panic, but do prepare.
If Claude is a critical tool for your work:
- check the email address attached to your account;
- keep account recovery options current;
- avoid violating platform policy;
- do not rely on a single personal account for team operations;
- document backup workflows for coding agents and API tools;
- separate personal experimentation from production work.
If identity verification appears, read the flow carefully before submitting documents. Check the domain, provider, privacy notice, and whether the request appears inside an official logged-in product flow.
What this means for developers
For developers using Claude Code or other agents, the risk is not only chat access. It is workflow continuity. A blocked account can interrupt:
- repository work;
- code review support;
- document processing;
- agent tasks;
- integrations;
- team automation.
API-based access and provider gateways may reduce some operational friction, but they do not remove all platform-policy risk. Teams should understand which account, provider, and billing path each workflow depends on.
The bigger trend
The more AI products act on behalf of users, the more they will look like infrastructure. Infrastructure attracts compliance, identity, abuse prevention, logging, and enterprise controls.
That does not mean every user will verify identity tomorrow. It does mean AI accounts are becoming more like financial or cloud accounts: valuable, sensitive, and governed by stricter rules.
Bottom line
Anthropic's policy language does not prove that every Claude user will immediately need passport verification. But it does show the direction of travel. Age and identity checks are becoming part of the AI platform toolkit.
If you use Claude casually, keep an eye on notices. If you use Claude for work, treat account access as operational infrastructure: document ownership, recovery, backup providers, and what to do if a verification prompt appears at the worst possible time.