Skip to content

Data Processing Agreement

Last updated:

1. Subject and parties

1.1 This agreement governs how Kadmo GmbH, Linienstraße 148, 10115 Berlin, Germany (“Kadmo”) processes personal data on behalf of its customer (the “Customer”) when it provides the Kadmo platform under the Terms of Service at kadmo.ai/terms (the “Terms”). The Customer is the controller and Kadmo the processor within the meaning of Article 28 of the General Data Protection Regulation (GDPR). Where the Customer itself processes the data on behalf of a third party, Kadmo is its subprocessor, and the Customer passes that party’s instructions on to Kadmo.

1.2 This agreement forms part of the contract under the Terms and is concluded with it; no signature is needed. Terms used here have the meaning the GDPR gives them. On data protection, this agreement prevails over the Terms and over any other agreement between the parties, unless an individual agreement expressly says otherwise.

1.3 Annex 1 sets out the subject, nature and purpose of the processing, the types of personal data and the categories of data subjects. Annex 2 sets out the technical and organisational measures, and Annex 3 the subprocessors.

1.4 This agreement does not cover the processing Kadmo does for its own purposes, such as its website, its sales and the administration of the Customer’s contract and invoices. The privacy policy at kadmo.ai/privacy describes that processing.

2. Duration

2.1 This agreement runs for as long as the contract under the Terms and, after the contract ends, for as long as Kadmo still holds personal data it processes for the Customer (section 10).

3. Instructions

3.1 Kadmo processes the personal data only on the Customer’s documented instructions, including with regard to transfers to a third country, unless Union or Member State law requires it to do otherwise. In that case Kadmo informs the Customer of that legal requirement before the processing, unless the law prohibits this.

3.2 The Customer’s instructions are the contract and the way the Customer and its users set up and use the platform, for example by connecting a tool, assigning a work item to Kadmo, choosing models, regions and agents, or deleting content. The Customer may give further instructions in text form. An instruction that goes beyond the agreed service is treated as a request to change it.

3.3 Kadmo informs the Customer without delay if it believes that an instruction infringes data protection law. It may suspend carrying out that instruction until the Customer confirms or changes it.

3.4 Kadmo does not use the personal data for its own purposes and does not use customer content to train AI models.

4. Confidentiality

4.1 Kadmo gives access to the personal data only to persons who need it to provide the service and who have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

5. Security of processing

5.1 Kadmo takes the technical and organisational measures described in Annex 2 (Article 32 GDPR). They ensure a level of security appropriate to the risk, taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of the processing.

5.2 Kadmo may develop the measures further, provided that the level of protection does not fall below that of Annex 2. Kadmo documents material changes.

6. Subprocessors

6.1 The Customer gives Kadmo general authorisation to engage subprocessors. The subprocessors listed in Annex 3 are approved with the conclusion of this agreement.

6.2 Kadmo informs the Customer of any intended addition or replacement of a subprocessor, by e-mail to the account’s admins or by a notice in the platform, and updates Annex 3. The Customer may object to the change in text form for reasons of data protection. If the parties find no solution, the Customer may terminate the affected service, or the contract, with immediate effect.

6.3 Kadmo binds each subprocessor by contract to data protection obligations that offer the same level of protection as this agreement, in particular sufficient guarantees for appropriate technical and organisational measures. Kadmo is responsible for its subprocessors as for itself.

6.4 Services that the Customer connects or chooses itself and that act under its own contract with them are not subprocessors of Kadmo. These include the Customer’s Atlassian, Slack, GitHub, Linear, Notion, Figma or Microsoft accounts, model providers reached with the Customer’s own keys, and machines the Customer provides for its agents. Kadmo passes data to them on the Customer’s instruction (section 3.2). Ancillary services such as telecommunications or postal services are not subprocessors either.

7. Transfers to third countries

7.1 Kadmo hosts the platform and stores customer content in the European Union, in Frankfurt am Main (Annex 3). Some subprocessors process data in a third country, in particular the providers that run the AI models the Customer uses. The platform shows the region in which each model runs, and the Customer can restrict its account and its workspaces to the regions it accepts (Guardrails, data residency).

7.2 Kadmo transfers personal data to a third country, or lets a subprocessor do so, only where the conditions of Chapter V GDPR are met: on the basis of an adequacy decision of the European Commission, including the EU-US Data Privacy Framework for certified recipients, or of the EU Standard Contractual Clauses (Article 46(2)(c) GDPR) concluded with the subprocessor, together with any additional measures they require.

