Draft — under legal review This text is a draft. A lawyer still reviews it; until then the terms in your quote or agreement apply.

cloud.novarint.com Data Processing Agreement

Last updated: 18 November 2026

Version 1.0 — draft, 18 November 2026

Draft, do not publish yet. This is a carefully prepared draft, not legal advice. A Dutch lawyer must review it before it is published. Points that still need a choice are marked [TO DECIDE: …]; points still to be checked are marked [to verify: …]. This English text is a translation; if the two differ, the Dutch text prevails.

This data processing agreement goes with the terms of service of cloud.novarint.com and forms part of the Agreement between:

It applies from the moment the Customer accepts the Agreement, including during the Trial. Capitalised terms have the meaning given in the terms of service or in article 4 of the General Data Protection Regulation (GDPR).

1. Subject

1.1 The Processor processes personal data in the Customer Data on behalf of the Controller, solely to provide the Service as described in the Agreement. Annex 1 describes the nature, purpose, types of data and data subjects.

1.2 The Controller determines the purpose and means. It warrants that it puts and processes the data in the Service lawfully, that the data subjects have been informed and that it has a legal basis.

1.3 This agreement does not cover the data the Processor processes for itself as controller (such as invoicing, contact persons and the Service's security logs); the privacy statement applies to those.

2. Instructions

2.1 The Processor processes the personal data only on the Controller's documented instructions. The Agreement, this data processing agreement and what the Controller and its Users set and do in the Service (such as entering data, running scripts and workflows, exporting, deleting or turning on a Connection) count as those instructions.

2.2 A deviation is only allowed if a legal obligation requires it; the Processor then informs the Controller of that obligation in advance, unless the law prohibits it.

2.3 If the Processor considers that an instruction infringes the GDPR or other data protection rules, it informs the Controller immediately.

2.4 The Processor does not use the personal data for its own purposes. It does not sell them, does not use them for advertising or profiling, and does not use them to train AI models. It may keep usage data without content (such as the number of Active Users and the number of questions to the Assistant) to invoice and to secure the Service.

3. Confidentiality

3.1 The Processor and everyone working for it keep the personal data confidential. Only staff who need it for their work get access; they are bound to confidentiality in their employment or service contract.

3.2 The Processor's staff do not look into the Customer Data, except at the Controller's request (such as with a support question), or when needed to resolve a failure or security incident, and then no more than needed.

4. Security

4.1 The Processor takes appropriate technical and organisational measures under article 32 GDPR, taking into account the state of the art, the costs and the risks. The measures are in annex 2.

4.2 The Processor may adjust the measures, as long as the level of security does not decrease.

4.3 The Controller takes care of what is within its control, such as whom it gives access and which rights, strong passwords and two-step verification for its people, and which Connections it turns on.

5. Sub-processors

5.1 The Controller gives the Processor general authorisation to engage sub-processors. The current ones are in annex 3 and on the sub-processors page.

5.2 The Processor announces a new or replacement sub-processor at least 30 days in advance, by e-mail to the owners of the Organisation and on that page. The Controller may object in writing on reasonable grounds within that period. If the parties cannot agree, the Controller may terminate the Agreement free of charge as of the date the change takes effect. In an emergency (such as a supplier failing) the period may be shorter; the Processor then announces it as soon as possible.

5.3 The Processor imposes on each sub-processor in writing at least the same obligations as in this agreement, and remains responsible towards the Controller for their performance.

5.4 Not sub-processors are the parties the Controller or its Users connect to the Service themselves: their own AI service through MCP (such as Claude, Mistral Vibe, Cursor or GitHub Copilot), web services, webhooks, their own mail accounts and systems with an API key. They receive data on the Controller's instruction (article 2.1), under the arrangements between the Controller and that party. The same applies if the Controller sets its own Mistral AI key for the Assistant in the Service.

6. Where the data are

6.1 The Processor and its sub-processors process the personal data only within the European Economic Area (EEA).

6.2 A transfer outside the EEA only takes place on the Controller's instruction (such as a Connection under article 5.4). The Controller is then responsible for an appropriate basis for that transfer.

6.3 If an authority outside the EEA asks the Processor for data, the Processor does not provide them unless a Dutch or European rule of law requires it, and informs the Controller where allowed.

7. Assistance to the Controller

7.1 Data subject rights. The Service lets the Controller access, correct, export and delete data itself. If the Processor receives a request directly from a data subject, it forwards it to the Controller without undue delay and does not answer it itself, unless agreed.

7.2 Other assistance. The Processor reasonably assists the Controller with its obligations under articles 32 to 36 GDPR (such as a data protection impact assessment or a prior consultation), with the information available to it.

7.3 Assistance that goes beyond what the Service already offers and costs more than a reasonable effort may be charged by the Processor at a reasonable rate stated in advance. The Processor charges nothing for assistance with a data breach it caused.

8. Data breaches

8.1 The Processor notifies a personal data breach (data breach) affecting the Customer Data without undue delay, and at the latest within 36 hours after discovering it, to the owners of the Organisation, by e-mail and if needed by phone.

8.2 The notification contains, as far as known: what happened and when; which types of data and approximately how many data subjects and records are affected; the likely consequences; the measures the Processor has taken or proposes; and a contact person. The Processor adds what is not yet known as soon as it knows it.

8.3 The Processor immediately takes reasonable measures to stop the breach and limit its consequences, and keeps the Controller informed.

8.4 The Controller decides whether it notifies the breach to the Dutch Data Protection Authority (within 72 hours) and to the data subjects. The Processor does not notify them itself, unless the law requires it or the Controller asks.

8.5 The Processor keeps a record of all data breaches, with the facts, consequences and measures.

9. Information and audits

9.1 On request, the Processor gives the Controller all information needed to demonstrate that it complies with this agreement and article 28 GDPR. This includes at least a description of the security, the threat model and the assessment against OWASP ASVS level 2.

9.2 If that information is reasonably insufficient, the Controller may have an audit carried out at most once a year (and additionally after a serious data breach) by an independent expert bound to confidentiality. It announces this at least 30 days in advance. The audit does not disrupt the Service or other customers and does not concern other customers' data. Security tests on the Service only take place after written agreement on what, how and when.

9.3 The Controller bears the costs of an audit, unless the audit shows that the Processor materially fails to comply with this agreement; then the Processor bears the costs. The Processor remedies shortcomings an audit reveals as soon as possible.

10. Term, end, return and deletion

10.1 This agreement runs as long as the Processor processes personal data for the Controller.

10.2 The Controller can export its Customer Data itself at any time, also for 30 days after the end of the Agreement (the Organisation is then read-only). This counts as returning the data.

10.3 After that the Processor deletes the Organisation and all Customer Data from the Service. They remain in the Service's encrypted backups until those backups are replaced under the retention schedule, at the latest 12 months. Those backups are only used to restore the whole Service after a failure; if the Processor has to restore a backup in that period, it deletes the data of ended Organisations again afterwards. On request, the Processor confirms the deletion in writing.

10.4 The Processor keeps personal data longer only if a legal obligation requires it, and then no longer than needed.

11. Liability

11.1 Liability between the parties is governed by article 13 of the terms of service, insofar as the law permits. The rights of data subjects under article 82 GDPR remain unaffected. [to verify: whether the limitation should also apply to fines and to damage from breach of this agreement.]

12. Final provisions

12.1 In case of conflict between this agreement and the terms of service, this agreement prevails insofar as personal data are concerned.

12.2 The Processor may amend this agreement in the manner of article 18 of the terms of service. An amendment that reduces the protection of personal data requires the Controller's consent.

12.3 This agreement is governed by Dutch law; disputes go to the District Court of The Hague.


Annex 1 — Description of the processing

SubjectDescription
NatureStoring, organising, retrieving, displaying, changing, computing (formulas, scripts and workflows), sending (notifications, mail and Connections the Controller sets up), backing up, restoring, exporting and deleting; answering questions to the Assistant.
PurposeProviding the Service: letting the Controller and its Users build in and work with their own apps; support and security thereof.
Types of personal dataWhatever the Controller chooses to store in its apps, such as name, contact details, address, job title, customer and order data, notes, files and images; in addition, data of Users in the Organisation (name, e-mail address, role, rights, who changed what when, comments).
Special categoriesThe Service is not specifically designed for them. If the Controller puts special categories of personal data (art. 9 GDPR), criminal data or a Dutch citizen service number (BSN) into the Service, it assesses itself whether the measures in annex 2 are appropriate and whether this is allowed.
Data subjectsThe Controller's Users; and the people about whom the Controller keeps data, such as its customers, suppliers, employees, members or contacts.
DurationThe term of the Agreement, plus the periods of article 10.
LocationThe Netherlands (EU).

Annex 2 — Technical and organisational measures

Hosting and network

Separation between customers

Access and identity

Secrets and encryption

[to verify: whether the storage volumes at TransIP are encrypted ("encryption at rest").]

Backups and recovery

Recording and monitoring

Software and development

Organisation

Annex 3 — Sub-processors

Sub-processorWhat it doesDataLocation
TransIP B.V., the NetherlandsServers, storage and network of the Kubernetes cluster in which the Service and the backups runAll Customer Data (storage)The Netherlands [to verify: data centre(s)]
TransIP B.V. (e-mail), the NetherlandsSending the Service's e-mail (welcome links, passwords, notifications, mail from scripts and workflows when it goes through the Service)E-mail address, name, message contentThe Netherlands [to verify]
Mistral AI SAS, FranceThe Assistant and the support chat (language model), when the Controller uses the Assistant with the Processor's keyThe question and the data needed for the answerEU [to verify: location and Mistral AI's own sub-processors]

The current list, including what is not a sub-processor, is on the sub-processors page.