Trust and privacy

Release status

Outcome

Select a product path whose trust boundary fits the workload.

Prerequisites

1. Know who owns the serving device
2. Classify whether application content is sensitive

Current path

1. Use the Network only for workloads appropriate for contributor-operated infrastructure.
2. Use Private Access for sensitive work on devices you own and explicitly pair.
3. Treat Network Sharing, private pairing, and API credentials as separate permissions.
4. Revoke a device or credential when its trust assumptions change.

Authoritative success state

The chosen path makes the plaintext boundary, account authority, and failure behavior explicit before traffic is sent.

Common failures and recovery

1. If the boundary is unclear, do not send the workload.
2. A Private Access failure must not be recovered by silently using the paid Network.

Security and privacy boundary

Shared Inference exposes content where required to serve it. Private Access encrypts native content between paired CLIs but still exposes necessary routing metadata.

Next valid action