Documentation Last reviewed 2026-11-14

Security and data

Where your data sits, what is recorded, what leaves the machine, and how keys are held.

Where the data sits

On your machine. Customer records, message history, configuration, documents and the audit log live in one Postgres cluster on the node, and nothing copies them anywhere else.

The machine does not need to be reachable from the internet for any of this to work. Every channel opens its own connection outward, so a node can sit entirely inside your network. That is covered in more detail on install and requirements.

What is recorded

Two tables are append-only, enforced by the database itself: every message, and every event. Nothing in the system edits them through the normal path, including an administrator.

Permission changes are written into the same log as the work. Granting a tool, creating a rule, putting an agent under a rule: each is an event next to the messages it later affects. So the record of what an agent was allowed to do sits beside the record of what it did, in one place and in order.

What leaves the machine

The complete list:

Goes out toWhy
Your model providerThe model call. This is the one that always happens
Your mail serverReading and sending mail on the mailbox you gave it
Any chat platform you connectedReading and sending on that channel
Google, if you connect itWhatever scope you approve when you connect it

Nothing is sent to the project: no telemetry and no copy of your data.

The Google row is worth one more sentence, because it is the one people wave through. The connector asks for a scope and you approve it in your own Google account. Read what it asks for before you press the button, the same as you would for any other application.

Keys

Provider keys and channel credentials are held in an encrypted store on the node, not in the prompts and not in the agent files. An agent reaches a service through a tool, and the tool holds the credential. So an agent can use a mailbox without being able to read the password for it, and rotating a key is one change in one place, not an edit across every agent that uses it.

Retention and backups

Messages, events and documents are kept until someone removes them deliberately. Backup and restore are documented procedures in the repository.

Reviewed 2026-11-14. Older than 90 days counts as broken. Something here wrong? Tell me