LEGAL
Data Processing Agreement (DPA)
yappyBuy GmbH · yappyOne platform · pursuant to Art. 28 GDPR
Last updated: November 2026
Download DPA as PDF (German)
Note
This is a convenience translation. The German version at /auftragsverarbeitung is legally binding.
Preamble
yappyBuy GmbH ("Processor") operates the AI-based SaaS platform yappyOne. In the course of the use of this platform, the Processor processes personal data on behalf of the customer ("Controller"). This data processing agreement (DPA) governs the data protection requirements of this processing pursuant to Art. 28 GDPR and forms part of the main contract concluded between the parties.
1. Subject matter and duration of processing
1.1 This DPA governs the processing of personal data by yappyBuy GmbH on behalf of the customer in the course of the use of the yappyOne platform and its modules (yappyOne Helpdesk, Chat, Commerce, ERP, CRM, Workflows, Knowledge Base).
1.2 Processing takes place exclusively within the scope of the contractually agreed purposes and begins upon conclusion of the main contract. Its duration corresponds to the term of the respective module or of the main contract.
1.3 After termination of the contractual relationship, the provisions on deletion and return pursuant to section 7 apply.
2. Nature and purpose of processing
2.1 The personal data processed is data arising from the use of the yappyOne platform, in particular:
- customer data and usage data of the Controller
- communication data (e.g. requests via yappyOne Chat or Helpdesk)
- ERP, CRM and commerce data that the Controller provides via connectors
- support data and log data
3. Types of data and data subjects
3.1 The processing concerns in particular the following categories of data:
- contact data (e.g. names, email addresses, telephone numbers)
- technical usage data (e.g. IP addresses, log data, access times)
- communication content (e.g. requests via yappyOne Chat or Helpdesk)
- business data (e.g. order data, ERP data, CRM data), insofar as the Controller provides it
- authentication data of users of the yappyOne platform
- employees and users of the Controller
- customers and end users of the Controller
- contact persons at business partners of the Controller
4. Rights and obligations of the Controller
4.1 The Controller is the controller within the meaning of Art. 4 No. 7 GDPR and bears sole responsibility for the lawfulness of data processing within its area of responsibility.
4.2 The Controller is obliged:
- to fulfil its information obligations towards data subjects pursuant to Art. 13 and 14 GDPR,
- to obtain any required consents itself,
- to document the use of the yappyOne platform in its privacy policy,
- to inform the Processor without undue delay if it detects errors or irregularities in the processing of personal data.
5. Obligations of the Processor (yappyBuy GmbH)
5.1 The Processor processes personal data only on documented instructions from the Controller, unless required to do otherwise by law. In the latter case, the Processor informs the Controller before processing, insofar as this is legally permitted.
5.2 The Processor commits all persons involved in the processing to confidentiality or ensures that they are subject to an appropriate statutory obligation of confidentiality.
5.3 The Processor takes all required technical and organisational measures pursuant to Art. 32 GDPR (see section 11).
5.4 The Processor supports the Controller as far as possible with:
- the fulfilment of data subject rights (Art. 15–22 GDPR),
- the notification of personal data breaches to supervisory authorities (Art. 33 GDPR),
- the communication of personal data breaches to data subjects (Art. 34 GDPR),
- the carrying out of data protection impact assessments (Art. 35 GDPR),
- the consultation of supervisory authorities (Art. 36 GDPR).
6. Sub-processors
6.1 The Processor uses the following sub-processors to provide its services:
- Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany · Service: hosting of all services, databases and storage; backups on Hetzner Storage Box · Location: Germany (Nuremberg data centre); development system in Finland (Helsinki) · Third-country reference: none
- Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855 Luxembourg · Service: language models (Amazon Bedrock: Claude models by Anthropic, operated by AWS); email delivery (Amazon SES); speech output (Amazon Polly); receipt of helpdesk emails (Amazon S3), where set up · Location: EU: eu-central-1 (Frankfurt), Bedrock via the EU cross-region inference profile · Third-country reference: parent company in the USA; EU-US Data Privacy Framework, standard contractual clauses; no training with customer data
- IBM Deutschland GmbH, IBM Campus 1, 71139 Ehningen, Germany · Service: fallback language models in case of a Bedrock outage (personal data masked beforehand); analysis of images in chat (IBM watsonx) · Location: Germany (Frankfurt) · Third-country reference: parent company in the USA; EU-US Data Privacy Framework, standard contractual clauses; no training with customer data
- Anthropic Ireland, Limited and Anthropic, PBC (USA) · Service: AI tool Claude Code for development, error analysis and operations · Location: USA · Third-country reference: standard contractual clauses (DPA); no training; retention 30 days
- Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland · Service: receiving and sending WhatsApp messages via the WhatsApp Business Platform (Cloud API) for the WhatsApp channel in the helpdesk and for the Buddy on WhatsApp; data processed: phone number, WhatsApp profile name, message content, and images and documents; only active for Controllers who set up the channel themselves. If the Controller sets up the channel with its own WhatsApp Business Account, the Controller concludes its own contract with Meta for this, and Meta is, under the WhatsApp Business Platform Cloud API Terms, directly the Controller's processor; the Processor accesses the messages on the Controller's behalf. Meta may use data as an independent controller to ensure the safety, security and integrity of the Cloud API · Location: Meta data centres in Ireland, Denmark, Sweden and the USA (list of sub-processors in the Cloud API Terms); stored by Meta encrypted and for a maximum of 30 days · Third-country reference: parent company Meta Platforms, Inc., USA; EU-US Data Privacy Framework (Meta Platforms, Inc. and WhatsApp LLC certified), supplemented by the European Commission's standard contractual clauses (Module 3, Decision (EU) 2021/914)
7. Deletion and return of personal data
7.1 After termination of the main contract or on instruction from the Controller, the Processor deletes all personal data processed under this DPA or returns it to the Controller, at the Controller's choice. This includes all processing results, documents, data carriers and copies.
7.2 There is no obligation to delete insofar as a statutory obligation to continue storing the data exists. In this case, the Processor restricts processing to the legally required minimum.
7.3 Deletion shall be carried out in such a way that recovery of the data is technically impossible (e.g. by secure overwriting or physical destruction of data carriers).
7.4 The Processor logs all deletion and return operations, stating the date and the person carrying them out. The logs and written proof are made available to the Controller within 72 hours of completion.
8. Audits and proof of compliance
8.1 The Processor makes available to the Controller all information necessary to demonstrate compliance with the obligations laid down in Art. 28 GDPR.
8.2 The Processor allows the Controller to carry out appropriate audits, including:
- inspection of technical documentation and security concepts,
- on-site audits after prior written notice with a reasonable period (at least 14 days),
- audits by third parties commissioned by the Controller, subject to confidentiality.
9. Instructions and support obligations
9.1 The Processor processes personal data exclusively within the scope of the Controller's documented instructions.
9.2 Changes, revocations or additions to instructions are only effective in written or electronic form.
9.3 Both Controller and Processor document all instructions in text form. The documentation shall be retained for the term of the contract and a further three years.
9.4 The Processor informs the Controller without undue delay if, in its opinion, an instruction infringes statutory provisions. The Processor is entitled to suspend execution until the matter is clarified.
9.5 The Controller names one or more persons authorised to give instructions. The Processor names corresponding recipients of instructions. Changes shall be communicated in writing without undue delay.
9.6 The Processor supports the Controller through appropriate technical and organisational measures in fulfilling data subject rights pursuant to Art. 12–22 GDPR.
9.7 The Processor supports the Controller in complying with the obligations pursuant to Art. 32–36 GDPR, in particular with security measures, notification obligations and data protection impact assessments.
9.8 If a data subject or a supervisory authority contacts the Processor directly, the Processor informs the Controller without undue delay and coordinates further steps with it.
10. Data protection officer
The Processor's data protection officer is:
PROLIANCE GmbH
www.datenschutzexperte.de
Leopoldstraße 21
80802 München, Germany
datenschutzbeauftragter@datenschutzexperte.de
Further information on data processing can be found in our privacy policy:
https://www.yappyone.ai/en/privacy
11. Technical and organisational measures (TOMs)
11.1 The Processor takes appropriate technical and organisational measures pursuant to Art. 32 GDPR to ensure a level of protection appropriate to the risk. This includes in particular:
Confidentiality:
- SSL/TLS encryption of all data transfers
- encryption of stored data (at rest and in transit)
- pseudonymisation of personal data where possible
- role-based access control (RBAC)
- tenant separation through row-level security (RLS)
- hosting in Germany (Hetzner, Nuremberg data centre); language models via AWS Bedrock in the EU (Frankfurt), fallback via IBM watsonx in Frankfurt
- targeted annual availability of 98.5 %
- regular data backups
- emergency and recovery concept
- logging of all access and processing operations
- measures against unauthorised modification of data
- regular internal security reviews
- vulnerability management and patch management
12. Personal data breaches and information obligations
12.1 The Processor informs the Controller without undue delay, at the latest within 24 hours of becoming aware, of any personal data breach.
12.2 The notification contains at least:
- the nature of the breach and the categories of data affected,
- the approximate number of data subjects and records affected,
- the likely consequences of the breach,
- the measures taken or planned to remedy it.
13. Final provisions
13.1 The defence of the right of retention pursuant to § 273 BGB (German Civil Code) is excluded with regard to the data processed for the Controller.
13.2 This DPA forms part of the main contract. In the event of conflict, the DPA takes precedence in data protection matters.
13.3 Amendments to this DPA require written form or an electronic format. This also applies to any amendment of this form requirement.
13.4 Should any provision of this DPA be invalid, the validity of the remaining provisions is not affected. The invalid provision shall be replaced by a valid one that comes closest to the economic purpose of the invalid provision.
13.5 The law of the Federal Republic of Germany applies. Place of jurisdiction is the registered office of yappyBuy GmbH.
Contact
yappyBuy GmbH
Kaiselsbergstraße 41
63808 Haibach, Germany
web@yappybuy.com
+49 (0) 6021 5804852
https://www.yappyone.ai
Johannes P. Hattingh, Managing Director
Office hours: Monday to Wednesday 09:00–17:00 (CET),
Thursday and Friday 09:00–12:00 (CET)
Last updated: November 2026