For the purposes of Article 28(3) of Regulation 2016/679 (the GDPR)

between

HAVE AGREED on the following Contractual Clauses (the Clauses) in order to meet the requirements of the GDPR and to ensure the protection of the rights of the data subject.

1.Table of Contents

1. Preamble
2. The rights and obligations of the data controller
3. The data processor acts according to instructions
4. Confidentiality
5. Security of processing
6. Use of sub-processors
7. Transfer of data to third countries or international organisations
8. Assistance to the data controller
9. Notification of personal data breach
10. Erasure and return of data
11. Audit and inspection
12. The parties' agreement on other terms
13. Commencement and termination
14. Data controller and data processor contacts/contact points
15. Appendix A — Information about the processing
16. Appendix B — Authorised sub-processors
17. Appendix C — Instruction pertaining to the use of personal data
18. Appendix D — The parties' terms of agreement on other subjects
19. Signature page

2.Preamble

2.1 These Contractual Clauses (the Clauses) set out the rights and obligations of the data controller and the data processor, when processing personal data on behalf of the data controller.

2.2 The Clauses have been designed to ensure the parties' compliance with Article 28(3) of Regulation 2016/679 of the European Parliament and of the Council of 27 April 2016 (General Data Protection Regulation).

2.3 These Clauses constitute the Data Processing Agreement (DPA) of the Zeldoc AI Platform (ZControl, ZCore, ZDev, ZRouter etc.) and form an integral part of the Zeldoc AI Platform Terms of Service. In the context of the provision of Zeldoc.ai services, the data processor will process personal data on behalf of the data controller in accordance with the Clauses. The current version of the Clauses is published at zeldoc.ai/dpa, and the sub-processor list at zeldoc.ai/subprocessors.

2.4 The Clauses shall take priority over any similar provisions contained in other agreements between the parties.

2.5 Four appendices are attached to the Clauses and form an integral part of the Clauses.

2.6 Appendix A contains details about the processing of personal data, including the purpose and nature of the processing, type of personal data, categories of data subject and duration of the processing.

2.7 Appendix B contains the data controller's conditions for the data processor's use of sub-processors and a list of sub-processors authorised by the data controller.

2.8 Appendix C contains the data controller's instructions with regards to the processing of personal data, the minimum security measures to be implemented by the data processor and how audits of the data processor and any sub-processors are to be performed.

2.9 Appendix D contains provisions for other activities which are not covered by the Clauses.

2.10 The Clauses along with appendices shall be retained in writing, including electronically, by both parties.

2.11 The Clauses shall not exempt the data processor from obligations to which the data processor is subject pursuant to the GDPR or other legislation.

3.The rights and obligations of the data controller

3.1 The data controller is responsible for ensuring that the processing of personal data takes place in compliance with the GDPR (see Article 24 GDPR), the applicable EU or Member State¹ data protection provisions and the Clauses.

3.2 The data controller has the right and obligation to make decisions about the purposes and means of the processing of personal data.

3.3 The data controller shall be responsible, among other, for ensuring that the processing of personal data, which the data processor is instructed to perform, has a legal basis.

4.The data processor acts according to instructions

4.1 The data processor shall process personal data only on documented instructions from the data controller, unless required to do so by Union or Member State law to which the processor is subject. Such instructions shall be specified in appendices A and C. Subsequent instructions can also be given by the data controller throughout the duration of the processing of personal data, but such instructions shall always be documented and kept in writing, including electronically, in connection with the Clauses.

4.2 The data processor shall immediately inform the data controller if instructions given by the data controller, in the opinion of the data processor, contravene the GDPR or the applicable EU or Member State data protection provisions.

5.Confidentiality

5.1 The data processor shall only grant access to the personal data being processed on behalf of the data controller to persons under the data processor's authority who have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality and only on a need to know basis. The list of persons to whom access has been granted shall be kept under periodic review. On the basis of this review, such access to personal data can be withdrawn, if access is no longer necessary, and personal data shall consequently not be accessible anymore to those persons.

5.2 The data processor shall at the request of the data controller demonstrate that the concerned persons under the data processor's authority are subject to the abovementioned confidentiality.

6.Security of processing

6.1 Article 32 GDPR stipulates that, taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, the data controller and data processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk.

