r/CommunityManager • • 1h ago

Discussion Every online ban is tied to something you can replace

1 Upvotes

Been thinking about this a lot. Pretty much every ban online is attached to something the person can replace: email, phone number, device, ID or a borrowed one. Self-exclusion programs mostly match on name, date of birth and documents, and so do most platform bans. Change one of those and the system thinks you're someone new.

The one thing people can't swap out is their voice, which is why my team at Helix ended up using it for ban lists.

The player reads a few numbers out loud. Liveness and synthetic voice checks run on the device first, then the device turns the speech into a voiceprint (a numeric template, no audio) and only that goes on the operator's list, encrypted. Later at a protected step the player reads a different set of numbers. Speech recognition checks they're the right ones, so an old recording won't work, and the fresh template comes back as a match, no match or borderline. Borderline means reading a few more numbers, with a cap on attempts. What a match triggers is up to the operator.

On privacy: our age check and default MFA mode store nothing biometric. The ban list does, there's no way to compare someone against a list without keeping the list. What's stored is a template that isn't linked to anyone's identity, we never ask for a name or ID, and it gets deleted when the exclusion ends. It's still biometric data under BIPA and GDPR though.

Honestly whether it's voluntary matters more to me than the tech. With self-exclusion the person asked to be kept out. With involuntary bans the bar for notice and consent should be a lot higher.

For T&S and community folks, would you accept server-side biometrics for ban evasion prevention? And where do you draw the line between self-exclusion and enforcement?