8. Assistance

8.1 Taking into account the nature of the processing, Kadmo assists the Customer with appropriate technical and organisational measures in responding to requests from data subjects who exercise their rights under Chapter III GDPR. The Customer can view and delete its content in the platform; for anything it cannot do there, such as an export, Kadmo helps on request. Kadmo forwards to the Customer without delay any request it receives directly from a data subject about the Customer’s data, and answers it only by referring the person to the Customer.

8.2 Taking into account the nature of the processing and the information available to it, Kadmo assists the Customer in meeting its obligations under Articles 32 to 36 GDPR: the security of processing, the notification of personal data breaches, data protection impact assessments and prior consultation of the supervisory authority.

8.3 Kadmo may charge reasonable costs for assistance under sections 8.1 and 8.2 that goes beyond what the platform provides, unless the assistance is needed because Kadmo breached this agreement or the law.

9. Personal data breaches

9.1 Kadmo notifies the Customer without undue delay after becoming aware of a personal data breach that affects the Customer’s data. As far as it is known at the time, the notification describes the nature of the breach, the categories and approximate numbers of data subjects and records concerned, its likely consequences and the measures taken or proposed. Kadmo supplies further information as it becomes available.

9.2 Kadmo takes the measures needed to secure the data and to mitigate possible adverse effects, and coordinates them with the Customer. Notifying the supervisory authority and the data subjects is the Customer’s task, in which Kadmo assists it (section 8.2).

10. Deletion and return

10.1 When the contract ends, Kadmo deletes the personal data it processes for the Customer no later than 30 days after the end, as section 13.5 of the Terms provides, unless Union or Member State law requires it to keep the data. Before the end, the Customer exports what it wants to keep; Kadmo helps on request. Copies in backups are overwritten in their regular cycle, within seven days (Annex 2).

10.2 While the contract runs, the Customer deletes content in the platform or asks Kadmo to delete it. When the Customer removes an integration or uninstalls one of Kadmo’s apps, Kadmo stops receiving data through it and gives up the access it held. Data already in the account remains customer content until the Customer deletes it or the contract ends.

10.3 On request, Kadmo confirms the deletion in text form.

11. Information and audits

11.1 Kadmo makes available to the Customer the information necessary to demonstrate compliance with the obligations of Article 28 GDPR, in particular this agreement with its annexes and, where they exist, current certificates or audit reports.

11.2 Where that information is not sufficient, the Customer may verify compliance by an inspection, carried out by itself or by an auditor who is bound to confidentiality and is not a competitor of Kadmo. An inspection takes place during Kadmo’s business hours, without disrupting its operations, and no more than once a year, unless a personal data breach or a request of a supervisory authority gives cause. Each party bears its own costs.

11.3 Kadmo supports inspections by supervisory authorities as the law requires.

12. Final provisions

12.1 Each party’s liability towards data subjects follows Article 82 GDPR. Between the parties, the liability rules of the Terms (section 11) apply, unless the GDPR mandatorily provides otherwise.

12.2 Changes to this agreement follow section 14 of the Terms. A change that the law or a supervisory authority requires takes effect at the time they set.

12.3 If a provision of this agreement is or becomes invalid, the rest remain valid. German law applies, and the place of jurisdiction follows section 15.2 of the Terms.

12.4 This agreement exists in German and in English. Where the two differ, the German version prevails.

12.5 Questions about this agreement and about data protection reach Kadmo at legal@kadmo.ai.

Annex 1: Details of the processing

Subject matter. Providing the Kadmo platform under the Terms.

Nature of the processing. Collecting data from the tools the Customer connects; storing, organising and reading it; analysing and transforming it with AI agents and AI models; transmitting it to the subprocessors in Annex 3 and back to the Customer’s tools; displaying it; deleting it.

Purpose. AI agents do work for the Customer. They take work items, messages and requests from the Customer’s tools, run the workflows and playbooks the Customer chooses, and report their results where the work came from. The processing also serves the accounts, workspaces, billing records and support this service needs.

Types of personal data.

  • Users of the platform: name, work e-mail address, sign-in identifiers, role and settings, and records of their actions, such as who started a job or answered an agent’s question.
  • People in the Customer’s connected tools: the identifiers and profile data those tools pass on, such as Atlassian account IDs, display names and, where a person’s profile shows it, their e-mail address; user identifiers and names from Slack, Microsoft Teams, GitHub, Linear and Figma.
  • Content: work items, comments, messages, documents, code, files and prompts that the Customer brings into the platform, and the results agents create, with whatever personal data they contain.
  • Usage records: jobs and their logs, and model calls with their tokens and costs, by user, agent and workspace.
  • E-mails the platform sends: recipient, message and delivery outcome.

