Security and trust

Encryption

Encrypted in transit and at rest

All traffic is served over TLS 1.2+ with HSTS. Integration credentials and OAuth tokens are encrypted at rest using authenticated symmetric encryption (Fernet — AES-128-CBC with HMAC-SHA256).

Isolation

Every run is sandboxed

Each agent run executes in its own isolated, ephemeral cloud sandbox. Tool subprocesses run with a cleaned environment, so your credentials never reach the processes that read your data.

Secrets

Credentials never leak

Secrets reach a sandbox through the provider's authenticated API, never via command-line arguments or the process list. Logs and error reports are redacted so tokens and passwords are never recorded.

Access

Strong authentication

Sessions use signed tokens with instant revocation, single-use password resets, and rate-limited auth endpoints. Sign in with email or Google OAuth 2.0.

Network

Outbound request protection

Webhook and bridge destinations are validated and IP-pinned to block SSRF and DNS-rebinding attacks. Connections to private or internal addresses are rejected.

Monitoring

Continuous integrity checks

Automated health checks and dozens of data-consistency invariants run continuously, with error monitoring and alerting. Dependencies and secrets are scanned on every change in CI.

Your data

We never train on your data

Your content, customer data, and outputs are never used to train AI models — by us or our subprocessors. You can request a copy of your data or its deletion at any time.

Infrastructure

Certified providers

Core infrastructure runs on providers that maintain their own independent certifications, including DigitalOcean (SOC 2), Anthropic (SOC 2), and Stripe (PCI DSS).