The digital brand handbook from MerkBrouwers

Data processing agreement MarkBase

Do you put personal data in your brand manual, such as names of team members or photos of people? Then we process it on your behalf. These are the arrangements the GDPR requires for that.

Version 1.0 — effective from 23 October 2026

This data processing agreement forms part of the General Terms and Conditions of MarkBase (a trade name of MerkBrouwers, Chamber of Commerce no. 85502006, hereinafter: Processor) and applies between Processor and the Customer (hereinafter: Controller). It applies as soon as Customer creates an account, including during the trial period. Terms have the meaning given in the GDPR.

1. Subject and duration

  1. Processor processes personal data on behalf of Controller in order to provide the Service: the digital brand manual, asset library, templates, share links and AI brand checks.
  2. This agreement runs for as long as Processor processes personal data for Controller, including the trial period and the export period after termination.

2. What data, about whom

Data subjectsPersonal data
Users (employees, freelancers, agencies)Name, email, role, organisation, login and activity data
External guests (printers, photographers)Name, email, use of share and upload links
People in contentImages and names in photos, templates and texts uploaded by Customer

Controller does not put special categories of personal data (such as health data or national ID numbers) in the Service.

3. Instructions

  1. Processor only processes the data on Controller's written instructions. The Agreement and the use of the Service count as such an instruction.
  2. Processor does not use the data for its own purposes, including to train AI models.
  3. If Processor considers an instruction to be in breach of the GDPR, it reports this immediately.
  4. If Processor is legally required to disclose data, it reports this in advance, unless the law prohibits doing so.

4. Confidentiality

Everyone who has access to the data on behalf of Processor is bound by confidentiality.

5. Security

Processor takes appropriate technical and organisational measures (art. 32 GDPR). These include at least: encryption in transit (TLS) and at rest, role-based access, regular backups, access logging and timely installation of security updates.

6. Sub-processors

  1. Controller gives general authorisation for the sub-processors in annex 1.
  2. Processor announces a new or replacement sub-processor at least thirty (30) days in advance. Controller may object with reasons within that period. If the parties cannot agree, Controller may terminate the Agreement free of charge.
  3. Processor imposes the same obligations on sub-processors as in this agreement and remains liable for them.
  4. Transfers outside the EEA only take place with an appropriate safeguard, such as an adequacy decision (including the EU-US Data Privacy Framework) or standard contractual clauses.

7. Assistance with rights and obligations

  1. Processor assists Controller with requests from data subjects (access, correction, deletion). Requests received directly by Processor are forwarded.
  2. Processor assists with a DPIA or prior consultation of the supervisory authority, insofar as this can reasonably be asked of it.

8. Data breaches

  1. Processor reports a personal data breach without undue delay, and no later than forty-eight (48) hours after discovery.
  2. The notification includes at least: what happened, which data and data subjects are affected, the likely consequences and the measures taken or proposed.
  3. Controller decides whether the breach is reported to the supervisory authority and to data subjects.

9. Audits

On request, Processor provides all information needed to demonstrate compliance. Controller may have an audit carried out by an independent expert at most once a year, with at least fourteen (14) days' notice and at its own expense.

10. End

After termination of the Agreement, Controller can export the data for thirty (30) days. Processor then deletes all personal data, including copies, unless the law requires retention. Backups are overwritten within ninety (90) days.

11. Liability and order of precedence

Article 13 of the General Terms and Conditions applies to liability. In the event of conflict, this data processing agreement prevails on matters of data protection.

Annex 1 — Sub-processors

Sub-processorServiceLocationSafeguard
Lovable / CloudflareHosting of the website and platform, file storageEU / VSEU-US Data Privacy Framework and standard contractual clauses
GitHub (Microsoft)Storage and management of the source codeNetherlands / EUData processing agreement
Microsoft (Bookings, Outlook)Demo appointments and emailEU Data BoundaryData processing agreement
Google (Gemini API)AI brand checks and suggestionsVSEU-US Data Privacy Framework and standard contractual clauses
Google (Analytics)Website statistics, only after consentVSEU-US Data Privacy Framework and standard contractual clauses
StripePaymentsEU / VSEU-US Data Privacy Framework and standard contractual clauses
MoneybirdInvoicing and accountingNetherlandsData processing agreement

Would you like to receive this data processing agreement signed, or use your own template? Email privacy@betermerk.nl.