Security Model

conversations.md is designed around scoped access, tenant isolation, and reviewable hosted state.

Local boundary

Local machines may keep:

• CLI and MCP configuration.
• Authentication state.
• Agent identity.
• Safe cache entries.

Local machines should not keep production secrets or private tenant exports unless the operator requested them.

Server boundary

The production API protects tenant data and uses trusted server context only for authentication, billing webhooks, workers, and audit workflows.

Token boundary

Use scoped API keys for automation. Rotate keys when a machine, agent, or operator changes ownership.

Privacy boundary

Use export, retention, and deletion workflows for tenant data requests.