Data and privacy

This page describes how connect0 handles the data you entrust to it — your connection credentials, the files your agents work on, and the memories agents accumulate. It sticks to what the platform actually does today.

Where your data lives

connect0 runs on Google Cloud and Cloudflare. Structured data — accounts, projects, agents, usage, memory — lives in managed Postgres. Files your agents upload, download, or generate live in object storage. Everything is encrypted at rest by the underlying platform, and traffic between services stays on private networking rather than the public internet.

Credentials and provider keys are encrypted

The secrets that matter most — the credentials behind your connected sources and the provider API keys behind model calls — are never stored in plaintext. They are KMS-wrapped: encrypted with a key held in a managed key-management service, and unwrapped only in the service that needs them, at the moment it needs them. A leaked database row does not leak a usable secret. Access to unwrap is granted narrowly, per service.

Agent memory

Agents can accumulate long-term memory — durable facts learned across runs. Memory is scoped against the same access graph as everything else (user, agent, account), so an agent only retrieves memories it's entitled to. Memory is designed with prompt-injection and memory-poisoning as a first-class threat, and includes redaction so sensitive values aren't retained verbatim. On enterprise plans, sensitive memories can be KMS-wrapped like other secrets.

Running out of credits never deletes data

If your wallet hits zero, credit-burning actions stop — but reads, dashboards, and data export keep working. Running out of credits pauses work; it does not hold your data hostage. See Spend controls for exactly what fails closed.

What you control

• Access — restrict any connection to specific teams, users, or agents; see Access model.
• Visibility — every state-changing action is recorded in the audit log with the actor who made it.
• Scope — keep separate workstreams in separate projects so their connections and data don't mingle.

Where to go next

• Access model — who can reach which data.
• Audit — the record of who did what.