Dash

Security and trust

Built so your security team can say yes.

Approval-first design, workspace-isolated execution, OAuth-based access, encrypted credential storage, no training on your data, full data wipe on demand.

Workspace isolation

Every Dash workspace runs in its own execution context. Data never crosses workspace boundaries. Two customers running Dash share zero state.

OAuth where supported

Dash uses OAuth where supported and keeps tool access revocable. You can disconnect a tool in one click.

Approval flow on mutating actions

Anything that sends an email, posts publicly, writes to your CRM, or spends money requires explicit approval in Slack. Dash drafts, you ship.

Encrypted credential storage

Sensitive workspace credentials are encrypted at rest, handled server-side, and only used when Dash needs to act on your behalf.

No training on your data

Conversations and tool outputs stay yours. We use model APIs with training opt-out enabled across the board.

Clean workspace on demand

Wipe your entire Dash workspace, including memory and history, with one command. Deletion is irreversible and complete within 24 hours.

Security review

What teams can review.

Security review

Available on request

Privacy requests

Supported

Data processing terms

Available on request

Regional hosting options

Enterprise

Vendor review support

Available on request

Sub-processors

Who Dash works with.

We use a short list of trusted vendors. All sub-processors are reviewed annually.

  • Anthropic Model inference, opted-out of training
  • Composio OAuth integration catalog
  • Browserbase Cloud browser sandbox
  • E2B Code execution sandbox
  • AWS Hosting, US-East and EU-West
  • Stripe Payment processing

Have a security question?

Ask for our security overview deck or send a question to the team.