English translation of the German text.

Data processing agreement

Version of 20 November 2026, available for reference. Processing on the customer's behalf is governed by the version agreed for the relevant contract, including its annexes.

1. Parties, subject matter, and duration

This agreement is between the customer named in the Dengel contract as controller and NMA Venture Capital GmbH, Am Sandtorkai 27, 20457 Hamburg, Germany, as processor. Contact for instructions, personal data breaches, and data subject requests: info@nma.vc, phone +49 178 4497585.

This agreement applies where NMA processes personal data on the customer's behalf and takes precedence over the general terms for that processing. If the customer is itself a processor, it must be authorised to engage NMA. NMA's own purposes, such as statutory invoice retention, are described separately in the privacy notice.

The agreement covers the agreed Git hosting and expressly commissioned development, verification, and integration services. Processing includes receipt, storage, organisation, display, transmission to authorised recipients, job-related analysis, return, and deletion. It continues for the agreed service, including the agreed return and deletion period.

Data subjects may include the customer's users and employees, repository contributors, and people whose personal data the customer processes in its content. Data types include contact and identity information, Git metadata, access restrictions, and personal data in source code, tasks, documents, and results. The customer defines the purpose and permitted scope of its content and identifies any particular risks before commissioning the service. Where special categories of data are involved, suitable safeguards must be agreed expressly.

2. Instructions and confidentiality

NMA processes data on the customer's behalf only on documented instructions, including for international transfers. The contract, authorised configuration, and jobs document the standing instructions. The customer can give further instructions in text form. NMA documents those instructions and immediately informs the customer if, in its opinion, an instruction infringes the law. The affected processing is suspended pending resolution.

If Union or Member State law requires NMA to process data, NMA informs the customer in advance unless the law prohibits this on important grounds of public interest. Data processed on the customer's behalf are not used for NMA's own advertising, general-purpose model training, or unrelated purposes.

Access is limited to people who need it and who are under a contractual or statutory duty of confidentiality. The duty continues after their work ends.

3. Security

NMA takes the measures required under Article 32 GDPR, taking into account risk, the state of the art, and the circumstances of processing. Annex A sets out the specific measures. NMA regularly reviews their effectiveness. Updates must maintain the agreed level of protection. NMA documents material changes and communicates them to the customer.

4. Assistance and incidents

Taking into account the nature of processing and the information available, NMA assists the customer with data subject rights, security, personal data breaches, data protection impact assessments, and prior consultations under Articles 32 to 36 GDPR. NMA forwards data subject requests about data processed on the customer's behalf without delay. It responds to the substance of a request only on instructions or where legally required.

When NMA becomes aware of a breach involving personal data processed on the customer's behalf, it notifies the customer without delay. The notice includes, where known, the nature and extent of the breach, affected data and people, contact details, likely consequences, and measures taken or planned. NMA supplies missing information without undue delay, preserves necessary evidence, and assists with remediation.

5. Subprocessors and processing locations

The customer gives general written authorisation for the list of subprocessors expressly attached as Annex B when the contract is concluded. The list identifies their functions, legal entities, locations, and relevant third-country safeguards. Authorisation covers only the providers actually listed.

NMA gives notice in text form of an addition or replacement of a subprocessor at least 30 days before that subprocessor first gains access. The customer may object on substantiated data protection grounds. NMA and the customer work to agree on a suitable alternative. Until they resolve the objection, NMA does not use the new provider for that customer's data. If the service cannot continue as a result, the customer may terminate the affected part without additional charge. NMA refunds prepaid fees for services not provided on a pro rata basis.

NMA imposes the applicable data protection obligations on subprocessors and remains responsible to the customer for their compliance. Processing in a third country requires documented instructions and compliance in practice with Chapter V GDPR. General customer authorisation does not replace the required safeguards.

6. Evidence and audits

NMA makes available the information necessary to demonstrate compliance and allows audits, including inspections, by the customer or an independent auditor it appoints. Where possible, suitable reports or records are used first. Necessary inspections remain available. Planning and confidentiality protect operations and other customers while preserving statutory audit rights and the powers of supervisory authorities.

7. Return and deletion

At the end of the commissioned processing, NMA returns or deletes personal data processed on the customer's behalf, including existing copies, at the customer's choice, unless retention is required by law. Applicable switching and retrieval periods must be taken into account first. On request, NMA confirms completion and explains what data remain, the legal basis, and the retention period.

