CLOUD
Privacy for hosted cells.
A Cloud cell stores chat history and settings for that customer only. This is not the docs demo at runtime.sveda.dev.
Operator draft · Last updated 19 September 2026
Not the marketing site.
Privacy on sveda.dev covers the brochure and docs chat demo. Native clients have their own notices: App Privacy for iOS and Android Privacy. This notice covers Sveda Cloud cells we operate. Self-hosted sveda-server remains your processing.
What a cell holds.
Each customer gets an isolated Postgres (histories, settings), Redis (occupancy, throttles, MCP creds), and an optional code index volume. Prompts and completions for that cell stay in that cell. We do not mix customers in one sveda-server process.
Model keys you paste are stored sealed in the control plane and injected into the cell. We do not use your prompts or repository contents to train models. Provider APIs you choose (OpenAI, Anthropic, DeepSeek, and similar) receive what the runtime sends them under those providers' terms.
Operators and subprocessors.
The VPS or cloud account that runs Docker, DNS for *.runtime.sveda.dev, and TLS termination (for example Caddy plus a DNS provider) see connection metadata. The control plane stores org/project metadata, key last-four, and audit events. There is no public Cloud account signup on sveda.dev.
Questions: hello@sveda.dev. A DPA can be issued with a paid cell; this draft is not that DPA.