Queue & Match
During matchmaking, Ember runs passive checks — client version, process fingerprint, and low-noise device traits. Nothing intrusive; everything is hashed and ephemeral.
Account identity stitching
Risk-aware linking for email, provider, and profile history keeps smurfs in check.
Light reputation cache
Soft risk from recent bans/timeouts travels with the account for tempered matching.