Privacy by Default: Who Can See Your Workflows
We believe privacy is not a feature — it's a responsibility. Here's how we think about it, and what we do to protect your family's data.
Where Your Data Lives
When you build a workflow, data flows through three places:
1. **Your browser**: Workflow design, editing, visualization
2. **Our servers**: Workflow execution, model calls, persistence
3. **Third-party services**: Only if you explicitly connect them (Gmail, calendar, etc.)
Each layer has different privacy guarantees.
Your Browser
The canvas runs locally. Your workflow definitions, test runs, and the data you preview are stored in your browser cache. We don't transmit them by default.
This means:
You can build offlineYour workflow structure stays private until you saveWe never see a workflow you've only designed and not shared
Our Servers
When you save and run workflows, we store:
The workflow structure (nodes, connections, prompts)Execution logs (when your agent ran, how long it took)Model outputs (what Claude said, what action was taken)
We never store:
Personally identifiable information, unless you explicitly put it in a promptMessage contents from your family's chatsPasswords or authentication credentials
Your data is encrypted in transit (TLS) and at rest. We use key rotation and compliance with GDPR/CCPA.
Sharing & Permissions
By default, workflows are private to you. You control who sees them:
**Private**: Only you can view and edit**View-only**: Share the canvas with family members who can see but not change**Collaborate**: Invite others to edit your workflow together**Public**: Share a workflow with the community (you choose what to publish)
When you share a workflow, the person you're sharing with can see:
The workflow structure and promptsTheir own execution resultsNOT other people's data or execution history
Model Calls
When your workflow calls Claude or another model:
We send only the data your prompt requiresThe model provider (Anthropic, etc.) processes it per their privacy policyWe don't log model inputs/outputs by default unless you enable workflow historyYou can run models on-device if you self-host
Compliance
We comply with:
**GDPR**: You own your data. You can export, modify, or delete any workflow and its history.**CCPA**: You have the right to know what we store, who we share it with, and to request deletion.**SOC 2 Type II**: Our infrastructure is audited annually. Access is logged.
What We're Building
We're working on:
**End-to-end encryption**: Workflows encrypted so only you can decrypt them**Local execution**: Run complex workflows entirely on your device**Differential privacy**: Share aggregate insights without exposing individual data**Privacy reports**: Transparency about what's flowing where in your workflow
The Bottom Line
Your family's automation is yours. We're not mining it for data. We're not selling it. We're not even looking at it unless you ask us to help debug.
That's the trust we're building.
