MergeLabs GmbH provides the Cothena platform and processes personal data on behalf of its clients as their processor. These are the subprocessors MergeLabs engages to do so, with what each one does, which data it handles and where. The list also names providers that handle data for which MergeLabs is itself the controller (crash reports, app installation and device registrations, sign-in security records), so that every provider appears in one place; the privacy policy describes that processing.
| Activity | Provider | Data categories | Location | Transfer mechanism |
|---|---|---|---|---|
| Hosting and storage | Akamai Technologies International AG (Akamai Cloud) | All client data | Frankfurt, Germany | Servers in Germany; contracting entity in Switzerland (EU adequacy decision) |
| Network security and delivery | Cloudflare, Inc. | All data sent to and from Cothena while in transit, including IP addresses | Global network | EU–US Data Privacy Framework; standard contractual clauses in the provider’s data processing terms |
| Backup storage (encrypted) | Google Cloud EMEA Limited, Ireland (Google Cloud Storage) | Encrypted database backups | Berlin, Germany | Data stored in Germany; contracting entity in the EU |
| Email to the client’s own users (e.g. sign-in codes, password resets) | Bird B.V., Netherlands (SparkPost, EU-hosted) | Name, email address, message content | European Union | Processed in the EU; contracting entity in the EU |
| Support by email | Google Cloud EMEA Limited, Ireland (Google Workspace) | Personal data a client includes in emails to MergeLabs support | Google’s global data centres | Standard contractual clauses in Google’s Cloud Data Processing Addendum; EU–US Data Privacy Framework |
| Push notifications (staff and guest apps), only for clients who use MergeLabs’ Google account instead of their own | Google LLC, USA (Firebase Cloud Messaging) | Notification text (alert headline and message; in the staff app, also team chat sender name and message text), internal user number, event and resource identifiers, device push token, installation identifier | Global, including the USA | EU–US Data Privacy Framework; standard contractual clauses in the provider’s data processing terms |
| Push delivery to iPhones, via Firebase Cloud Messaging, only for clients who use MergeLabs’ Google account | Apple Inc., USA (Apple Push Notification service) | Notification text, device push token | Global, including the USA | EU–US Data Privacy Framework |
| App diagnostics and crash reporting (staff and guest apps; MergeLabs as controller, only with the user’s consent) | New Relic, Inc., USA (New Relic) | Crash reports, error logs, screens opened, device model, OS and app version, language, IP address, internal staff user number | EU region | EU–US Data Privacy Framework; standard contractual clauses in the provider’s data processing terms |
| Cothena Assist (AI provider account) | SwingStep GmbH, Germany, which holds the API account through which Cothena Assist uses the AI model below, under a written agreement with MergeLabs based on the EU standard contractual clauses for processors (Commission Implementing Decision (EU) 2021/915) | Prompts and the event data relevant to each request, passed on to the AI model | European Union (contracting entity); processing as for the AI model below | Contracting entity in the EU |
| Cothena Assist (AI model) | Anthropic Ireland, Limited (Claude models), engaged by SwingStep GmbH | Prompts and the event data relevant to each request; inputs and outputs are kept by the AI provider for up to 30 days for safety and security, and are not used for training | Processing with global routing; storage in the USA | Standard contractual clauses in Anthropic’s data processing addendum |
Not subprocessors
Some services a client may connect to Cothena are chosen and contracted by the client, so they are not MergeLabs subprocessors:
- the client’s own AI app or provider, when connected to Cothena through MCP;
- the client’s own payment provider;
- the client’s own email provider, which sends all emails to the client’s guests and customers;
- the client’s own Google Cloud account, which sends push notifications to the apps through Google Firebase Cloud Messaging and, for iPhones, Apple’s push service. If a client asks to use MergeLabs’ account instead, Google and Apple act as MergeLabs subprocessors, as listed above.
Changes to this list
MergeLabs announces any new or replacement subprocessor at least 30 days before it takes effect, by publishing a new version of this list and by email to each client’s contact named in their agreement. Every new version also appears in the legal updates feed. A client may object during that period by writing to [email protected], as set out in the client’s agreement and the Data Processing Addendum. If the objection cannot be resolved, the client may terminate without penalty.