Short answer for most people: no. You can create a UIID, use aliases, sign in across Web4 applications and reserve a short code without ever verifying.
When it matters: Where a service genuinely needs to know a real person is behind the identity — regulated finance, government services, or anywhere trust has real consequences.
The three states: unverified (nothing submitted), pending (submitted and being reviewed), and verified, which carries an associated trust score.
How it is checked: Verification runs against the rules of a jurisdiction you choose, and can include NFC verification of a biometric passport for the higher European assurance levels.
What it does not do: Verification attaches to your Core ID, not to your everyday activity. You stay anonymous where you use aliases — that separation is the entire point of the design.
Who can read it: Applications need a specific sensitive-data permission, requested and granted explicitly. It is not part of ordinary profile access.
Start or check your status: uiid.me