Data Processing Agreement

Version: 2026-10-23

This English translation is provided for information only. The German version is the only legally binding one: Auftragsverarbeitung.

Parties

This agreement is concluded between the customer business that uses KARLA (the “Controller”) and

CordtoCapital UG (haftungsbeschränkt)
represented by its managing director Matteo Cordtomeikel
Obernstraße 50
33602 Bielefeld
Email: matteo@cordtomeikel.com

(the “Processor”).

It becomes effective when the Controller accepts the offer for KARLA and forms part of that contract.

§ 1 Subject matter and duration

The subject matter is the processing of personal data that the Processor carries out for the Controller in the set-up, operation and support of KARLA. The basis is the contract for KARLA with the Terms.

This agreement runs for as long as the contract for KARLA runs and ends with it. The deletion obligations under § 9 continue to apply beyond that.

The Controller remains responsible for the lawfulness of the processing. The Processor processes its own contract, contact and invoicing data as a controller in its own right. These are not subject matter of this agreement but are described in the Privacy Policy.

§ 2 Nature, purpose, types of data and data subjects

Purpose

KARLA answers questions from the Controller’s employees on the basis of its documents. This also includes managing access to its workspace.

Nature of the processing

Collecting, storing, organising, retrieving, querying, transmitting to the Sub-processors under Annex 2 and deleting.

Data subjects

  • Employees of the Controller who use KARLA,
  • Persons named in the Controller’s documents, such as contact persons, representatives, customers and suppliers.

Types of personal data

  • Access data: name, work email address, role in the workspace,
  • Usage data: time of use, agent used, consumption,
  • Content: questions and answers, uploaded files and documents, to the extent they relate to individuals.

Special categories of personal data under Art. 9 GDPR are not subject matter of the processing. The Controller ensures that such data is not uploaded.

§ 3 Instructions

The Processor processes the data exclusively on documented instructions from the Controller. This agreement and the use of KARLA by the Controller’s employees constitute the standing instruction.

The Controller issues further instructions in text form to matteo@cordtomeikel.com. The persons named by the Controller are authorised to give instructions.

If the Processor considers an instruction to be unlawful, it informs the Controller without undue delay and may suspend the instruction until the Controller confirms or changes it.

No processing for its own purposes takes place. In particular, the Controller’s content is not used to train AI models.

§ 4 Confidentiality

The Processor processes the data itself and is bound to confidentiality. If it involves further persons, it binds them to confidentiality beforehand. The obligation continues after the activity has ended.

The Processor accesses content only to the extent necessary for set-up, maintenance, troubleshooting or an instruction.

§ 5 Technical and organisational measures

The Processor implements the measures under Art. 32 GDPR described in Annex 1. It may develop them further as long as the level of protection does not fall. It informs the Controller of material changes.

§ 6 Sub-processors

The Controller authorises the use of the Sub-processors listed in Annex 2.

If the Processor plans to add or replace a Sub-processor, it informs the Controller beforehand in text form. If it learns of such a change at a Sub-processor, it informs the Controller without undue delay. The Controller may object on data protection grounds within 14 days of the information. If the parties do not agree, either party may terminate the contract for KARLA as of the date of the change.

The Processor contractually binds each Sub-processor to data protection obligations corresponding to those in this agreement. It remains responsible to the Controller for the Sub-processor’s actions.

§ 7 Assistance with data subject rights

If a data subject contacts the Processor directly, the Processor forwards the request to the Controller without undue delay and does not answer it itself.

The Processor assists the Controller in responding on time to requests for access, rectification, erasure, restriction, data portability and objection (Art. 12(3) GDPR). On instruction, it compiles the necessary data or deletes it.

§ 8 Notification of personal data breaches and further assistance

If the Processor becomes aware of a personal data breach, it notifies the Controller without undue delay so that the Controller can meet its 72-hour notification deadline under Art. 33 GDPR. The notification states, as far as known, the nature of the breach, the data and persons concerned, the likely consequences and the measures taken.

The Processor also assists the Controller with the security of processing (Art. 32), with a data protection impact assessment (Art. 35) and with prior consultation of the supervisory authority (Art. 36), to the extent the information is available to it.

§ 9 Return and deletion after the end of the contract

Until the end of the contract, the Controller may require the Processor to return the uploaded documents. Within 30 days after the end of the contract, the Processor deletes the Controller’s workspace with all data.

Where Sub-processors keep backup copies, the data is removed there in the course of their regular backup cycles. On request, the Processor confirms the deletion in text form.

§ 10 Evidence and audits

On request, the Processor demonstrates compliance with its obligations, above all through the description of the measures (Annex 1), the list of Sub-processors (Annex 2) and the documents provided to it by its Sub-processors.

If this is not sufficient, the Controller may, after giving reasonable notice, carry out an inspection or have it carried out by an auditor bound to confidentiality, as a rule once a year. The inspection must not disrupt operations unreasonably.

§ 11 Processing outside the EU

KARLA’s answers are computed exclusively in the EU or the EEA. No transfer to a third country takes place under this agreement. Should one become necessary, the Processor informs the Controller beforehand and ensures the safeguards under Art. 44 et seq. GDPR.

If the Controller uses KARLA in Microsoft Teams, the messages run through Microsoft’s bot service under the Controller’s Microsoft contract. Microsoft does not guarantee processing exclusively in the EU for this. This processing by Microsoft is not subject matter of this agreement.

§ 12 Final provisions

Amendments require text form. If this agreement and the Terms conflict, this agreement prevails in matters of data protection.

If a provision is invalid, the rest of the agreement remains valid. German law applies.

Annex 1: Technical and organisational measures (Art. 32 GDPR)

Confidentiality

  • Each Controller has its own workspace. Document stores always belong to exactly one workspace and cannot be shared with other businesses.
  • Roles with different rights (administrator and user). Agents are accessible only to authorised users.
  • Sign-in via a personal sign-in link sent to the work email address.
  • Encrypted transmission via HTTPS, including between the platform and the language model.
  • Access credentials for connected services are stored encrypted on the server.
  • The Processor’s support view shows consumption and activity, but not the content of conversations.

Integrity

  • Before any action that sends or changes something, approval by a human is required.
  • In Microsoft Teams, KARLA can only read and reply.
  • Every work step is logged and can be traced in the workspace.

Availability and place of processing

  • The language models run exclusively in data centres in the EU or the EEA. According to Melious, there are no fallback servers outside Europe.
  • KARLA is permanently set to a model that processes data in the EU. The Processor checks this setting with every change to KARLA.
  • Information from lowcloud on the server location and data backup of the platform will be added as soon as it is available in writing.

Regular review

  • The Processor checks the accesses and approvals in the workspace with every change and removes accesses that are no longer needed, after consulting the Controller.
  • It follows the statements of its Sub-processors and adapts this agreement if they change.

Annex 2: Sub-processors

ProviderPurposePlace of processing
lowcloud UG (haftungsbeschränkt), Obernstraße 50, 33602 Bielefeld, HRB 46637 Local Court (Amtsgericht) of BielefeldAgent platform: workspaces, conversations, documents, logs and sign-inEU (according to lowcloud)
Melious AI GmbH, Universität des Saarlandes, Campus, Gebäude A1.2, 66123 Saarbrücken, HRB 111794 Local Court (Amtsgericht) of Saarbrücken (Sub-processor of lowcloud)Computing the answers and preparing the documents for searchEU or EEA
Data centre partners of Melious, all based in the EU. The current list is available at melious.ai/legal/subprocessors.Running the language modelsEU or EEA

Privacy PolicyLegal NoticeTerms and Conditions