These are the technical and organisational measures MergeLabs GmbH maintains as processor for the Cothena platform. They form Annex 2 of the Data Processing Addendum. A more detailed description is available to clients and prospective clients on request, under a confidentiality agreement.
Hosting
- All Cothena production servers and databases are hosted in Frankfurt, Germany.
Encryption
- Connections between your browser or app and Cothena are encrypted with TLS (HTTPS only, with HSTS).
- Every backup is encrypted with AES-256 before it leaves our servers.
- Emails to a client’s own users (such as sign-in codes and password resets) leave the platform over an encrypted connection to MergeLabs’ email provider. Emails to a client’s guests and customers are sent through the email provider the client connects.
Access control
- Fine-grained, role-based permissions: roles, sub-roles and individual permissions control what each team member can see and do.
- Sign-in uses time-limited access tokens, renewed automatically. In the Management Panel, users can see and end their own sign-in sessions.
- Users cannot grant permissions they don’t hold themselves.
- Connected apps sign in through OAuth 2.1 with PKCE: users approve each app by name, and the app never sees their password.
- Sign-in attempts are rate-limited.
- Passwords are stored only as salted hashes, never in readable form.
- MergeLabs staff access to production is limited to personnel who need it and bound by confidentiality.
Separation of client data
- Cothena is designed so that each signed-in request is limited to the user’s organisation: the organisation is taken from the user’s session, not from data a user or integration sends.
- Cothena is built as independent services, each with its own database.
- The application services run in minimal, hardened containers without a shell or package manager, as non-root users.
Credentials
- The credentials Cothena’s own services use are managed centrally in a dedicated secrets vault, stored there encrypted and loaded at runtime.
- Cothena’s interfaces and AI tools are designed not to return stored credentials (e.g. email server passwords, payment keys).
Change management
- Every production release is built and deployed from version control through automated pipelines.
- Builds check third-party dependencies for known vulnerabilities.
- Cothena runs on current, vendor-supported versions of its runtime and frameworks, which we update regularly, including for security fixes.
Integrity
- Changes made through Cothena Assist are recorded with who approved them, and when.
Subprocessor management
- Subprocessors are engaged only under data processing terms and are reviewed before they are engaged.
Availability and recovery
- Encrypted backups of the production databases are stored offsite in Google Cloud in Berlin, Germany, separate from our hosting provider.
- Certain destructive maintenance operations are blocked in production.
Physical security
- The data centres are operated by our hosting provider, which is responsible for their physical security.
Incidents
- Security incidents are handled under a documented internal procedure.
- Personal data breaches are reported to clients without undue delay and within 72 hours, as set out in the Data Processing Addendum.