V1 trust is a short list: encrypt keys, redact secrets, approve before send, block private IPs, and keep a full run audit. We do not claim SOC 2, ISO 27001, HIPAA, FedRAMP, or a private-cloud edition. Those wait until a paying team requires them.
What we do today
- Credentials at rest. BYO model keys and OAuth tokens are encrypted (AES-256-GCM). Builder API keys are hashed and shown once.
- No secrets in prompts or public JSON. Authorization headers on HTTP steps are redacted. Public pages do not include your keys.
- Human approval. Dangerous or gated skills become
WAITING_APPROVAL. Email drafts by default; send only when the approved payload says send. - SSRF controls.
web.extract,http.request, and Outcomes URL ingest use HTTPS and block private, link-local, and metadata addresses. - Skill allow-list. An employee may only use skills you enabled. Unknown skills fail closed.
- Audit trail. Every model and tool call is a persisted run step (tokens, cost, duration, errors). You can download a run and an ROI report of labor you measured.
- Auth and billing. Google or Microsoft for sign-in. Any.win keeps the session. Stripe for Checkout and the customer portal.
- Rate limits on runs, public fork, and Outcomes ingest.
What we do not claim
- SSO / SAML, SCIM, customer-managed keys, data residency, or DLP product features.
- A signed penetration-test report or a compliance attestation for V1.
- That platform model providers will not train on prompts — that is their policy, not ours. Prefer BYO keys when you need a contractual stance with the lab.
- Outcome billing or attributed revenue. Outcomes are measurement.
Your responsibilities
Do not put secrets in public instructions. Review packs before approve. Restrict HTTP allow-lists. Treat PUBLIC employees as public. See the Terms, Privacy Policy, and DPA.
Incidents
Report a vulnerability or suspected incident to [email protected]. We will acknowledge and work the issue. Please do not test against other customers’ workspaces. The same contact is published in /.well-known/security.txt.
Subprocessors
Infrastructure we use is listed on the subprocessors page.