First-person forum account: a long-time Character.AI user who says they are an adult says the app's AI age verification, run through Persona, kept judging them a minor despite ID photos, answered more than five support tickets only with automated replies, and locked them out of their account
In a public post to r/CharacterAI at 21:47 UTC on 2 October 2026, a person who describes themselves as a veteran user of the Character.AI app says they returned about a month earlier to verify their age, and that the AI verification by Persona assumed they were a minor although they are not. They say they sent photos of their ID, tried desktop and different lighting, and kept getting an error message; that more than five support tickets asking for manual verification drew only replies from automated bots; and that the age verification system has now locked them out of their account. In a reply they say the system should identify people properly instead of "locking it out on permenent basis". A commenter says the same check called them underage. The account is uncorroborated, and Character.AI's and Persona's handling is described only by the poster.
- AI system
- Character.AI age verification
- Character.AI
- Occurred
- 2 Sept 2026 to 2 Oct 2026
- Reported
- 2 October 2026
- Event location
- Unknown
- What the AI did
- Made a decision about the person
- Reported harm
- Other Material Harm
- Whose AI use
- An institution’s AI use
- Setting
- Everyday life · Privacy
- Evidence
- AI involvement reported · Causal attribution alleged · 1 source
- 3 claims: 3 reported. 3 open questions
- People reported harmed
- 1 person
AI system as recorded: Character.AI's age verification, which the poster says is an AI verification run through Persona, plus automated support replies to the poster's tickets
What Happened
The check. The poster says they had used the Character.AI app for a long time, left for a few months after its age verification system was introduced, and "came back a month ago to verify my age". They write that "the AI verification by Persona and the system is severely faulty" and assumed they were a minor, which they say they are not.
Attempts. They say they sent photos of their ID, tried verifying from a desktop, cleared the cache and adjusted lighting and position as others had advised, but the verification system kept sending an error message and remained "adamant on assuming me as a minor".
Support. The poster says they sent more than five support tickets asking for manual verification and received only replies "from their automated bots".
Lockout. They write that "now the age verification system has locked out from my account". In a reply they say that if the system is used it should identify people properly "instead of just making assumptions and locking it out on permenent basis".
Limits. Single uncorroborated account. The post's three screenshots show an "Unable to verify age" error over the app's profile, library and settings screens. The post does not say what the lockout covers, what age the system estimated, or what the poster's age is. Persona's role is the poster's description.
Reported harm
The poster says Character.AI's AI age verification through Persona wrongly judged them a minor, that support tickets drew only automated replies, and that the system locked them out of their account (first-person account, uncorroborated).
Outcome
OngoingThe poster asks the subreddit's moderators or the developers to resolve the lockout. In replies, one commenter says the check also called them underage and that they moved to other apps; another suggests opening a new account with a false birth date. No response from Character.AI or Persona is reported.
What remains unknown
- The exact dates of the verification attempts and the lockout; the post says the poster came back 'a month ago'.
- What age the system estimated, the poster's actual age and what the lockout covers. The post's screenshots show the app's profile, library and settings screens still open beneath the age error; the post does not say whether they were taken before the lockout.
- Whether Character.AI or Persona has reviewed the tickets.
What the evidence supports
AI involvement: reported. The poster says Character.AI's age verification is an AI verification by Persona and that it repeatedly assumed they were a minor. The post's three screenshots show the app's "Unable to verify age" error with a prompt to contact support; they show no age estimate, no vendor name and no lockout notice. No company statement was published.
3 claims: 3 reported. What the statuses mean
Reported The poster says they returned to Character.AI about a month before the post to verify their age and that the AI verification by Persona assumed they were a minor, which they say they are not.
Causal attribution. Poster's account; the poster's age is not documented.
- reddit.com(opens in new tab) supports · English
'came back a month ago to verify my age'; 'the AI verification by Persona and the system is severely faulty'; 'adamant on assuming me as a minor'
Reported The poster says they sent ID photos and the verification system kept returning an error, and that more than five support tickets drew only replies from automated bots.
Causal attribution. Poster's account.
- reddit.com(opens in new tab) supports · English
'photos as well but the AI verification system keeps sending the error message'; 'replies from their automated bots'; 'I think it has been more than 5 tickets already'
Reported The poster says the age verification system has locked them out of their account and, in a reply, complains of the system "locking it out on permenent basis".
Causal attribution. Poster attributes the lockout to the AI age verification.
- reddit.com(opens in new tab) supports · English
'now the age verification system has locked out from my account'; reply by the poster: 'locking it out on permenent basis'
Sources
1 source inspected. Sources that repeat one account do not corroborate each other.
- r/CharacterAI, 2 October 2026: "Age verification"(opens in new tab)
s1 · reddit.com · Forum post · English · Inspected · 2 October 2026 · Primary
How the sources were read, and where the events happened
Read in English on 2026-10-03: full self-text, the post's three screenshots and the thread's 4 comments, two of them replies by the poster, retrieved through the arctic_shift archive API by post ID and from i.redd.it. The poster handle and the display name visible in a screenshot are not recorded. Applies to s1.
Event countries: Unknown. Affected-person countries: Unknown. Court countries: Unknown.
The post does not say where the poster lives. Unknown after review.
Reviewed for publication 2026-10-03: Published under the 2026-09-15 charter's public-forum rule as a concrete first-person account of an adult locked out of an account after an AI age check judged them a minor, described with attribution and without corroboration. The poster's handle is not recorded.
People described
The poster, a long-time Character.AI user who says they are an adult (age and country not stated)
People reported harmed in this case
1 person
1 AI participant · 0 other people harmed
One person: the poster. A commenter who says the check also called them underage gives no further detail and is not counted. Exact 1.
Counted once within this case. The same person may appear in other cases. This count does not establish AI causation.
Tags
Cite this case
Compiled per our published methodology: verification statuses, sourcing standards, and corrections process.
APA
NOPE. (2026). First-person forum account: a long-time Character.AI user who says they are an adult says the app's AI age verification, run through Persona, kept judging them a minor despite ID photos, answered more than five support tickets only with automated replies, and locked them out of their account. AI incidents. https://nope.net/incidents/2026-characterai-age-verification-judged-adult-user-a-minor-account-locked-first-person
BibTeX
@misc{2026_characterai_age_verification_judged_adult_user_a_minor_account_locked_first_person,
title = {First-person forum account: a long-time Character.AI user who says they are an adult says the app's AI age verification, run through Persona, kept judging them a minor despite ID photos, answered more than five support tickets only with automated replies, and locked them out of their account},
author = {NOPE},
year = {2026},
howpublished = {AI incidents},
url = {https://nope.net/incidents/2026-characterai-age-verification-judged-adult-user-a-minor-account-locked-first-person}
} Related cases
Ray-Ban Meta glasses owner says Meta AI stored recordings and transcripts of conversations captured without the wake word; Meta says the issue is resolved
In a Reddit post on 13 October 2026, an owner of Ray-Ban Meta smart glasses says the glasses captured conversations they were having with another person although they had not said the wake word "Hey Meta" and the setting for responding without it was turned off. The owner says the Meta AI app saved audio recordings and text transcripts of these conversations in their history, that Meta AI never answered, and that they saw the same behaviour on three pairs (second and third generation) after a recent firmware update. A screenshot attached to the post shows the app's voice activity log with stored entries dated 12 October. The owner says Meta Support advised turning off microphone and camera permissions, Wear Detection and automatic updates and deleting voice history, and later replied that recording continued with everything turned off. On 16 October 2026, after Meta's statement, the owner replied that a new update had been pushed to their glasses and the issue was unchanged. A Meta spokesperson told Android Authority, as relayed by Futurism, Ars Technica and Mashable, that the issue had been resolved. Ars Technica reports that Meta has not said what caused the recordings or how many glasses were affected, and that Android Authority could not reproduce the problem before Meta's statement. The owner says they cannot establish whether the recordings were sent to Meta's servers. On 19 October 2026 a California buyer filed a proposed class action against Meta in federal court (Subia v. Meta Platforms) alleging that Meta AI glasses recorded his conversations without the wake phrase, in violation of California's wiretapping law; the complaint quotes reporting of this owner's three-pairs account. Its allegations are unproven.
Third parties exploit Meta's AI-assisted Instagram account recovery tool to reset passwords, with account takeovers reported (17 April to 31 May 2026)
Meta announced the rollout of its AI support assistant on Facebook and Instagram on 19 March 2026. Meta's filing with the Maine Attorney General (notice dated 5 June 2026) says unauthorized third parties exploited a vulnerability in its AI-assisted Instagram account recovery tool (High Touch Support) to receive password reset links for accounts they did not own, and the listing gives 17 April 2026 as the breach date and 31 May 2026 as the discovery date. Videos that attackers posted, as described by TechCrunch, 404 Media and Krebs on Security, show attackers asking the assistant in a chat to link a new email address to a target username. Reported victims include the security researcher Jane Manchun Wong, who posted that her password was changed without her knowledge, the Instagram account of the U.S. Space Force's Chief Master Sergeant, and the accounts of Sephora and a dormant Obama White House page (TechCrunch marks the last as disputed by Meta). Krebs and the BBC report pro-Iran defacement of some accounts, and TechCrunch reports that some victims were locked out and that short handles were offered for resale. The filing gives 20225 persons affected in total and 30 in Maine, and the notice calls the Maine figure an upper bound. Meta says the tool worked as intended, that a bug in a separate code path failed to check the email address, and (through a spokesperson to Gizmodo) that the failure was not due to the AI agent itself. Meta says it disabled the tool on 31 May 2026, the day it discovered the exploitation.
Adult ChatGPT Plus subscriber says the account was classified as a teen and restricted, and that OpenAI said profiling had to come first; first-person post
In a Reddit post of 11 October 2026, a ChatGPT Plus subscriber who says they are an adult (36, by the post's own account) writes that when OpenAI's age checks rolled out their account was classified as a teen account and put on a restricted account. The poster says they had earlier emailed OpenAI asking for verification options without ID or a photo, received a canned reply about the verification provider Persona, and on escalating to data protection was told they had to be profiled first. The poster says they then cancelled the subscription. OpenAI's Help Center says ChatGPT uses an age prediction system that reads account signals, automatically enables the teen experience when it predicts an account may belong to someone under 18, can get this wrong, and lets adults verify their age to remove it. The account is the poster's own and is not corroborated.
AI governance adviser says Gemini in Google Drive summarised his tax return unrequested while its summary setting was off; Google says users must enable Gemini
In a thread on X on 10 July 2024, an AI governance adviser wrote that he had just opened his tax return and that Gemini, Google's AI assistant, summarised it without being asked. He wrote that he could not find a setting to stop it, that the two locations Gemini itself suggested did not work, and that when another user showed him the setting meant to keep Gemini out of his documents it was already turned off while Gemini kept giving document summaries. His later testing, in the same thread, suggested that once Gemini had been opened for one PDF in Google Drive it was invoked again for every PDF he opened until he closed it, and he put forward a working theory that his 2023 sign-up for Workspace Labs had overridden the opt-out. A Google spokesperson told technology outlets that using Gemini in Google Workspace requires a user to enable it proactively and that content is not stored without permission; Tom's Hardware reports that Google suggested he may have used Gemini through the Drive side panel and that closing the panel might solve the issue.
If you or someone you know is struggling, free and confidential support is available. Find a helpline near you at Signpost.