How we protect your data at every layer.
Container isolation
Every user gets a private container with multiple layers of isolation:
| Layer | What it protects |
|---|
| Process isolation | Your container can’t see other containers. |
| Access control | Mandatory profiles restrict system calls and file access. |
| System call filtering | Dangerous kernel interactions are blocked. |
| Unprivileged mode | Container root maps to a non-root user on the host. |
| Network isolation | Each container gets a private IP. No direct access between containers. |
Encryption
In transit
All connections use TLS encryption:
- Browser to API (HTTPS)
- API to Fleet Agent (HTTPS with shared secret)
- Browser to container (WSS through reverse proxy)
- Container to AI providers (HTTPS)
At rest
- API keys — encrypted before database storage
- Database — PostgreSQL with encryption at rest
- Container filesystems — stored on encrypted volumes
Authentication
User authentication
EasyClaw uses managed authentication with:
- Email/password with secure hashing
- Session tokens with automatic refresh
- Rate limiting on login attempts
Fleet Agent authentication
Communication between the public API and Fleet Agent uses a shared cluster secret, preventing unauthorized container operations.
AI provider keys
Your API keys are:
- Submitted once through the web console (TLS-encrypted in transit)
- Encrypted using a server-side key
- Stored in the database in encrypted form
- Decrypted only when injected into your container at spawn time
- Never logged, displayed, or transmitted in plaintext
Data handling
| Data type | Where it lives | Retention |
|---|
| Conversations | Your container only | Deleted when container is killed |
| AI memory | Your container filesystem | Deleted when container is killed |
| Channel credentials | Your container filesystem | Deleted when container is killed |
| API keys | Database (encrypted) | Until you delete them |
| Account data | Database | Until you delete your account |
| Usage metrics | Database | Aggregated, non-identifiable |
We don’t store your conversation content in our database. Conversations exist only inside your container. When your container is destroyed, conversations are permanently gone.
Infrastructure security
| Component | Security measures |
|---|
| Frontend | DDoS protection, edge caching, automatic HTTPS |
| Public API | Private networking, automatic TLS, environment encryption |
| Fleet servers | Dedicated servers, firewall rules, SSH key auth only |
| Database | Row-level security, connection pooling, encrypted backups |
| DNS | DDoS protection, WAF, proxied DNS records |
What we don’t do
- We don’t sell, share, or monetize your data
- We don’t use your conversations to train AI models
- We don’t log message content outside your container
- We don’t track your browsing activity inside containers
- We don’t access your container without your explicit request
