Safety

What is true today.

An autonomous workforce needs the same things a human one does before it touches real systems: its own credentials, a limit on what it can spend, and a record of what it did. This page says which of those are in place, which are not, and where to check.

In place
01

Per-agent identity

Every agent is its own principal with its own credentials and endpoints. Nothing runs under a shared key; access is granted per agent, per resource, and default-closed.
02

Scoped connections

GitHub, Google Drive, databases and SaaS connect once with credentials held centrally, and each agent gets exactly the scope you grant it — never the whole connection.
03

Audit of every action

Every tool call, shell command and access is recorded server-side — including the ones that failed — and exportable. It is not a setting; it cannot be turned off by the agent.
04

Spend caps and budgets

A hard cap per account and budgets per project or per agent. Runs stop before the cap, every action has a published price first, and running out of credits fails closed — never a debt.
05

Keys wrapped at rest

Provider keys — ours and yours (BYOK) — and connection credentials are envelope-encrypted with a cloud KMS key; the plaintext never lands in the database.
06

Data handling

We store the minimum needed to run the service. Sandbox stdout and stderr are never logged; Stripe holds payment data, we never see a card; sessions and OAuth grants are revocable from the dashboard. The full notice is public.
In progress, or not yet

Only what a spec says. Nothing here is a certification; the day one starts, this section changes.

01

Tamper-evident audit export

The audit log is server-side and complete but is not yet a WORM (write-once) export with a hash chain. The ledger block already chains its postings; the platform audit log does not yet.
02

Certifications

connect0 is not yet SOC 2, ISO 27001 or HIPAA certified, and no audit is in progress today. We will say so here the day one starts. Until then, the table below is the honest substitute: control by control, with evidence.
03

Self-serve data export

Data-subject requests (GDPR / CCPA) are handled by email at privacy@connect0.ai; a self-serve export is not yet in the dashboard.
Responsible disclosure

If you find a vulnerability, email security@connect0.ai (hi@connect0.ai also reaches us). Tell us what you found and how to reproduce it; we acknowledge within two business days, keep you informed while we fix it, and credit you if you want to be credited. Please give us a reasonable window before publishing, and do not access data that is not yours. We do not run a paid bounty programme today; we will say so here if that changes.

Email security@connect0.ai
Compliance status

Control by control, with evidence.

Compliance status by control
ControlStatusEvidence
Per-agent identity and scoped credentialsIn place

Each agent is a principal; access is per agent, per resource, default-closed.

Access model
Scoped third-party connectionsIn place

Credentials held centrally; each agent gets only the scopes granted.

About connectors
Server-side audit of every actionIn place

Tool calls, shell commands, accesses — including failures — recorded and exportable.

Audit
Spend caps, budgets, fail-closed on empty walletIn place

Hard cap per account, budgets per project or agent, price published before each action.

Spend controls
Provider keys and connection credentials KMS-wrapped at restIn place

Envelope encryption with a cloud KMS key; plaintext never stored.

Bring your own key
Sandbox output never loggedIn place

Command, exit code and duration are recorded; stdout, stderr, env and files are not.

Privacy notice §2.3
Payment data held by the processorIn place

Stripe holds cards and addresses; connect0 stores ids and invoice metadata only.

Privacy notice §2.4
Session and OAuth-grant revocationIn place

Active sessions and grants are listed and revocable from the dashboard; tokens stored as hashes.

Privacy notice §2.5
Ledger postings append-only with a hash chainIn place

The ledger block chains postings per book; corrections are reversals, never edits.

connect0 Blocks
Tamper-evident (WORM) platform audit exportNot yet

The platform audit log is complete and server-side, not yet a hash-chained WORM export.

Audit
Self-serve data export (DSAR)Partial

Handled by email at privacy@connect0.ai; not yet self-serve in the dashboard.

Privacy notice
SOC 2 / ISO 27001 / HIPAANot yet

Not certified; no audit in progress. This page changes the day one starts.

Ask us

Not yet certified. This table is the substitute until a certification exists — every row links the page that proves it. Machine-readable version: curl -H 'Accept: text/markdown' https://connect0.ai/safety