Trust & Security
Agents run untrusted code and touch real credentials on your behalf. Here's exactly how that's contained, what happens to your data, and how to reach us if something looks wrong.
How agent execution is contained
Every run is boxed in
Every run is sandboxed with gVisor, a userspace kernel between your code and the host.
Containers never hold your keys
A worker gets a short-lived, audience-restricted token and nothing else — no database URL, no provider key. The gateway holds the credentials and makes the call on its behalf.
Egress it cannot redirect
Outbound requests are checked against a per-connector allowlist and then pinned to the address that was checked — so a DNS answer cannot change between the check and the connection.
Secrets live in Vault
Never in a container's environment, never in a log. Bring your own AWS Secrets Manager account instead if you would rather hold them yourself.
Everything is written down
Every model call, tool call and connector request is recorded append-only, with what it cost — so "what did it do at 3am" has an answer.
Isolation the database enforces
Row-level security means one account cannot read another's data even if a query forgets its WHERE clause. It is not a convention we maintain; it is a rule Postgres applies.
What happens to your data
Your data stays in your account
Project files, agent conversations, connector credentials and run history are scoped to your account by row-level security, not by application-level filtering alone. Support cannot browse it without a reason tied to a request you made.
Credentials are never logged
API keys and OAuth tokens are written once, encrypted, into the secrets store and referenced by an opaque id everywhere else — audit logs and error reports record that a credential was used, never the value.
Closing an account stops everything at once
Closing your account (Delete account, in your account settings) revokes every session and stops every agent immediately. Your data is kept until you ask us to delete it: email [email protected] and the deletion is completed within 30 days of your request. Deleting a project, by contrast, removes its rows and its workspace volume. If you need something more formal (a deletion certificate, a DPA), email us and we'll handle it directly.
Third parties see what a run needs to see, and no more
A connector call reaches only the third-party API it's configured for, with only the credential you gave it. Model calls go to the provider you picked (your key, ours, or a free-tier rotation) — never to a provider you didn't choose. We don't sell or share your data for advertising.
Where the program stands today
Said plainly rather than left implied, the way /features already lists what the product can't do yet.
We don't yet hold a formal compliance certification (SOC 2, ISO 27001, or similar). The controls above are real and enforced in the running system today; a third-party audit of them is a planned step, not a completed one. If a certification is a requirement for your team, tell us — it shapes what we prioritize next.
Found a security issue?
Email us directly and we'll respond. Please don't test against other customers' accounts or data — use your own test account.