How your data flows
Chief's local relay app (chief-relay) runs on your machine as a lightweight background process. It spawns agent processes that call LLM providers directly using your subscriptions or API keys, and streams orchestration status to Chief's servers via a secure WebSocket connection.
Your source code never passes through Chief. The relay talks to LLM providers under your own agreement and keys; Chief only sees the coordination metadata it needs to orchestrate your work.
What Chief stores
- Chat messages between you and Chief
- Task prompts, results, and progress logs
- Project names, goals, and milestones
- Token usage and performance metrics
What Chief never stores
- Source code files or repository contents
- Your LLM API keys or credentials
- Your agents' full code context sent to LLM providers
No model training on your data
Chief does not use your data to train, fine-tune, or improve any AI model. This applies to all users on all plans, unconditionally.
Chief orchestrates third-party AI agents; it does not run its own models. Your interactions with LLM providers (Anthropic, OpenAI, Google, etc.) are governed by your own agreements with those providers and use your own API keys or subscriptions.
Encryption
All data is encrypted both in transit and at rest.
| Layer | Protection |
|---|---|
| In transit | TLS 1.3 for all connections: API, WebSocket, Redis |
| At rest | AWS encryption for database and object storage |
| Sessions | Secure, HttpOnly, SameSite cookies; HSTS preload |
| Relay auth | Device code flow — no static API keys stored on your machine |
| Callback tokens | SHA-256 hashed before storage |
Sub-processors
- AWS — infrastructure (encrypted in transit and at rest)
- Stripe — payments (PCI-compliant)
- LLM providers (Anthropic, OpenAI, Google, etc.) — via your own API keys or subscriptions
Related policies
For more detail on how we handle your data, see our Privacy Policy and Terms of Service.