Data minimization
U-net is designed around scoped identities, local device keys, attestations, and proof flows so services do not receive more data than a specific interaction requires.
Privacy
This page describes the privacy posture of the U-net mobile app, web login flows, miniapps, verification checks, and partner integrations.
U-net is designed around scoped identities, local device keys, attestations, and proof flows so services do not receive more data than a specific interaction requires.
The system may store public profile data, scoped relationship records, attestation metadata, verification session state, encrypted message envelopes, and operational logs needed to run the service.
Partners receive service-scoped IDs and permission state for their relationship. They do not receive the holder's private keys, FCM token, unrelated scoped IDs, or global device identity.
Holders can revoke miniapp permissions, notification categories, attestations, connected services, and scoped relationships from the U-net app.