For teams
The questions a team asks before it adopts a tool, answered in one place — with links to the documents rather than adjectives.
Last updated 2026-09-05
Where the data lives
All workloads and storage run on dedicated infrastructure in Germany (Hetzner, Falkenstein). We do not replicate data outside the EU. The one exception you control is the AI provider: a prompt and its surrounding code context go to the LLM provider you choose — the built-in one, or your own OpenRouter or Ollama endpoint — under that provider's terms.
What we never do with your code
- We do not train models on your code or your chats with the agents.
- We do not sell data or use it for profiling.
- We do not read your workspace files unless you explicitly ask support to.
Documents
Export and erasure
Every record we hold about an account is downloadable as JSON at GET /api/me/export while logged in. Code is in private git repos you can clone at any time. Delete cluster on the dashboard erases the whole tenancy: namespace, agents, workspaces, custom domains, per-app repos, encrypted settings and every database row tied to the account.
Security you can install yourself
Because the cluster is yours, the security posture is not fixed by us. From Cluster tools you can add Kyverno (admission policies), Trivy (continuous CVE scanning), Falco (runtime detection) and External Secrets (secrets from your own vault instead of Git), and read the results in your own Grafana.
Talking to a person
Questions about procurement, a signed DPA, or a use case these pages do not cover: hello@my-app.engineer. Privacy requests: privacy@my-app.engineer.