The data controller shall evaluate the risks to the rights and freedoms of natural persons inherent in the processing and implement measures to mitigate those risks. Depending on their relevance, the measures may include the following:

1. Pseudonymisation and encryption of personal data;
2. the ability to ensure ongoing confidentiality, integrity, availability and resilience of processing systems and services;
3. the ability to restore the availability and access to personal data in a timely manner in the event of a physical or technical incident;
4. a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing.

6.2 According to Article 32 GDPR, the data processor shall also – independently from the data controller – evaluate the risks to the rights and freedoms of natural persons inherent in the processing and implement measures to mitigate those risks. To this effect, the data controller shall provide the data processor with all information necessary to identify and evaluate such risks.

6.3 Furthermore, the data processor shall assist the data controller in ensuring compliance with the data controller's obligations pursuant to Article 32 GDPR, by inter alia providing the data controller with information concerning the technical and organisational measures already implemented by the data processor pursuant to Article 32 GDPR along with all other information necessary for the data controller to comply with the data controller's obligation under Article 32 GDPR.

6.4 If subsequently – in the assessment of the data controller – mitigation of the identified risks require further measures to be implemented by the data processor, than those already implemented by the data processor pursuant to Article 32 GDPR, the data controller shall specify these additional measures to be implemented in Appendix C.

7.Use of sub-processors

7.1 The data processor shall meet the requirements specified in Article 28(2) and (4) GDPR in order to engage another processor (a sub-processor).

7.2 The data processor shall therefore not engage another processor (sub-processor) for the fulfilment of the Clauses without the prior general written authorisation of the data controller.

7.3 The data processor has the data controller's general authorisation for the engagement of sub-processors. The data processor shall inform in writing the data controller of any intended changes concerning the addition or replacement of sub-processors at least 30 days in advance, thereby giving the data controller the opportunity to object to such changes prior to the engagement of the concerned sub-processor(s). Longer time periods of prior notice for specific sub-processing services can be provided in Appendix B. The list of sub-processors already authorised by the data controller can be found in Appendix B. If the data controller objects on reasonable grounds and the parties cannot resolve the disagreement, the data controller has the right to terminate the affected part of the subscription with effect from the planned change.

7.4 Where the data processor engages a sub-processor for carrying out specific processing activities on behalf of the data controller, the same data protection obligations as set out in the Clauses shall be imposed on that sub-processor by way of a contract or other legal act under EU or Member State law, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of the Clauses and the GDPR. The data processor shall therefore be responsible for requiring that the sub-processor at least complies with the obligations to which the data processor is subject pursuant to the Clauses and the GDPR.

7.5 A copy of such a sub-processor agreement and subsequent amendments shall – at the data controller's request – be submitted to the data controller, thereby giving the data controller the opportunity to ensure that the same data protection obligations as set out in the Clauses are imposed on the sub-processor. Clauses on business related issues that do not affect the legal data protection content of the sub-processor agreement, shall not require submission to the data controller.

7.6 If the sub-processor does not fulfil his data protection obligations, the data processor shall remain fully liable to the data controller as regards the fulfilment of the obligations of the sub-processor. This does not affect the rights of the data subjects under the GDPR – in particular those foreseen in Articles 79 and 82 GDPR – against the data controller and the data processor, including the sub-processor.

7.7 AI model providers as independent recipients. The Platform enables the data controller to select external AI models (including EU-hosted ones) via model choice in ZRouter. Such AI model providers are independent recipients of personal data selected by the data controller; they are not sub-processors in the data processor's contract chain, and the data processor's liability under Article 28(2) and (4) GDPR does not cover them. The data controller is responsible for the legal basis for transfers to AI model providers, cf. Clause 8 and Appendix C.6. The data processor cannot guarantee Zero Data Retention for external model inference; the selected model provider's own retention policy applies, cf. the sub-processor list.

8.Transfer of data to third countries or international organisations

8.1 Any transfer of personal data to third countries or international organisations by the data processor shall only occur on the basis of documented instructions from the data controller and shall always take place in compliance with Chapter V GDPR.

8.2 In case transfers to third countries or international organisations, which the data processor has not been instructed to perform by the data controller, is required under EU or Member State law to which the data processor is subject, the data processor shall inform the data controller of that legal requirement prior to processing unless that law prohibits such information on important grounds of public interest.

