Data protection and security
This page is for the people responsible for data protection and NIS2 at our customers. It shows where we process data, who is involved, how we protect it and how we report incidents.
Last updated: 12 November 2026
- Role
- Art. 28Processor, with a DPA before we process real data for the first time
- Server
- EUContabo, Lauterbourg data centre in France
- Language models
- EuropeOnly Mistral and Cortecs, in data centres in Europe
- Your content
- 0 minutesstored by the AI provider, no training with your data
- Incident reporting
- 12 hfrom awareness, before your 24-hour deadline under NIS2
Role and contract
For data we process on your behalf, we are the processor and you are the controller. Before we process real data for the first time, we conclude a data processing agreement (DPA) with you under Art. 28 GDPR. It ties the data to the purpose of the engagement. We conclude the contracts with the AI providers ourselves, and you approve these sub-processors in the DPA (Variant B). Large customers may keep their own contracts (Variant A).
Where data is processed
Our services run on a virtual server at Contabo in the Lauterbourg data centre in France. Each application has its own container and its own data directory. Where the system allows it, your data stays on your servers. What a product stores with us is stated in its data sheet, with location, period and purpose. For your data we use language models only through Mistral AI in Paris and Cortecs in Vienna. Mistral processes in data centres in EU and EFTA countries, Cortecs only at data centres in the EEA that we approve.
Sub-processors
These four companies are on our list of sub-processors. Which of them act for you depends on the product and is stated in Annex 3 of your DPA. If you have your own contracts with AI providers (Variant A), Mistral and Cortecs do not apply.
| Company | Service | Location | Contract | Storage and separation |
|---|---|---|---|---|
| Mistral AI SASParis, France | Language models from Mistral and open models such as GLM and DeepSeek through Mistral's EU endpoint. | Europe. Data centres in EU and EFTA countries. | Data Processing Addendum (version of 27 July 2026) with Standard Contractual Clauses, valid since 31 October 2026. We process health data through Mistral only after a written commitment from Mistral. | Zero Data Retention, active since 5 November 2026: no storage beyond the answer. Training with API data is switched off. A separate key for each customer. |
| Cortecs GmbHVienna, Austria | Forwarding to open language models such as Kimi, GLM and DeepSeek, operated by data centres in the EEA. Never through the makers' APIs. | EEA. Only data centres that we approve, for example in France, Germany, Finland and Sweden. | Data Processing Agreement under Art. 28 GDPR (version of 11 August 2026), valid since 31 October 2026. On 5 November 2026 Cortecs confirmed in writing that it may process health data on documented instructions, provided that you, as the controller, lawfully commission the use under Art. 9 GDPR. | Inputs and outputs only in memory, request metadata for up to 12 months. Only data centres that, according to Cortecs, do not store. No training. A separate key for each customer. |
| Contabo GmbHMunich, Germany | Virtual server for our services, such as web interfaces, the sign-in service and mail. | EU. Lauterbourg data centre in France, operated by Contabo France SAS. | Data processing agreement under Art. 28 GDPR, concluded on 31 October 2026, also for health data. | What a product stores with us is on this server. The data sheet states periods and deletion. |
| Brevo SASParis, France | Sending our emails, such as notifications and sign-in codes. | EU, data centres in France and Belgium. Some of Brevo's sub-processors, for example for support, also in the USA. | Data Processing Agreement in the terms of use (version of 1 October 2025), with Standard Contractual Clauses and the EU-U.S. Data Privacy Framework. | Sending data: recipient, subject, time and a preview of the content. |
Mistral AI SAS
Paris, France
- Service
- Language models from Mistral and open models such as GLM and DeepSeek through Mistral's EU endpoint.
- Location
- Europe. Data centres in EU and EFTA countries.
- Contract
- Data Processing Addendum (version of 27 July 2026) with Standard Contractual Clauses, valid since 31 October 2026. We process health data through Mistral only after a written commitment from Mistral.
- Storage and separation
- Zero Data Retention, active since 5 November 2026: no storage beyond the answer. Training with API data is switched off. A separate key for each customer.
Cortecs GmbH
Vienna, Austria
- Service
- Forwarding to open language models such as Kimi, GLM and DeepSeek, operated by data centres in the EEA. Never through the makers' APIs.
- Location
- EEA. Only data centres that we approve, for example in France, Germany, Finland and Sweden.
- Contract
- Data Processing Agreement under Art. 28 GDPR (version of 11 August 2026), valid since 31 October 2026. On 5 November 2026 Cortecs confirmed in writing that it may process health data on documented instructions, provided that you, as the controller, lawfully commission the use under Art. 9 GDPR.
- Storage and separation
- Inputs and outputs only in memory, request metadata for up to 12 months. Only data centres that, according to Cortecs, do not store. No training. A separate key for each customer.
Contabo GmbH
Munich, Germany
- Service
- Virtual server for our services, such as web interfaces, the sign-in service and mail.
- Location
- EU. Lauterbourg data centre in France, operated by Contabo France SAS.
- Contract
- Data processing agreement under Art. 28 GDPR, concluded on 31 October 2026, also for health data.
- Storage and separation
- What a product stores with us is on this server. The data sheet states periods and deletion.
Brevo SAS
Paris, France
- Service
- Sending our emails, such as notifications and sign-in codes.
- Location
- EU, data centres in France and Belgium. Some of Brevo's sub-processors, for example for support, also in the USA.
- Contract
- Data Processing Agreement in the terms of use (version of 1 October 2025), with Standard Contractual Clauses and the EU-U.S. Data Privacy Framework.
- Storage and separation
- Sending data: recipient, subject, time and a preview of the content.
We announce any planned change to this list in text form at least 30 days in advance. You may object.
Training and storage
We do not train any models with your data. At Mistral, training with API data is switched off, and Cortecs does not train. Mistral does not store inputs and outputs beyond the answer. Cortecs keeps them only in memory and forwards only to data centres that, according to Cortecs, do not store. Cortecs keeps request metadata for up to 12 months.
Measures
A selection of the measures that are in place. We send the complete technical and organisational measures (TOMs) under Art. 32 GDPR on request.
Responsibility
Philipp Gurndin provides the services personally and is responsible for data protection and security. Other people only with your written consent and after a written commitment to confidentiality.
Confidentiality
Confidentiality with no time limit, under the project contract and the non-disclosure agreement.
Sign-in
Personal accounts with a second factor through our sign-in service, roles per application.
Separation of customers
Each customer has a separate area, each application its own container with its own data directory.
Access to language models
Only through accounts with a data processing agreement, with a separate key for each customer.
Server administration
Only Philipp Gurndin. SSH only with a key, passwords switched off, lockout after failed attempts.
Country filter
Administration, internal web interfaces and SSH respond only from approved countries.
Access to your systems
Only by the route you specify, for example through your VPN, with personal accounts.
Encrypted transmission
HTTPS with TLS for all web services and interfaces, TLS for mail.
Keys and passwords
Encrypted in the server configuration or in the password vault. Not in the source code, not in logs, not in extensions.
Logs
No customer inputs in logs. Web server access without headers, on a rolling basis up to a maximum of 30 MB.
Development and testing
With fictitious data or data you have approved. ChatGPT and Claude subscriptions only for such tests.
Backup
Daily. Restoration tested, most recently on 24 October 2026.
Updates
Security updates of the operating system automatically, platform and applications regularly.
Monitoring
Automatic check of the services with an alarm, central error log on our server.
Deletion at the end of the contract
We delete data, copies and access, and confirm it in writing. Data in backups expires with their rotation.
Incidents
An incident is any event in which a customer's data could be lost, altered or made accessible to unauthorised persons. Even a suspicion counts. We report to you any incident that may affect your data at the latest 12 hours after we become aware of it: by email to your contact persons, by phone if necessary, with the information required by Art. 33(3) GDPR. You make the notifications to the authorities as the controller, and we supply the technical details for this.
Immediately
We contain the incident: switch off affected services, block access, replace keys, preserve traces.
12 hours
At the latest by then, we report the incident to you.
24 hours
Your early warning to the CSIRT under NIS2, in Italy CSIRT Italia, if you fall under NIS2.
72 hours
Your notification to the supervisory authority under Art. 33 GDPR, in Italy the Garante.
Afterwards
A written report on sequence of events, cause, consequences and measures.
Documents
Depending on the product, we prepare these documents for you before the start.
Data processing agreement (DPA)
Under Art. 28 GDPR, with the technical and organisational measures, the contact points and the list of sub-processors as annexes.
Data sheet
One sheet per product for your software and supplier inventory under NIS2: which data the product reads, sends and stores.
Data protection impact assessment (DPIA), technical part
The technical part under Art. 35 GDPR. You add the remaining part.
Zero Data Retention overview
Which AI provider stores inputs and outputs, with evidence.
AI guidance
Suggestions for using AI at your organisation: informing patients or clients, instructions and training for employees, approval before routine operation.
Non-disclosure agreement
Also before the first meeting with real data.
Project contract
With a separate section on professional secrecy, data protection and data security. Before production use, you can commission a security test by a third party.
We send the TOMs, the list of sub-processors, the Zero Data Retention overview and the security profile on request to gurndin@invariance.co, currently only in German.
What you need to tell your customers about AI: AI disclosure for customers
Answers to NIS2 supplier questions
- Does data go to AI providers or other services? To which ones, in which countries?
- For processing on your behalf, only to the sub-processors in Annex 3 of your DPA or to providers with whom you have a contract yourself. Language models run only through Mistral and Cortecs in Europe, our own services at Contabo in France.
- Are inputs, results, errors or usage logged?
- Inputs and results are not. We log errors without content, and access to the web server without headers and on a rolling basis.
- Is data used to train AI models?
- Not through the APIs we use on your behalf. We do not train any models with your data, at Mistral training with API data is switched off, and Cortecs does not train.
- Is there a data processing agreement that excludes other purposes?
- Yes. Before we process real data for the first time, we conclude a DPA with you under Art. 28 GDPR, which ties the data to the purpose of the engagement. We have our own contracts with Mistral, Cortecs, Contabo and Brevo.
- Can data transmission be limited or the software be switched off at short notice?
- Yes. You can block extensions by policy and block our services at your firewall. We can switch off immediately any service that we operate.
Contact for security questions and incidents
Philipp Gurndin gurndin@invariance.co +39 350 0404 001 PEC gurndin@pec.it