This Data Processing Addendum (“DPA”) applies to the agreement between the client named in the order form (the “Client”) and MergeLabs GmbH (“MergeLabs”) for the use of the Cothena platform, including an order form under the Cothena Master Services Agreement (the “Agreement”). It governs personal data that MergeLabs processes on behalf of the Client under the Agreement, including during onboarding, support and any grace or retrieval period, and until return or deletion is complete. This DPA forms part of the Agreement where the Agreement or its order form refers to it. It applies in the version in effect on the date the Agreement is signed, unless the Agreement says otherwise.
1. Roles and scope
The Client is the controller and MergeLabs is the processor of the personal data described in Annex 1. Where the Client is itself a processor for another controller, MergeLabs acts as its sub-processor. Each party will comply with applicable data protection law, including the GDPR. The Client determines the purpose and lawful basis of the processing, provides the required notices to data subjects and controls who has access. MergeLabs processes sign-in security records, app installation and device registrations, and crash reports as an independent controller, as described in its privacy policy. Delivering the notifications the Client sends, including their text, is processing on the Client’s behalf under this DPA.
2. Instructions
MergeLabs processes personal data only on the Client’s documented instructions, including the Agreement, this DPA, the settings the Client’s authorised users choose in the platform and the Client’s written requests. MergeLabs will immediately tell the Client if it believes an instruction infringes data protection law, and may suspend carrying it out until the Client confirms or changes it. Instructions that go beyond the services agreed in the Agreement may be charged, after MergeLabs has told the Client the expected cost. If MergeLabs is legally required to process personal data otherwise, it will inform the Client beforehand, unless the law prohibits that.
3. Confidentiality
MergeLabs ensures that persons authorised to process the personal data are bound by confidentiality.
4. Security of processing
MergeLabs implements and maintains the technical and organisational measures set out in Annex 2. MergeLabs may update these measures, provided the overall level of protection is not reduced. Updates are published as new, dated versions, listed in the feed at /legal/feed.xml, and earlier versions remain available.
5. Subprocessors
The Client gives MergeLabs general authorisation to engage the subprocessors listed in Annex 3. MergeLabs announces any intended addition or replacement at least 30 days before it takes effect, by publishing a new version of the list and by email to the Client’s contact named in the Agreement. Each new version is also listed in the feed at /legal/feed.xml. If a subprocessor must be replaced urgently for reasons outside MergeLabs’ control, such as the subprocessor’s insolvency or a security incident, MergeLabs may make the replacement with shorter notice and informs the Client without undue delay. The Client may object to a change, on reasonable data protection grounds, within that period (for an urgent replacement, within 30 days of being informed) by writing to [email protected]. If the objection cannot be resolved, the Client may terminate the Agreement without penalty. Personal data the Client sends to MergeLabs support by email is processed in Google Workspace, which is listed in Annex 3; the Client does not send personal data of its data subjects through other channels, such as WhatsApp or LinkedIn. MergeLabs imposes data protection obligations on each subprocessor that are equivalent to those in this DPA and remains responsible for their performance. Services MergeLabs uses for its own business that do not process the Client’s personal data, such as telephone, post or general office software, are not subprocessors.
Services the Client connects under its own contract are not subprocessors of MergeLabs: its email provider, its payment provider, its Google Cloud account for push notifications (Firebase Cloud Messaging and, for iPhones, Apple’s push service) and any AI provider connected through MCP. The Client instructs MergeLabs to send the relevant data to them and is responsible for its contracts with them and for any international transfer they involve. If the Client asks MergeLabs to send push notifications from MergeLabs’ Google account, Google and Apple act as subprocessors as listed in Annex 3.
6. International transfers
Where a subprocessor processes personal data outside the EU, MergeLabs ensures the transfer is covered by an adequacy decision, including the EU–US Data Privacy Framework, or by standard contractual clauses. The subprocessor list states the mechanism for each subprocessor.
7. Cothena Assist
Prompts, inputs and outputs of Cothena Assist are the Client’s personal data to the extent they contain personal data, and are processed only to provide Assist to the Client. Neither MergeLabs nor the AI provider listed in Annex 3 uses them to train or improve AI models. The AI provider keeps inputs and outputs only for as long as Annex 3 states.
8. Assistance to the Client
MergeLabs will forward requests from data subjects to the Client and assist the Client in responding to them. Taking into account the nature of the processing and the information available to it, MergeLabs also assists the Client with security, breach notifications, data protection impact assessments and consultations with supervisory authorities. This assistance is included in the service. Where a request needs substantial effort beyond what the platform’s features provide, MergeLabs may charge reasonable costs after telling the Client in advance.
9. Personal data breaches
MergeLabs notifies the Client without undue delay, and in any case within 72 hours, after becoming aware of a personal data breach affecting the Client’s personal data. The notice describes, as far as known, the nature of the breach, the categories and approximate number of data subjects and records concerned, its likely consequences and the measures taken or proposed, and names a contact for further information. MergeLabs updates the Client as more information becomes available. A notification is not an acknowledgement of fault or liability. The contact for data protection matters is [email protected].
10. Return and deletion
The Client may retrieve its data throughout the term, including any grace period, and for 30 days after the Agreement ends, using the export features, the documented REST API and the MCP server; making the data available in this way constitutes its return. Within 30 days after that retrieval period ends, or earlier at the Client’s request, MergeLabs deletes the Client’s event data and all personal data processed on its behalf from the live platform, and confirms the deletion in writing on request. MergeLabs may keep the Client’s organisation and its settings, which contain no personal data, so that the Client can return later, unless the Client asks for them to be deleted as well. Where applicable law requires MergeLabs to keep data, MergeLabs restricts its processing to that purpose. Deletion is started by MergeLabs staff and then runs automatically across all platform services, including Cothena Assist conversation data and search indexes. Residual backup copies remain encrypted, are used only for recovery and are deleted no later than 12 months after the end of the Agreement. Any restored data remains subject to the deletion instruction.
11. Audits and information
MergeLabs makes available the information necessary to demonstrate compliance with this DPA and cooperates with audits and inspections by the Client or an auditor the Client mandates. MergeLabs first answers audit requests with documentation. Where that is not sufficient, the Client may audit at most once a year, with 30 days’ notice, during business hours, through an auditor bound by confidentiality, at the Client’s own cost. Audits must not unreasonably disrupt MergeLabs’ operations, and the auditor may not be a competitor of MergeLabs. More frequent audits are allowed after a personal data breach or when a supervisory authority requires them.
12. Liability, term and precedence
Liability under this DPA follows the liability clauses of the Agreement, without prejudice to data subjects’ rights under Art. 82 GDPR, and this DPA is governed by the law and venue the Agreement specifies. This DPA applies for as long as MergeLabs processes personal data on the Client’s behalf, and the obligations on return and deletion survive the end of the Agreement. Where this DPA and the Agreement conflict on the processing of personal data, this DPA prevails, except for terms an order form expressly identifies as deviating from this DPA.
Annex 1: Details of processing
| Subject matter | Provision of the Cothena platform under the Agreement |
| Duration | The term of the Agreement, including any grace and retrieval period, and until deletion under section 10 |
| Nature and purpose | Collecting, hosting, organising, displaying, making available through the documented APIs, transmitting and deleting operational data, to provide the Cothena platform and support under the Agreement |
| Categories of data subjects | The Client’s authorised staff, volunteers, contractors and suppliers, and individuals identified in schedules or bookings, such as participants |
| Categories of personal data | Names, email addresses, roles, assignments, locations, account identifiers, preferences, operational messages and notes, chat messages, Cothena Assist conversations, records of emails sent, booking details (what was booked, when, for whom and the price paid), and invoices and the billing details on them. Card numbers are not processed; card payments are handled by the Client’s own payment provider. |
| Special categories | Cothena is not designed to process special categories of personal data. The Client agrees not to enter them beyond what event logistics strictly require, such as dietary or access needs, and is responsible for the lawful basis if it does. |
Annex 2: Technical and organisational measures
The measures in Cothena Security Measures, published at https://www.cothena.com/legal/security-measures, in the version in effect at the relevant time.
Annex 3: Subprocessors
The subprocessors in Cothena Subprocessors, published at https://www.cothena.com/legal/subprocessors, in the version in effect at the relevant time, as updated under section 5.