Security
Your keys, credentials and files stay on your machine. The cloud coordinates; your runner executes.
What the cloud stores
- Messages, tasks and the event feed of your workspace.
- Names of your credentials and connectors, and which streams can use them.
- Tokens of the connectors you enable thread tracking for, such as Slack.
- Usage metadata from your runner: model, tokens, duration. Never the content.
What never leaves your machine
- Model API keys.
- Credential values: passwords and tokens stay in your OS keychain.
- Files in your stream folders.
- Model calls: the cloud never calls a model. Your runner does, with your key.
The runner executes, the cloud coordinates
The runner is a separate module with a simple contract: take a task, run it, send messages and status back. It runs on your laptop by default, or on your own server. It connects out to the cloud, so it needs no open ports and works behind NAT. A stream is bound to the runner whose machine holds its folders and credentials.
Keys entered in the browser are sealed for your runner
When you add a model key in the web app, your browser encrypts it with your runner’s public key. The cloud relays the ciphertext without storing it and only learns the last four characters for display. The runner decrypts the key and puts it in the OS keychain.
Credentials are scoped per stream
Each stream is given only the credentials it needs, so the assistant in your Personal stream never sees work keys. The model sees a credential’s name, never its value.
Permissions you control
Files are available only inside a stream’s folders. Commands run in the mode you choose per stream: ask every time (the default), an allow list, or full auto. Writes to external services follow the connector’s access level. Every permission request shows the exact action with Allow, Always and Deny.
Connector tokens are encrypted
Tokens of cloud connectors are encrypted with a separate data key, which is itself encrypted with a master key kept outside the database.
We do not read your conversations
Our back office does not show message or task content. Access to it happens only at your request to support, and is logged. We do not train models on your data.
Your data is portable
Export everything as a ZIP of JSON and attachments, move your cloud data back to the local app, or delete it all from Settings → Privacy & data.
Verify it yourself
The client and the runner are source-available under the FSL, so you can read exactly what runs on your machine and where your keys go.
Open source