8.3 Without documented instructions from the data controller, the data processor therefore cannot within the framework of the Clauses:

1. transfer personal data to a data controller or a data processor in a third country or in an international organisation;
2. transfer the processing of personal data to a sub-processor in a third country;
3. have the personal data processed by the data processor in a third country.

8.4 The data controller's instructions regarding the transfer of personal data to a third country including, if applicable, the transfer tool under Chapter V GDPR on which they are based, shall be set out in Appendix C.6.

8.5 The Clauses shall not be confused with standard data protection clauses within the meaning of Article 46(2)(c) and (d) GDPR, and the Clauses cannot be relied upon by the parties as a transfer tool under Chapter V GDPR.

9.Assistance to the data controller

9.1 Taking into account the nature of the processing, the data processor shall assist the data controller by appropriate technical and organisational measures, insofar as this is possible, in the fulfilment of the data controller's obligations to respond to requests for exercising the data subject's rights laid down in Chapter III GDPR.

This entails that the data processor shall, insofar as this is possible, assist the data controller in the data controller's compliance with:

1. the right to be informed when collecting personal data from the data subject;
2. the right to be informed when personal data have not been obtained from the data subject;
3. the right of access by the data subject;
4. the right to rectification;
5. the right to erasure ('the right to be forgotten');
6. the right to restriction of processing;
7. notification obligation regarding rectification or erasure of personal data or restriction of processing;
8. the right to data portability;
9. the right to object;
10. the right not to be subject to a decision based solely on automated processing, including profiling.

9.2 In addition to the data processor's obligation to assist the data controller pursuant to Clause 6.3, the data processor shall furthermore, taking into account the nature of the processing and the information available to the data processor, assist the data controller in ensuring compliance with:

1. The data controller's obligation to without undue delay and, where feasible, not later than 72 hours after having become aware of it, notify the personal data breach to the competent supervisory authority, Datatilsynet, unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons;
2. the data controller's obligation to without undue delay communicate the personal data breach to the data subject, when the personal data breach is likely to result in a high risk to the rights and freedoms of natural persons;
3. the data controller's obligation to carry out an assessment of the impact of the envisaged processing operations on the protection of personal data (a data protection impact assessment);
4. the data controller's obligation to consult the competent supervisory authority, Datatilsynet, prior to processing where a data protection impact assessment indicates that the processing would result in a high risk in the absence of measures taken by the data controller to mitigate the risk.

The parties shall define in Appendix C the appropriate technical and organisational measures by which the data processor is required to assist the data controller as well as the scope and the extent of the assistance required. This applies to the obligations foreseen in Clause 9.1. and 9.2.

10.Notification of personal data breach

10.1 In case of any personal data breach, the data processor shall, without undue delay and at the latest 48 hours after having become aware of it, notify the data controller of the personal data breach.

10.2 The data processor's notification to the data controller shall cover the nature, scope, likely consequences and the remedial measures, to enable the data controller to comply with the data controller's obligation to notify the personal data breach to the competent supervisory authority, cf. Article 33 GDPR.

10.3 In accordance with Clause 9.2(a), the data processor shall assist the data controller in notifying the personal data breach to the competent supervisory authority, meaning that the data processor is required to assist in obtaining the information listed below which, pursuant to Article 33(3) GDPR, shall be stated in the data controller's notification to the competent supervisory authority:

1. The nature of the personal data breach including where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned;
2. the likely consequences of the personal data breach;
3. the measures taken or proposed to be taken by the controller to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects.

10.4 The parties shall define in Appendix C all the elements to be provided by the data processor when assisting the data controller in the notification of a personal data breach to the competent supervisory authority.

11.Erasure and return of data

11.1 On termination of the provision of personal data processing services, the data processor shall be under obligation to return all the personal data to the data controller and delete existing copies unless Union or Member State law requires storage of the personal data.

11.2 The manner of return or deletion is set out in Appendix C.4: Upon termination, the data controller chooses whether the data shall be (i) returned or (ii) deleted. Return or deletion takes place no later than 30 days after termination, except where Union or Member State law requires storage of the personal data. Written confirmation is provided upon request.

12.Audit and inspection

12.1 The data processor shall make available to the data controller all information necessary to demonstrate compliance with the obligations laid down in Article 28 and the Clauses and allow for and contribute to audits, including inspections, conducted by the data controller or another auditor mandated by the data controller.

