U-net legal and acceptable use.

U-net is in active development. These terms summarize expected usage for partners, developers, and testers while production policies mature.

Do not collect, infer, sell, or combine personal data beyond the explicit scoped relationship and permissions granted by a holder.

Official account and attestation type access is reviewed, including legal fields, origins, manifests, and trust-sensitive profile changes.

Developers integrating U-net must verify login assertions server-side and must not treat QR approval alone as a durable personal identity claim.

Stays on your device

Holder private keys, unrelated scoped IDs, and global device identity stay outside partner access.

QR approval is not a substitute for server-side assertion verification.

Shared, scoped to this relationship

Provider access may depend on legal identity, origin, manifest, and notification behavior.

U-net may suspend access for abuse, misleading identity, unsafe notifications, or origin/manifest mismatch.

Trust-sensitive access stays reviewed

The acceptable-use posture is meant to protect holders, partners, and the network while the production policy set matures.

Partners provide company, support, origin, manifest, and policy information for review.

Access is tied to the approved relationship, permissions, notification behavior, and integration surface.

Profile, trust, and release changes can remain under review when they affect holder expectations.