Their identity, not your account: Users arrive with an identity they already own, rather than creating a new account that belongs to your platform.
Aliases by default: Everyday sign-ins can run through anonymous aliases rather than the user's Core ID, so your service cannot be cross-referenced against their activity elsewhere — and neither can anyone else's.
Bot resistance: Because identity creation requires localized biometrics on real hardware, mass bot networks and throwaway deepfake profiles become economically and technically impractical.
Coming from Web2: Users can convert traditional social or banking logins into decoupled Web4 keys, after which the link to legacy tracking is severed.