Where client data lives, who can reach it, how AI is used, and the documents behind it.
This page is a summary. The binding commitments are in the Master Services Agreement, the Data Processing Addendum, Security Measures and Subprocessors.
Who operates Cothena
Cothena is developed and operated by MergeLabs GmbH, a company registered in Germany. For client data in Cothena, MergeLabs acts as a processor under the GDPR and other applicable data protection laws, on the client’s instructions. For sign-in security records, app installation and device registrations, and crash reports, MergeLabs is the controller, as described in the privacy policy. Every client signs an order form under the Cothena Master Services Agreement, which includes the Data Processing Addendum.
Where your data lives
All Cothena production servers and databases are hosted in Frankfurt, Germany. Our hosting provider is Akamai Cloud (Akamai Technologies International AG, Switzerland).
All web traffic passes through Cloudflare, which provides DDoS protection and TLS encryption at the edge. Emails to a client’s own users, such as sign-in codes and password resets, are sent through an email platform that processes them in the EU. Emails to a client’s guests and customers are sent through the client’s own email provider, and push notifications through the client’s own Google Cloud account, unless the client asks to use MergeLabs’ account.
Some processing happens outside the EU:
| What | Where | Why |
|---|---|---|
| Cloudflare network | Global network | Visitors connect to their nearest Cloudflare edge |
| Push notifications to the staff and guest apps | Global, including the USA | Delivered through Google Firebase Cloud Messaging and, on iPhone, Apple’s push service, from the client’s own Google Cloud account or, on request, MergeLabs’ |
| Support by email | Google’s global data centres | Our email runs on Google Workspace; personal data you include in a support email is processed there |
| Cothena Assist | Global routing; storage in the USA | The AI model behind Assist is Anthropic’s Claude, currently reached through an account held by SwingStep GmbH (see the subprocessor list) |
How AI is used
- Assist is optional: core workflows work without it. Access is set per role: only users whose role includes Assist can use it, and approving its changes is a separate permission.
- In the Management Panel and in Cothena Management (the staff app), every change Assist proposes must be approved by a person before it is saved. You can ask Assist what it changed recently.
- Client data is not used to train AI models.
- Cothena’s AI tools are designed not to browse the web, run code, or read or write files. They perform only defined actions within the user’s own permissions.
- When clients connect their own AI app through MCP (an open standard for connecting AI apps), Cothena calls no AI model itself. The client’s provider processes that data under the client’s own terms, which may differ (e.g. on training).
- Assist uses Anthropic’s Claude models via Anthropic’s commercial API. The AI provider keeps inputs and outputs for up to 30 days for safety and security. Processing uses global routing; storage is in the United States.
Access and permissions
- Fine-grained, role-based permissions: roles, sub-roles and individual permissions control what each team member can see and do.
- Users cannot grant permissions they don’t hold themselves.
- External AI apps connect via OAuth 2.1 with PKCE (the standard secure sign-in for connected apps): users approve each app by name, and the app never sees their password.
- Passwords are stored only as salted hashes, never in readable form.
Guests have no account or password.
Data separation and architecture
- Cothena is built as independent services, each with its own database, which limits the impact of a fault to one area.
- 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’s application services run in minimal, hardened containers without a shell or package manager, as non-root users.
Encryption
- Connections between your browser or app and Cothena are encrypted with TLS (HTTPS only).
- Every backup is encrypted with AES-256 before it leaves our servers.
- Encrypted backups of the production databases are stored offsite in Google Cloud in Berlin, Germany, separate from our hosting provider.
- The credentials Cothena’s own services use to reach their databases and each other are stored encrypted in a dedicated secrets vault.
- In addition to HTTPS, each installation of the Cothena App (the guest app) registers its own key with the platform, which protects the push configuration the platform sends to it. Cothena Management (the staff app) receives its configuration only after the staff member has signed in.
Operations and releases
Certain destructive maintenance operations are blocked in production. Background jobs are built so that a retry does not repeat work, and maintenance tasks cannot run over each other. Every production release is built and deployed from version control through automated pipelines. Cothena runs on current, vendor-supported versions of its runtime and frameworks, which we update regularly, including for security fixes.
Mobile apps
Cothena has two apps: Cothena Management, the staff app for event teams, and Cothena App, the guest app for event participants.
Cothena App, the guest app (for event participants)
- Participants need no account. In the app, participants are never asked for their name, email address or phone number. They open their programme with the link or QR code from their booking.
- The guest app uses the camera only to scan the event QR code. The picture never leaves the phone.
- Your location is used on the phone to show where you are. The guest app never sends your location.
Cothena Management, the staff app (for event teams)
- Sign-in tokens are designed to be kept in the phone’s secure credential store (iOS Keychain, Android Keystore). They are excluded from cloud backups.
- The staff app never stores your password on the phone.
- The staff app offers a Face ID / fingerprint lock that each user can switch on. While it is on, the app’s content is hidden in the app switcher and, on Android, screenshots and screen recording are blocked.
- Signing out removes the sign-in tokens and the offline copies of event data from the phone, and unsubscribes the phone from the account’s notifications (if the phone is offline, as soon as it reconnects).
- Your location is sent to Cothena only when a staff member chooses to, in two ways: dropping a pin to propose a new place, which is processed by Cothena Assist including its AI provider; or sending their team a “running late” message with an approximate distance.
Both apps
- The apps connect only over encrypted HTTPS. On iPhone, Apple’s App Transport Security is enforced with no exceptions.
- Location is used only while the app is open, never in the background. The camera and location are requested only when a feature first needs them.
- The apps do not ask for access to your contacts, photos or microphone.
- Event data saved for offline use stays in the app’s private storage and is excluded from cloud backups.
- Crash reports are off until you turn them on. Both apps ask once whether to send crash reports, and the choice can be changed at any time in Settings. Until you say yes, no crash or diagnostic data leaves the phone.
- The apps contain no advertising or analytics SDKs. The only third-party SDKs in them are for push notifications and, if you allow it, crash reporting.
Third parties that receive data from the apps
| What | App | To whom | Details |
|---|---|---|---|
| Push notifications | Both apps | Google Firebase Cloud Messaging and, on iPhone, Apple’s push service | Sent from the organiser’s own Google Cloud account or, on request, MergeLabs’. A notification carries its visible text: the alert’s headline and message, plus technical identifiers (internal user number, event and resource identifiers, device push token, installation identifier). Whether that text shows on a locked screen follows the phone’s notification settings. |
| Team chat notifications | Staff app | Google Firebase Cloud Messaging and, on iPhone, Apple’s push service | The sender’s name and the message text. |
| A dropped pin, when proposing a new place | Staff app | Cothena Assist and its AI provider (Anthropic) | The pin’s coordinates, as part of the Assist request |
| Media an organiser embeds in event content | Both apps | The provider the organiser chose | Loaded by the phone directly from that provider |
On Android, notifications show no text on a secure lock screen. On iPhone, this follows your notification preview settings.
Diagnostics are described in the privacy policy.
This website
- cothena.com sets no cookies, stores nothing in your browser and currently uses no analytics. Nothing on these pages tracks you, so there is no cookie banner.
- Traffic to the site passes through Cloudflare, like all traffic to Cothena.
- The privacy policy covers the website in full: server logs, getting in touch and booking a meeting.
Exporting and deleting your data
- Clients can access their data at any time during their licence: through our documented REST API, or through Cothena’s MCP server (
https://www.cothena.com/mcp, the address you add to your AI app), which lets an AI assistant of the client’s choice read their schedules and help recreate them in other tools. - Bookings, session attendee lists and archived booking emails can be exported as CSV or JSON, with email addresses left out for anyone not allowed to see them. Operational data such as schedules, runsheets, tasks and products can also be read through our documented API and MCP server, within each user’s permissions. There is no single export of all data.
- Clients can retrieve their data using the features above throughout their licence and for 30 days after it ends; we then delete their data from the live platform within 30 days, as set out in the Data Processing Addendum. The organisation and its settings, which contain no personal data, can be kept so the client can return later, unless the client asks for them to be deleted too. Deletion is started by our team and then runs automatically across all of the platform’s services, including Assist conversation data and search indexes. Encrypted backup copies are used only for recovery and are deleted no later than 12 months after the agreement ends.
- Card payments are handled by the client’s own payment provider. Cothena never stores card numbers.
- Cothena is not designed to collect special-category data (e.g. health, religion). Clients agree not to enter it beyond what event logistics strictly require, such as dietary or access needs.
Subprocessors and notice of changes
The subprocessor list names the companies that process client data for Cothena. New or replacement subprocessors are announced at least 30 days before they take effect, in the legal updates feed and by email to each client’s named contact. Every version stays available at its own address.
Contact
A Security Pack with more detail is available on request, under a confidentiality agreement. For security questions and reports, and to request the Security Pack, write to [email protected]. For anything about personal data, write to [email protected].