This English version is a translation provided for information. The German version is the legally binding one.

Data Processing Agreement (DPA)

pursuant to Art. 28 GDPR · As of: October 2026

Contractual Parties

Controller (Data Controller)

The company that uses the platform draftgo.io on the basis of the Terms (“controller”).

Processor

draftgo.io is operated jointly by the following companies. For the purposes of this agreement, both act jointly as processor (“processor”):

Mai Ventures GmbH
Heinrich-Bettinger-Str. 14, 78333 Stockach
Represented by: Simon Mai
Amtsgericht Freiburg i. Br., HRB 727282

pacutec UG (haftungsbeschränkt)
Heinrich-Bettingerstr. 11, 78333 Stockach
Represented by: Pascal von Briel
Amtsgericht Freiburg i. Br., HRB 735059

Central point of contact: service@draftgo.io

Section 1 Subject Matter, Duration and Conclusion of the Contract

The subject matter of this contract is the processing of personal data by the processor within the scope of the provision of the proofing and approval platform draftgo.io under the Terms and Conditions (“Main Contract”). The processing shall take place exclusively for this purpose.

The term of this contract corresponds to the term of the Main Contract. It shall end automatically upon its termination; the provisions in Section 9 shall continue to apply thereafter.

Upon registration on draftgo.io, this contract automatically becomes an integral part of the Main Contract. A separate signature is not required. In the event of conflicts between this contract and the Terms and Conditions, the provisions of this contract shall take precedence in matters of data protection.

§ 2 Nature, Scope and Purpose of the Processing

Nature and purpose of the processing: Storage, display, alteration, transmission and erasure of personal data in connection with projects, files, comments and approval processes, the dispatch of invitations and notifications, the creation of screenshots of websites upon request, as well as the evaluation of content by AI features, to the extent that the controller uses them.

Categories of personal data:

  • Master data (name, email address, company, role, profile picture) of users and invited guests
  • Usage data (login times, actions, approvals, activity log)
  • Communication data (comments, mentions, attachments to comments, notifications)
  • Content uploaded by the controller (files, images, videos, PDFs, captured websites) and personal data contained therein
  • Technical data (IP address, browser, timestamps, device information)

Categories of data subjects:

  • Employees and team members of the controller
  • External guests and reviewers whom the controller invites to the platform
  • Other natural persons whose data are contained in uploaded content

Excluded data: Special categories of personal data (Art. 9 GDPR), data relating to criminal convictions and offences (Art. 10 GDPR), as well as identity card, credit card and bank account numbers of natural persons are not the subject matter of this agreement. The controller shall not upload such data; the processor’s infrastructure is not intended for them.

The processing of contract, payment and invoice data of the controller is not the subject matter of this agreement; in this respect, the processor is itself the controller. Further details are governed by the Privacy Policy.

Likewise not the subject matter of this agreement is the processing of account and usage data of the controller’s users to the extent that the processor processes them for its own purposes: for the administration of user accounts, the security of the platform, support and billing, as well as for its own communication with users, such as notices regarding the account, the trial phase and plan limits, information about draftgo via email, and in-platform notices (for example, regarding reviews or the referral programme). In this respect, the processor is itself the controller; further details are governed by the Privacy Policy.

The processor does not process data of guests or the controller’s content (projects, files, comments and approvals) for its own advertising or sales purposes. AI features of the platform only process content of the controller if the controller or its users trigger them. The notice “powered by draftgo” in the guest view is part of the platform; no data of guests or of the controller are processed via it for purposes of the processor, and its link contains no reference to the guest or to the controller.

Section 3 Rights and Obligations of the Controller

The controller is the controller within the meaning of Art. 4(7) GDPR. It is solely responsible for the lawfulness of the processing, in particular for the permissibility of uploading content, capturing websites and inviting guests, as well as for safeguarding the rights of data subjects.

The controller shall inform the processor without undue delay if it detects errors or irregularities in the processing.

Section 4 Instructions

The processor processes personal data exclusively on documented instructions from the controller, unless it is legally required to carry out other processing. In this case, it shall notify the controller of this requirement in advance, unless the law prohibits such notification.

The controller generally issues instructions by using the functions of the platform. It issues supplementary instructions in text form. Instructions that go beyond the agreed scope of services shall be treated as a request for a change of service.

If the processor is of the opinion that an instruction infringes data protection provisions, it shall inform the controller without undue delay. It may suspend the execution of the instruction until the controller confirms or amends it.

Section 5 Obligations of the Processor

  • It only engages persons who are committed to confidentiality or are subject to a statutory obligation of confidentiality (Art. 28(3)(b) GDPR).
  • It implements the technical and organisational measures described in Section 7 and Annex 2.
  • It assists the controller with appropriate measures in fulfilling data subjects’ rights (Art. 12 to 23 GDPR) and in complying with the obligations under Art. 32 to 36 GDPR. It forwards requests from data subjects received directly by the processor to the controller without undue delay.
  • It notifies the controller of personal data breaches without undue delay, at the latest within 72 hours after becoming aware of them – even if the breach occurred at a sub-processor. The notification contains, to the extent available, the information pursuant to Art. 33(3) GDPR; it provides missing information as soon as it is available.
  • It demonstrates compliance with its obligations under Art. 28 GDPR to the controller upon request (Section 8).

The processor may demand reasonable remuneration for support services that go beyond the standard functions of the platform and are not based on a breach by the processor.

Section 6 Sub-processors

The controller grants general authorisation for the engagement of sub-processors. The sub-processors engaged at the time of the conclusion of the contract are listed in Annex 1 and shall be deemed approved.

The processor shall inform the controller of any intended engagement or replacement of a direct sub-processor in text form, such as by email or via the platform, at least four weeks in advance. The controller may object within this period on good cause under data protection law. If the parties do not reach an agreement, either party may terminate the main contract extraordinarily with effect from the date of the change.

The sub-processors for their part engage further sub-processors, which they publish in their own lists and amend according to their own timelines; the material ones are named in Annex 1. If the processor becomes aware of a material change to these lists, it shall inform the controller without undue delay; paragraph 2, sentences 2 and 3 shall apply accordingly.

The processor shall contractually impose data protection obligations on each sub-processor that correspond to those of this contract, unless paragraph 6 provides otherwise. Transfers to third countries outside the EU and the EEA shall only take place if the requirements of Art. 44 et seq. GDPR are met, in particular on the basis of an adequacy decision (e.g. EU-US Data Privacy Framework) or the EU Standard Contractual Clauses.

The infrastructure provider Lovable also processes technical log data (e.g. IP addresses as well as device and session identifiers) of users and guests when accessing the platform as an independent controller, for instance for the security and operation of its services. This processing is not part of the data processing under this contract.

“Capture website” function: For this function, the processor engages the service Browserless (USA). Browserless accesses the address specified by the controller and creates a screenshot; Browserless does not receive any further data of the controller, its users or guests.

§ 7 Technical and Organisational Measures

The processor shall implement appropriate technical and organisational measures pursuant to Art. 32 GDPR to ensure a level of protection appropriate to the risk. The measures are described in Annex 2. The processor may adapt them to technical progress, provided that the level of protection is not reduced thereby.

Section 8 Evidence and Audits

The processor shall demonstrate compliance with its obligations primarily through suitable documentation, such as current certificates, inspection reports or audit results, including those of the sub-processors.

If this is not sufficient in an individual case, the controller may carry out an inspection or have it carried out by an auditor bound by confidentiality who is not in competition with the processor. Inspections shall take place following notification with a notice period of as a rule, four weeks, at most once per calendar year, during normal business hours and without avoidable disruption to operations. Audits for cause following a data protection breach or by order of a supervisory authority shall remain unaffected thereby. Inspections at sub-processors shall be governed by their contracts; the processor shall provide their inspection reports insofar as they are available to it. The processor may demand reasonable remuneration for the expense incurred for inspections.

§ 9 Deletion and Return

Following termination of the main contract, the processor shall delete all personal data of the controller within a reasonable period, at the latest after 90 days, unless statutory retention obligations prevent this. Data in backup copies shall be deleted in the course of regular backup cycles.

At the request of the controller prior to the end of the contract, the processor shall return the data prior to deletion in a structured, commonly used and machine-readable format, insofar as they cannot be exported via the functions of the platform itself.

§ 10 Liability

Art. 82 GDPR shall apply to liability towards data subjects. As between the parties, the parties shall be liable in proportion to their respective share of responsibility for the damage incurred. In all other respects, the liability provisions of the Terms and Conditions shall apply.

§ 11 Final Provisions

Amendments to this agreement shall be made in accordance with the procedure governed in the Terms and Conditions or in text form. Should individual provisions be invalid, the validity of the remaining provisions shall remain unaffected. The law of the Federal Republic of Germany shall apply, to the exclusion of the UN Convention on Contracts for the International Sale of Goods (CISG). If the controller is a merchant, a legal entity under public law, or a special fund under public law, the place of jurisdiction shall be Stockach.

Annex 1 – Sub-processors

Sub-processorServicePlace of processingBasis of transfer
Lovable Labs Incorporated, 1 Lincoln St, Boston, MA 02111, USALovable Cloud: Provision of the platform, server-side functions, dispatch of log-in and account security emails as well as fallback dispatch in the event of disruptions, AI functions via the Lovable AI GatewayUSA; stored data in the EUEU Standard Contractual Clauses
– via Lovable: Supabase Pte. Ltd. (Singapore) on Amazon Web ServicesDatabase, authentication, file storageEU (Frankfurt); maintenance and support access possible worldwideEU Standard Contractual Clauses (via Lovable)
– via Lovable: Cloudflare, Inc. (USA)Runtime environment and delivery of the platformworldwide (global data centre network)via Lovable
– via Lovable: Google (Gemini)Language models for the AI functions (AI review, assistant “GO”), only if the controller or its users trigger themworldwidevia Lovable
Google Cloud EMEA Limited, 70 Sir John Rogerson's Quay, Dublin 2, IrelandGoogle Workspace: Dispatch of emails, e.g. invitations and notifications (access via an interface of Lovable)EU, USA possibleGoogle Cloud Data Processing Addendum: EU-US Data Privacy Framework or EU Standard Contractual Clauses
Browserless (USA)Screenshot of a website specified by the controller (“Capture website” function, Section 6)USA–

The complete lists of further sub-processors are published by Lovable, Supabase and Google themselves; the processor will disclose them upon request.

Annex 2 – Technical and Organisational Measures

Confidentiality

  • Physical access control: Operation exclusively in the data centres of the cloud providers used
  • System and data access control: role-based permissions, token-based authentication, row-level security at database level; two-factor authentication for all accounts with administration rights for the platform, also enforced at database level and server-side function level
  • Separation control: Multi-tenant separation via row-level security policies per company and project; uploads only to the storage areas assigned to the uploader
  • Encryption of data at rest (AES-256 at storage level)
  • Data-minimised logging: E-mail addresses, access keys and links containing access keys are not logged in plain text

Integrity

  • Transfer control: Encryption of all transmissions (HTTPS, TLS 1.2 or higher)
  • Input control: Audit log for security-relevant actions and error log with notification of administrators
  • Protection against misuse: Rate limiting of requests per time period, verification of each request identifier against the authorisation of the requester

Availability and resilience

  • Redundant cloud infrastructure and automated backups
  • Rapid recoverability through a disaster recovery process

Instruction control

  • Commitment of employees to confidentiality
  • Documented instructions
  • Contracts with sub-processors pursuant to Section 6

Review and incident management

  • Regular testing, assessing and evaluating of the measures (data protection reviews, security scans with a maintained register of all findings, automated nightly self-tests, updating of dependencies)
  • Defined process for reporting and handling data protection incidents, including notification of the controller within 72 hours

For the processor

Simon Mai, Managing Director, Mai Ventures GmbH
Pascal von Briel, Managing Director, pacutec UG (haftungsbeschränkt)

Stockach, October 2026