12.2 Procedures applicable to the data controller's audits, including inspections, of the data processor and sub-processors are specified in appendices C.7. and C.8.

12.3 The data processor shall be required to provide the supervisory authorities, which pursuant to applicable legislation have access to the data controller's and data processor's facilities, or representatives acting on behalf of such supervisory authorities, with access to the data processor's physical facilities on presentation of appropriate identification.

13.The parties' agreement on other terms

The parties may agree other clauses concerning the provision of the personal data processing service specifying e.g. liability, as long as they do not contradict directly or indirectly the Clauses or prejudice the fundamental rights or freedoms of the data subject and the protection afforded by the GDPR. Such terms are set out in Appendix D.

14.Commencement and termination

14.1 The Clauses form an integral part of the Zeldoc AI Platform Terms of Service and become effective when the Customer accepts the Terms of Service or otherwise commences use of the Platform. Where the parties incorporate these Clauses into a signed contract or addendum, they take effect on the date of such signature.

14.2 Both parties shall be entitled to require the Clauses renegotiated if changes to the law or inexpediency of the Clauses should give rise to such renegotiation.

14.3 The Clauses shall apply for the duration of the provision of personal data processing services. For the duration of the provision of personal data processing services, the Clauses cannot be terminated unless other Clauses governing the provision of personal data processing services have been agreed between the parties.

14.4 If the provision of personal data processing services is terminated, and the personal data is deleted or returned to the data controller pursuant to Clause 11 and Appendix C.4, the Clauses may be terminated by written notice by either party.

15.Data controller and data processor contacts/contact points

The client may contact the data processor using the following contacts/contact points:

• Telephone: +45 88 88 61 60
• E-mail: [email protected]
• Data protection matters: [email protected]
• Address: Zeldoc.ai ApS, CVR 46329902, Åboulevarden 69, 8000 Aarhus C, Denmark

Appendix A.Information about the processing

A.1. The purpose of the data processor's processing of personal data on behalf of the data controller is:

To deliver, operate, secure and support the Zeldoc AI Platform.

A.2. The data processor's processing of personal data on behalf of the data controller shall mainly pertain to (the nature of the processing):

(a) Transient processing during AI inference: Prompts, files and context are transmitted to the selected model and processed during the inference itself. Zeldoc's AI infrastructure (ZCore/ZDev) does not store content; request/response storage is disabled.

(b) Storage at Zeldoc: Account/administration data, operational, security and technical data and backups, cf. A.3(b) and C.4.

(c) Application layer (not covered): Storage of e.g. chats and history takes place in the application layer chosen by the Customer (e.g. OpenWebUI, development clients or partner apps), cf. A.3(c). For inference on model providers, reference is made to each provider's data processing and retention policies, as stated on the sub-processor list.

A.3. The processing includes the following types of personal data about data subjects:

(a) Processed transiently — not stored by Zeldoc: Prompts, files, context and outputs are processed during the AI inference itself; request/response storage is disabled. Content is not retained by Zeldoc's AI infrastructure (ZCore/ZDev).

(b) Stored by Zeldoc — complete inventory:

