SECURITY & PRIVACY
Security, data protection, professional secrecy, and official secrecy.
The protection of confidential information and the security of your data are our highest priority. On this page, we provide full transparency and detail regarding how Sereos protects the data you upload and process on Sereos. Please do not hesitate to contact us if you have any questions.
Swiss Cloud
Encryption at rest and in transit
Zero Data Retention
No AI Training
Professional and Official Secrecy
WHAT YOU CAN RELY ON
Your data remains protected. Your client matters remain confidential.
Multi-Layered Security
All customer content is protected by multi-layered security measures ("Defense in Depth"). Our security architecture strictly restricts who can store, transmit, process, or decrypt data.
Sovereign Swiss Cloud
Data is stored exclusively in encrypted form ("encryption at rest") within a sovereign, ISO 27001-certified Swiss cloud environment with no ties to the EU or the US.
Professional Secrecy and Official Secrecy
As an auxiliary person, Sereos is contractually bound by the professional secrecy and official secrecy obligations of its clients. Furthermore, all engaged technology providers—particularly those for hosting and AI inference—are bound by specific supplementary agreements to comply with the corresponding confidentiality obligations.
Zero Data Retention
A "Zero Data Retention" policy applies to all language models used. There is no permanent storage of prompts, files, audio recordings, or AI outputs by the LLM providers.
No AI training on your data
No use of your data for model training or for the providers' own purposes.
No human review
Human review of your content by the LLM providers, including for abuse monitoring purposes, is disabled. There is no access to or inspection of your content by employees of the LLM providers.
AI MODELS
You select which AI models are deployed.
Depending on the requirements for sovereignty and performance, three deployment options are available. All of them comply with data protection regulations and preserve professional and official secrecy.
Sereos Horizon – our standard solution
Sereos Horizon combines sovereign EU language models with high-performance frontier models via Microsoft Azure. Processing via Microsoft Azure takes place at server locations within the EU or EEA and includes all necessary technical configurations and contractual assurances to maintain professional secrecy and official confidentiality.
Sereos Alps – Non-US
Sereos Alps relies exclusively on open AI models hosted by sovereign EU-based providers and operated within a hardware-secured "Trusted Execution Environment" (Confidential Computing). This provides you with an alternative that has no nexus to the United States.
Operation within your own infrastructure
Upon request, you may operate Sereos on-premises in your own data center or private cloud. We also support installations that are fully isolated from the internet (“air-gapped deployments”).
SPECIFIC PROTECTIVE MEASURES
How Sereos specifically protects your data.
Find out what measures we implement to protect your data and the rationale behind them.
Data Residency and Encryption
protective measure
What We Do
Protects against
Purpose of Processing
Data residency in Switzerland
Customer content is stored exclusively in Swiss data centers with a sovereign Swiss cloud provider (with no EU or US nexus).
Unnecessary cross-border data transfers and the associated legal and geopolitical risks.
Confidential client and official government data should be hosted in Switzerland with a sovereign Swiss provider.
Encryption of data at rest (Encryption at Rest)
Content, file names, paths, and extracted text within protected workspaces are encrypted at the application level prior to storage. Additionally, standard encryption at rest is applied to the data.
The reading of confidential content in the event of unauthorized database access or the loss of a data storage medium.
Protection shall not rely solely on the database never being compromised.
Segregated Key Management
Cryptographic keys are stored and managed separately from encrypted data. Each customer maintains separate keys and access permissions.
To the joint compromise of data and keys, as well as unauthorized cross-organizational or cross-client access.
Encryption is effective only when keys are managed separately and subject to restricted access controls.
Searchable Encryption
Searching encrypted files uses key-derived search terms that cannot be read in plain text, rather than plain text indices.
The disclosure of confidential terms, names, or case information via the search index.
A search function must not circumvent the encryption of the documents.
Encryption in Transit
The connection between the browser and Sereos is established via TLS/HTTPS. HSTS, Content Security Policy, and additional security headers supplement this transport layer security. Internal traffic between individual Sereos servers is likewise conducted exclusively via the even more secure mTLS encryption.
The interception or tampering with data in transit, standard browser attacks, and compromised internal services eavesdropping on network traffic (defense-in-depth).
Confidential data must be protected both at rest and in transit.
AI Processing
protective measure
What We Do
Protects against
Purpose of Processing
No AI Training and Zero Data Retention
For customer content, we solely deploy authorized LLM configurations under which prompt and response content are neither utilized for model training nor permanently retained following the completion of processing (strictly limited to volatile use on GPU hardware for inference and prompt/KV caching). Human review of this content by the LLM provider is strictly excluded. Technical usage and billing metadata are segregated and kept to the minimum necessary.
Any subsequent reuse, human review, or disclosure of confidential AI inputs and outputs.
Client-matter and public authority data must not be retained in a model provider's content data repositories and/or used by the provider for its own purposes (e.g., AI training).
No human abuse review by LLM providers (no abuse monitoring)
For all language models deployed, human abuse monitoring and review by the providers (referred to as abuse monitoring) is disabled.
The review, tagging, or transmission of confidential client and regulatory data by the model provider for human abuse monitoring and verification.
Even abuse protection mechanisms must not grant the LLM provider access to confidential content.
Confidential computing at LLM provider (only applicable to Sereos Alps)
To the extent that AI processing takes place outside of Switzerland, we engage a sovereign European provider that processes data within a hardware-secured Trusted Execution Environment (TEE).
access by infrastructure providers, administrators, or the AI provider during processing.
Traditional encryption protects data at rest and in transit. Confidential computing extends this protection to data in use.
Remote attestation (only for Sereos Alps)
Prior to processing, the identity and integrity of the confidential execution environment are cryptographically verified. Data is transmitted exclusively to successfully attested environments.
Processing by manipulated or unauthorized systems.
We do not intend to rely solely on security assurances, but rather to conduct technical audits and verifications of the processing environment deployed.
Access Control and Application Security
protective measure
What We Do
Protects against
Purpose of Processing
Tenant Isolation
Organizations and their data scopes are technically segregated. This segregation is further enforced at the database level.
Access to data of other organizations—even with knowledge of an internal object identifier.
Multi-tenant isolation must not rely solely on the user interface or isolated application-level checks.
Role-Based Access Control (RBAC) and Access Control Lists (ACL)
Read, edit, and administrative privileges may be assigned separately to users, groups, roles, and automated agents. Explicit denials shall supersede all other permissions.
Excessive, improperly inherited, or ambiguous access permissions.
Not every authorized reader should be permitted to modify content or manage access rights. This also applies to AI agents.
Principle of Least Privilege (Least Privilege)
Users, services, background processes, and AI agents are granted only the permissions strictly necessary for their specific tasks. Standard user access rights shall not include any privileged bypass permissions.
The escalation of damages resulting from compromised accounts or services.
A security incident shall be contained to the smallest possible scope of data and functionality.
Secure Sessions
The browser does not receive any access or refresh tokens, but merely a randomized session identifier stored in a cookie secured with the Secure, HttpOnly, and SameSite attributes.
Token theft, session hijacking, and unauthorized access via browser scripts.
Long-lived authentication credentials shall be processed exclusively on the server side.
Time Limitation and Revocation
Sessions and technical permissions are of limited duration. Users may revoke active sessions and devices that are no longer trusted.
The permanent use of lost, stolen, or no longer required access credentials.
Access rights shall only be retained for as long as strictly necessary.
Protection against Cross-Site Request Forgery (CSRF Protection)
State-altering requests require a session-bound CSRF token and must originate from an authorized Sereos domain.
Actions that an external website attempts to execute on behalf of an authenticated user.
A valid session alone does not constitute proof that an action was intentionally performed from within Sereos.
Controlled external connections, no web search
External connections may only be established to explicitly authorized destinations and interfaces. Requests shall be restricted by size limits, timeouts, rate limits, and response validation. Furthermore, all agents are precluded by default from accessing the internet or web search capabilities.
Uncontrolled data transfers and manipulated external destination addresses; data exfiltration via prompt injections or other malicious instructions or tools.
An application handling confidential data must not be permitted to invoke arbitrary external services.
Separate Provider Access Credentials
Third-party provider credentials are administered separately. User tokens and internal access credentials are not disclosed to third-party providers.
The disclosure of internal access credentials and user identities to third parties.
Each provider shall only receive the information necessary for its specific assignment.
Data-minimizing logging
Content data logging is disabled along sensitive processing pathways. Specifically, our logging policies prohibit the storage of document contents, prompts, cookies, tokens, and API keys within technical logs.
Additional copies of confidential content in technical logging systems.
Logs should ensure secure operations without constituting a sensitive dataset in their own right.
Operations and Organization
protective measure
What We Do
Protects against
Purpose of Processing
Hardened Infrastructure
Services operate in isolated, hardened containers.
The propagation of successful attacks to other services or the host system.
Even a compromised service should have as few privileges and as little latitude of movement as possible.
Versioning and Audit Events
Modifications shall be subject to auditable version control. Security-relevant events shall be recorded via protected audit logs.
Undetected modifications and lack of traceability.
Confidential work and security-sensitive processes must remain auditable.
Automated Security Testing
Tests examine, among other things, multi-tenant isolation, access permissions, encryption, plaintext leaks, session management, CSRF, and manipulated input.
Recurring security vulnerabilities and inadvertent degradation of existing safeguards.
Failed security testing precludes release approval.
GDPR-compliant data processing
Sereos acts as a data processor pursuant to Art. 9 FADP. A data processing agreement compliant with legal requirements is concluded with customers. If sub-processors are engaged, they are likewise contractually obligated to comply with data protection requirements.
The transfer of personal data to third parties without authorization or without equivalent data protection obligations.
Compliance with data protection requirements must be ensured throughout the entire processing chain.
Preservation of Professional and Official Secrecy
Sereos is contractually bound as an auxiliary person to professional secrecy (Art. 321 of the Swiss Criminal Code [SCC] and Art. 13 of the Swiss Federal Act on the Freedom of Movement for Lawyers [BGFA]) or official secrecy (Art. 320 SCC) and is committed to confidentiality accordingly. When engaging additional service providers, Sereos contractually passes this confidentiality obligation on to such providers. The transmitted data is additionally protected by the technical measures described in this overview.
A disclosure that, although permissible under data protection law, could breach specific statutory confidentiality obligations.
Persons bound by professional or official secrecy obligations may only engage service providers if they are selected with due care, their duty of confidentiality is contractually secured—including with respect to subcontractors—and the transmitted data is adequately protected.
Data protection by design and by default
Data protection, data minimization, and privacy by default are mandatory development principles.
Risks that are only identified retroactively and can only be remedied with difficulty.
Protective measures shall be an integral component of the architecture by design and shall not be added retroactively.
Controlled Software Supply Chain
External dependencies shall be minimized and vetted for security, licensing compliance, maintainability, and trustworthiness prior to deployment. Security-relevant updates are prioritized and applied on a risk-based approach.
malicious code, compromised packages, and uncontrolled dependencies.
A significant portion of modern software attacks is perpetrated via the software supply chain.
READY FOR A CONSULTATION?
Speak with us about your specific requirements regarding data privacy, professional and official secrecy, and legal compliance.