Roblox's Face-Scan Age Check: What It Misses on a Shared Phone

Since January 2026, anyone who wants to chat on Roblox has to pass a face-scan age check first. It's a real, meaningful change, but it checks the account, not the person holding the phone, and that distinction matters a lot on a phone more than one person uses.

What actually changed with Roblox's age check in January 2026?

Roblox now requires every user, worldwide, to complete an age check before chat features work at all, text, voice, or direct messages. Playing games without chatting still works with no check. The rollout followed real pressure, lawsuits and government scrutiny over adults contacting children through the platform's chat, and it sorts every account into one of six age bands, under 9, 9 to 12, 13 to 15, 16 to 17, 18 to 20, and 21 and up, with chat permissions that differ by band.

How does the age check actually work?

The default method is a short selfie-style video, processed by a third-party vendor, that estimates age from facial features in a few seconds. A government ID is available as an alternative for users 13 and older, and a parent can verify a child's age directly through parental controls instead, which skips the face scan entirely. Whichever method is used, the result gets attached to the account, not repeated for every session.

Does my child need to redo the check every time, or does it stick to the account?

It sticks to the account. Once an account passes the check and lands in an age band, that band applies to whoever is logged into that account going forward. Roblox has no way to tell who is physically holding the phone at any given moment, only which account is active.

What happens if my child logs into my account, or an older sibling's, instead of their own?

They inherit whatever age band that account was sorted into, chat permissions included. A parent's or an older sibling's account, verified as an adult or an older teen, gives a much younger child the same chat access as whoever the account actually belongs to, which is precisely the kind of contact the age check was built to prevent. On a phone where the same Roblox account gets used by more than one person, the age check is really only checking the account's history, not who's playing right now.

What can I actually do about it on a shared phone?

Roblox's own controls can cap total daily hours on an account, which is worth setting regardless, but they can't schedule when that time is used, a capped hour can still get spent right in the middle of homework time. Blocking the app entirely during specific hours closes that gap: CrenelView lets you schedule Roblox, or any other app, to stay closed outside the hours you choose, which holds regardless of which account is logged in or what age band it's sorted into. For the account-sharing problem specifically, the more direct fix is making sure your child has their own Roblox account with their own actual age on it, rather than one that inherited someone else's verification.

The face scan checks the account. The account doesn't know whose hands are actually on the phone.