Every service meets
a different you.
No passwords, no forms, no shared email. Each app gets its own identity and only the answer it needs — and you can cut any one of them loose without touching the rest.
What changes for you
Three things are true every time you connect to a service through U-net, in this order.
Every connection gets its own identity
Demo Supermarket and Issuer Example each see a different, unrelated U-net identity for you. Neither can tell the other exists, and neither can piece together a profile from the other's side.
Approval happens on your device
When a sign-in or check arrives, you approve it locally with a tap or biometric. Your private keys never leave your phone, and no approval is silent or automatic.
You can see and revoke everything
Every connected service, notification category, and issued attestation is listed in the app. Disconnect any one of them without disturbing the rest.
What actually happens when a service asks you something
Say a miniapp needs to confirm you're old enough to continue. Here's the whole exchange.
A specific question arrives
“Is this holder age-eligible?” — not a request for your ID, birthdate, or name.
You approve locally
A biometric or device unlock confirms it's you. Nothing about the request leaves your phone yet.
A proof goes out, not a document
The service receives a verified yes — never the ID, the birthdate, or a way to look either up again.
The boundary, plainly
This is the actual line between what's yours and what a service ever sees.
Curious what this looks like from the other side?
See how developers integrate the same check, or what it solves for a company deciding whether to ask for one at all.