Licensed to be used in conjunction with basebox, only.
// security
Security & Compliance
Applies to
Product: Cloud · Server · Audience: Security / Compliance reviewer
For decision makers
Overview, ISO 27001 and topics for the works council: basebox.ai/en/security. These pages provide the technical evidence.
For security officers, data protection officers and compliance reviewers. The section follows the product model: what applies to Cloud and Server is kept separate – and where the Cloud transition phase until November 2026 differs, that is stated separately, and a customer-owned server hosted at basebox sits under Server security – not under Cloud. Where a statement is not yet substantiated, that is said explicitly.
In this section
- Deployment models – Cloud, Server, the model of shared responsibility and the Cloud transition phase until November 2026
- Data & architecture – flows, storage, encryption, retention, deletion
- Cloud security – isolation, infrastructure, administrative access, backup
- Server security – dedicated hardware, customer data center, hosting at basebox, remote maintenance, air-gapped operation
- External services – model providers, web search, connectors
- Audit & logging
- Compliance – GDPR, Data processing & sub-processors, ISO 27001, NIS2, EU AI Act
The short version
| Question | One-sentence answer | Details |
|---|---|---|
| Do chats and documents leave the environment? | In Cloud and Server, in normal operation no; the deliberate, administrator-controlled exceptions are web search, connectors and the optional app with an external model. In the Cloud transition phase until November 2026 every model request goes to Google Vertex AI in Frankfurt | Data flows |
| Where do the language models run? | In the Cloud on servers operated by basebox in the data center of noris network AG in Munich-East; customers share the AI model, a model just for your organization is available on request. Providers of additional compute only if they are on your list of sub-processors. In the transition phase until November 2026 the Cloud uses Google Vertex in Frankfurt until the move. On Server on customer-controlled hardware | Model providers |
| Who is the controller under data protection law? | Always the customer; in the Cloud basebox is a processor, the DPA is part of every contract; on a self-operated server basebox has no access | Data processing |
| Is everything encrypted? | From outside, basebox is reachable only via HTTPS; inside the cluster the services talk over a private network without encryption of their own, and across host or zone boundaries TLS is mandatory. At rest the application itself does not encrypt today – encrypted disks do that; the Cloud's backups are encrypted | Encryption |
| What does the audit log record? | At level "Standard" sign-ins and changes, no chats; chats only at level "High", then with a visible notice in the chat | Audit & logging |
| How does basebox get onto a server? | Only when commissioned, via PAM/VPN, time-limited, approved by the customer and revocable | Remote maintenance |
| Does it work without internet? | Yes – basebox Server can run air-gapped; web search and online model download are then unavailable | Air-gapped environments |
| Which certifications are there? | ISO 27001 certified (ISMS of basebox GmbH); the BSI C5 Type 1 attestation for the Cloud is in progress; basebox is not a medical device | ISO 27001 |
| Is there a software bill of materials (SBOM)? | Yes, generated automatically for every release, in CycloneDX 1.6 format; customers download it in basebox under Version Info | Software bill of materials (SBOM) |
| Which availability applies? | basebox does not commit to a minimum availability; support is available on working days from 9:00 to 17:00, first response within one working day | Infrastructure |
How to read these pages
- Every page carries an Applies to box at the top. Check first whether your deployment is meant – statements about the Cloud do not apply to a server and vice versa.
- Assess the transition phase separately. For Cloud accounts in the transition phase until November 2026, different processing locations and sub-processors apply until the move (Transition phase).
- Where this documentation cannot yet substantiate a statement, it points to the way to clarification – usually datenschutz@basebox.ai for data protection and compliance questions and support@basebox.ai for technical ones.
- The EU AI Act compliance package – Compliance, Infrastructure policy, Model register, Safety notice, Disclaimer – refers to basebox Server and is dated October 2025. The pages here are the continuously maintained description; where they differ, the versioned package governs for contractual purposes.
What to take into a review
When you describe basebox in a data protection impact assessment, a security concept or a vendor assessment, these pages are usually sufficient: Deployment model or Server, Data flows, Storage, Encryption, Audit & logging, Shared responsibility and GDPR. For the web search connector there is additionally the Introduction to web search security and, on request, the full policy.
Next step: Deployment models · Data processing & sub-processors