Annex C specifies retention periods and the treatment of backups. Lawfully retained backups remain protected until they expire and are kept out of routine use. Deletion instructions must be reapplied after a restoration. A signature or an immutable journal alone does not justify indefinite retention of personal data.

Annex A: Technical and organisational measures

The measures apply to the commissioned processing in proportion to the risk. NMA documents responsibilities, regularly reviews effectiveness, and remedies any issues identified. NMA makes no commitment to certification or complete automated anonymisation.

Area Measures
Access and tenant isolation Individual user identities, role-based workspace and repository checks, and service and execution permissions limited to the task. Administrative access is separately restricted. Permissions are reviewed regularly and revoked when no longer needed
Transmission and execution HTTPS/TLS for public web and API connections. Separate execution environments with limited network and model permissions. Credentials must be kept out of jobs and application logs
Integrity Version-bound jobs, approvals, verification results, and signed delivery receipts. The worker doing the work cannot independently certify its own work
Backups Encrypted backups in a separate OVH region. Daily backups, time-limited protection against premature deletion, documented restoration, and reapplication of earlier deletion instructions after a restore
AI data Only necessary job content is sent through approved routes. Data processed on the customer's behalf are not used for general-purpose model training. Full anonymisation does not replace instructions, a legal basis, or access protection
Deletion Project deletion removes files and redacts free text from the journal. Association and access to remaining records are limited. Work logs, artefacts with shared references, and backups are subject to Annex C
Operations and incidents Support access limited to its purpose, confidentiality obligations, security updates, and documented handling of vulnerabilities and personal data breaches. Records and regular checks of permissions, deletion, and restoration

Encryption of backups and transmission channels does not constitute a commitment to verified end-to-end encryption or full encryption of all live databases. Any additional measures necessary for particular risks are agreed before processing begins.

Annex B: Subprocessors

A fixed copy of the "Service providers and processing locations" annex to the privacy notice as of 20 November 2026 is attached when the contract is concluded. It identifies legal entities, functions, data, and locations. A link that can change does not by itself replace the contractual annex.

We provide hosting with OVH GmbH, Germany. Cortecs GmbH provides the gateway for commissioned managed inference. Its approved subprocessor chain is listed in the same annex. AhaSend B.V. handles transactional email. Cloudflare, Inc. provides network and protection services in front of the application. The associated provider chains and third-country safeguards must be taken into account when engaging them. European server locations alone do not establish that all processing occurs in the EEA.

Routing must stay within the attached authorisation. A broader selection of providers or a new subprocessor chain requires the procedure in Section 5 first. Provider access supplied by the customer is enabled only on separately documented instructions and after a review of the provider's terms. Payment services acting as independent controllers and customer-commissioned connections must be treated according to their actual roles.

Annex C: Return and deletion periods

Data Rule for the agreed processing on the customer's behalf
Active data processed on the customer's behalf Delete without undue delay and no later than 30 days after an applicable deletion instruction or the end of the agreed return or switching period. Handle an explicit instruction to delete earlier separately
AI work logs 30 days after the attempt ends. Parts of an agreed result that are still needed follow the project retention period. Shared references do not justify indefinite retention
Technical logs No more than 14 days. Specifically required incident evidence is kept separately and only for investigation or legal proceedings
Regular backups Current backup objects: 30 days. Non-current object versions: a further 30 days. Backups must not recapture data already deleted from active systems. Restrict access to existing copies until expiry and reapply deletion instructions after restoration
Service providers The provider-specific retention periods in Section 6 of the privacy notice apply according to the provider's role. Distinguish content from operational metadata. Pass necessary deletion instructions down the subprocessor chain
NMA's own contract and billing records Keep separately in accordance with the privacy notice, only insofar as NMA is the controller and is entitled to retain them. This does not authorise indefinite retention of complete customer content for NMA's own evidentiary purposes

Statutory switching and retrieval periods remain in effect. On request, NMA confirms deletion and identifies the specific data it may lawfully retain, the purpose, and the end date. An immutable storage format does not replace a legal basis for retention. One-off legacy archives must be cleaned up before this annex is applied or expressly agreed as a specifically justified and time-limited exception.