Trust
Built like infrastructure. Calm, careful, and visible.
Echo handles real work for real businesses. That means it touches real data. Here is exactly how we treat it.
Never trained on your data
Your messages, files, and tool data are used to do the work in front of Echo and nothing else. No model is fine-tuned on your account, and your content is not shared with anyone outside the providers needed to complete a task.
Encrypted in transit and at rest
All traffic uses TLS 1.2 or higher. Data at rest is encrypted with AES-256 in Supabase Postgres and Supabase Storage. Tool credentials are stored encrypted and never exposed to the browser.
Regional storage
Customer Data is stored in the United States (AWS, us-east-1) in Supabase Postgres and Supabase Storage. Backup retention defaults to thirty days.
Approvals on every write
Echo asks before it changes external data. The approval card shows exactly what it wants to do, on which connected account. You approve or skip in one click. There is no implicit consent for write actions.
Audit trail by default
Every tool call is logged with the workspace, the user, the input, and the result, so you can review exactly what Echo did and when.
You can see and delete everything
Threads, files, memories, and connections are visible in the dashboard. Workspace owners can delete data, disconnect tools, or wipe the workspace at any time. Deletion is final within thirty days.
Subprocessors
Who else touches the data.
Echo uses a small number of services to function. Each one is named, scoped, and listed below. We notify workspace owners before adding a new subprocessor.
| Provider | Purpose | Region |
|---|---|---|
| OpenRouter | Model inference gateway; routes prompts to model providers. | US |
| Anthropic | Model provider (Claude), accessed via OpenRouter. | US |
| OpenAI | Text embeddings for search and memory, and speech-to-text transcription of voice notes. | US |
| Supabase | Postgres database, storage, and auth. | US |
| Pipedream | Managed tool connections and OAuth (default connector). | US |
| Composio | Managed tool connections and OAuth. | US |
| Modal | Sandboxed code execution for Projects, browser tasks, and media generation. | US |
| Railway | Agent worker hosting. | EU |
| Vercel | Marketing site and dashboard hosting. | Edge |
| Resend | Transactional email delivery. | EU |
| Stripe | Billing and payment processing. | US |
Network
How a request actually moves.
The short version: Slack to Echo, Echo to your tools, output back to Slack. Nothing else.
- 01
Slack
You message Echo. Slack signs the event with your team's secret.
- 02
Echo
The agent worker authenticates the event and plans the task with Claude.
- 03
Tools
Echo calls only the tools it needs, using credentials your workspace authorised.
- 04
Output
Finished work is posted back into Slack and stored against your workspace.
All hops are TLS. Tool credentials never reach the browser.
Need a DPA, our security docs, or to report a vulnerability?
Write to [email protected]. We will share the DPA and our security documentation, and answer the rest. To report a vulnerability, see our disclosure policy.