Security and data
Where a studio's work is stored, who can see it and how it is protected.
Where data is stored
- The main server is in Germany: the app, the database and the studio's files.
- A live copy of the database and our own computing capacity are in Kazakhstan.
- Encrypted backups are kept in Kazakhstan and Ireland.
- Another copy of the files sits in storage in the European Union.
How the work is protected
- Encryption
- Every connection runs over HTTPS, including on a studio's own domain. Passwords are stored only as hashes, and backups are encrypted.
- Studio isolation
- One studio's work is never visible to another. Only a studio's own people can sign in on its domain.
- Roles
- Everyone in a studio has a role: owner, art lead or artist. A studio's characters and styles are available only to its people.
- Activity log
- Actions in the studio and failed sign-ins are recorded: who did what, and when.
- Backups
- The database copy updates continuously. Encrypted backups are kept in Kazakhstan and Ireland.
- No training on your work
- A studio's work does not go into training our models unless the studio has agreed to it in its contract. Its characters and styles are never given to other studios.
- Deletion on request
- At a studio's request we delete the data of its people. It disappears from backups as they are renewed.
Cloud models
A prompt and the chosen images go to a cloud model's provider only when an artist picks that model. Names and email addresses of studio members are not sent.
Before generation, a language model from one of the providers below may refine the prompt text, again without names or email addresses.
Cloud models can be switched off for a studio at its request.
Subprocessors
- netcupMain server: app, database, filesGermany
- Our own hardwareDatabase copy, backups, computingKazakhstan
- CloudflareSecure connection, studio domains, file copyEuropean Union, worldwide
- MegahostEncrypted backupsKazakhstan
- Microsoft AzureEncrypted backupsIreland
- Amazon Web ServicesAdditional computing capacityJapan, India
- Vast.aiAdditional computing capacityHungary
- Microsoft Azure OpenAICloud models: GPT Image, FLUX.2, MAI Image, GPT-6Sweden, Poland, United States
- Microsoft Azure AI SpeechVoice and voice-overSweden
- Google CloudCloud models: Nano Banana, Gemini, Lyriaworldwide
- AnthropicPrompt refinement: ClaudeUnited States
- BytePlusCloud models: SeedreamSingapore
- OpenRouter, xAICloud models: Grok ImagineUnited States
- ElevenLabsVoice and voice-overUnited States
- ReplicateImage upscaling: TopazUnited States
- World LabsWorlds from photos: MarbleUnited States
| Company | What it does | Where |
|---|---|---|
| netcup | Main server: app, database, files | Germany |
| Our own hardware | Database copy, backups, computing | Kazakhstan |
| Cloudflare | Secure connection, studio domains, file copy | European Union, worldwide |
| Megahost | Encrypted backups | Kazakhstan |
| Microsoft Azure | Encrypted backups | Ireland |
| Amazon Web Services | Additional computing capacity | Japan, India |
| Vast.ai | Additional computing capacity | Hungary |
| Microsoft Azure OpenAI | Cloud models: GPT Image, FLUX.2, MAI Image, GPT-6 | Sweden, Poland, United States |
| Microsoft Azure AI Speech | Voice and voice-over | Sweden |
| Google Cloud | Cloud models: Nano Banana, Gemini, Lyria | worldwide |
| Anthropic | Prompt refinement: Claude | United States |
| BytePlus | Cloud models: Seedream | Singapore |
| OpenRouter, xAI | Cloud models: Grok Imagine | United States |
| ElevenLabs | Voice and voice-over | United States |
| Replicate | Image upscaling: Topaz | United States |
| World Labs | Worlds from photos: Marble | United States |
List checked on November 4, 2026.
Questions about data
Questions go to [email protected].
Report a vulnerability
We take vulnerability reports at [email protected]: what you found and how to reproduce it.
We do not pursue researchers acting in good faith, as long as you leave other people's data alone, do not disrupt studios' work and keep the finding private until we have fixed it.
/.well-known/security.txt