Access

How access works

Secrets unlock and cloud calls only happen when you act. Access is gated by your unlock, OS/process boundaries, and account-scoped sync — not an always-on agent with Allow/Deny prompts for every tool call.

Unlock gate

Secure Data stays locked until you unlock the vault with your master password — which we never store and only you know. The vault auto-locks after idle time. While locked, private keys and credentials are not available to sessions or the UI.

Process boundary

Encryption and credential handling run in a privileged core of the desktop app. The UI is sandboxed and talks to that core over a narrow bridge — it never holds raw vault keys.

• Vault crypto stays in the privileged core
• SSH private keys served from an in-memory agent, not temp files
• Cloud credentials increasingly confined behind opaque handles

Account-scoped sync

Firestore security rules scope records to the authenticated account owner (verified email). Another user's client cannot read your documents by guessing an ID. What syncs as Secure Data is still ciphertext.

You initiate cloud actions

Discovery, terminals, metrics, and kubectl run only when you start them in the app — not because a background agent decided to. Provider traffic uses your credentials against that provider; CloudCMD is not a content middlebox for your SSH sessions.

AI stays out of the vault

Command assistance, when enabled, sends your prompt and limited context to a model provider. Master password, derived keys, vault secrets, and raw credentials are not part of that payload. Prefer reading generated commands before you run anything destructive.

Devices

Each install is a device on your account. Deactivate devices you no longer use. Losing a device: revoke cloud OAuth at the provider, change your master password on a trusted machine, and remove the lost device from the account.

Data map: Privacy & Data · Habits: Security best practices