Connecta – How we ensure IT security, data protection and availability.
As of: 7 November 2026 (Connecta 4.1)
1 Introduction
The highest protection of the data of our customers, and especially of the advice seekers who place their trust in our software, is one of the core aspects of the Connecta product.
Our standards go beyond compliance with regulations. For us, data protection is not just a checklist. It is one of our most important principles.
Based on this conviction, we designed and built the software from the outset with a "zero data leakage concept".
Furthermore, our technical implementation relies on the best available methods and technologies, such as complete end-to-end encryption of all chat and video/audio communication.
2 How we secure our customers' content
2.1 Hosting in certified data centres
Connecta services are operated exclusively in selected data centres that meet the highest data protection and security standards (ISO 27001, ISO 27018, BSI C5, Trusted Cloud Service). Our hosting partner is gridscale, with data centres in Germany.
2.2 Change management
Connecta applies a systematic approach to change management, so that updates are thoroughly reviewed, tested, approved and well communicated.
2.3 Regular penetration tests
We regularly conduct manual and automated vulnerability and penetration tests.
2.4 Web Application Firewall (WAF)
Our Connecta infrastructure is protected by a WAF (Web Application Firewall).
2.5 Secured technical interfaces
Technical interfaces for operations and monitoring are secured and not publicly accessible.
3 How we ensure the reliability of our services
3.1 Guaranteed service levels
We offer Service Level Agreements for all our customers.
3.2 Emergency planning
We maintain an active contingency plan for our production environment.
3.3 Scaling
We use automatic scaling during times of high demand.
3.4 Monitoring and reporting
We continuously monitor performance to ensure consistently fast response times and service availability. Anomalies automatically trigger an alert to our operations team.
4 How we protect our customers' data
4.1 GDPR compliance
Connecta is fully GDPR-compliant and follows data protection regulations.
4.2 Data encryption
All data is encrypted both in transit and at rest using state-of-the-art key lengths and algorithms.
- TLS 1.2 or TLS 1.3 (transport encryption, in line with BSI TR-02102-2)
- AES-128, AES-192, AES-256 (symmetric encryption, in line with BSI TR-02102-1)
- RSA-OAEP with 3072 bit (asymmetric encryption for end-to-end encryption, in line with BSI TR-02102-1)
- SHA-256, SHA-512/256, SHA-384, SHA-512 (hash algorithm)
- We follow the requirements of the BSI's technical guidelines.
4.3 End-to-end encryption of all communication
Communication between advice seekers and counselors is end-to-end encrypted, in chat as well as in audio and video calls. A master key is generated on the user's device and never leaves that device.
- New conversation rooms receive keys based on AES-256-GCM, in line with BSI TR-02102-1. With 256-bit keys, we exceed the current BSI recommendations, which call for at least 128 bits.
- The private key of each account is encrypted with AES-256-GCM. The key for this is derived from the password using PBKDF2 with 600,000 iterations.
- No server decrypts room keys. Keys are converted exclusively in the user's browser.
- End-to-end encryption is mandatory in video calls. No one can switch it off for the other participants, and a device that cannot encrypt does not join the call unencrypted.
- The contents of file attachments are also stored and transmitted end-to-end encrypted.
4.4 Backups and recovery
Data is replicated across three affinity zones. Daily S3 backups are created encrypted. Manual recovery tests are conducted at least every six months. The configuration of the user management is also backed up, and the backup encryption key is protected against accidental changes.
4.5 Information security management
A structured process is followed for information security incidents.
4.6 Secure login and sessions
- Two-factor authentication via app or email, as recommended by the BSI.
- After a password change or password reset, every active session of the account ends, on all devices.
- Logging in, logging out and renewing a session only affect the session for which they were started, even when Connecta is open in several tabs.
- Passwords are reset exclusively through the secured Connecta process.
4.7 Tenant separation and access rights
The data of each organisation is strictly separated. This separation is additionally safeguarded in the statistics and in the user management as well. Additional roles do not override the separation. Only the authorised participants of a conversation receive access to video calls.
4.8 Data-minimising logs
We do not write access tokens, passwords, names or the contents of requests to our logs. Where browser or system messages may contain such details, we remove them before storing.
4.9 Traceable audit log
Changes in the admin area are recorded in a chained audit log. Gaps or subsequent changes are detected automatically, even after old entries are deleted at the end of the retention period. Instead of names or internal identifiers, statistics reports contain pseudonyms that are generated with a secret key (HMAC-SHA256, in line with BSI TR-02102-1).
5 How we make our software source code secure
5.1 OWASP
Connecta development follows the standards of the Open Web Application Security Project (OWASP).
5.2 Code reviews
Every code change is subject to the four-eyes principle.
5.3 Automated vulnerability testing
Our code is automatically tested and scanned for vulnerabilities. Third-party libraries in use are continuously monitored for security-relevant vulnerabilities. We apply security updates promptly, and once a quarter we update all libraries to their latest versions.
5.4 Quality assurance (QA)
Connecta's quality assurance follows proven practices of secure software development, including formal design reviews, threat modelling and risk assessments.
5.5 Secure display of content
Connecta displays messages, texts from your organisation and inserted content without inserting HTML directly into the page. Only approved elements and checked links reach the display. This protects against injected malicious code.
5.6 Content Security Policy
A Content Security Policy notifies us when a browser would load content from external addresses. This allows us to detect unexpected access early.