• Account/administration data: name, email, role and login metadata (deleted 30 days after termination)
• Pseudonymised key/team IDs for API-key customers (can be linked to the Customer's organisation and therefore potentially to identifiable users)
• Operational and usage metadata per AI call: timestamp, model, token count, cost, pseudonymised key/team ID, status — retained 2 years, as it forms the basis for invoicing (operation, billing, security)
• Technical logs, including access logs — retained 90 days
• Session and security records in the Platform's database (e.g. login sessions with IP address) — no automatic deletion period; login sessions are deleted with the user account
• Operational telemetry (metrics) linked to pseudonymised key and team identifiers, whose names can contain personal names — retained 60 days
• Technical data: internal IP addresses in connection with AI calls, session data
• Encrypted backups of the Platform's databases, including account, administration and usage data — retained 1 month (content is not backed up)

(c) Not covered by these Clauses (application layer): Chat history, notes, knowledge bases, memories and similar content data are stored in the application layer operated and hosted by the Customer or a partner authorised by the Customer (e.g. OpenWebUI, development clients or partner apps). Zeldoc neither hosts nor has access to this layer, cf. A.2(c).

A.4. Processing includes the following categories of data subject:

The Customer's users (employees); the Customer's end customers and other natural persons contained in Customer content. For customers who use only API keys, pseudonymised key/team IDs are processed instead of named account data.

A.5. The data processor's processing of personal data on behalf of the data controller may be performed when the Clauses commence. Processing has the following duration:

Until the main agreement (the Zeldoc AI Platform Terms of Service, including these Clauses) has been terminated and the data has been deleted or returned pursuant to Clause 11 and Appendix C.4.

Appendix B.Authorised sub-processors

B.1. Approved sub-processors

On commencement of the Clauses, the data controller authorises the engagement of the following sub-processors:

zeldoc.ai/subprocessors

The current named list is published at zeldoc.ai/subprocessors stating name, purpose, data categories, location (EU/non-EU), transfer mechanism and retention status. The list is versioned and dated. Categories: hosting, email and operational/network services.

OpenRouter is listed for routing external model inference but is not in use. When taken into use, the data processor's liability under Article 28(2) and (4) GDPR covers OpenRouter for the routing leg, cf. Clause 7.7 and Appendix C.6.

The data controller shall on the commencement of the Clauses authorise the use of the abovementioned sub-processors for the processing described for that party. The data processor shall not be entitled – without the data controller's explicit written authorisation – to engage a sub-processor for a 'different' processing than the one which has been agreed upon or have another sub-processor perform the described processing.

B.2. Prior notice for the authorisation of sub-processors

30 days

Appendix C.Instruction pertaining to the use of personal data

C.1. The subject of/instruction for the processing

The data processor shall process personal data only on documented instructions from the data controller, cf. Clause 4, including the instructions in this Appendix C and in Appendices A and B. The processing consists of delivering, operating, securing and supporting the Zeldoc AI Platform (ZControl, ZCore, ZDev, ZRouter etc.), cf. A.1–A.3.

The Customer's tenant is accessed by the Customer's authorised users, including the Customer's advisors and implementation partners, for whom the Customer has secured DPA/confidentiality obligations. Zeldoc processes only on the Customer's instructions.

The data processor shall immediately inform the data controller if instructions given by the data controller, in the opinion of the data processor, contravene the GDPR or applicable EU or Member State data protection provisions, cf. Clause 4.2.

C.2. Security of processing

The level of security shall take into account:

That the processing can involve a large volume of personal data which can be subject to Article 9 GDPR on 'special categories of personal data' which is why a 'high' level of security should be established.

The data processor shall hereafter be entitled and under obligation to make decisions about the technical and organisational security measures that are to be applied to create the necessary (and agreed) level of data security.

The data processor shall however – in any event and at a minimum – implement the following measures that have been agreed with the data controller:

• Role-based access control and the principle of least privilege.
• Individual user accounts and appropriate authentication mechanisms.
• Segregation of Customer environments and data.
• Firewalls, network restrictions and secure administrative connections.
• Vulnerability identification, remediation and security patching.
• Protection against malware and other malicious activity.
• Change management and secure configuration of systems.
• Confidentiality obligations for employees, consultants and subcontractors.
• Capacity, availability and incident-management procedures proportionate to the service.
• Access logging and technical logs (technical logs retained for 90 days).
• Pseudonymisation and anonymisation where appropriate.
• Personal data shall be encrypted during transmission using current and industry-recognised encryption protocols (TLS).

No persistent content storage (compensating measure): Inference on ZCore/ZDev runs in memory on the inference servers; request/response storage is disabled, and content is not retained by the AI infrastructure, cf. A.3(a). The inference servers have neither swap, crash dumps nor disk-backed KV cache enabled, so content is not written to disk. Encryption at rest for transient content is therefore not relevant.

GPU colocation (team.blue): Data is secured through the data centre's physical security (access control, surveillance), the data processor's network controls (firewall, VPN/overlay network) and memory-only processing without persistent content storage on the colocation equipment.

Encryption at rest: Disks and volumes in the Platform's Kubernetes cluster are encrypted, and database backups are encrypted by the backup system. The database volume and the log and metrics volumes at the hosting provider (Hetzner), which contain the data listed in A.3(b), are not encrypted at rest. Compensating measures are maintained: the data centre's physical security (access control, surveillance), network controls (firewall, VPN/overlay network), restricted access and data minimisation (only the data listed in A.3(b) is stored; no customer content, and prompts and outputs are not logged).

C.3. Assistance to the data controller

The data processor shall insofar as this is possible assist the data controller in accordance with Clause 9.1. and 9.2.

C.4. Storage period/erasure procedures

Account and administration data (name, email) are stored for the subscription term and deleted 30 days after termination. Content is not stored by Zeldoc's AI infrastructure; request/response storage is disabled. Operational and usage metadata per AI call is retained for 2 years, as it forms the basis for invoicing. Technical logs, including access logs, are retained for 90 days; session and security records in the database have no automatic deletion period (login sessions are deleted with the user account), and operational telemetry is retained for 60 days. The Platform's databases, including account, administration and usage data, are backed up encrypted, and backups are retained for 1 month; the Customer's content is not backed up.

Upon termination, the Customer chooses whether Customer data and associated tenant data shall be (i) returned or (ii) deleted, cf. Clause 11.2. Usage data and invoices can be retrieved in ZControl; other tenant data is provided on request in a common, machine-readable format. Return or deletion takes place no later than 30 days after termination; statutory retention (the Danish Bookkeeping Act) is excepted. Data in backups is deleted when the backups expire in the ordinary course after 1 month: backups are encrypted, access to them is restricted, they are used only for recovery, and if a backup is restored, the deletion is carried out again. Written confirmation is provided upon request.

C.5. Processing location

Processing of the personal data under the Clauses cannot be performed at other locations than the following without the data controller's prior written authorisation:

• The data processor's location mentioned in the beginning of the data processing agreement.
• The data centres of the hosting and GPU-colocation providers named on zeldoc.ai/subprocessors (EU/EEA).
• The addresses of the sub-processors: zeldoc.ai/subprocessors

C.6. Instruction on the transfer of personal data to third countries

Baseline: EU/EEA models and infrastructure only. Frontier add-on: inference may be processed outside the EU; in that case the transfer is governed by the European Commission's Standard Contractual Clauses (2021/914) and a Transfer Impact Assessment (TIA). Providers are identified on the sub-processor list with their transfer mechanism. External model inference is sent directly to the selected model provider or via OpenRouter; the sub-processor list states which providers are in use. Zeldoc cannot guarantee Zero Data Retention; the selected model provider's own retention policy applies, cf. the sub-processor list. Cf. also Clause 7.7 on AI model providers as independent recipients.

C.7. Procedures for the data controller's audits, including inspections, of the processing of personal data being performed by the data processor

Upon the Customer's request, once a year, Zeldoc provides written documentation (self-declaration) of compliance with the data locality and security terms, cf. Clause 12. Upon reasoned suspicion, the Customer may, with 30 days' written notice, have an independent third party review relevant systems and procedures under confidentiality and without disruption of operations.

C.8. Procedures for audits, including inspections, of the processing of personal data being performed by sub-processors

Based on a risk evaluation the data processor will perform proper inspection of sub-processors.

The parties have agreed that the following types of inspection reports may be used:

• ISO27001 certification
• SOC 2 report
• ISAE 3000 or ISAE 3402
• Self-declaration report

Based on the results of such an audit/inspection, the data controller may request further measures to be taken to ensure compliance with the GDPR, the applicable EU or Member State data protection provisions and the Clauses.

Appendix D.The parties' terms of agreement on other subjects

D.1. Liability. Liability is governed by the liability clause of the Zeldoc AI Platform Terms of Service, cf. Clause 13.

D.2. Amendments. These Clauses may be amended with 30 days' written notice. A material disadvantage to the data controller gives the data controller the right to terminate the affected part of the subscription with effect from the amendment.

D.3. Relationship to published terms. These Clauses constitute the Data Processing Agreement (DPA) of the Zeldoc AI Platform and form an integral part of the Terms of Service, cf. Clause 2.3. The current version is published at zeldoc.ai/dpa.

D.4. Signature-ready version. Enterprise customers whose procurement processes require a countersigned copy may request a PDF of the current published Clauses via [email protected]. The text is identical to the published version, and the Clauses remain effective by acceptance of the Terms of Service regardless.

¹ References to "Member States" made throughout the Clauses shall be understood as references to "EEA Member States".