ZeroLog
Private preview

Trust and security

Who runs ZeroLog, how a workspace is isolated, where the service is hosted, and which outside parties see your data.

Where your data goesYou reach the app server through the Cloudflare edge. The app server, your workspace and the key service are operator systems in Switzerland. Prompts and attached files go from the app server to Featherless and its subprocessors outside Switzerland. Payment providers, the egress gateway and backups, system email, error reports and optional Google connectors are other recipients outside Switzerland.starts, stopsplaceholdersmodel inferenceYoubrowser, CLI or appCloudflare edge(USA) reaches the siteApp server, SwitzerlandSeon (Aargau)chats, files, workspace diskssign-in via own KeycloakYour workspace, Switzerlandown container, approvalbefore each commandKey service, Switzerlandseparate VM, keys encryptedFeatherless andsubprocessorsUSA and othersprompts, files, imagesStripe, MoonPaypaymentsIONOS (DE), SMTP2GOegress gateway, backups,system emailAnthropic, Googleredacted error reports;Google only if connected
Chats, files and keys stay on operator systems in Switzerland; the prompt you send to a model is the one path that leaves Switzerland by default.
Diagram as text
  1. You reach the site through the Cloudflare edge, which is a US company and terminates the connection at the location nearest you.
  2. The app server in Seon, Aargau, holds chats, files and workspace disks. Sign-in runs through the operator's own Keycloak.
  3. Your workspace is its own container; a command the AI wants to run waits for your approval. The app server starts and stops it.
  4. Third-party API keys sit in a separate key service on its own Swiss VM; the workspace only ever holds placeholders.
  5. 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.
  6. 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.
  7. 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

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

RecipientLocationPurpose
Featherless and Global DPA Annex III subprocessorsUSA, Singapore and other locations without a region guaranteeModel inference; provider-internal fallback possible
StripeIreland and USAPayment processing
CloudflareUSA; edge location nearest youReaching the site, DDoS protection
IONOS SEGermanyOutbound network gateway for containers; encrypted offsite backup copies, without the decryption key
SMTP2GONew Zealand company; sending locations depend on provider routingSystem email; incoming operator mailbox is hosted in Switzerland
GoogleUSAOptional Gmail, Drive and Calendar connectors, only if enabled; sign-in uses the operator’s Keycloak
InfomaniakSwitzerlandImage generation, only when you request an image
MoonPay Commerce / Helio, BybitSee the Privacy PolicyManual credit top-ups; the payment settles to the operator’s custodial Bybit USDC wallet
AnthropicUSAAutomated, 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

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