Platform News

Character.AI's face-scan rollout, explained.

Mandatory age verification, biometric data, false-positive minor flags, and what your options actually are if you're not into scanning your face just to chat with an OC.

Updated May 4, 20268 min read

Character.AI's age-verification rollout is the most consequential product change the platform has made since launch. It's also the most misunderstood. We're going to walk through exactly what changed, what it means for filter strictness, why so many adults are getting flagged as minors, and what your options are.

What actually changed

Character.AI now uses Persona as a third-party age verification provider. Most users complete a selfie-based face scan. A subset gets routed to ID verification as a fallback. The check is designed to confirm whether you are likely above or below the age threshold rather than to confirm your exact identity.

The selfie is sent to Persona, not stored by Character.AI directly. Persona is a regulated identity provider used by many other consumer apps (Coinbase, DoorDash, etc.) so the data-handling posture is a known quantity. That doesn't make Reddit happy about it, but it's not the worst-case scenario either.

Why Reddit is mad

Three reasons, and they're all legitimate:

  • Biometric data anywhere is a soft target. Persona is well-run, but adding a face scan to the threat model of "things that could leak" is a real change. The vibe shift on r/CharacterAI is mostly about this.
  • False-positive minor flags. Adults with low lighting, beardless faces, or specific facial structures get flagged. The fix flow is friction-heavy. Some users have paid for Plus and lost access during the verification cycle.
  • Verifying didn't remove the filter. A lot of users assumed that proving they're adults would unlock the older, looser filter. It doesn't. The filter is still on for everyone. Verification only adjusts strictness within the existing filter, not whether it's there.

How to pass the scan if you're a real adult

If you keep getting flagged, the boring fixes work surprisingly often:

  • Use natural light, look at the camera straight on. Most adult false-positives are lighting and angle issues.
  • Remove glasses and any face covering. Glare on lenses confuses the model.
  • Don't smile. Models trained on age estimation are biased downward by smiling.
  • Use the ID fallback if scan fails twice. Persona will offer this. It's a stronger signal and resolves most stuck cases.

What this means for the filter

Verified adults get a slightly more permissive filter, but the difference is smaller than people expect. The filter in 2026 is context-aware, meaning it reads the tone of the whole scene, not just the words in the latest message. So a scene that drifts adult will get blocked even if no single line is explicit. That's the change that actually matters, not the verification.

If your goal is mature roleplay or creative writing with adult themes, age verification on Character.AI does not solve your problem. It marginally reduces friction within an experience that is still designed to keep that content out.

If you don't want to scan your face

You have actual options:

  • Sutorichat: email-based signup, no biometric verification, mature roleplay supported between adult characters. Visual novel scenes baked in.
  • PolyBuzz: email signup, soft filter, no face scan. Closest UX to Character.AI without the friction.
  • Janitor AI: email + ID verification (no face scan as of May 2026), but uptime is what it is. See our Janitor AI down guide for context.
  • SillyTavern: self-hosted, no platform-level identity check at all. Power-user setup.

Bottom line

Character.AI's age verification is more reasonable than the worst Reddit takes suggest, and less helpful than the best Character.AI defenders suggest. It's a real privacy ask. It doesn't unlock the old filter. False-positive flags are a real, fixable annoyance. If you're a casual user who chats SFW anyway, you'll barely notice. If you wanted Character.AI to become more like 2023-era Character.AI, verification isn't the lever that does that. The right move is to keep Character.AI for what it's good at and use a hosted alternative for everything else.

Frequently asked questions

Keep reading