Trust and security
Who runs ZeroLog, how a workspace is isolated, where the service is hosted, and which outside parties see your data.
Diagram as text
- You reach the site through the Cloudflare edge, which is a US company and terminates the connection at the location nearest you.
- The app server in Seon, Aargau, holds chats, files and workspace disks. Sign-in runs through the operator's own Keycloak.
- Your workspace is its own container; a command the AI wants to run waits for your approval. The app server starts and stops it.
- Third-party API keys sit in a separate key service on its own Swiss VM; the workspace only ever holds placeholders.
- Prompts, attached files and images go to Featherless and its subprocessors (USA, Singapore and other places without a location guarantee) for model inference. This is the highlighted path.
- Other recipients outside Switzerland: Stripe for plan payments and MoonPay for manual top-ups; IONOS (Germany) for the container egress gateway and encrypted backups; SMTP2GO for system email; Anthropic for redacted error reports; Google only if you connect Gmail, Drive or Calendar.
- Image generation goes to Infomaniak in Switzerland, only when you request an image.
Operator and contact
ZeroLog is run by Gian-Luca Luongo, a sole proprietor (natural person) based in Wettingen, Switzerland. Contact for any question, including security reports, is info@zerolog.ch. Full legal details are in the Impressum. Vulnerability reports follow security.txt (RFC 9116).
Architecture, from your workspace's side
- Each workspace is its own container, not shared with any other user: a gVisor container, or on Ultra optionally a Kata micro-VM with its own kernel — see Isolation.
- Third-party API keys you store are not kept in the main application. A separate key service on its own Swiss VM holds them encrypted; agents only see placeholders — see Key proxy.
- Outbound traffic from a workspace runs through a filtered network path — see Outbound network.
- A command the AI wants to run waits for your approval first — see Command approval.
- Chats, files and workspace disks are stored on the server in Seon (Aargau), Switzerland; pausing a workspace keeps its disk until you delete it yourself.
Where prompts go
Prompts and the files or images you attach are sent to Featherless, based in the USA, to generate a reply: this is the model inference behind every customer account and is the core of the service. Optional connectors only receive data if you switch them on.
Who receives data
| Recipient | Location | Purpose |
|---|---|---|
| Featherless and Global DPA Annex III subprocessors | USA, Singapore and other locations without a region guarantee | Model inference; provider-internal fallback possible |
| Stripe | Ireland and USA | Payment processing |
| Cloudflare | USA; edge location nearest you | Reaching the site, DDoS protection |
| IONOS SE | Germany | Outbound network gateway for containers; encrypted offsite backup copies, without the decryption key |
| SMTP2GO | New Zealand company; sending locations depend on provider routing | System email; incoming operator mailbox is hosted in Switzerland |
| USA | Optional Gmail, Drive and Calendar connectors, only if enabled; sign-in uses the operator’s Keycloak | |
| Infomaniak | Switzerland | Image generation, only when you request an image |
| MoonPay Commerce / Helio, Bybit | See the Privacy Policy | Manual credit top-ups; the payment settles to the operator’s custodial Bybit USDC wallet |
| Anthropic | USA | Automated, redacted error reports |
Featherless confirmed on 29 September 2026 that the Global DPA automatically applies to ZeroLog’s Developer API account. Its EU SCC Module 2 covers EEA/UK transfers; no Swiss Addendum has been agreed. The operator relies on Art. 17(1)(b) FADP for Swiss transfers, with unresolved legal uncertainty for regular transfers. The Developer plan remains in use, without a processing-location guarantee or per-account routing control. The Privacy Policy explains the recipients, provider commitment and remaining risks.
Limits, status and changes
- Compute and credit limits are set per plan — see Plans and Spend limits.
- Live model-provider status is at /status; platform uptime history is on the operator's status page.
- Changes to the service, including security-relevant ones, are announced in the Newsroom.
Something missing or wrong here? Say so. The documentation is part of the product, not an afterthought. All topics · Security · Status · X · Legal & privacy · Home