B1 Data Processing Agreement
Agreement pursuant to Article 28 of the General Data Protection Regulation
| Document | Details |
|---|---|
| Applies to | RR42 Rufio and RR42 PharmaPhone — AI telephone assistant for incoming calls |
| Document type | Annex to the General Terms and Conditions of RR42 UG (haftungsbeschränkt) |
| Version | Version 1.4.0, as of 9 November 2026 |
| Structure | Part A applies to all Customers. Part B applies in addition to Customers who are subject to a duty of confidentiality under section 203 para. 1 StGB. Annexes 1 to 6, including Annexes 5a and 5b, form part of this Agreement. |
| Status | Approved version; ready for signature. |
| Contracting parties | The Customer as controller / RR42 UG (haftungsbeschränkt) as processor |
Product guardrails. Incoming calls only. No audio recording: the audio signal is used only transiently for call processing and is not stored. Transcripts are stored in accordance with the agreed configuration and erased in accordance with Annex 4. No professional advice in individual cases; no information on specific prices, stock levels or delivery availability.
Contracting parties
| Role | Contracting party |
|---|---|
| Controller (principal) | [Full company name] · [Address] · [Authorised representative] · [Data protection contact] |
| Processor (contractor) | RR42 UG (haftungsbeschränkt) · Marienstraße 4, 31832 Springe · Amtsgericht Hannover (local court) HRB 230929 · represented by its management · Data protection contact: see § 19 |
Together the "Parties", individually a "Party". The Party designated above as controller is hereinafter referred to as the "Customer", and RR42 UG (haftungsbeschränkt) as "RR42". Where the Customer is a professional secrecy holder within the meaning of Part B, Part B additionally takes effect for the Customer.
The order process carries the Customer's details over into the table above from the data collected there; they can be viewed and corrected in the customer account.
Part A — General Provisions
§ 1 Subject matter, scope and order of precedence
(1) The subject matter of this Agreement is the processing of personal data by RR42 on behalf of the Customer in connection with the provision, configuration, operation, support, maintenance and securing of the Service.
(2) This Agreement supplements the General Terms and Conditions of RR42 (hereinafter "AGB") and applies to all orders that refer to it. In the event of conflict, the data protection provisions of this Agreement take precedence over the other contractual documents, provided they do not fall short of the commitments in the AGB; where a provision of this Agreement falls short of them, the AGB apply (A § 3 para. 1 sentence 6 AGB). The service description in A § 5 paras. 12 and 13 AGB, the order, the technical and organisational measures (Annex 2) and the list of sub-processors (Annex 3) give specific effect to this Agreement.
(3) Where RR42 processes personal data for its own purposes not determined by the Customer, RR42 does not act in that respect as processor but as controller. This applies in particular to customer and contract administration, billing, the handling of enquiries from the Customer and its employees in the support system, the reach and usage measurement of the customer account and of the RR42 websites, and the secure operation of RR42's own systems. For this processing RR42 alone determines the purposes and means; the Customer gives no instructions in this regard, and this Agreement does not apply to it. Order data — call content, transcripts, handover summaries, structured cases and the telephone numbers of callers — is not used for these purposes and is not transferred into the systems used for them (§ 11 paragraph 9). The recipients of this processing are shown separately in Annex 3.
(4) This Agreement governs data protection. A professional duty of confidentiality of the Customer is separately safeguarded by Part B and Annex 5.
§ 2 Duration
(1) This Agreement takes effect together with the contract for the Service and applies for its duration and beyond, for as long as RR42 or a sub-processor processes or retains personal data on behalf of the Customer.
(2) Termination and ending of the contract are governed by the AGB. Data protection obligations which by their nature continue to apply, in particular confidentiality, professional secrecy, return, erasure and the furnishing of evidence, remain in force until fully performed.
§ 3 Nature and purpose of the processing
(1) RR42 processes personal data exclusively for the provision of the contractually agreed services. The main processing operations comprise:
- receiving and technically processing incoming telephone calls;
- transient real-time processing of the audio signal for speech recognition and conducting the dialogue, without audio recording;
- generating synthetic speech output for conducting the dialogue;
- creating, storing, displaying, forwarding and erasing transcripts in accordance with the agreed configuration;
- capturing and forwarding administrative requests, callback requests, pre-orders, messages and status enquiries;
- detecting defined escalation signals and handing over to the Customer's staff;
- tenant administration, authentication, permissions management, logging, and abuse and security monitoring;
- support, error analysis, maintenance, data backup and restoration to the agreed extent.
(2) The Service does not provide professional advice in individual cases and makes no decision reserved to the Customer or its specialist staff. If the language model detects in the statements of callers indications of an acute danger to life, limb or mind, it flags the handover to the Customer's staff as an emergency (emergency flag). The emergency flag is a function owed under the Service and a documented processing operation within the meaning of this Agreement; its effects and its limits are determined by A § 6 paragraph 2 AGB. It is not a medical assessment, not a triage, not a ranking and not a prioritisation relative to other callers; the Service makes no further assessment of the urgency of a request beyond this. The intended purpose under the AI Act is set out in Document C3.
(3) No audio recording takes place. RR42 does not offer it and cannot activate it even at the Customer's request (A § 5 para. 5 AGB). The audio signal is processed transiently; a text transcript is stored in accordance with Annex 4. The processing path contains no recording capability: there is no function, no switch and no diagnostic tool by which the raw audio of a call could be written. At the beginning of the call, callers are informed that the call is transcribed and stored and that they may object to the storage; the wording of the announcement is set out in Document C3.
§ 4 Categories of data subjects and data
| Category | Description |
|---|---|
| Data subjects | Callers and other customers of the Customer; persons authorised to receive or collect; employees and contact persons of the Customer; where applicable, relatives, carers or other third parties named in the call. |
| Master and contact data | Name, form of address, telephone number, e-mail address, postal address, customer number or other identifiers. |
| Communication and content data | Call transcript, time of call, request, messages, callback requests, status information and call metadata. The audio signal is not stored. |
| Case data | Details of pre-orders, orders and other approved processes and their processing status. |
| Caller profile | The name stored for a telephone number, the time of the last name query, the number and time of handovers to the Customer's staff, and the proposal for the priority list derived from them (Annex 1). |
| Special categories (Art. 9 GDPR) | May arise depending on the context of use. Part B applies to professional secrecy holders; there the occurrence of health data is the normal case. Such content is not assessed professionally but handled in accordance with the escalation rules. |
| Usage, log and security data | User ID, roles, access and change logs, IP address, device and session data, error, security and performance events. |
The Customer, as controller, decides on the legal basis, necessity and permissibility of the commissioned processing.
§ 5 Customer's right to give instructions
(1) RR42 processes personal data only on the documented instructions of the Customer, unless an obligation under the law of the European Union or of a Member State applies.
(2) The following count as documented instructions: this Agreement, the AGB, the order, the service description, the operating configuration under sentence 2, and subsequent instructions in text form. The operating configuration — the approved processes, the recipients of notifications, the permissions, the retention periods under Annex 4 and the escalation paths — is determined by the Customer itself in onboarding and thereafter at any time in the customer account; the configuration in force at any time can be viewed there and counts as a documented instruction of the Customer. A separately countersigned configuration record is not agreed. An instruction that brooks no delay in order to avert a specific danger to the rights of data subjects may also be given orally or by telephone; RR42 carries it out without undue delay and records it in text form (A § 30 para. 1 sentence 4 AGB).
(3) If RR42 considers an instruction to infringe data protection law, RR42 shall inform the Customer without undue delay and may suspend execution until the instruction is confirmed or amended. RR42 does not replace legal advice for the Customer.
(4) Instructions that materially change or extend the scope of services laid down in A § 5 para. 12 AGB and in the approved configuration may require a separate technical review and an agreement on remuneration.
§ 6 Obligations of RR42
(1) RR42 undertakes in particular:
- to process personal data exclusively within the documented order;
- to comply with the requirements of Articles 28 to 36 GDPR;
- to implement suitable technical and organisational measures under Article 32 GDPR (§ 10, Annex 2);
- to maintain a record under Article 30 para. 2 GDPR and to present it to the supervisory authority on request;
- to provide the Customer with the information necessary for the Customer to meet its obligations to furnish evidence;
- not to make any audio recording;
- to restrict access to Customer data and to log security-relevant administrative access;
- to support data protection by design.
(2) RR42 has appointed an external data protection officer. The appointment is not a voluntary measure: it follows from section 38 para. 1 sentence 2 BDSG (Federal Data Protection Act), because the processing is subject to a data protection impact assessment under § 14 paragraph 2, and, within the scope of Part B, additionally from Article 37 para. 1 letter c GDPR, because there the large-scale processing of special categories of personal data under Article 9 GDPR forms part of the core activities (B § 1 paragraph 3). RR42 maintains the appointment for the duration of this Agreement. RR42 communicates the contact details to the Customer in text form on conclusion of the contract and on every change, and keeps them retrievable in the customer account. In addition, the contact under § 19 remains the point of contact for data protection matters.
§ 7 Confidentiality and personnel
(1) RR42 deploys for the processing only persons who have been bound to confidentiality or are subject to a statutory duty of secrecy. The obligation continues to apply after the end of the activity.
(2) Permissions are granted on a role basis, reviewed regularly and withdrawn when the need ceases.
(3) RR42 instructs the persons involved in the processing on data protection, information security and the particular protection requirements of the data processed.
§ 8 Professional secrecy
Where the Customer is subject to a duty of confidentiality under section 203 para. 1 StGB, Part B of this Agreement applies to the involvement of RR42 as another person contributing to the service. In the event of conflict, Part B takes precedence over Part A.
§ 9 No use for training or own purposes
(1) RR42 does not use order data, in particular audio signals, transcripts, prompt and output data, for the training, fine-tuning, evaluation or other further development of AI models or other products and services.
(2) RR42 ensures by contract that sub-processors, in particular providers of language models, speech recognition and speech synthesis, likewise do not use order data for these purposes, and demonstrates this on request. Zero Data Retention is activated on the path of the language models. If a sub-processor nevertheless stores call content for a purpose other than the provision of the Service, in particular for abuse control, this is permissible only if the provider, purpose, place of processing and storage period are shown in Annex 3 and the Customer has separately agreed to it before use (A § 13 para. 3 AGB); silence on the part of the Customer does not count as agreement. If the Customer does not agree, RR42 does not deploy the provider for it or provides it with a processing path without such storage. Within the scope of Part B, B § 2 applies in addition.
(3) The use of anonymised or aggregated data is permissible only if re-identification is excluded and the Customer has previously given separate agreement.
§ 10 Technical and organisational measures
(1) RR42 ensures a level of protection appropriate to the risk under Article 32 GDPR. The measures are described in Annex 2. RR42 checks them before activation and thereafter annually and on material changes to the Service against the state actually delivered, and records the result with a date; deviations are incorporated into Annex 2.
(2) The measures comprise in particular encryption in transit and at rest, role-based access control, secure authentication, tenant separation, logging, backup and restoration, vulnerability and patch management, key and secrets management, incident management, and regular review of their effectiveness.
(3) Queries on call data are bound to the tenant identifier of the logged-in account; a call of a different tenant is answered like an unknown identifier. For the call interfaces this binding is safeguarded by automated regression tests, including negative tests, which run on every change. For the other interfaces the same binding procedure is implemented; a systematic negative test across all interfaces of the system is still outstanding and will be added to Annex 2 (no. 3.4) once it has been carried out. The cross-tenant attempt is rejected and logged.
(4) RR42 may further develop measures, provided the agreed level of protection is not undercut.
(5) Support and administration access is restricted to the necessary extent, authorised and logged. In particular, the following are logged: every access via the cross-tenant administration interface, every retrieval of a transcript or call record outside the customer account, and every rejected cross-tenant attempt. The log records identifiers, not call content.
§ 11 Sub-processors
(1) Approved providers. The Customer grants RR42 the authorisation to deploy the sub-processors named in Annex 3 Lists A.1 and A.2, in each case on the processing path stated there. Switching between these providers and starting to use one of them require no advance notice; the authorisation is granted on conclusion of this Agreement.
(2) Conditions of the authorisation under paragraph 1. A provider on List A.1 may be deployed only for as long as the following are cumulatively in place for it: a data processing agreement under Article 28 GDPR; for a place of processing outside the Union, a permissible transfer instrument together with a transfer impact assessment; and, within the scope of Part B, the undertaking in text form under B § 2. For a provider on List A.2, evidence that the intermediary company has imposed the same obligations on it takes the place of its own contract. If one of these conditions is missing, paragraph 3 applies to that provider. The processing path stated for each provider in Annex 3 forms part of the authorisation; a different path of the same provider is not approved.
(3) All other providers. For the engagement or replacement of a sub-processor listed neither in List A.1 nor in List A.2, RR42 shall inform the Customer in text form at least 30 calendar days in advance and shall allow reasoned objections. An objection must relate to specific circumstances. If the Parties do not reach a reasonable solution, the Customer may terminate the contract without a notice period with effect from the intended date on which the change takes effect; fees paid in advance are refunded pro rata for the period thereafter.
(4) Immediate switch. In the event of a disruption, a security incident or the cessation of performance by a deployed provider, RR42 may switch without advance notice to another provider on Lists A.1 or A.2 for which the conditions under paragraph 2 are met. RR42 shall inform the Customer in text form without undue delay thereafter, stating the reason and the duration.
(5) Transparency. On request, RR42 shall inform the Customer in text form within five working days which providers are actually deployed at the time of the request. RR42 keeps the version of Annex 3 in force at any time available and transmits it on every change.
(6) RR42 binds every sub-processor to at least the same obligations, including § 9 and, within the scope of Part B, B § 2, and remains responsible to the Customer.
(7) A change of the language model deployed is not an event under this section and requires no announcement, as long as it remains within the approved providers and processing paths named in Annex 3. The sole decisive factor is that the model deployed is served on one of the serving stacks in the Union named in Annex 3 and that the obligations under § 9 and § 17 are complied with; RR42 checks both before every change. The procedure for model governance is regulated in Document C5. § 11 paragraph 5 remains unaffected: on request, RR42 shall state which model is deployed on which path at the time of the request.
(8) Purely ancillary services without access to personal data do not count as sub-processing.
(9) RR42's own systems. RR42 operates for its own purposes under § 1 paragraph 3 the support system through which it handles enquiries from the Customer and its employees, and the reach and usage measurement of the customer account; the recipients deployed there are not sub-processors under this Agreement. Order data is not transferred into these systems: call content, transcripts, handover summaries or structured cases are not mirrored into the support system, and RR42 does not offer this. If RR42 requires access to call content to remedy a fault, it takes this in the production system and not in the support system; the access is logged under § 10 paragraph 5. The recipients of these own systems are nevertheless shown in full in Annex 3, because A § 5 para. 12 last sentence and B § 2 para. 5 AGB require the disclosure of every provider deployed. Should RR42 in future transfer order data into one of these systems, that would be the engagement of a sub-processor; it is governed by paragraph 3 and, within the scope of Part B, additionally requires the undertaking under B § 2 paragraph 3 and the entry in Annex 5a.
§ 12 Processing in third countries
(1) Processing outside the Union and the European Economic Area takes place only where necessary, disclosed in Annex 3 and permissible under Chapter V GDPR.
(2) Before a transfer to a third country RR42 ensures a permissible transfer instrument, in particular the standard contractual clauses under Implementing Decision (EU) 2021/914, and assesses the consequences of the transfer.
(3) A place of processing in the Union does not end the third-country connection if the provider is subject to a legal system outside the Union and remote access from the third country remains possible. Annex 3 therefore shows the place of processing and the legal system separately.
(4) RR42 presents the transfer impact assessments on request.
§ 13 Support with data subject rights
(1) RR42 supports the Customer by suitable technical and organisational measures with requests for access, rectification, erasure, restriction, data portability and objection.
(2) If a request is received directly by RR42, RR42 shall forward it to the Customer without undue delay and shall not answer it independently.
(3) The Customer remains responsible for examination, identity verification, compliance with deadlines and decision.
§ 14 Support with security, personal data breaches and impact assessment
(1) RR42 supports the Customer in its obligations under Articles 32 to 36 GDPR.
(2) The Parties jointly proceed on the basis that the use of the Service requires a data protection impact assessment under Article 35 GDPR. The processing meets no. 11 of the list of the Data Protection Conference under Article 35 para. 4 GDPR; a threshold analysis is therefore unnecessary. RR42 provides a pre-filled working template. Performance and responsibility remain with the Customer.
(3) RR42 shall notify the Customer of a personal data breach without undue delay after becoming aware of it. The notification form in accordance with Annex 6 is to be used for the initial notification; RR42 provides it in the customer account as a fillable form. The notification contains, to the extent available:
- nature and extent of the incident, including the systems, categories of data and categories of persons affected;
- approximate number of data subjects and records affected;
- likely consequences and initial risk assessment;
- measures taken or proposed;
- point of contact and times of discovery, onset and containment.
(4) Missing information is supplied without undue further delay. The notification does not constitute an acknowledgement.
(5) The decision on notifications under Article 33 or 34 GDPR lies with the Customer.
§ 15 Evidence, inspections and audits
(1) RR42 makes available all information necessary to demonstrate compliance with the obligations under Article 28 GDPR. Certificates, audit reports and questionnaire responses may be used as a first resort.
(2) After reasonable advance notice, the Customer may in principle carry out inspections once a year and on specific occasion, on a risk-oriented basis and with protection of the data of other customers.
(3) A specific occasion exists in particular in the case of a significant data protection incident or at the request of a supervisory authority.
(4) Each Party bears the costs it incurs through an inspection. By way of derogation, RR42 reimburses the Customer for the reasonable and evidenced costs of an inspection if it reveals a material breach of this Agreement, the AGB or the General Data Protection Regulation, or if it became necessary because RR42 failed, despite a request with a reasonable deadline, to provide the evidence owed under paragraph 1 and Article 28 para. 3 letter h GDPR (A § 29 para. 1 sentences 5 and 6 AGB). Further claims for damages and the rights of supervisory authorities remain unaffected.
§ 16 Return, erasure and end of the contract
(1) After completion of the services, RR42 shall, at the Customer's choice, erase or return all personal data. Without instruction, erasure takes place in accordance with Annex 4.
(2) Production data is erased within 30 calendar days after the end of the contract; if the retrieval period under A § 26 para. 1, 2 or 6 AGB is extended or suspended, the erasure is postponed accordingly. For backup copies the period laid down in Annex 4 applies. The end of the contract and the closing of the customer account are recorded in the system and trigger the erasure; an expired trial access is deactivated and treated like a terminated contract. RR42 shall point out the forthcoming erasure to the Customer before the retrieval period under A § 26 para. 2 AGB expires.
(3) Retention required by law is restricted and processed exclusively for the retention purpose.
(4) RR42 confirms contractual erasure unprompted in text form. The content and deadline of the confirmation are governed by A § 26 para. 3 AGB.
(5) On request, RR42 provides the order data of a tenant as a whole in a structured, commonly used and machine-readable format, optionally as JSON or as CSV in accordance with RFC 4180 together with a field description. On the Customer's request, RR42 provides the same output filtered to a single data subject, so that the Customer can answer a request under Article 15 GDPR. Scope, retrieval route and deadlines are governed by A § 26 of the General Terms and Conditions.
(6) RR42 makes the provision, retrieval and export of the order data, their return or erasure, the erasure confirmation and the support with requests from data subjects dependent neither on payment of outstanding fees nor on any other consideration, nor on the settlement of a dispute about fees; RR42 has no right of retention or to refuse performance in this respect (A § 18 para. 3 AGB). This also applies during a suspension and after the end of the contract.
§ 17 AI-specific obligations
(1) The Service is an AI system within the meaning of Regulation (EU) 2024/1689 (AI Act, KI-VO). RR42 is the provider, the Customer is the deployer.
(2) RR42 fulfils the disclosure under Article 50 para. 1 AI Act (KI-VO) as provider: at the beginning of the call, the Service informs callers that they are interacting with an AI system. This Agreement does not establish a separate disclosure obligation of the Customer. The Customer may not remove, shorten, delay or misleadingly design the notice and may not give callers the impression that they are speaking with a human (B § 10 para. 3 AGB). Wording and furnishing of evidence are set out in Document C3.
(3) A machine-readable marking of the synthetically generated speech output under Article 50 para. 2 AI Act (KI-VO) does not currently take place. RR42 has assessed and documented the technical feasibility; in the telephony channel a machine-readable marking does not survive the speech coding used. RR42 reviews the assessment annually — the next review is scheduled for 16 September 2027 — and on every change of speech synthesis provider and every change of the output channel. Beyond these dates, RR42 shall repeat the assessment without undue delay after becoming aware that a speech synthesis provider deployed has introduced a machine-readable marking or that guidelines of the Commission, codes of practice under Article 50 para. 7 AI Act (KI-VO), harmonised standards or a statement of the competent market surveillance authority identify a state of the art for narrowband speech channels. RR42 implements the marking as soon as it is feasible. The assessment and the result of the most recent review are available to the Customer on request.
(4) RR42 supports the Customer in its deployer obligations, in particular under Article 4 AI Act (KI-VO). To this end, RR42 hands the Customer an information sheet in text form on conclusion of the contract, keeps it permanently retrievable in the customer account, carries out the handover in onboarding as a mandatory step with proof, and transmits the version in force at any time on material changes to the Service (B § 10 para. 2 AGB).
(5) The Service is not intended to assess or classify emergency calls, to triage requests or to rank callers by urgency, severity or need for treatment; the emergency flag under § 3 paragraph 2 is not such an assessment. The Customer does not use the system for such purposes. A deviating use may trigger classification as a high-risk AI system under Annex III and is not the subject of this contract.
§ 18 Obligations of the Customer
The Customer is responsible in particular for:
- the lawfulness of the processing and the fulfilment of information obligations;
- the legal basis under Article 9 GDPR, where special categories are processed;
- carrying out the data protection impact assessment under § 14 paragraph 2;
- data minimisation, accuracy and professional approval of the content provided by it;
- determining permissible processes, recipients, permissions and erasure periods in onboarding and in the customer account (§ 5 paragraph 2);
- the decision on connecting an external AI assistant to the customer account via the connector under Annex 3 and on the persons authorised to do so;
- handling requests from data subjects;
- the secure management of its own user accounts and access credentials;
- use in accordance with the intended purpose under § 3 paragraph 2 and § 17 paragraph 5;
- timely, unambiguous and lawful instructions.
The further duties of cooperation and of the deployer are regulated in A § 11 of the AGB.
§ 19 Contact persons and communication
| Function | Customer | RR42 |
|---|---|---|
| Contract contact | Name / e-mail / telephone | info@rr42.de |
| Data protection contact | Name / e-mail / telephone | datenschutz@rr42.de (A § 14 para. 7 letter c AGB) |
| Security incidents | E-mail / telephone | security@rr42.de (A § 14 para. 7 letter b AGB) |
| Persons authorised to give instructions | Names or roles | Reception: info@rr42.de |
| Data protection officer | Name / e-mail, where appointed | appointed externally; contact details under § 6 paragraph 2 |
The order and onboarding route collects the Customer's details bindingly and carries them over into this table. If the Customer names no person for a function, the contact details of the account holder stored in the customer account count as contract, data protection and security contact, and the persons listed in the customer account as administrators count as authorised to give instructions. The Customer makes changes in the customer account; they take effect from the time they are saved.
§ 20 Liability, final provisions and amendments
(1) Liability is governed by Article 82 GDPR and by A § 20 and A § 21 of the AGB.
(2) Amendments require text form.
(3) Should individual provisions be invalid, the validity of the remainder is unaffected.
(4) Choice of law, place of jurisdiction and dispute resolution under A § 31 of the AGB apply.
Part B — Special Provisions for Professional Secrecy Holders
B § 1 Scope of application
(1) This Part applies if the Customer is subject to a duty of confidentiality under section 203 para. 1 StGB, in particular as pharmacist, physician, lawyer or tax adviser, and the processing may concern secrets within the meaning of that provision.
(2) In the event of conflict, this Part takes precedence over Part A.
(3) For Customers under paragraph 1, health data or other special data under Article 9 GDPR arise not exceptionally but regularly. For health data, the processing regularly rests on Article 9 para. 2 letter h GDPR in conjunction with section 22 para. 1 no. 1 letter b BDSG. This basis presupposes that the processing is carried out by or under the responsibility of persons who are subject to professional secrecy; the involvement of RR42 in this chain of responsibility is established through B § 2 and Annex 5.
B § 2 Professional secrecy under section 203 StGB
(1) RR42 is involved as another person contributing to the service within the meaning of section 203 para. 3 sentence 2 StGB.
(2) RR42 undertakes not to disclose third-party secrets without authorisation. RR42 shall be separately bound to secrecy in accordance with Annex 5. This undertaking exists alongside and independently of the data protection obligations of this Agreement.
(3) RR42 binds all its own employees and all other persons contributing to the service and sub-processors who may gain access to secrets, in text form in accordance with section 203 para. 4 sentence 2 StGB, before their first access, and instructs them on the criminal-law consequences of a breach of duty. For this purpose, RR42 uses a uniform template which corresponds to paragraphs 1 to 4 and binds the authority to engage further persons to the same undertaking. The status of the undertaking is shown, with date, for each person and each provider in Annex 5a; without an entry, the person or provider receives no access. RR42 presents the undertaking declarations to the Customer on request.
(4) RR42 discloses secrets to persons contributing to the service only to the extent necessary for proper performance of the service.
(5) The Customer is advised that involving persons contributing to the service without an effective undertaking under paragraph 3 may establish criminal liability of its management under section 203 para. 4 sentence 2 no. 1 StGB.
B § 3 Additional restrictions
(1) The Service does not give out professional information reserved to the professional secrecy holder or its specialist staff, but records it as a request or hands it over.
(2) Call content is transmitted by e-mail only to the extent that the sending service deployed is shown in Annex 3 and bound under B § 2 paragraph 3.
Annex 1 – Description of the Processing
| Mandatory item | Specification |
|---|---|
| Subject matter | Provision and operation of the AI telephone assistant for the Customer's incoming calls. |
| Duration | Term of the contract plus the necessary wind-down, backup and erasure periods. |
| Nature of the processing | Collecting, recording, structuring, storing, retrieving, displaying, transmitting, matching, logging, restricting and erasing; transient audio processing; generation of synthetic speech output. |
| Purposes | Availability by telephone; administrative information; taking messages and callback requests; approved case and status processes; escalation to the Customer's staff; secure operation, support and furnishing of evidence. |
| Data subjects | Callers, customers of the Customer, persons authorised to receive or collect, relatives and representatives, employees and contact persons of the Customer, and third parties named in the call. |
| Categories of data | Master, contact, communication, transcript, case, status, user, log and security data and caller profiles under § 4; within the scope of Part B, additionally health data. |
| Special categories | Regularly within the scope of Part B; otherwise depending on the context of use. No professional assessment of individual cases. |
| Emergency flag | If the language model detects indications of an acute danger to life, limb or mind, it flags the handover to the Customer's staff as an emergency. The flag solely controls the course of the handover and the naming of the competent public body under A § 6 para. 3 AGB; it is not a medical assessment, not a triage and not a ranking (§ 3 paragraph 2). It is stored with the call and erased with it. |
| Evaluation of forwarding behaviour | The Service evaluates for each telephone number how often a call has been handed over to staff and, after three handovers within 90 calendar days, proposes to the Customer that the number be added to the priority list. The decision is made by the Customer. |
| Recipients | Authorised employees of the Customer and of RR42, and approved sub-processors under Annex 3. |
| Erasure periods | In accordance with § 16 and Annex 4. |
Annex 2 – Technical and organisational measures
Document B2 applies, in the version in force at any time that was incorporated on conclusion of the contract. B2 documents at least: physical access, system access and data access control, including role-based permissions; tenant and separation control; encryption of transport, storage, telephony signalling and media paths; pseudonymisation and data minimisation; logging and monitoring; availability, backup, restoration and emergency preparedness; patch, vulnerability, secrets and key management; secure development and change process; incident detection and reporting channels; regular review of effectiveness.
RR42 reconciles the measures of Annex 2 under § 10 paragraph 1 against the state actually delivered and records the result with a date. RR42 presents the reconciliation in force at any time to the Customer on request.
Annex 3 – Sub-processors
As of: 16 September 2026. The decisive entity is the company that acts as contracting party in the respective data processing agreement; where there are several group companies, for Customers established in the Union this is regularly a company in the Union. RR42 keeps this Annex complete and up to date and transmits every change to the Customer (§ 11 paragraph 5).
List A.1 – approved providers with a direct contractual relationship (§ 11 paragraph 1)
The deployment of these providers on the processing path stated requires no advance notice. The authorisation is subject to the conditions of § 11 paragraph 2.
| Provider (company, address) | Service | Approved processing path | Legal system | Data types |
|---|---|---|---|---|
| Railway Corporation, 548 Market Street PMB 68956, San Francisco, CA 94104, United States | Hosting, database | Provision in Amsterdam | United States | all stored order data |
| OpenRouter, Inc., 169 Madison Avenue #2404, New York, NY 10016, United States | Brokering of the language models for the call path and for the Evidenz-Check evidence-check function | eu.openrouter.ai, in-region routing, fail-closed | United States | all call content, prompt and output data |
| Deepgram, Inc., 548 Market Street, Suite 25104, San Francisco, CA 94104-5401, United States | Speech recognition | api.eu.deepgram.com, Frankfurt | United States | transient audio, transcript |
| Corti ApS, Store Strandstræde 21, 4., 1255 København K, Denmark (CVR 35669825) | Speech recognition and verification of recognised medicinal product names | Union | Denmark | transient audio, transcript |
| Eleven Labs Inc., 169 Madison Avenue #2484, New York, NY 10016, United States | Speech synthesis | outside the Union; supported by standard contractual clauses and transfer impact assessment | United States | output text, synthetic speech output |
| OpenAI Ireland Ltd., 1st Floor, The Liffey Trust Centre, 117–126 Sheriff Street Upper, Dublin 1, D01 YC43, Ireland | Speech synthesis on the fallback path | global endpoint, outside the Union; supported by standard contractual clauses and transfer impact assessment | Ireland; ultimate group parent company United States | output text, synthetic speech output |
| easybell GmbH, Brückenstraße 5a, 10179 Berlin (AG Charlottenburg HRB 137060) | Telephony: SIP trunk and telephone numbers | Germany | Germany | signalling, media path, connection data and metadata |
| fonial GmbH, Kaiser-Wilhelm-Ring 7–9, 50672 Köln (HRB 83052) | Telephony: telephone numbers | Germany | Germany | connection data and metadata |
| DigitalOcean, LLC, 105 Edgeview Drive, Suite 425, Broomfield, CO 80021, United States | Operation of the SIP servers and object storage for the encrypted backups and for the contract documents of contracts concluded in text form | SIP servers Amsterdam, object storage Frankfurt (fra1) | United States | signalling and media path (transient); encrypted backups |
| Cloudflare, Inc., 101 Townsend Street, San Francisco, CA 94107, United States | Network access | distributed | United States | connection data |
| Clerk, Inc., 660 King Street, Unit 345, San Francisco, CA 94107, United States | Authentication | United States | United States | Customer's user accounts |
| Stripe Payments Europe, Limited, One Wilton Park, Wilton Place, Dublin 2, D02 FX04, Ireland | Payment processing | Union | Ireland | Customer's contract and payment data |
| PostHog, Inc., 25 Cabot Square, London E14 4QZ, United Kingdom, with processing by the US parent company PostHog Inc., San Francisco, California, United States | Reach and usage measurement of the customer account and of the public web presences | Frankfurt am Main (EU cloud); supported by the EU-US Data Privacy Framework (Art. 45 GDPR), in the alternative standard contractual clauses together with transfer impact assessment | United States | Sign-in service user ID, tenant identifier, plan tier, industry, role; page visited without resource identifiers (call, tenant and other identifiers are redacted before transmission, frontend/components/posthog-provider.tsx:redactedPathname) |
| Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, D04 E5W5, Ireland | E-mail sending (Gmail API) | Sending via infrastructure in the United States; supported by standard contractual clauses and transfer impact assessment | Ireland; ultimate group parent company United States | call summaries transmitted |
| Plus Five Five, Inc. (brand "Resend"), 2261 Market Street #5039, San Francisco, CA 94114, United States | E-mail sending | United States; supported by standard contractual clauses and transfer impact assessment | United States | call summaries transmitted |
RR42 operates the SIP servers itself on the infrastructure stated above. The supplier of the SIP software used there has no access to personal data and is therefore not a sub-processor (§ 11 paragraph 8).
RR42 deploys a provider on this list only once the conditions of § 11 paragraph 2 are met for it — a data processing agreement under Article 28 GDPR, for a place of processing outside the Union a permissible transfer instrument together with a transfer impact assessment, and, within the scope of Part B, the undertaking in text form under B § 2. RR42 presents the evidence on request (§ 12 paragraph 4).
List A.2 – approved further sub-processors without a direct contractual relationship
These providers are engaged via the intermediary under List A.1. RR42 has no contract of its own with them. The obligations under § 11 para. 6 and, within the scope of Part B, the obligation under B § 2 para. 3 must therefore be passed down via the intermediary company; RR42 cannot impose them directly.
| Provider (company, address) | Service | Engaged via | Approved processing route | Legal system |
|---|---|---|---|---|
| Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855 Luxembourg | Provision of the language model (Amazon Bedrock) | OpenRouter | amazon-bedrock/eu-west-1 (Ireland) | Luxembourg; ultimate parent company in the United States |
| Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, D04 E5W5, Ireland | Provision of the language model (Google Vertex) | OpenRouter | in-region route only (google-vertex/eu, google-vertex/europe) | Ireland; ultimate parent company in the United States |
| Microsoft Ireland Operations Limited, One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, D18 P521, Ireland | Provision of the language model (Azure OpenAI) | OpenRouter | azure/eu, EU Data Zone | Ireland; ultimate parent company in the United States |
| Mistral AI SAS, 15 rue des Halles, 75001 Paris, France | Language model | OpenRouter | mistral/eu (Union) | France |
| Anthropic Ireland, Limited, 6th Floor, South Bank House, Barrow Street, Dublin 4, Ireland (CRO 760497) | Originator of the language model made available via Bedrock and Vertex | OpenRouter | in-region route only | Ireland; ultimate parent company in the United States |
| OpenAI Ireland Ltd., 1st Floor, The Liffey Trust Centre, 117–126 Sheriff Street Upper, Dublin 1, D01 YC43, Ireland | Originator of the language model made available via Azure | OpenRouter | in-region route only | Ireland; ultimate parent company in the United States |
Not approved and therefore not in any list: direct access to the global programming interfaces of OpenAI, Anthropic and Google for language models, bypassing an in-region route. Such access requires the procedure under § 11 para. 3 and a contractual relationship of its own. No such access exists: both the call path and the Evidenz-Check call language models exclusively via the EU access under List A.1, and a call for which no endpoint in the Union is available fails closed instead of leaving the Union.
EU serving whitelist of the model route. The route via OpenRouter is technically restricted to serving stacks in the Union (provider.only): Microsoft Azure EU (azure/eu), Google Vertex EU and Europe (google-vertex/eu, google-vertex/europe), Amazon Bedrock Ireland (amazon-bedrock/eu-west-1) and Mistral EU (mistral/eu). A model without an endpoint on one of these stacks is not served. A change of the model in use therefore requires no change to the approved processing route, as long as the model is on one of these EU stacks (§ 11 para. 7). Which stack serves a model is determined by the provider: the same model may run via Amazon Bedrock or Google Vertex, both in the Union; both are therefore approved here.
Abuse monitoring at Microsoft Azure OpenAI. As long as Microsoft has not approved restricted abuse monitoring for the deployment in use, Microsoft stores inputs and outputs for the purpose of abuse monitoring for up to 30 calendar days in the EU Data Zone; Microsoft employees may view them in doing so. Purpose: abuse monitoring. Place of processing: EU Data Zone. Duration: up to 30 calendar days. RR42 uses this stack for a Customer only if the Customer has previously given separate agreement under A § 13 para. 3 AGB; without agreement, the call path is served via a stack without such storage. For Customers within the scope of Part B, B § 2 additionally applies.
In use as of this version: Railway (Amsterdam); OpenRouter with in-region routing, whereby the language model of the call path — Claude Haiku — is served on the EU stacks of Amazon Bedrock (Ireland) and Google Vertex (Union); Deepgram via the EU endpoint and Corti for the verification of recognised medicine names; for speech synthesis Eleven Labs, with OpenAI on the fallback route; for telephony easybell as SIP trunk and easybell and fonial for the telephone numbers, in addition to the self-operated SIP servers on DigitalOcean infrastructure; Clerk; Stripe; Google and Resend for dispatch. RR42 will inform the Customer under § 11 para. 5 which providers are actually in use at the time of a request.
Speech synthesis. Speech synthesis takes place outside the Union. The assistant reads back captured names for confirmation, so that this transfer covers personal data. For each synthesis route — main route and fallback route — it is supported by the standard contractual clauses and a transfer impact assessment of its own (document TIA). Processing of speech synthesis in the Union is planned as a subsequent measure; it is not a precondition of the approval under § 11 para. 1.
Connector for external AI assistants. In the settings of the customer account, the Customer can connect an external AI assistant via an OAuth connector; the customer account shows instructions for this. The connector releases data of the Customer's own tenant — calls and the further information named in the online register of data formats — only to persons who have access in the customer account, to the extent of their role; every retrieval is logged (§ 10 para. 5). Accesses by RR42 via the same connector are support and administration accesses under § 10 para. 5. There is no access without sign-in. The Customer chooses the provider of the assistant; the provider does not thereby become a sub-processor of RR42, but a recipient on the Customer's instruction. The Customer is responsible for the permissibility of this transfer; within the scope of Part B, it additionally requires that the Customer has bound the provider under section 203 para. 4 sentence 2 StGB (German Criminal Code).
Services called in the Customer's browser. The customer account integrates two third-party services that are called directly by the browser of the Customer's employees: the address search of OpenStreetMap (Nominatim, operated by the OpenStreetMap Foundation) for entering the location address, and the public-holiday service feiertage-api.de for the statutory public holidays of the selected federal state. What is transmitted is the address entered or, respectively, the year and federal state, together with the technical connection data of the browser. Call contents, transcripts and telephone numbers of callers do not reach these services. They do not process the information on behalf of RR42 and are therefore not sub-processors; the entry is made for transparency.
List B – all other providers
For every sub-processor not named in List A.1 or A.2, the procedure under § 11 para. 3 applies: 30 calendar days' advance notice, right to object, right of termination.
Evidenz-Check. The Evidenz-Check is a research function for the Customer's staff; it is not part of call acceptance and processes no call data. It is offered in the product variants Pharmacy and Medical Practice. It is available to the Customer to the extent that its plan includes the research function (A § 2 no. 11, A § 5 para. 14, A § 16 para. 1 and para. 4a AGB) and the accesses to the literature search service and to the model access have been set up. RR42 can switch the function off per tenant; by default it is not switched off, and the Customer cannot switch it itself. If it is switched off for a tenant or the tenant's plan does not include it, it cannot be called up for that tenant, and none of the processing described below takes place. The language model calls of the Evidenz-Check run via the same EU access and the same whitelist as the call path. For the literature search, the function calls the Consensus API (Consensus NLP, Inc., 2261 Market Street #5039, San Francisco, CA 94114, United States). What is transmitted is exclusively a research question in English, formulated as a search query, on an active substance, indication or population. Personal data must not be transmitted to this service and are not intended for it; the Customer ensures that its employees enter no information about a specific person into the research. RR42 backs this requirement technically: before transmission, the application mechanically checks the search query for direct identifiers — salutation with name, telephone number, e-mail address, long digit sequence, IBAN, full date — and aborts the search instead of sending it; the same safeguard sits a second time immediately before dispatch. The check is not a promise of completeness: it detects direct identifiers, not every individualising piece of information, and supplements the contractual requirement without replacing it. Consensus is therefore not a recipient of personal data; the entry is made for transparency. Research question, answer and source list are stored in the customer account and erased after the period in Annex 4.
Systems that RR42 operates on its own responsibility. A recipient processes for purposes that RR42 itself determines under § 1 para. 3. PostHog was initially listed here as well, although the measurement in the customer account transmits a tenant identifier set via the sign-in service as well as plan tier, sector and role — features of the processing that RR42 carries out for the Customer, not its own. That is processing on behalf, not a purpose of its own; PostHog is therefore now in List A.1. They are not sub-processors under this agreement and are therefore not listed in either of Lists A.1 and A.2; they are disclosed because A § 5 para. 12 last sentence and B § 2 para. 5 AGB require the complete disclosure of every provider used, with company name, registered office, place of processing, subject matter of the service and extent of possible access to secrets. Neither receives order data (§ 11 para. 9). Because neither can obtain access to secrets within the meaning of section 203 para. 1 StGB, they are not persons contributing to the service within the meaning of section 203 para. 3 sentence 2 StGB; the obligation under B § 2 para. 3 and an entry in Annex 5a are therefore neither provided for nor required for them. Should that change, they could be used for Customers within the scope of Part B only after being bound and entered.
| Recipient (company, registered office) | Subject matter of the service | Place of processing | Legal system | Transfer instrument | Extent of possible access to secrets |
|---|---|---|---|---|---|
| Salesforce, Inc. together with the co-certified Slack Technologies, LLC, San Francisco, California, United States | Messaging service through which RR42's employees process the requests from the support system | United States | United States | EU-US Data Privacy Framework (Article 45 GDPR (DSGVO)), in the alternative standard contractual clauses together with a transfer impact assessment | none |
Support system. RR42 operates the support system itself (Chatwoot, open source) on its own infrastructure in the Union; it is therefore not a recipient of its own and is not to be listed in the table above. Requests of the Customer and its employees are processed there — name, business contact details and the content of the request. Mirroring of calls into the support system is not in operation and is not offered; call contents, transcripts, handover summaries, structured cases and telephone numbers of callers are not entered there and therefore do not reach the connected messaging service. Their inclusion would be the engagement of a sub-processor and is governed by § 11 para. 3.
Reach and usage measurement. It runs exclusively in the browser of the Customer's employees and on RR42's websites against a deployment in the Union. What is transmitted is usage events, the path called in the customer account, device characteristics and a pseudonymous identifier of the signed-in account together with sector, tenant identifier, plan and role. No session recording takes place; no cookies are set, which is why section 25 para. 1 TDDDG is not applicable. The path transmitted may contain the identifier of a call; it does not contain call contents, transcripts or telephone numbers of callers. The measurement is not processing on behalf of the Customer: the Customer determines neither purpose nor means and cannot unsubscribe from it as a service of the Service; RR42 is the controller for it (Article 4 no. 7 GDPR).
Annex 4 – Erasure and return specifications
Separate periods for transcript and case. The full-text transcript and the structured case are different data sets and therefore receive different periods. The transcript is free text and, within the scope of Part B, regularly contains health data; its purpose is exhausted once the matter has been handled. The structured case — name, call-back number, type of concern, status — is considerably less sensitive, but is operationally required by the Customer for longer.
| Type of data | Standard period / event | Procedure / evidence |
|---|---|---|
| Transient audio | No storage; processing ends with the real-time processing. | Technical configuration and architecture evidence; annual verification. |
| Full-text transcript | 30 calendar days from the end of the call; at the Customer's request in text form, RR42 sets a shorter period for its customer account (the interface does not yet show a control element for this; the value is maintained per tenant and enforced by the nightly run). An extension only on the Customer's documented instruction with reasons and only by agreement in text form. | Automated erasure in the nightly run; early erasure on instruction. |
| Detailed call record for error analysis | 24 hours from the start of the call; it is emptied in the first nightly run after this period has expired and thus at the latest 48 hours from the start of the call. | Automated emptying in the nightly run. |
| Structured case | 90 calendar days from the end of the call or completion plus 30 calendar days, whichever occurs earlier; on the Customer's instruction in text form, RR42 sets a shorter period (A § 12 para. 6 sentence 3 AGB). | Automated erasure; the status is set by the Customer. |
| Ratings of individual calls including their free-text fields | With the associated call, at the latest 30 calendar days from the end of the call. | Automated erasure together with the transcript; also covers a request for erasure under Article 17 GDPR. |
| Caller profile including the analysis of forwarding behaviour | 30 calendar days after its creation (A § 12 para. 6, B § 12 para. 1 AGB). | Automated erasure; erasure of individual entries in the customer account. |
| Suggestions to the Customer (priority list, knowledge gaps) | With the Customer's decision, at the latest 30 calendar days after their generation. | Automated erasure. |
| Evidenz-Check: research question, answer and source list | 180 calendar days from the last follow-up question asked on the query; if no follow-up question was asked, 180 calendar days from the query (A § 12 para. 6 AGB). | Automated erasure; in addition, erasure of the entire customer account. There is no selection by which a single history or a single contribution could be erased — a research is not tied to any telephone number or any call. A request that relates to a person named in the free text is carried out by RR42 manually before the period expires, and RR42 records the execution. |
| Call metadata | The identifying contents lapse with the transcript after 30 calendar days. The remaining billing line — identifiers, time, duration, costs, status and concern category — is erased 12 months after the call (A § 12 para. 6 AGB). | Automated emptying of the person-related columns. The result is pseudonymous and not anonymous: the call identifier remains the key by which the minute count is reconciled against the telephony provider's invoice. Retention until then supports the attribution and the reconciliation of the provider's invoice, not the evidence of the claim for payment: that depends on the separately kept billing records under A § 16 para. 5 sentence 7 AGB, which are not the subject of this line and are subject to statutory retention periods of their own (A § 12 para. 6 sentences 9 and 10 AGB). Their retention does not justify keeping this line beyond twelve months. |
| Audit and security logs | 12 months. | Purpose-bound, access-restricted retention; required as evidence under § 10 and Part B. Automated erasure after expiry in the nightly run. |
| Evidence of an objection to storage | 12 months from the call, irrespective of the transcript's period. | Own columns on the call line; automated erasure in the nightly run. The evidence remains even when the transcript was erased long ago — it names no one. |
| Consent log for contract documents and declarations | Duration of the contract and until expiry of the regular limitation period after its end; IP address and browser identifier at the latest 12 months after the end of the contract (C § 9 para. 1 AGB). The data set is deliberately not tied to the customer account and is not erased together with it. | No automated pass; until then the period is tracked as a case. The line is written and never changed; a revocation is a new line (Annex 2, T list, T37). |
| Dispatch log of the notifications owed under the contract (recipient address, occasion, subject, time, transport route, identifier of the dispatch service) | Not yet determined. The period follows the limitation of the contractual claims; it will be determined before the first order. | No automated pass (Annex 2, T list, T37). The log evidences dispatch, not receipt. |
| Traffic check of a returned target number (fact and time of an incoming call, their number) | They persist as long as the number is held in the pool; they lapse with it. | Only the fact and the time are recorded — no telephone number of the caller, no content, no connection data (A § 26 para. 4 sentence 10 AGB). |
| Support and incident data | Case closure plus 12 months. | Erasure after expiry of the evidence period. |
| Production data at the end of the contract | 30 calendar days after the end of the contract; postponement under § 16 para. 2. | Confirmation of erasure in text form under § 16 para. 4. |
| Backup copies | At most 180 calendar days after the erasure under § 16 para. 2. | Regular overwriting. Backup is performed in two procedures: volume backup at the hosting provider and an encrypted database dump in an object storage in the Union. The retention of both procedures is limited to this period; for the volume backup at the hosting provider, the backup plan is set accordingly per environment before activation (Annex 2, no. 5.2). Backup copies are not used productively and are kept exclusively for restoration in the event of a fault. |
Note on implementation. The periods are enforced by an automated nightly erasure run. The retention period for transcript and caller data is stored per tenant and is set at the Customer's request in text form; the other periods in this Annex apply equally to all tenants. The same erasure path ensures the fulfilment of requests for erasure under Article 17 GDPR (§ 13); before execution, a dry run shows which records would be affected. The scope and limits of the procedure are described in the internal erasure concept (document B4).
Annex 5 – Undertaking to observe professional secrecy (section 203 StGB)
Undertaking of RR42 UG (haftungsbeschränkt) as another person contributing to the service within the meaning of section 203 para. 3 sentence 2 StGB. This Annex applies only to Customers within the scope of Part B. RR42 issues it signed in text form, namely at the conclusion of the contract and, towards a Customer that has already been activated, before the first access to secrets (B § 2 para. 3, B § 13 para. 2 AGB).
RR42 declares to the Customer:
- RR42 is aware that the Customer and its staff are subject to the duty of confidentiality under section 203 para. 1 StGB and that RR42 may gain knowledge of third-party secrets.
- RR42 undertakes not to disclose such secrets without authorisation and not to exploit them without authorisation. The undertaking applies without limit in time and beyond the termination of the contractual relationship.
- RR42 has been instructed that unauthorised disclosure is punishable under section 203 para. 4 sentence 1 and para. 6 StGB and unauthorised exploitation under section 204 StGB. The wording of both provisions is attached as Annex 5b.
- RR42 acquires knowledge of third-party secrets only to the extent necessary to perform the contract. Access by RR42's employees to call contents takes place only on a case-by-case basis for the rectification of faults or on the Customer's instruction. RR42 records each such access with time, accessing person, matter concerned and occasion and, on request, presents the Customer with the records concerning it (B § 2 para. 3 AGB).
- RR42 binds all its own employees as well as all further persons contributing to the service and sub-processors who may obtain access to secrets, in text form before the first access, corresponding to section 203 para. 4 sentence 2 StGB, and instructs them about the criminal consequences of a breach of duty; the undertaking makes the authority to engage further persons subject to the same undertaking. The status is shown with date in the register under Annex 5a; RR42 presents the declarations on request.
- RR42 passes secrets on to persons contributing to the service only to the extent necessary for the provision of the service and, for Customers within the scope of Part B, uses no person and no provider that is not disclosed in Annex 3 or not entered in Annex 5a.
Place, date:
Function:
Signature for RR42 UG (haftungsbeschränkt):
Annex 5a – Register of bound persons and sub-processors
The register evidences the undertaking under section 203 para. 4 sentence 2 StGB for each person and each provider. RR42 maintains it on an ongoing basis, keeps it up to date in the customer account and presents it on request (B § 13 para. 2 AGB). A person without an entry receives no access to secrets; a provider without an entry does not satisfy the requirement of § 11 para. 2 and is not used for Customers within the scope of Part B.
The following is maintained for each entry:
| Item | Content |
|---|---|
| Person or company | Name of the person or company name of the provider |
| Role | own employed person, other person contributing to the service, or sub-processor |
| Extent of possible access | which data the person or the provider can reach |
| Date of undertaking | Day of the declaration in text form |
| Evidence | Location reference of the declaration in text form |
| End of access | Day on which the access ceased; while it persists, the field remains empty |
Retention. The entry and the associated declarations in text form — the undertaking to confidentiality, the undertaking to observe professional secrecy under section 203 para. 4 sentence 2 StGB and the declaration required by RR42 on the use of own end devices — are retained for the duration of the access and thereafter three years from the end of the calendar year in which the access ceased; they are then erased. The period is oriented to the need for evidence and is not arbitrarily chosen: it covers the regular limitation under section 195 in conjunction with section 199 para. 1 BGB (German Civil Code) as well as the limitation of prosecution under section 78 para. 3 no. 5 StGB for an offence under section 203 para. 1 and para. 4 sentence 1 StGB and corresponds to the period that A § 29 para. 4 AGB imposes on the Customer for its own evidence. Longer statutory retention obligations remain unaffected; if an official or judicial proceeding is pending for which a declaration may be relevant as evidence, it continues to be retained until its conclusion and is restricted until then.
This register and the declarations are kept outside the Service's production database. The automated erasure run under Annex 4 does not cover them; erasure after expiry of the period under the preceding paragraph takes place during the annual review of the register, the performance of which is recorded with date.
Annex 5b – Wording of sections 203, 204 StGB
Attached because B § 2 para. 2 of the General Terms and Conditions provides for instruction about these provisions. Statutory texts are official works and in the public domain (section 5 UrhG (German Copyright Act)). The version currently in force is authoritative; retrieved on 9 September 2026.
§ 203 StGB – Breach of private secrets
(1) Whoever without authorisation discloses a third-party secret, in particular a secret belonging to the personal sphere of life or a trade or business secret, that was entrusted to or otherwise became known to them as
- 1. a physician, dentist, veterinarian, pharmacist or member of another healthcare profession that requires state-regulated training for the exercise of the profession or the use of the professional title,
- 2. a professional psychologist with a state-recognised academic final examination,
- 3. a lawyer, chamber legal adviser, patent attorney, notary, defence counsel in a statutorily regulated proceeding, auditor, sworn accountant, tax adviser, tax agent,
- 3a. a body or member of a body of an auditing firm, accounting firm or a professional practice company of tax advisers and tax agents, a professional practice company of lawyers or European established lawyers or a professional practice company of patent attorneys or established European patent attorneys in connection with the advising and representation of the auditing firm, accounting firm or professional practice company in the field of auditing, accounting or assistance in tax matters or of its legal or patent-attorney activity,
- 4. a marriage, family, education or youth counsellor as well as a counsellor for addiction issues at a counselling centre that is recognised by an authority or by a corporation, institution or foundation under public law,
- 5. a member or agent of a recognised counselling centre under sections 3 and 8 para. 1 of the Pregnancy Conflict Act (Schwangerschaftskonfliktgesetz),
- 6. a state-recognised social worker or state-recognised social pedagogue, or
- 7. a member of a private health, accident or life insurance undertaking or of a private-physician, tax-adviser or lawyer billing agency
shall be punished with imprisonment for up to one year or with a fine.
(2) The same punishment applies to whoever without authorisation discloses a third-party secret, in particular a secret belonging to the personal sphere of life or a trade or business secret, that was entrusted to or otherwise became known to them as
- 1. a public official or European public official,
- 2. a person especially obliged to the public service,
- 3. a person who performs tasks or powers under staff representation law,
- 4. a member of an investigative committee, other committee or council working for a legislative body of the Federation or of a Land who is not themselves a member of the legislative body, or as an auxiliary of such a committee or council,
- 5. a publicly appointed expert who has been formally obliged by law to conscientiously fulfil their duties, or
- 6. a person who has been formally obliged by law to conscientiously fulfil their duty of secrecy in carrying out scientific research projects,
which was entrusted to or otherwise became known to them. Individual details about the personal or material circumstances of another that have been collected for tasks of public administration are equivalent to a secret within the meaning of sentence 1; sentence 1 does not apply, however, to the extent that such individual details are communicated to other authorities or other bodies for tasks of public administration and the law does not prohibit this.
(2a) (repealed)
(3) There is no disclosure within the meaning of this provision where the persons named in paragraphs 1 and 2 make secrets accessible to assistants working for them professionally or to persons working for them in preparation for the profession. The persons named in paragraphs 1 and 2 may disclose third-party secrets to other persons who contribute to their professional or official activity, to the extent that this is necessary for making use of the activity of the other contributing persons; the same applies to other contributing persons where they make use of further persons who contribute to the professional or official activity of the persons named in paragraphs 1 and 2.
(4) Whoever without authorisation discloses a third-party secret that became known to them in the exercise of, or on the occasion of, their activity as a contributing person or as a data protection officer working for the persons named in paragraphs 1 and 2 shall be punished with imprisonment for up to one year or with a fine. The same punishment applies to whoever
- 1. as a person named in paragraphs 1 and 2 has not ensured that another contributing person who without authorisation discloses a third-party secret that became known to them in the exercise of, or on the occasion of, their activity was obliged to secrecy; this does not apply to other contributing persons who are themselves a person named in paragraphs 1 or 2,
- 2. as a contributing person named in paragraph 3 makes use of a further contributing person who without authorisation discloses a third-party secret that became known to them in the exercise of, or on the occasion of, their activity and has not ensured that this person was obliged to secrecy; this does not apply to other contributing persons who are themselves a person named in paragraphs 1 or 2, or
- 3. after the death of the person obliged under sentence 1 or under paragraphs 1 or 2 discloses without authorisation a third-party secret that they learned from the deceased or obtained from the deceased's estate.
(5) Paragraphs 1 to 4 also apply where the offender discloses the third-party secret without authorisation after the death of the person concerned.
(6) Where the offender acts for remuneration or with the intention of enriching themselves or another or of harming another, the penalty is imprisonment for up to two years or a fine.
§ 204 StGB – Exploitation of third-party secrets
(1) Whoever without authorisation exploits a third-party secret, in particular a trade or business secret, which they are obliged to keep secret under § 203, shall be punished with imprisonment for up to two years or with a fine.
(2) § 203 para. 5 applies accordingly.
Annex 6 – Notification form for a data protection incident
The notification form below is to be used for the initial notification under § 14 para. 3. RR42 transmits the completed initial notification in text form to the Customer's data protection contact under § 19. A fillable form in the customer account does not yet exist for this; until then, the notification form is used in text form. It asks for at least:
- the notifying person, telephone, e-mail and contact person at RR42;
- time of the incident and time of its detection as well as the detecting person;
- course of events, cause and effect;
- systems affected and external service providers involved;
- categorisation of the data affected, within the scope of Part B including health data;
- number of data subjects and records affected;
- whether the problem persists;
- measures initiated with time;
- assessment of the risk of misuse.
Signatures
This agreement is concluded with the order. The ordering process transfers the Customer's details into the caption, displays the agreement in the version applicable at the conclusion of the contract and records the Customer's signing with time; RR42 signs upon activation. Signing outside the ordering process in text form remains possible; the following applies to this:
For the Customer — place and date, name and function, signature:
For RR42 UG (haftungsbeschränkt) — place and date, function, signature: