Legal

Data Processing Agreement (GDPR / UK GDPR, Art. 28)

Version: v2 · Effective date: August 24, 2026

Data Processing Agreement (GDPR / UK GDPR, Art. 28) — v2

Which law applies: this agreement is written for customers whose processing falls under the EU GDPR or the UK GDPR, whichever applies. Both regimes require the same processor terms; where they differ, the difference is stated expressly. Customers subject to Turkish data protection law use the separate B2B-DPA at /legal/b2b-dpa instead of this document.

Scope Note: This Agreement relates to the processing of personal data belonging to the Customer's own end users within the scope of the Service provided by DoWaba to its corporate customer (panel owner). In this Agreement the Customer is the controller and DoWaba is the processor. The current list of sub-processors that may actually be used is published at /legal/alt-isleyenler; DoWaba's relationship with each provider is subject to the terms actually executed with that provider. This Agreement is not a representation that any particular provider agreement has been executed.

Article 1 — Parties and Definitions

Article 2 — Subject Matter

The subject matter is the authority and obligations of DoWaba to process personal data in accordance with the documented instructions of the Customer while providing omnichannel communication (WhatsApp, Instagram, Telegram, email, Messenger, web widget, telephone AI voice) and automation services towards the Customer's end users.

Within the scope of the Service, DoWaba provides the Customer with technical infrastructure only. Providing the information required by Art. 13-14, obtaining any consent, and the content of the communications are the Customer's responsibility.

Article 3 — Nature and Purpose of Processing

Processing consists of collection, storage, structuring, transmission, transient analysis by an AI model, transcription of speech, retrieval and erasure, carried out solely for the purpose of operating the communication and automation service that the Customer has configured, and for no independent purpose of DoWaba.

DoWaba does not use the Customer's end-user personal data to train, fine-tune or improve models of its own, and does not disclose it to third parties except as required to provide the Service or by law.

Article 4 — Categories of Personal Data

Categories that may be processed on behalf of the Customer: identity and contact data (name, telephone number, email address, messaging account identifier); communication content (message text, call audio and transcript, attachments sent by the end user, and any content contained in them); transaction data (appointment, order, form and support records created by the end user); and technical data (IP address, device/browser data, timestamps, consent and objection records).

The Customer must not send special categories of data (Art. 9), criminal-offence data (Art. 10), biometric or health data, or personal data of children, unless the corresponding category has been expressly enabled for the Customer and recorded in the scope declaration in Annex I of the SCC Annexes. Where such a category has not been declared, the Customer bears sole responsibility for uploading it.

Article 5 — Categories of Data Subjects

The Customer's customers and prospective customers, the natural persons who call or write to the Customer, the Customer's employees using the panel, and any third parties whose data appear in the content of a communication.

Article 6 — Duration of Processing

Processing continues for the duration of the service relationship. Content is retained for the period configured by the Customer in the panel; the default is 90 days for message content and for voice content, after which it is destroyed automatically. Records required by other legislation (invoices, accounting and audit records) are kept for the period prescribed by that legislation.

Article 7 — Obligations of the Controller (Customer)

  1. To determine the purposes and means of processing and to give instructions that comply with data protection law.
  2. To provide end users with the information required by Art. 13-14, including the identity of the controller, the purposes and lawful bases, the retention period, recipients, transfers and rights.
  3. To identify a lawful basis under Art. 6 and, where relevant, a condition under Art. 9(2), before the processing begins; to carry out and document the balancing test where legitimate interests are relied upon.
  4. To carry out a data protection impact assessment (Art. 35) where the processing is likely to result in a high risk, and to consult the supervisory authority where required (Art. 36).
  5. To comply with the electronic marketing rules at /legal/eprivacy-marketing before sending any marketing communication.
  6. To manage the panel users to whom it grants access, and to keep the identity and contact details announced to end users accurate and current.
  7. To respond to data subject requests as controller, and to keep its own records of processing activities (Art. 30(1)).

Article 8 — Obligations of the Processor (DoWaba)

DoWaba, in accordance with Art. 28(3):

  1. processes personal data only on documented instructions from the Customer, including as regards transfers to a third country, and informs the Customer if it considers an instruction to infringe data protection law;
  2. ensures that persons authorised to process the data are bound by confidentiality;
  3. implements the technical and organisational measures required by Art. 32 (see Article 9 below);
  4. respects the conditions in Art. 28(2) and (4) for engaging sub-processors (Article 10 below);
  5. assists the Customer, taking into account the nature of the processing, in responding to data subject requests under Chapter III;
  6. assists the Customer in complying with Art. 32-36 (security, breach notification, impact assessment, prior consultation);
  7. at the Customer's choice, deletes or returns the personal data at the end of the service relationship, and deletes existing copies unless retention is required by law (Article 13 below);
  8. makes available the information necessary to demonstrate compliance with Art. 28 and allows for and contributes to audits (Article 12 below);
  9. maintains a record of processing activities carried out on behalf of the Customer (Art. 30(2)).

Article 9 — Security of Processing (Art. 32)

Measures appropriate to the risk include: encryption of data in transit; access control and tenant isolation so that one customer's data is not accessible from another customer's account; role-based authorisation within the panel; audit logging of legally significant actions (acceptances, policy changes, exports and deletions); segregation of duties between service components; regular backups with restricted access; and periodic review of the effectiveness of the measures.

Where the Customer configures the Service with its own AI provider account or API key, the security terms of that provider apply to the provider's part of the processing, and the Customer is the party to that relationship.

Article 10 — Sub-processors

The Customer gives general written authorisation for the engagement of sub-processors. The current list is published at /legal/alt-isleyenler and forms Annex III of the SCC Annexes. DoWaba notifies the Customer of the intended addition or replacement of a sub-processor at least 15 days in advance by e-mail and by a panel notification. The Customer may object within that period on reasoned data protection grounds. Where the parties cannot agree on an alternative, DoWaba may suspend only the affected feature; fees already accrued remain payable and the remainder of the Service continues.

DoWaba imposes on each sub-processor, by contract, data protection obligations equivalent to those in this Agreement, and remains fully liable to the Customer for the performance of the sub-processor's obligations.

Article 11 — International Transfers (Chapter V)

Service infrastructure (application servers, databases and object storage) is operated in Germany (EU) by Hetzner Online GmbH. Personal data is stored there and no permanent copy of Customer content is kept in Türkiye.

DoWaba is established in Türkiye. Named members of DoWaba personnel access the systems remotely from Türkiye for operation, support and security purposes, under least-privilege access, two-factor authentication and logging. This remote access constitutes a transfer within the meaning of Chapter V and is covered by the instruments set out below.

Where the Customer selects an AI or messaging provider, the content necessary to produce the response is transmitted to that provider. The AI providers are established in the United States: Google LLC and OpenAI, L.L.C., both of which are certified under the EU-U.S. Data Privacy Framework (and the UK Extension where applicable). Content transmitted to a provider is retained in accordance with that provider's published terms for its own abuse-monitoring and security purposes; DoWaba makes no representation that the provider deletes the content at the end of the operation.

For transfers to Türkiye and to any other third country not covered by an adequacy decision, the parties incorporate the standard contractual clauses adopted by Commission Implementing Decision (EU) 2021/914, Module Two (controller to processor) for this Agreement, together with the UK International Data Transfer Addendum where the UK GDPR applies. By accepting this Agreement in the panel, the parties agree that those clauses are in force and deemed executed between them; no separate signature is required. Annexes I, II and III to the clauses are set out in the SCC Annexes: Annex I (parties, categories of data, data subjects, purposes and the scope declaration), Annex II (technical and organisational measures, see /legal/tom) and Annex III (sub-processors).

The Customer's own instruments. The Customer's selection of a provider in the panel constitutes a documented instruction within the meaning of Art. 28(3)(a). That instruction does not remove DoWaba's own obligations under Chapter V. The Customer warrants that it has a lawful basis for the personal data it uploads and that, where it acts as controller towards its own end users, it has put in place its own transfer mechanism and information notices. The Customer acknowledges that it has received the transfer risk assessment summary (/legal/tra-summary) and has carried out its own assessment; the parties' duty to cooperate under Clause 14 of the standard contractual clauses is unaffected.

If an instrument ceases to be valid. If an adequacy decision or a certification framework relied upon (including the Data Privacy Framework) is invalidated, suspended or amended, this does not by itself constitute a breach of this Agreement by either party. DoWaba notifies the Customer without undue delay, suspends the affected transfer, and may either replace the provider or discontinue the affected feature. Fees accrued up to that point remain payable.

Government access requests. Where DoWaba receives a binding request from a public authority relating to Customer personal data, it reviews the lawfulness of the request, challenges it where there are reasonable grounds to do so, and discloses only the minimum data necessary. Where notification to the Customer is not prohibited, DoWaba informs the Customer; where it is prohibited, DoWaba seeks permission to notify. Each request is logged. DoWaba does not undertake to challenge every request.

Article 12 — Audit and Information

DoWaba makes available to the Customer the information necessary to demonstrate compliance with Art. 28, including the list of sub-processors, the description of technical and organisational measures (/legal/tom) and the relevant audit records. A request for information is satisfied in the first instance by an existing report, certification or written answer. Where that is not sufficient, the Customer may request an audit specific to it once a year, and additionally after a personal data breach affecting its data, with at least 30 days' written notice, at its own cost, during business hours, subject to confidentiality and without disrupting the Service. The audit may not access another customer's data, and penetration testing against production systems is not permitted. Where an audit establishes a material non-compliance attributable to DoWaba, DoWaba bears the reasonable cost of that audit.

Article 13 — Personal Data Breach

DoWaba notifies the Customer without undue delay after becoming aware, with reasonable certainty, of a breach affecting the Customer's personal data. The first notification is made with the information known and reasonably available at that time; material additional information is provided in stages and without undue delay. A notification, or any assistance provided, does not constitute an admission of fault or liability.

Notification to the supervisory authority within 72 hours (Art. 33) and, where required, communication to the data subjects (Art. 34) are the responsibility of the Customer as controller; DoWaba assists to the extent legally required with the information in its possession. The Customer keeps its notification address in the panel up to date; a notification sent to that address is deemed delivered. Where an incident originates from the Customer, its sub-users or its own devices and credentials, the Customer notifies DoWaba without undue delay.

Article 14 — Deletion and Return

At the end of the service relationship, at the Customer's choice, DoWaba deletes or returns the personal data processed on the Customer's behalf and deletes existing copies, unless retention is required by applicable law. Content subject to periodic destruction is deleted automatically according to the configured retention period even during the relationship. Where the Customer's account is closed, records that must be kept for accounting, tax or evidentiary purposes are retained for the period prescribed by that legislation and are otherwise anonymised.

Article 15 — Liability

Each party is liable for the damage it causes by infringing data protection law in accordance with Art. 82. Administrative fines and compensation arising from instructions given by the Customer, from content sent by the Customer, or from the Customer's failure to inform data subjects or to establish a lawful basis, are borne by the Customer. Liability arising from DoWaba's failure to comply with the obligations specifically imposed on processors, or from acting outside the Customer's lawful instructions, is borne by DoWaba. The limitations of liability in the general service terms apply to the fullest extent permitted by the standard contractual clauses, the IDTA and mandatory law, and do not limit either party's liability towards data subjects or supervisory authorities. DoWaba is not established in the European Union or in the United Kingdom and has not appointed a representative under Art. 27; data subject requests are handled at kvkk@dowaba.com.

Article 16 — Amendments and Continued Use

DoWaba reserves the right to update this Agreement due to changes in legislation, changes in the scope of service, or reasonable commercial reasons. Changes are announced to the Customer by email and/or panel notification at least 15 days, and material changes at least 30 days, before they take effect. The notice states the changed documents, the new version number and the document digest (SHA-256).

The Customer may object before the notice period expires, through the panel or by writing to kvkk@dowaba.com; upon objection the new version does not automatically take effect for that Customer, the parties consider a resolution in good faith, and if none is found the Customer may terminate the relevant service. If no objection is raised and the Customer continues to use the service after the notice period has expired, such continued use constitutes acceptance of the new version, recorded in the audit log with the notice date, waiting period, evidence of use, version number and document digest.

This provision covers only the contractual relationship between the Customer and DoWaba. It cannot establish the information to be given under Art. 13-14, nor any consent under Art. 6(1)(a) or Art. 9(2)(a), of the Customer's end users.

Article 17 — Governing Law, Disputes and Entry into Force

This Agreement is governed by the mandatory provisions of the data protection law applicable to the Customer's processing (EU GDPR or UK GDPR) and, for the remainder of the contractual relationship, by the law stated in the general service terms. Disputes are resolved by the courts stated in those terms, without prejudice to the data subject's right to bring proceedings under Art. 79 or to lodge a complaint with a supervisory authority.

The Agreement enters into force upon electronic acceptance in the panel and remains in force for the duration of the service relationship. Acceptance is recorded in the audit log together with the version number, document digest (SHA-256), date and acting user.


This document sets out the processor terms required by Art. 28(3) and, together with the SCC Annexes, incorporates the standard contractual clauses (Module Two) and the UK Addendum. Version v2 supersedes v1: the international transfers article was rewritten (remote access from Türkiye, US AI providers and the Data Privacy Framework, clauses deemed executed, annexes, the Customer's own instruments, invalidation and government access), sub-processor changes are now notified 15 days in advance with a right to object, the audit procedure was clarified, the fixed 48-hour breach deadline was removed in favour of "without undue delay", and the scope declaration for special categories and children's data was added.