New: WhatsApp AI that knows your customers. What's new

Security and architecture

Built in the EU, scoped per workspace, honest about AI.

This page describes the system as it runs today: what talks to what, where the data lives, and which controls sit between a visitor's message and anyone who shouldn't see it. If something here doesn't match what you find, let us know and we'll fix either the system or the page.

How the pieces work together

A message from your website passes through five layers. None of them is reachable from the internet, except the first.

  1. Low 1

    Web app · cybix.app

    Next.js, server-side rendered

    Dashboard, marketing site, Messenger widget page and the WordPress/mobile handoffs. Every browser call goes through this layer. The API is never exposed directly.

  2. Low 2

    API · FastAPI

    Python, scoped per workspace

    Conversations, contacts, tickets, knowledge, billing. Every request carries a signed token with the user and the workspace. Queries are filtered to that workspace.

  3. Low 3

    Real-time gateway

    WebSockets + push

    Delivers new messages to the dashboard, the mobile app, and the Messenger widget. Payloads contain only what the recipient is allowed to see.

  4. Low 4

    BIX · AI agent

    Retrieval + model call

    Answers are based on your own crawled knowledge hub, stored as documents per workspace on our servers. Only the current conversation and the retrieved snippets are sent to the model provider.

  5. Low 5

    Data

    Database + volumes per deployment

    Each workspace has its own database file for conversations, contacts, tickets, and inboxes, and its own folder for the knowledge hub. The main database only contains accounts and billing. White-label and reseller customers get their own stack and volumes on top of that. Everything stays on the same EU volume.

Where your data lives

In storage

Hetzner data centers in Germany and Finland. The contractual processing location is the EU/EEA only. Transfers outside it require your prior consent under the DPA.

On its way to providers

The AI model provider receives the conversation text needed to produce a reply. Translation and transcription providers only receive the text or audio being processed. The full versioned list is on the subprocessors page.

Self-hosted

Customers with a license run the same container stack on their own infrastructure. Nothing leaves their network except the provider calls they configure themselves.

Checks

Identity and access

  • Passwords are stored as scrypt hashes (N=2^14), never as plain text. Signing in with Google or SSO doesn't store a password at all.
  • Sign-in with Google is only accepted for verified email addresses. An unverified address therefore cannot claim an existing account.
  • Sessions use HttpOnly, secure cookies. API tokens are signed JWTs containing the user, role, and workspace. A token from one workspace can't read another.
  • Roles: owner, admin, agent, and lite. Platform-level access is checked against the database on every request, so an account loses it immediately after being downgraded.

Isolation between tenants

  • Conversations, contacts, tickets, and inboxes live in a separate database file per workspace: a request is tied to exactly one file of one workspace, so rows from another workspace aren't just filtered out, they're not on the connection at all. Knowledge documents live in a separate folder per workspace, so BIX can only retrieve from the workspace it's answering for.
  • Visitors who talk to the Messenger get their own token, tied to a single conversation. They can't request or read other conversations.
  • White-label and reseller deployments run as separate stacks with separate databases and volumes. The isolation is physical, not just a WHERE clause.

Encryption and transport

  • All traffic runs over TLS (Let's Encrypt certificates, automatically renewed at the edge proxy). Internal services are not exposed to the internet.
  • Voice and video calls are streamed peer-to-peer via WebRTC (DTLS-SRTP), with no media relay provider in between, and are not recorded unless your workspace enables conversation transcripts.
  • Secrets (API keys, signing secrets, provider credentials) live only in the server's environment configuration, never in source code and never in logs.

AI safeguards

  • In the widget, BIX is always labeled as an AI agent and greets visitors that way too. The EU AI Act Art. 50 disclosure is on by default and can't be turned off.
  • A teammate can take over any conversation. The visitor can ask for that at any time. On handover, the bot pauses for that thread.
  • Answers are based on the customer's own content. Conversation text is only sent to the model provider to produce the answer and is not used by us to train models.
  • Workspaces that handle sensitive data can turn on restricted mode: message content then never appears in list previews or notifications, only in the thread itself.

Manage

  • Hosting in Hetzner Online GmbH data centers in Germany and Finland, certified under ISO 27001 and BSI C5 Type 2, under a signed data processing agreement per GDPR Art. 28.
  • Deployments are reproducible container stacks. The same image runs on cybix.app and on self-hosted installations.
  • Server logs (IP, timestamp, endpoint) are retained for 30 days for security and troubleshooting.
  • Deleting a workspace permanently and immediately erases its conversations, tickets, contacts, and knowledge documents.

Compliance, precisely worded

FrameworkWhat appliesProof
GDPRCYBIX is your processor. You remain the controller of your customers' data.Data processing agreement · Privacy policy
Hosting certificationsISO 27001, BSI C5 Type 2, and § 8a BSI-KritisV are held by Hetzner Online GmbH for the data centers where CYBIX runs. CYBIX itself does not hold an ISO certificate.Hetzner DPA v1.2 (signed on Aug 26, 2026), Appendix 2 TOMs · annual independent TOM audit
EU AI Act (Regulation 2024/1689)BIX is a limited-risk AI system. The Art. 50 disclosure, human handover, and logging are built in. Customers who use BIX for Annex III purposes take on high-risk obligations.AI Act statement
Data residencyStorage and processing in the EU/EEA. Named non-EU providers only for the listed steps, under SCCs or the EU-US Data Privacy Framework.Subprocessors

Report a vulnerability

Email support@cybix.app with “Security” in the subject line. We confirm receipt within two business days, keep you informed, and take no action against researchers who test in good faith and stay within their own accounts.