Special categories. The service needs no special categories of personal data (Article 9 GDPR). Customer content contains them only where the Customer decides to bring them in; the measures in Annex 2 apply to them as well.

Categories of data subjects. The Customer’s users, such as its employees and contractors, and the people whose data is in the Customer’s connected tools and content, such as colleagues, customers and other people named in work items and messages.

Duration. As section 2 provides.

Annex 2: Technical and organisational measures

  • Location and physical security. The platform runs in the Frankfurt region (eu-central-1) of Amazon Web Services, whose data centres AWS secures and has certified, among others under ISO/IEC 27001 and the BSI’s C5. Kadmo keeps no customer data on premises of its own.
  • Encryption. All traffic to the platform uses TLS 1.2 or higher, with HSTS. The database, the servers’ volumes and the stored files are encrypted at rest, and Kubernetes secrets are encrypted. Credentials for connected tools are additionally encrypted in the application (AES-256-GCM) with a key that is kept outside the database.
  • Access to the platform. Users sign in through Kadmo’s identity service (Auth0, EU region). The session is held in a cookie that scripts cannot read and that is sent only over encrypted connections. Within an account, roles separate admins from members, and every request is checked against the account and workspace it belongs to, so that no customer can reach another customer’s data.
  • Access by Kadmo’s staff. Administrative access to Kadmo’s cloud accounts goes through AWS IAM Identity Center only, with personal accounts and multi-factor authentication. The root accounts are kept for emergencies, protected by multi-factor authentication and without access keys. Access is limited to the people who operate the platform. An organisation-wide audit trail (AWS CloudTrail) records administrative actions, threat detection (Amazon GuardDuty) runs in every account, and sensitive changes raise alerts.
  • Separation. Test and production are separate environments with their own data and credentials. Customer content serves only the purposes in Annex 1 and is not used to train AI models. Kadmo uses model providers under their commercial API terms, under which they do not train their models on the data.
  • Agents. Agents run on machines the Customer provides or on hosted machines in Kadmo’s AWS fleet in Frankfurt; each hosted machine belongs to one account. An agent receives credentials only for the account it works for.
  • Logging. Application logs are kept in AWS CloudWatch in Frankfurt for 30 days. They contain no credentials.
  • Availability and recovery. The database has automated backups with point-in-time recovery, kept for seven days, and deletion protection prevents its accidental removal.
  • Data minimisation. The statistics of the platform’s pages record kinds of page, never their contents, and use no cookies (privacy policy, section 7).
  • Secure development. Every change is reviewed before it is merged. Dependencies are checked for known vulnerabilities, and critical and high findings are fixed with priority.
  • Incidents. Alerts on security-relevant events reach the people who operate the platform. Kadmo handles incidents and notifies affected customers as section 9 provides.

Annex 3: Subprocessors

SubprocessorWhat it does for the platformWhere the data is processedBasis for a transfer
Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855 LuxembourgHosting: servers, database, files, logs and hosted machinesFrankfurt am Main, GermanyEU; Standard Contractual Clauses in the AWS Data Processing Addendum for any access from outside the EU
Okta, Inc. (Auth0), United StatesSigning in to the platformEuropean Union (Auth0’s EU region)Standard Contractual Clauses; EU-US Data Privacy Framework
Anthropic Ireland, Limited, Dublin, Ireland, with Anthropic, PBC, United StatesAI models (Claude)United StatesStandard Contractual Clauses in Anthropic’s Data Processing Addendum
OpenAI Ireland Limited, Dublin, Ireland, with its affiliates in the United StatesAI models (GPT)United StatesStandard Contractual Clauses in OpenAI’s Data Processing Addendum
AC PM LLC (Postmark), United StatesSending the platform’s e-mailUnited StatesStandard Contractual Clauses; EU-US Data Privacy Framework
Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, IrelandKadmo’s mailboxes, for example support@kadmo.aiEuropean Union and other countriesStandard Contractual Clauses; EU-US Data Privacy Framework (Google LLC)

Which AI models the platform serves, and in which region, is listed at kadmo.ai/pricing and in the platform under Settings › Models. A model provider that is not listed here is added only as section 6.2 provides.