General Terms and Conditions of RR42 UG (haftungsbeschränkt) for the AI Telephone Assistants "Pharmaphone" and "Ask Ruf.io"
Version 1.4.0 · As of 9 November 2026
| Item | Value |
|---|---|
| User of these terms | RR42 UG (haftungsbeschränkt) |
| Business address | Marienstraße 4, 31832 Springe |
| Registration court, registration number | Amtsgericht Hannover, HRB 230929 |
| VAT identification number | DE463354727 |
| Representation | the managing directors entered in the commercial register, each with sole power of representation |
| Contact | info@rr42.de |
| Scope | All contracts for the AI telephone assistants "Pharmaphone" (pharmacies) and "Ask Ruf.io"/"Rufio" (medical practices, businesses) with business customers, whether concluded via the customer account or in text form |
| Structure | Part A General Terms · Part B Special Terms for Professional Secrecy Holders · Part C Special Terms for the Online Order · Annex index |
These AGB replace the former "Master Service Agreement" as the set of rules for all product variants and all ordering routes. Annexes A5 and B1 remain in place and are incorporated in the version that RR42 transmits to the Customer pursuant to A § 4 para. 4.
Table of Contents
Part A – General Terms
- A § 1 Provider, Scope of Application, Customer Group
- A § 2 Definitions
- A § 3 Components of the Contract, Order of Precedence, Version, Customer's Terms
- A § 4 Conclusion of the Contract
- A § 5 Subject Matter of Performance and Quality of the Service
- A § 6 Not an Emergency Call System; Conduct on Emergency Indications
- A § 7 Target Number, Call Diversion, Transferring the Call, Number Porting
- A § 8 Availability, Maintenance, Disruptions
- A § 9 Support
- A § 10 Changes to the Service; Beta Functions
- A § 11 Customer's Cooperation; Forwarding Destination, Reachability, Content, Safeguards
- A § 12 Data Protection; Data Processing; Processing of the Call; Information to Callers
- A § 13 Rights of Use, Customer Data, Use of Data, Feedback, Open Source, AI Outputs
- A § 14 Confidentiality; Information Security; Security Incidents; Contact Points
- A § 15 Warranty
- A § 16 Fees, Billing Period, Metering, Plan Change, Value Added Tax
- A § 17 Payment, Invoice, Default, Returned Direct Debit
- A § 18 Set-off and Right of Retention
- A § 19 Price Change
- A § 20 Liability
- A § 21 Third-Party Claims; Indemnification; Contribution Between the Parties
- A § 22 Force Majeure
- A § 23 Term and Ordinary Termination
- A § 24 Termination for Good Cause
- A § 25 Suspension
- A § 26 End of the Contract, Data Export, Erasure, Switching
- A § 27 Changes to these AGB
- A § 28 References and Public Relations
- A § 29 Evidence, Audits, Legal Compliance, Sanctions
- A § 30 Form, Declarations, Notices
- A § 31 Governing Law, Place of Jurisdiction, Dispute Resolution
- A § 32 Assignment, Transfer of the Contract, Language, Interpretation, Severability Clause
Part B – Special Terms for Professional Secrecy Holders
- B § 1 Scope of Application and Precedence
- B § 2 Confidentiality and Undertaking under section 203 StGB
- B § 3 Time of the Undertaking; Activation
- B § 4 Customer's Responsibility under Professional Rules
- B § 5 No Pharmaceutical, Medical, Legal or Tax Advice
- B § 6 Statements on Stock, Availability and Prices; Advertising Law for Medicinal Products and Therapies
- B § 7 On-Call Availability and Out-of-Hours Service (Pharmacies); Reachability of Practices
- B § 8 Emergencies and Urgency
- B § 9 Health Data, Legal Basis, Data Protection Impact Assessment
- B § 10 AI Act: Roles, Competence, Transparency
- B § 11 Prohibition of Change of Purpose; Configuration Limits; Indemnification
- B § 12 Call Data, Transcripts, Release
- B § 13 Declaration of Undertaking (Annex 5 to Annex B1)
Part C – Special Terms for the Online Order
- C § 1 Scope of Application; Registration and Activation of the Customer Account
- C § 2 Business Customer Declaration; "Einzelunternehmer" Plan
- C § 3 Trial Period
- C § 4 Ordering a Subscription via the Customer Account
- C § 5 Payment via the Payment Service Provider; SEPA Direct Debit
- C § 6 Termination in the Customer Portal
- C § 7 User Accounts, Team, Access Credentials
- C § 8 End of Call Answering; Advance Information; Call Diversion
- C § 9 Evidence of Incorporation; Contract Text; Existing Customers
Annex index
The headings of this index are taken verbatim from the text; A § 32 para. 4 sentence 1 (headings serve for orientation) applies to them equally.
Part A – General Terms
A § 1 Provider, Scope of Application, Customer Group
(1) These General Terms and Conditions ("AGB") apply to all contracts between RR42 UG (haftungsbeschränkt), Marienstraße 4, 31832 Springe, entered in the commercial register of the Amtsgericht Hannover under HRB 230929, represented by its managing directors entered in the commercial register, each with sole power of representation ("RR42"), and its Customers for the provision of the AI telephone assistant offered under the names "Pharmaphone" and "Ask Ruf.io" ("Rufio") (the "Service"). They apply to the free trial period as well as to paid subscriptions and irrespective of whether the contract is concluded via the customer account (Part C) or in text form pursuant to A § 4 para. 3.
(2) RR42 offers the Service exclusively to business customers (Unternehmer) within the meaning of section 14 BGB (German Civil Code), legal entities under public law and special funds under public law. Consumers within the meaning of section 13 BGB cannot order the Service. By placing the order, the Customer declares that it concludes the contract in the exercise of its commercial or self-employed professional activity, and designates in the order the business, practice, pharmacy or law firm for which the Service is used. This declaration is a declaration by the Customer about the purpose it pursues; it is not a confirmation of facts to the Customer's detriment, does not alter the statutory burden of proof and does not exclude the application of mandatory consumer protection provisions if the Customer is in fact a consumer. For the "Einzelunternehmer" plan, C § 2 applies in addition.
(3) The Service is aimed at Customers with their registered office or place of business in the Federal Republic of Germany. Customers with their registered office in another country can use the Service only following a separate agreement with RR42 in text form; the treatment for value added tax purposes will then be determined individually.
(4) If it turns out that a Customer, contrary to its declaration under paragraph 2, has acted as a consumer within the meaning of section 13 BGB, RR42 may terminate the contract in text form with a notice period of two weeks. Termination with immediate effect is permissible only if, after weighing the interests of both parties, RR42 cannot reasonably be expected to continue the contract until the end of this period, in particular in the case of a knowingly untrue declaration by the Customer; the right to terminate for good cause under A § 24 remains unaffected. In the termination, RR42 shall point out to the Customer that it must cancel the call diversion to the target number by the time the termination takes effect, and until then RR42 shall continue to answer calls. RR42 shall refund fees paid in advance pro rata for the period after the termination takes effect. The Customer's statutory rights remain unaffected; provisions of these AGB that conflict with mandatory consumer protection provisions do not apply to it.
(5) Part B applies in addition if the Customer or the persons for whom it uses the Service are subject to a duty of confidentiality under section 203 para. 1 StGB (German Criminal Code) (B § 1). Part C applies in addition to contracts that are concluded via the customer account and the online ordering process. In the event of conflicts, Part B takes precedence over Part C and Part A; Part C takes precedence over Part A.
A § 2 Definitions
The following terms apply to these AGB and their Annexes:
- Service: the AI telephone assistant operated by RR42 in the ordered product variant ("Pharmaphone" for pharmacies, "Ask Ruf.io"/"Rufio" for medical practices and other businesses), which RR42 makes available to the Customer for use as a software service provided over the internet ("software as a service"), including the customer account.
- Customer: the contracting party of RR42 pursuant to A § 1 para. 2.
- Callers: natural persons whose call the Service answers, as well as other persons whose statements are processed in the call.
- Customer account (also "Dashboard"): the web application operated by RR42 through which the Customer manages the Service, views call history, transcripts and requests, maintains settings, invites users and manages billing.
- Payment service provider: the provider commissioned by RR42 with payment processing; at the time of conclusion of the contract this is Stripe Payments Europe, Ltd., Ireland. A change of payment service provider is governed by the procedure for sub-processors under § 11 of Annex B1, including the advance information and the right of objection provided there; the functions under A § 16 para. 5, A § 17, C § 5 and C § 6 shall be made available to the Customer in an equivalent manner after a change as well. Customer portal: the portal provided by the payment service provider for managing the payment method, billing details and termination.
- Target number: the telephone number designated by RR42 to which the Customer diverts calls from its own line (A § 7 para. 1).
- Call diversion: the feature set up by the Customer with its own telecommunications provider by which calls to its line are routed to the target number.
- Forwarding destination: the telephone number stored by the Customer in the customer account to which the Service transfers calls (A § 7 para. 5).
- Subscription start: the point in time determined under A § 23 para. 1 sentence 2; billing period: the monthly period under A § 16 para. 2, which begins with the subscription start and does not correspond to the calendar month.
- Base fee: the fixed fee of the selected plan, payable in advance per billing period; included allowance: the call minutes included in the plan per billing period; additional minute: every full minute above the included allowance calculated under A § 16 para. 4; included queries: the number of queries of the research function (A § 5 para. 14) included in the plan per billing period; additional query: every query of the research function above the included queries calculated under A § 16 para. 4a.
- Plan overview: the presentation of the plans with base fee, included allowance, price per additional minute and, where the plan includes the research function, the number of included queries and the price per additional query, which is displayed to the Customer in its ordering process at the time of the order. If an individually agreed plan is stored for the Customer, its presentation in the Customer's ordering process is the plan overview applicable to it.
- Order: the order summary of the ordering process in the customer account, which the Customer submits with the button "order with obligation to pay" (C § 4), or an order confirmed by it in text form pursuant to A § 4 para. 3.
- Trial period: the free trial of the Service under C § 3, or, in the case of an order in text form, under A § 4 para. 5.
- Customer data: all data, content and configurations that the Customer introduces into the Service or that are generated for it through use, including call data; call data: all data of a call that RR42 or a subcontractor engaged by RR42 stores beyond the transient processing of the audio signal, in particular text transcript, handover summary, structured requests, call metadata (in particular telephone numbers, time, duration, status) as well as audio recordings and voice messages, irrespective of the occasion, the telephony route and whose system, where such data are generated or stored contrary to A § 12 para. 5. The obligations to provide information, to export, to release and to erase under A § 26, under Part B and under Annex B1 cover call data irrespective of whether they are stored in systems of RR42 or in systems of a subcontractor; RR42 shall evidence the erasure in text form at the Customer's request.
- Knowledge base: the content maintained by the Customer (opening hours, address, reachability, standard notices, approved answer content) from which the Service answers questions.
- Configuration: the settings of the Service made or approved by the Customer in the customer account, including forwarding destination, opening and on-call hours, forwarding approval outside opening hours, greeting text, knowledge base, voice and notification address.
- Safeguards: the rules and functions provided by RR42 that keep the Service within its intended purpose, in particular the identification as an AI assistant at the start of the call, the binding of answers to the knowledge base, the subject-matter limit on answers, the handover to the forwarding destination and the safety notice on emergency indications; system prompt: the control instruction for the language model specified by RR42, which contains these rules.
- Emergency flag: the flagging of a handover by the language model described in A § 6 para. 2.
- Annexes: the documents listed in the Annex index, A5 (Acceptable Use Policy) and B1 (Data Processing Agreement with annexes), in each case in the version applicable under A § 3 para. 2. The former Annexes A2 (service description), A3 (service level agreement) and A4 (cooperation and operator obligations) have been incorporated into Part A; there is no order form as an Annex.
- Subcontractors: third parties engaged by RR42 to provide the Service, in particular providers for hosting, language model, speech recognition, speech synthesis, telephony, payment, authentication and e-mail dispatch; the list relevant for data protection is Annex 3 to Annex B1.
- Text form: text form within the meaning of section 126b BGB; business day: Monday to Friday except statutory public holidays in Lower Saxony; support hours: the time determined in A § 9 para. 2; all times refer to the Europe/Berlin time zone.
- Professional secrecy holders: Customers pursuant to B § 1 para. 1.
- AI system, provider, deployer: the terms of Art. 3 nos. 1, 3 and 4 of Regulation (EU) 2024/1689 ("AI Act (KI-VO)") as amended by Regulation (EU) 2026/1744.
- Contract year: the period of twelve months from the subscription start and each following period of twelve months; a trial period preceding the subscription start is attributed to the first contract year. If no subscription comes into being, the first contract year is the period of twelve months from the start of the trial period under C § 3 para. 1 sentence 5 or, in the case of an order in text form, under A § 4 para. 5; C § 3 para. 2 remains unaffected (A § 20 para. 3 letter a).
- Contract contact: the person, together with e-mail address, designated by the Customer in the order or in the customer account for contract and billing matters; if the Customer does not designate such a person, the notification address stored in the customer account takes its place, and if there is none either, the e-mail address of the holder of the customer account (A § 30 para. 3 sentence 1). This definition applies to all provisions of these AGB and their Annexes in which the contract contact is mentioned, in particular to A § 4 para. 3, A § 8 para. 6, A § 14 para. 7, A § 23 para. 4, A § 25 para. 1 and para. 3, A § 26 para. 2 and para. 4, A § 27 para. 3, A § 30 para. 3 and para. 4, A § 32 para. 2, B § 7 para. 5, C § 6 para. 2 and C § 8 para. 2.
- Activation: the release by RR42 of the Service for answering calls for the Customer; it presupposes the assignment of the target number (A § 7 para. 1) and, for Customers under Part B, the conditions of B § 3 para. 1. The activation of the customer account (C § 1 para. 2) is not an activation within the meaning of these AGB; it is designated as such.
- Go-live: the point in time at which the Customer, following activation, first sets up the call diversion to the target number. RR42 notifies the Customer in text form of the point in time intended for go-live together with the activation. Declarations and notices that RR42 owes "before go-live" under these AGB are to be given at the latest with the activation; if such a notice is omitted, RR42 cannot hold against the Customer the circumstance about which it was to be informed.
- Start of performance: the day of the assignment of the target number (A § 4 para. 3 sentence 5), unless a later day is agreed; this applies to both ordering routes.
- Premium voice: a particularly authentic-sounding voice output designated as such in the plan overview, for which the plan may provide a higher price per additional minute (A § 16 para. 7); standard voice: every other voice that can be selected in the customer account. Which providers RR42 uses for voice output is set out in Annex 3 to Annex B1.
- Research function ("Evidenz-Check"): the function of the customer account described in A § 5 para. 14; query: every research triggered by the Customer, including the follow-up questions asked in connection with it.
A § 3 Components of the Contract, Order of Precedence, Version, Customer's Terms
(1) The components of the contract are, in this order of precedence:
a) arrangements individually negotiated between the parties, irrespective of their form (section 305b BGB); at the Customer's request RR42 shall record such arrangements in text form without delay, without their validity depending on this,
b) the order and the information displayed to the Customer in the ordering flow immediately before conclusion of the contract (A § 5 para. 9 sentence 2), but only with regard to plan, quantities, prices, base fee, included allowance, price per additional minute, start of performance, term and terminability, duration of the trial period, agreed availability, response times, number of simultaneously conducted calls, contact persons and provisions expressly designated as deviations,
c) the Data Processing Agreement (Annex B1) with its annexes for all data protection questions and, in the case of Part B, the declaration of undertaking (Annex 5 to Annex B1) for confidentiality,
d) Part B of these AGB,
e) Part C of these AGB,
f) Part A of these AGB,
g) the Acceptable Use Policy (Annex A5).
Service description, service quality and cooperation and operator obligations are regulated in Part A (A § 5 paras. 12 to 14, A § 8, A § 9, A § 11); there are no separate Annexes for these.
In the event of conflicts, the higher-ranking document prevails. A provision of a lower-ranking document does not prevail merely because it is more specific. This order of precedence applies subject to those provisions of these AGB that expressly designate a deviation from it; a deviation takes precedence over the order of precedence under sentence 1 only if it is expressly designated at its place as a deviation from this order of precedence or is mentioned in sentence 6. Such deviations are contained in A § 5 para. 9 sentence 2, A § 12 para. 2 sentences 2 and 4, A § 12 para. 6 sentence 6, A § 17 para. 3 sentence 6, A § 20 para. 6 sentence 4, A § 26 para. 2 sentence 4 and para. 3 sentence 1, A § 29 para. 1 sentences 4 to 6, B § 1 para. 3 sentences 2 and 3, B § 11 para. 3 last sentence and B § 12 para. 1 sentence 4; this enumeration is exhaustive. Where such a deviation places the Customer in a worse position than the provision applicable under sentence 1, the order of precedence under sentence 1 remains in place. The precedence of the Data Processing Agreement (Annex B1) with its annexes and of the declaration of undertaking under letter c exists only to the extent that their provisions do not fall short of the commitments of these AGB; if they fall short of them, the provisions of these AGB apply, and RR42 cannot rely on the deviating version of the Annex (precedence of the more favourable provision). The express precedence provisions in A § 12 para. 2 sentence 4, A § 20 para. 6 sentence 4, A § 26 para. 2 sentence 4 and A § 26 para. 3 sentence 1 as well as in B § 1 para. 3 sentence 3 and B § 12 para. 1 sentence 4 are applications of sentence 8; their enumeration is not exhaustive, and sentence 8 applies in particular also to A § 12 para. 4 sentences 6 and 7, A § 13 para. 3 sentence 2, A § 14 para. 6 and A § 30 para. 1 sentence 4. Provisions of the General Data Protection Regulation (GDPR) and of Annex B1 that grant the Customer further-reaching rights or bind RR42 more strictly remain unaffected; the Data Processing Agreement retains its precedence to the extent that it implements mandatory requirements of Art. 28 para. 3 GDPR (DSGVO). For Annex A5 the same already follows from its rank under letter g. References in Annex A5 and Annex B1 to a Master Service Agreement refer to these AGB; further-reaching rights of evidence and audit are governed exclusively by A § 29 para. 1 and § 15 of Annex B1. This order of precedence applies exclusively to pre-formulated contract terms. The precedence of individual contractual arrangements under section 305b BGB and the non-incorporation of surprising clauses under section 305c para. 1 BGB remain unaffected; they are neither restricted nor made dependent on a particular form by this order of precedence or by formal requirements of these AGB. A § 30 para. 2 sentence 2 applies accordingly. A § 5 para. 9 sentences 2 and 3 remain unaffected and take precedence over this order of precedence; letter b and A § 5 para. 9 sentence 2 are applicable side by side, and in the event of discrepancies between them the information more favourable to the Customer applies.
(2) The version of these AGB and of the Annexes that applies is the one to which the Customer agreed on conclusion of the respective contract by clicking a box provided for that purpose and not pre-selected, or in text form. For the contract on the trial period, this is the version to which the Customer agreed in the set-up under C § 1 para. 3; for a paid subscription, the version to which it agreed in the order. RR42 identifies the applicable version in the confirmation under A § 4 para. 4 by version number, date and SHA-256 checksum and attaches the documents to it as printable and saveable files. The Annexes are incorporated in the version that RR42 has identified and transmitted to the Customer under sentence 3 and that can be retrieved, with version number, date and checksum, at the address named in sentence 9; the Annex index identifies the Annexes, not their version. The Annexes apply to all product variants of the Service; RR42 makes available to the Customer the version prepared for its product variant, in which product-specific designations such as "PharmaPhone" or "pharmacy" are replaced by the designation applicable to it. References in an Annex to a "Master Service Agreement", to an "AI Safety & Controls Specification" or to documents that are not listed in the Annex index have no effect; the corresponding provisions of these AGB take their place. References in an Annex to an order form refer to the order within the meaning of A § 2 no. 12; there is no order form as an Annex. If an Annex contains a provision that conflicts with a provision of these AGB, paragraph 1 applies. RR42 keeps the current version and all earlier versions of these AGB and their Annexes permanently available for retrieval, printing and saving at https://www.rr42.de/agb/archiv and in the customer account in the "Verträge" section, with version number, date and checksum; at the Customer's request RR42 sends the Customer the version applicable to it in text form. RR42 logs the agreement under C § 9. If RR42 cannot prove the Customer's agreement to a particular version, RR42 cannot rely on these AGB against the Customer; the statutory provisions then apply (section 306 para. 2 BGB).
(3) RR42 makes these AGB and the Annexes available to the Customer before the order is placed in full text and as a printable and saveable PDF file and sends them to the Customer again with the confirmation under A § 4.
(4) The Customer's general terms and conditions, in particular purchasing or procurement terms, do not become part of the contract unless RR42 expressly agrees to their application in text form. If the Customer transmits such terms with its order, RR42 shall expressly reject them before activation.
(5) For further orders by the same Customer (additional locations, telephone numbers, plans), RR42 shall submit the then-current version of these AGB for agreement with each order; A § 27 remains unaffected.
(6) For contracts concluded in text form pursuant to A § 4 para. 3, C § 7 and C § 9 paras. 1, 2 and 5 apply accordingly; the order confirmed in text form takes the place of the agreement under C § 1 para. 3 and C § 4 para. 1, and the retention of the order together with the transmitted versions of these AGB and the Annexes, with version number, date and checksum, takes the place of the logging in the customer account. C § 9 para. 3 and para. 4 do not apply to these contracts.
A § 4 Conclusion of the Contract
(1) Presentations of the Service on websites, in price lists, presentations or in the customer account are not an offer to conclude a contract but an invitation to the Customer to submit an offer. Whether and to what extent such presentations determine the agreed quality of the Service is governed exclusively by A § 5 para. 9; this paragraph does not restrict A § 5 para. 9. Placement on a waiting list and the activation of a customer account do not yet create a contract; they are likewise not an offer by RR42.
(2) For the order via the customer account, C § 4 applies.
(3) In addition to the order via the customer account, which constitutes the standard route (paragraph 2, C § 4), the Customer may submit a binding offer in text form by transmitting to RR42 an order confirmed by it that states the plan, base fee, included allowance, price per additional minute and the designation of the applicable version of these AGB and the Annexes with version number and date; there is no separate order form as an Annex. RR42 accepts the offer within 14 calendar days of receipt, either by countersigning in text form or by activating the ordered scope of services for the Customer with confirmation in text form to the contract contact named in the order. Until the end of this period the Customer is bound by its offer; thereafter it lapses without any declaration being required. The decisive point in time for the conclusion of the contract is the receipt of the acceptance by the Customer. RR42 shall assign the target number (A § 7 para. 1) to the Customer within five business days after conclusion of the contract and shall notify it of the country and area code in text form; the start of performance is the day of assignment, unless a later day is agreed in the order. If RR42 does not assign the target number within twenty business days after conclusion of the contract, the Customer may terminate the contract in text form without observing a notice period; RR42 shall refund fees already paid without delay. If the confirmation, contrary to paragraph 4, does not state the version of these AGB and the Annexes, A § 3 para. 2 last sentence applies.
(4) RR42 shall confirm to the Customer in text form without delay the conclusion of the contract on the trial period (paragraph 5) and the conclusion of a subscription (paragraph 3, C § 4). The confirmation identifies the subject matter of the contract, in the case of a subscription additionally the ordered plan and the start of performance, and the applicable version of these AGB and the Annexes with version number and date; the documents are attached to it as printable and saveable files.
(5) The contract on the trial period is a separate contractual relationship that comes into being under C § 3 and ends automatically. If the trial period is agreed in the order under paragraph 3, C § 3 para. 1 sentences 3 to 6 and paragraphs 2 to 6 apply accordingly, with the proviso that the conclusion of the contract under paragraph 3 takes the place of the completion of the set-up under C § 1 para. 3 and that the trial period begins with the assignment of the target number under paragraph 3 sentence 5; in this case, too, there is no transition into a subscription. A paid subscription comes into being only through an order under paragraph 3 or C § 4.
(6) The contract language is German.
A § 5 Subject Matter of Performance and Quality of the Service
(1) RR42 makes the Service available to the Customer in the ordered product variant for the contract term as a service provided over the internet. The Service answers calls that the Customer diverts from its own telephone line to the target number, conducts an automated conversation with callers, answers questions from the knowledge base, captures matters in structured form and can transfer calls to the forwarding destination. The Customer manages the Service via the customer account.
(2) Scope, functions, interfaces, technical dependencies and the services not owed result from paragraphs 12 to 14. The ordered plan, the number of locations and target numbers and agreed deviations result from the order.
(3) Owed in particular are: the answering of incoming calls diverted to the target number within the availability agreed under A § 8; the identification as an AI assistant at the start of the automated conversation; the answering of questions exclusively on the basis of the knowledge base and the standard content provided by RR42; the structured capture of matters and their provision in the customer account and to the notification address; the forwarding to the forwarding destination according to the configuration; the output of the safety notice on recognised emergency indications under A § 6; the operation of the other safeguards described in paragraph 12.
(4) The Service generates speech and text outputs using machine learning methods that operate probabilistically. Individual outputs can therefore be incomplete, misleading or factually incorrect, even if RR42 complies with the safeguards. Freedom from error of every individual output is not owed; RR42 does not promise that the Service understands every statement, every name or every medicine name correctly. Whether an erroneous output constitutes a defect is governed by the statutory provisions and the quality agreed under paragraph 9; sentences 2 and 3 do not restrict the statutory concept of a defect and do not define it exhaustively. A defect exists in any event if the erroneous output is due to RR42 not having complied with the safeguards described in paragraph 3 and in paragraph 12, if the Service, contrary to paragraph 3, gives answers outside the knowledge base or outside the subject-matter limit on answers, or if erroneous outputs occur so frequently or so seriously that the contractual use of the Service is impaired for the Customer to more than an insignificant extent. The Customer's statutory rights in respect of defects under A § 15 remain otherwise unaffected; the burden of proof for the existence of a defect is governed by the law. At the Customer's request, RR42 shall provide the Customer in text form with the evaluations of recognition and handover errors from its calls that are available to RR42. RR42's liability is governed by A § 20; A § 20 para. 1 remains unaffected in any event.
(5) Not subject matter of performance, and incapable of becoming so even by separate agreement, are: the function of an emergency call system (A § 6 para. 1) and a recording function that makes audio recordings of calls accessible to the Customer; RR42 does not offer these functions and cannot activate them even at the Customer's request. The exclusion under sentence 1 concerns the recording function for the Customer (A § 12 para. 5 sentences 1 and 2). Whether audio recordings may nevertheless arise at the telephony provider is governed conclusively by A § 12 para. 5 sentences 3 to 5, according to which RR42 does not set up or provide the Service over such telephony routes; sentence 1 contains no deviating statement of quality in this respect. Likewise not subject matter of performance, unless expressly agreed in text form, are: the porting or provision of the Customer's telephone numbers (A § 7 para. 6); medical, pharmaceutical, legal or tax information or advice; individual integrations, data migration and on-site services. The Service neither states nor confirms stock levels, delivery availability, delivery times or prices; it records enquiries about these as matters and makes them available to the Customer for answering by its staff (Annex A5 no. 7). The reproduction of general operating procedures of the Customer's business that the Customer has approved, as a general rule, remains unaffected (Annex A5 no. 7 paragraph 4; for professional secrecy holders B § 6 para. 5). Outbound calls as well as information on stock, availability or prices are owed only once they have been technically implemented, in the case of information on stock, availability and prices additionally connected to a suitable data source, assessed in terms of data protection and subject matter, taken into account in the safeguard and escalation rules and released by an express contract amendment in text form; a mere technical possibility or a configuration by the Customer does not replace the release (Annex A5 no. 2 and no. 7).
(6) The Service handles several calls simultaneously per Customer. Per target number, RR42 provides at least the number of simultaneously conducted calls shown in the plan overview (A § 2 no. 11) and in the order summary; a higher number may be agreed in the order. If no number is shown, the number of simultaneously conducted calls is not limited. If the number of simultaneously incoming calls exceeds the number provided in this way, the Service puts the excess calls straight through to the forwarding destination, to the extent that the telephony route used for the Customer permits this; otherwise they are not answered, their duration is not recorded and not charged, and the periods in which the Service does not answer calls for this reason are countable downtime minutes within the meaning of A § 8 para. 1 sentence 4, without the threshold of five consecutive minutes being relevant. Sentence 4 does not apply to calls that are treated as busy because of the high-load mode activated by the Customer under sentence 9. During load peaks at the telecommunications and AI providers used by RR42, calls may be answered with delay or put through to the forwarding destination; sentence 6 describes a technical possibility and limits neither the availability agreed under A § 8 para. 1 nor the Customer's rights under A § 15 and A § 20. RR42 is responsible for the fault of the subcontractors engaged by RR42 pursuant to section 278 sentence 1 BGB; A § 8 para. 1 sentence 9 remains unaffected. The forwarding to the forwarding destination of a call flagged as an emergency under A § 6 para. 2 is not deferred either because of capacity utilisation or because of the high-load mode. The Customer can activate in the customer account a high-load mode in which forwardings, with the exception of emergency flags, are treated as busy. The statement under sentence 2 is understood per target number; if several target numbers have been ordered for the Customer, it applies to each of them (A § 7 para. 1, A § 16 para. 9).
(7) Statements of the Service to callers, in particular the taking of an order, a prescription request, an appointment request or a callback request, are the capture of a matter for the Customer. They do not constitute a commitment by RR42 to callers; whether and how a matter is dealt with is decided by the Customer.
(8) During the contract term RR42 keeps the Service in a condition conforming to the contract (section 535 para. 1 sentence 2 BGB) and installs security updates in the course of operation.
(9) Scope and quality of the performance result from the order and these AGB. Information that RR42 provides in the ordering flow immediately before conclusion of the contract (in particular plan overview, included allowance, price per additional minute, duration of the trial period, terminability) takes precedence over these AGB. Product descriptions on websites and in advertising materials describe typical uses; they become contract content to the extent that they are confirmed in the order or in text form as a feature of the performance, or the Customer could expect the quality of the Service according to them and RR42 has not corrected them in an equivalent manner before conclusion of the contract; this sentence is an express deviation from the order of precedence under A § 3 para. 1 sentence 1 and takes precedence over it.
(10) RR42's obligation under A § 14 para. 5 and under Art. 32 para. 1 letter c GDPR to be able to restore the availability of the personal data quickly after a physical or technical incident remains unaffected by this paragraph. Beyond that, RR42 owes neither a particular recovery point nor a particular recovery time nor a particular frequency of data backup, as long as this has not been agreed in text form; the values mentioned in A § 8 para. 9 are target values ("targeted recovery point") and not an agreed quality. RR42 does not owe archiving of Customer data beyond the erasure periods of A § 12 para. 6 or a backup of data in the Customer's systems. If RR42 operates no backup procedure for a component, it shall point this out to the Customer before the Customer places its order, separately and prominently in text form, shall name the component concerned and shall, until the procedure is set up, make the provision under A § 26 para. 1 sentence 3 available at any time, without notice period and without quantity limit; if the notice is omitted, the value in A § 8 para. 9 applies as the agreed quality. The provisions of A § 26 para. 3 on backup copies apply to the extent that backup copies exist. The Customer's rights under A § 15, A § 20 and A § 26 para. 1 remain unaffected.
(11) Before the Customer places its order, RR42 shall provide the Customer, prominently and in text form, with a list of the deviations known to it between the quality of the Service owed under these AGB and the Annexes and the quality actually provided (Annex "Known Limitations"); it keeps the list up to date in the customer account and informs the Customer in text form without delay of every newly added deviation. If the list is not provided or is incomplete at the time of conclusion of the contract, RR42 cannot rely on A § 15 para. 4 sentence 1; the Customer may terminate the contract without observing a notice period within four weeks of becoming aware of the undisclosed deviation, and fees paid in advance shall be refunded pro rata for the period after the end of the contract. Section 536d BGB, section 123 BGB and the Customer's statutory claims on account of incorrect or omitted pre-contractual information remain unaffected. The individual duties to give notice and to inform in A § 5 para. 10 sentence 4, A § 12 para. 5, A § 12 para. 6 last sentence, B § 2 para. 3, B § 2 para. 6 sentence 3 and B § 12 para. 3 continue to exist alongside; the deviations designated there are at the same time to be included in the list under sentence 1.
(12) The Service consists of telephony access (answering and audio transport of incoming calls over the telephony route used for the Customer), speech processing (speech recognition, dialogue model including the tools provided by RR42, speech synthesis), data storage (configuration, call records, captured requests, billing records) and the customer account. Core functions are the answering of calls and conduct of the conversation, the structured capture of matters and the forwarding to the forwarding destination. The functional scope further includes: the greeting with the standard text or a text set by the Customer, including the identification as an AI assistant and the data protection notice; the answering of questions on the basis of the stored opening hours, address data and the knowledge base; the interruption of the output by the caller, to the extent that the telephony route used supports this; a configurable maximum duration of a call with defined closing behaviour; a test call in the customer account without a telephone connection; the forwarding at the request of the caller, on the occasions determined in the dialogue specification, for priority numbers and, if the Customer has approved this, for all calls; the filing of captured matters in the customer account with processing status, the notification to the stored address and, as configured, the triggering of a webhook of the Customer; the call record under A § 26 para. 1. At most one successful capture of a matter is provided for per call. The Service also evaluates the forwarding behaviour per calling telephone number: if a call from the same telephone number has been handed over to the Customer's staff three times within 90 calendar days, the Service no longer offers this telephone number its own capture of the matter and proposes to the Customer the inclusion in the priority list; details, limits and the data kept in this connection result from B § 10 para. 5 and B § 12 para. 1, which apply accordingly to all Customers. The Service provides the Customer with an authenticated interface for account, call, request, usage, team and settings functions, the retrieval of the call record as a PDF file and in machine-readable form, the retrieval of the Customer data as a whole and of the same extract filtered to a designated data subject together with a field description, as well as status and monitoring endpoints; paragraph 13 and A § 26 para. 7 remain unaffected. Via a read access that the Customer sets up in the settings of its customer account, it can connect its own AI assistance system to this interface; access is granted only after login and is limited to the data for which the logging-in user is authorised in the customer account. There is no unauthenticated access to call data. One telephony route is active per Customer; RR42 shall tell the Customer which one it is in text form on request (A § 7). Application and data storage are operated as a service over the internet; development, test and production environments are separated from one another. Subcontractors, places of processing and data residency result from Annex B1 with its annexes.
(13) Beyond paragraph 5, the following are not owed unless expressly agreed in text form: a binding verification of the validity of prescriptions against the systems of the payers, the dispensing of medicines and a connection to practice management, merchandise management or pharmacy systems; the error-free recognition of all medicine names, proper names and dialect variants (paragraph 4); an unlimited number of simultaneously conducted calls beyond the number provided under paragraph 6; a connection to the Customer's data sources for status and availability information; as well as internal tools of RR42, in particular its cost evaluation, which are not part of the performance to the Customer.
(14) If the ordered plan includes the research function ("Evidenz-Check"), RR42 provides the Customer in the customer account with a function with which its staff can ask a professional question; the Service formulates a search query from it, searches a database of published scientific literature and produces an answer in which each statement is attributed to a source. The answer reproduces sources; it is not a professional assessment of the individual case and does not replace the review and decision by the Customer's professionally authorised staff (paragraphs 4 and 5, B § 5). The Customer shall not enter into the research function any information that makes a calling or other person identifiable; RR42 points this out to it in the customer account. RR42 transmits to the literature search service exclusively the English-language search query formed from it; personal data are not transmitted there. Before transmission, the Service checks the question for direct information about a person — salutation with name, telephone number, e-mail address, longer digit sequences, bank details and full date — and rejects it instead of transmitting it; this check covers only such direct information and does not relieve the Customer of sentence 3. RR42 stores the question itself and the answer in the Union. Which providers RR42 uses for the formulation of the search query, for the literature search and for the production of the answer, and at which locations they process, is set out in Annex 3 to Annex B1. The number of queries included per billing period and the price per additional query result from the plan overview (A § 2 no. 11); billing is governed by A § 16 para. 4a and para. 5. For the storage of the queries and their results, A § 12 para. 6 applies.
A § 6 No emergency call system; conduct on indications of an emergency
(1) The Service is not an emergency call system and does not replace an emergency call. It does not establish a connection to emergency call answering points (112, 110), to the medical on-call service (116117) or to poison information centres, does not alert rescue or on-call services and cannot trigger calls. In acute danger, callers can at any time dial the emergency number themselves; the Customer's call diversion does not affect the callers' own telephone line.
(2) If the language model recognises, in the callers' statements, indications of an acute danger to body, life or mind, it flags the handover as an emergency (emergency flag). This flag has the effect that the transfer to the forwarding destination is initiated without asking for the name, without offering to capture the request itself and without deferral on account of high-load mode, and that, in the cases of paragraph 3 sentences 1 and 3, the Service names the bodies stated there; it has no further effects. It is not a medical assessment, not triage, not a ranking and not a prioritisation as against other callers; it may be absent or incorrect and does not trigger an emergency call or any alerting of third parties. The emergency flag is a documented processing operation within the meaning of the Data Processing Agreement; RR42 describes it in Annex 1 to Annex B1 and provides the Customer with the information it needs for its record of processing activities and for its data protection impact assessment. Statements in the Annexes, in Annex B1 and in other documents of RR42 to the effect that the Service does not assess or does not flag the urgency of a request are replaced by this paragraph; they do not give rise to any deviating agreement on quality and no deviating position as regards instructions.
(3) If the handover is flagged as an emergency (paragraph 2) and a transfer is nevertheless not possible because the Customer has not enabled any transfer for the relevant point in time, the Service names to callers the public body provided for the situation described (in the case of mental distress the Telefonseelsorge, in the case of a physical emergency the ambulance service 112, otherwise the medical on-call service 116117) and asks them to dial it themselves. It does not name any specific out-of-hours pharmacy, any poison information centre, any address and any further telephone number. If a handover flagged as an emergency does not come about for another reason, in particular because the forwarding destination is not reached, the person reached there declines to take over the call (A § 7 para. 5 sentence 6), no forwarding destination or no reachable forwarding destination is stored, or the connection used technically does not support a transfer, the Service nevertheless names to callers the public body provided for under sentence 1 and asks them to dial it themselves; only thereafter does it state that it cannot transfer the call, and captures the request. If the emergency flag is absent or a transfer does not come about for one of the reasons stated in sentence 3, the Service informs callers that it cannot transfer the call, points out to them, irrespective of the emergency flag and irrespective of the course of the call, that in an emergency they can themselves dial the emergency number 112 and, if the Customer operates a pharmacy, a medical practice or another establishment of medical or dental care, outside consultation hours the medical on-call service 116117, and captures the request; the naming of a specific body relating to the situation described under sentence 1 is not owed in this case. The naming under sentences 1 and 3 and the notice under sentence 4 presuppose that RR42 has made available to the Customer a version of the Service that supports the emergency flag or the output of this notice, respectively; before the go-live and thereafter without undue delay upon each change, RR42 notifies the Customer prominently in text form if and for which of these outputs this is not the case. In this case the Customer may terminate the contract without observing a notice period within four weeks of receipt of the notice under sentence 5; the remuneration for the current billing period is refunded pro rata temporis, and its rights under A § 15 and A § 20 remain unaffected. Sentences 1 to 5 give concrete form to no. 6 of Annex A5; the commitment made there to a pre-approved safety notice otherwise remains unaffected. Replaced are solely the naming, provided for in Annex A5, of a competent poison information centre, of a specific out-of-hours pharmacy, of an address or of a further telephone number, and the description there of an unconditional emergency notice, to the extent that it goes beyond sentences 1 to 4; the Service does not name such bodies (sentence 2). Paragraph 5 and A § 11 para. 7 remain unaffected.
(4) The Service is not intended to assess or classify emergency calls, to dispatch or prioritise emergency or rescue services, or to rank callers by urgency, severity or need for treatment. The Customer does not use the Service for such purposes (A § 11 para. 5; B § 11).
(5) Within its own sphere, the Customer bears responsibility for ensuring that callers can reach a person in emergencies. To this end it stores an actually reachable forwarding destination, decides on the transfer enablement outside its opening hours, keeps staff capacity available for taking calls during the enabled times, sets up a human follow-up process for handovers flagged as an emergency, and informs callers on its own channels that in emergencies the emergency number is to be dialled (A § 11 paras. 2, 3 and 7). It may not give callers any deviating impression. The responsibility of RR42 for the performance of the Service in accordance with the contract remains unaffected, in particular for the answering of calls within the scope of the availability agreed under A § 8, for the operation of the protective mechanisms including the functions under paragraphs 2 and 3, and for the execution of the configuration made by the Customer. For disadvantages resulting from RR42 having failed to render, or having failed to render in accordance with the contract, the services incumbent on it under sentence 4, RR42 remains responsible under A § 20 and A § 21 para. 1; this paragraph does not entail any further shifting of this responsibility to the Customer.
A § 7 Target number, call diversion, transferring the call, number portability
(1) At the start of performance, RR42 designates to the Customer, for each ordered location, a target number to which the Customer diverts the calls of its own telephone line; A § 16 para. 9 remains unaffected. The target number is a technical endpoint of RR42. No right of use of the Customer in it arises; it is not allocated to the Customer and does not pass to the Customer at the end of the contract. The Customer may not use the target number as its own telephone number, in particular may not publish it, enter it in directories, state it on business stationery, websites or profiles, or give it to callers as a contact number. There is no entitlement to a specific local area code, in particular to the Customer's local area code, because under the requirements of the Bundesnetzagentur (Federal Network Agency) local-network numbers may be allocated on a derived basis only where there is a connection to the local network; the target number therefore has no connection to the Customer's local network. A number from the German numbering space is not owed. If RR42 provides for the Customer a target number outside the German numbering space, RR42 draws the Customer's attention to this prominently and in text form before the Customer places its order, names the country and dialling code, and explains that the Customer's telecommunications provider may charge foreign-call charges of unspecified amount for the diversion, which the Customer bears under paragraph 3 sentence 3, and that, when the connection is handed over from abroad, the display of the callers' telephone number must be suppressed (section 120 para. 4 sentence 2 TKG (German Telecommunications Act)), so that the functions named in paragraph 3 sentence 5 do not apply. The assignment of such a target number requires the Customer's separate consent in text form. If the notice under sentence 7 or the consent under sentence 8 is omitted, the Customer may terminate the contract without observing a notice period within two weeks of becoming aware of the country and dialling code of the target number; RR42 refunds charges paid in advance proportionately for the time after the termination takes effect. In every case RR42 notifies the Customer in text form of the country and dialling code of the target number before the Customer sets up the call diversion.
(2) RR42 may change the target number if this is necessary for technical or regulatory reasons, in particular because of requirements of the Bundesnetzagentur, because of a change in the allocation requirements or because the number provider no longer provides the number, and the change is reasonable for the Customer having regard to the interests of both parties. A change solely for commercial reasons, in particular because of a change of number provider for cost reasons, requires the Customer's consent. RR42 announces the change in text form at least 30 calendar days in advance and states the reason, the country and dialling code of the new target number and the time at which it takes effect; if a shorter period is unavoidable because of a requirement of an authority or of a provider for which RR42 is not responsible, RR42 informs the Customer without undue delay and observes the longest possible lead time. Where possible, RR42 keeps the previous target number reachable in parallel for at least 14 days after the change takes effect. The Customer adjusts its call diversion by the time the change takes effect; RR42 reimburses, against proof, the direct charges of the Customer's telecommunications provider incurred by the Customer as a result, to the extent RR42 is responsible for the reason for the change. The Customer may terminate the contract without observing a notice period, with effect as of the time the change takes effect, until the change takes effect; RR42 points out this right in the announcement. If the change alters the country of the target number, paragraph 1 sentences 7 to 9 apply mutatis mutandis. More than one change per contract year is permissible only if RR42 is not responsible for it. If the announcement is omitted for reasons for which RR42 is responsible, RR42 is liable under A § 20 for damage incurred by the Customer from calls that go nowhere.
(3) The Customer itself sets up, manages and cancels the call diversion with its telecommunications provider. The Customer determines the type and times of the diversion (immediate, on busy, after a time, outside business hours). Charges that its provider levies for the diversion or for the diverted connections are borne by the Customer; RR42 points out that diversion to mobile or foreign numbers is charged separately by many providers. The Customer may divert only lines of which it is the holder or whose holder has consented. If the Customer's provider does not transmit the callers' telephone number or callers suppress it, functions based on that number (pre-filling of the callback number, priority and block lists, display of the caller's number when transferring the call) are not available or are available only to a limited extent.
(4) RR42 does not provide the Customer with a telephone line, does not allocate telephone numbers to it, does not enable outgoing calls and does not owe any transmission of signals over telecommunications networks. The connection between callers and the target number is established by the Customer's telecommunications provider and by the telecommunications providers commissioned by RR42. The performance of RR42 consists in the processing of the content of the call (speech recognition, dialogue management, speech output, capture and provision of the results); transferring the call under paragraph 5 is a non-independent component of this performance.
(5) The Service can transfer an ongoing call to exactly one forwarding destination. The forwarding destination must be a telephone number of the Customer or of a person commissioned by it and authorised to take the call; special-rate numbers (in particular directory enquiry, mass-traffic, premium-rate, short-code and emergency numbers) and lines that in turn divert to the Service are not permitted. From the start of the transfer, the duration of a transferred call is not recorded as use of the Service, is not counted against the included allowance and is not charged as an additional minute; the measurement under A § 16 para. 3 ends when the transfer begins. No separate connection charge is levied for transferring the call. RR42 endeavours to display the callers' telephone number to the forwarding destination, to the extent it was transmitted and the telecommunications providers involved technically support and legally permit this; a particular display of the number is not assured, and in particular the target number may be displayed to the forwarding destination instead of the callers' telephone number, or the display may be suppressed. If the Service does not reach the forwarding destination or the person reached there declines to take over the call, the Service informs callers of this and continues the call itself; it handles the call according to the approved configuration by capturing the request, taking down a request for a callback or ending the call with a notice, and does not end the connection without such a notice. Asking callers to leave a voice message is not part of the Service; there is no recording function for the Customer (A § 5 para. 5 sentences 1 and 2). Whether an audio recording may nevertheless arise at the telephony provider is governed exclusively by A § 12 para. 5 sentences 3 to 5; if an audio recording arises or is nevertheless stored, this is, under A § 12 para. 5 sentence 5, a defect of the Service and at the same time a security incident under A § 14. Before the go-live, RR42 notifies the Customer in text form whether, on the telephony route used for it, a request under sentence 7 is issued and an audio recording arises in doing so; for Customers to whom Part B applies, B § 12 para. 3 sentence 4 is added.
(6) The Customer retains its own telephone numbers with its telecommunications provider. RR42 does not take over any of the Customer's telephone numbers (no porting to RR42) and is neither the receiving nor the donor provider within the meaning of the Telecommunications Act. There is no entitlement to take the target number along to another provider. Statements in an order summary or in advertising materials that present number porting to RR42 as an orderable service are void; if the Customer has selected such a statement, RR42 notifies it of this in text form before accepting the order, and the Customer may withdraw its offer at no cost until receipt of the acceptance. The surrender of the Customer's data at the end of the contract is governed by A § 26; telephone numbers are not covered by it.
(7) If the Customer or a third party commissioned by it operates the telephony server (SIP/VoIP server) via which the calls are routed to the Service (hybrid operation), the line, telephone numbers, trunk, firewall, network connection, number transmission and the outgoing leg of the transfer are the responsibility of the Customer or the third party, respectively. In this case RR42 provides exclusively the voice AI and the interfaces under A § 5 para. 12. The Customer itself complies with the telecommunications provisions applicable to it, in particular on the transmission of telephone numbers. If RR42 selects the telephony provider or the operator of the telephony server, or deploys it itself, that provider or operator is a subcontractor and vicarious agent of RR42 within the meaning of section 278 BGB (German Civil Code); sentences 1 to 3 then do not apply, and RR42 remains responsible for its services under this contract. Before the start of performance and upon each change, RR42 notifies the Customer in text form to which operating variant its line is assigned.
(8) The classification of the Service under telecommunications law is governed by statute and not by this contract. If the Service or a part of it is a publicly available number-based interpersonal telecommunications service, the mandatory provisions of the Telecommunications Act in favour of the Customer apply, in particular section 71 para. 1 and para. 3 TKG, irrespective of whether an authority or a court has so determined; conflicting provisions of these AGB and their Annexes are to that extent not to be applied. If a competent authority finally and non-appealably, or a court with final and binding effect, determines such a classification, RR42 notifies the Customer without undue delay in text form of the determination and of the changes resulting from it; each party may terminate the contract within four weeks of receipt of this notification with one month's notice. In all other respects the contract remains unaffected. Provisions for the protection of telecommunications that apply to providers of telecommunications services are observed by the telecommunications providers involved in each case; the confidentiality of the contents of calls as between the Customer and RR42 is governed by A § 12, A § 14 and, for professional secrecy holders, by Part B. RR42 does not classify the Service as an interpersonal telecommunications service under section 3 no. 24 TKG, and therefore not as a number-based interpersonal telecommunications service under section 3 no. 37 TKG: the exchange of information takes place between callers and a machine, RR42 does not transmit signals (paragraph 4), and transferring the call under paragraph 5 is a minor ancillary function inseparably linked to the Service within the meaning of section 3 no. 24 last clause TKG, because it is not marketed or priced separately (paragraph 5 sentence 4), leads to exactly one forwarding destination determined by the Customer (paragraph 5 sentence 2), callers do not dial the target number (paragraph 1 sentence 4) and outgoing calls initiated by the Customer are excluded (paragraph 4 sentence 1). Irrespective of this classification, without acknowledging any legal obligation and regardless of the size of the Customer's business, RR42 contractually grants the Customer the protection of the provisions named in section 71 para. 3 TKG; RR42 does not require a waiver under section 71 para. 3 clause 2 TKG, and such a waiver cannot be declared by these AGB. This protection is provided by the plan overview (A § 2 no. 11) and A § 16 (section 52 paras. 1 to 3 TKG), by A § 4 and A § 5 paras. 9 and 11 (section 54 paras. 1 and 4, section 55 TKG), by A § 23 para. 2 and para. 5 sentence 3 (section 56 para. 1 TKG) and by A § 25 paras. 1 to 3 (section 61 paras. 4 to 6 TKG); in addition, in the threat under A § 25 para. 1 sentence 1, RR42 points out to the Customer the possibility of seeking judicial legal protection (section 61 para. 4 TKG). RR42 remedies faults in call answering without undue delay and free of charge (section 58 para. 1 TKG); if a complete failure of call answering lasts longer than two calendar days after receipt of the fault report, RR42 owes the Customer for each further day of complete failure compensation in the amount determined in section 58 para. 3 TKG, calculated from the base fee of one billing period, unless the Customer is responsible for the failure; the compensation is credited against claims under A § 15 para. 3 and A § 20. Section 58 para. 4, section 60 and section 71 para. 2 TKG come to nothing, because RR42 does not agree on-site customer service appointments, provides the Service independently of location and does not provide it in connection with tenancy or lease relationships; section 66 TKG comes to nothing, because RR42 does not market the Service as part of a package offer with further telecommunications services. The commitments in this paragraph do not establish any classification of the Service under telecommunications law.
(9) When the contract ends, the use of the target number ends; it reverts to RR42. The Customer cancels the call diversion by the end of the contract at the latest. Calls arriving at the target number after the end of the contract, after the end of the trial period or during a block are not answered (A § 25, A § 26, C § 8).
A § 8 Availability, maintenance, faults
(1) RR42 operates the components of the Service for which it is responsible (call answering and speech processing, customer account) in principle around the clock. The agreed quality is a monthly availability of each of these components of 99.5%. It is calculated as 100 × [1 − countable outage minutes / (total minutes of the calendar month − excluded minutes)]. Any period in which a component is completely unavailable for longer than five consecutive minutes is countable, including the first five minutes. Shorter outages are disregarded to the extent that their total duration in the calendar month does not exceed 30 minutes; beyond that they are counted at their full duration. The following alone are excluded: a) maintenance under paragraph 3 to the extent regulated there; b) impairments, to the extent and for as long as they are demonstrably caused by systems, networks, terminal devices, SIP trunks, telephone numbers, configurations or forwarding destinations for which the Customer or a third party commissioned by it is responsible; c) impairments, to the extent and for as long as they demonstrably result from absent, late or defective cooperation by the Customer under A § 11 or from changes made by the Customer or a third party commissioned by it without approval by RR42; d) force majeure under A § 22; e) times of a block justified under A § 25 para. 1 or para. 4 and times of a suspension or discontinuation of call answering justified under A § 25 para. 7 sentence 2, under B § 1 para. 2 sentence 4 or under C § 9 para. 5 sentence 2, also in conjunction with A § 3 para. 6, in each case only to the extent the Customer is responsible for the reason. There are no further exclusions. RR42 bears the burden of presentation and proof that an exclusion applies. The use of subcontractors by RR42 does not preclude an outage from being counted; RR42 bears the procurement risk in this respect (section 535 para. 1 sentence 2 BGB). The description of around-the-clock operation does not constitute a commitment to uninterrupted availability; A § 5 para. 9 remains unaffected.
(2) RR42 determines the availability of a component on the basis of its operating, platform and incident data, to the extent it operates a measurement procedure for that component; RR42 notifies the Customer in text form, before the go-live, upon each change and on request, for which components it operates a measurement procedure, on what basis the determination rests and what informative value it has, and the absence of a measurement procedure is not to the Customer's detriment. For each calendar month, RR42 prepares from this data an evaluation without personal reference and retains it for at least 24 months; the erasure periods of A § 12 para. 6 for the underlying call data remain unaffected. On the Customer's request, RR42 provides in text form the data available to it for the month concerned on outages, faults and maintenance, stating the basis on which they rest; the request should be made within 30 calendar days after the end of the month so that RR42 can have the data ready in a targeted manner. Failure to observe this period does not affect the Customer's rights on account of unavailability. If the Customer conclusively shows an unavailability on the basis of its own records (for example call logs of its telecommunications provider, time and duration of failed calls) and RR42 cannot refute it, the unavailability shown by the Customer is decisive.
(3) RR42 carries out scheduled maintenance in the standard maintenance window on Tuesdays from 02:00 to 04:00 (Europe/Berlin), whereby scheduled maintenance in the standard maintenance window and outside the window together may not exceed four hours per calendar month, and announces it at least 48 hours in advance, stating the time window, the components affected and the expected effects, to the notification address stored in the customer account. Scheduled maintenance outside the window is permissible only to the extent the maintenance cannot technically be carried out in the maintenance window; it requires a separate announcement with the same notice period, may not fall within the time from 07:00 to 20:00 on business days, and within the joint scope under sentence 1 may not exceed two hours per calendar month. An announced start may be postponed by up to two hours, without the announced duration being extended and provided that duration and effects remain reasonable for the Customer. Emergency maintenance to avert a specific security or stability risk is permissible at any time; RR42 informs the Customer in advance where possible, otherwise without undue delay afterwards, and states the reason and the duration. In the calculation under paragraph 1, maintenance times are disregarded in total up to four hours per calendar month; this scope is available jointly to scheduled maintenance in the standard maintenance window, scheduled maintenance outside the window and emergency maintenance, of which no more than two hours may be attributed to scheduled maintenance outside the window and no more than two hours to emergency maintenance; maintenance times going beyond this are countable outage minutes. Maintenance is refrained from during times that the Customer has notified to RR42 in text form as emergency, on-call or standby times, unless it is unpostponable in order to avert a specific security or stability risk; in that case RR42 informs the Customer without undue delay, stating the reason. On request, RR42 demonstrates to the Customer in text form, for each calendar month, the start, end, duration and reason of each maintenance; if it cannot furnish the proof for a month, the maintenance times claimed for that month are deemed countable outage minutes. Maintenance may not be used to fall below the agreed availability. Software updates without interruption of ongoing calls are not maintenance.
(4) The Customer reports faults via the support channel under A § 9 with the details stated in paragraph 8. RR42 handles faults according to the priorities and target times of A § 9 paras. 5 and 6.
(5) Service credits are not agreed unless expressly agreed in the order and quantified; in that case they apply in addition to the Customer's statutory rights and are credited against a claim for damages. The Customer's statutory rights on account of unavailability or other defects, in particular reduction in accordance with A § 15, damages in accordance with A § 20 and termination for good cause, remain unaffected. If RR42 achieves the availability of 99.5% agreed under paragraph 1 in the calendar month, this alone does not constitute a breach of the availability commitment; the Customer's rights on account of individual outages and faults remain in existence in this case too, to the extent the impairment of suitability is not insignificant (section 536 para. 1 sentence 3 BGB). If recurring outages impair the contractual use more than insignificantly, a defect exists irrespective of the computed availability. Individual faults below the threshold of paragraph 1 sentence 4 are additionally handled as a fault under paragraph 4. Double compensation of the same disadvantage is excluded. The reference period for the availability calculation is the calendar month; for the calculation of a reduction under A § 15 para. 3, the share of the base fee attributable to the countable outage minutes is converted, on a daily basis, to the billing period concerned (A § 16 para. 2).
(6) RR42 informs the Customer of every fault known to it that wholly or partly prevents the answering of calls for the Customer, without undue delay after becoming aware of it, in text form to the notification address and, if stored, to the contract contact; the notification states the start, the functions affected, the status of remediation and the notice that the Customer may cancel the call diversion for the duration of the fault. RR42 communicates the remediation in the same manner. RR42 notifies the Customer in text form, before the go-live and upon each change, whether and by which route calls arriving at the target number can be put through directly to the forwarding destination in the event of a fault in call answering; if such a fallback route is available for the telephony route used, RR42 uses it. For the duration of a complete failure of call answering, the base fee lapses pro rata temporis, without any declaration by the Customer being required (section 536 para. 1 BGB); paragraph 5, A § 15 para. 3 and A § 20 remain unaffected. If RR42 breaches an obligation under sentences 1 to 3, it cannot hold a call diversion that remains in place against the Customer as contributory fault (section 254 BGB). The obligations under this paragraph exist irrespective of the support time under A § 9 para. 2 and irrespective of whether RR42 operates a monitoring procedure for the component concerned.
(7) The subject of the availability under paragraph 1 is call answering together with the start of speech processing, as well as the reachability of and login to the customer account; paragraph 2 sentence 1 remains unaffected. Not measured are the quality of an individual call, the substantive quality of an output of the Service, the content maintained by the Customer and the reachability of the forwarding destination; A § 5 paras. 3 and 4, A § 11 and A § 15 apply to them. A documented substitute or restricted operation counts as available only if the core functions under A § 5 para. 12 sentence 2 continue to be provided.
(8) The Customer's fault report should contain: its designation, the location affected and a reachable contact person; the time, the telephone number affected and the function affected; a description of the effects and the approximate number of calls affected; where available, the call identifier, the error message and the steps to reproduce the error; and indications of preceding changes to the Customer's telephony, network or systems. If details or access required for finding the cause or for restoration are missing, A § 11 para. 9 sentence 1 applies.
(9) For stored call and request data, RR42 aims for a recovery point of at most 24 hours. Zero data loss is not promised; A § 5 para. 10 remains unaffected.
A § 9 Support
(1) RR42 supports the Customer in the event of faults and questions on the use of the Service (support). Support comprises the receipt, classification and handling of fault reports and the answering of application questions on the customer account and on the configuration. Without separate remuneration, support also includes those settings and operations that the Customer cannot make itself in the customer account, in particular the assignment, change and return of the target number, the change of the telephony provider, the change of plan, and erasures and restrictions of processing on the Customer's instruction; RR42 carries them out within a reasonable period, and in the case of settings necessary for operation within two business days. Not part of support are training, the maintenance of the knowledge base, legal, medical, pharmaceutical or tax information, and assistance with the Customer's systems; RR42 may provide such services under a separate agreement.
(2) The support channel is the e-mail address info@rr42.de or a channel named in the order. Human support is available on business days from 09:00 to 17:00 (Europe/Berlin) (support time). Solely for the calculation of the response and recovery targets under paragraph 3, fault reports received outside the support time are deemed received at the start of the next support time; the receipt of legally operative declarations by the Customer, in particular notices of defects, setting of deadlines, reminders, objections, reports under A § 14 para. 6 and terminations, is governed by the statutory provisions (section 130 BGB). RR42 also monitors technical operation in an automated manner outside the support time, to the extent it operates a monitoring procedure for the component concerned; RR42 notifies the Customer in text form, before the go-live and on request, which components are covered. Automated monitoring does not constitute a commitment that an outage outside the support time will be detected or remedied. The obligations to inform and to provide a fallback under A § 8 para. 6 exist irrespective of the support time and irrespective of whether RR42 operates a monitoring procedure for the component concerned. The availability agreed under A § 8 para. 1 remains owed irrespective of whether RR42 has noticed an outage. A human on-call service outside the support time is owed only if expressly agreed in the order.
(3) Priorities, response times and recovery targets follow from paragraphs 5 and 6. The response time is the period within which RR42 begins handling a fault report and gives the Customer a first qualified response on classification and further procedure; it runs exclusively within the support time and is binding. Recovery targets are target values; a particular time to remedy a fault is not owed. RR42 makes the classification according to the criteria stated in paragraph 5 and at its reasonable discretion (section 315 para. 1 BGB) and gives the Customer its reasons in text form on request. If the Customer, stating the operational effects, requests a reassessment, RR42 decides on this within the current support time, otherwise within the next. If a classification proves incorrect, the periods of the correct priority apply retroactively from receipt of the report. A complete failure of call answering for the Customer is always priority P1. Escalations are governed by paragraph 7.
(4) If a “prioritised support” or “premium support” is shown in the plan overview, in the order flow or in the order, this comprises at least that RR42 handles reports of this Customer, at equal priority, ahead of reports of other customers and escalates them directly to the competent internal unit. RR42 determines which person takes over the handling; it does not owe a contact person named by name. Further response or recovery times and other additional support services apply to the extent shown in the plan overview, the order flow or the order; A § 5 para. 9 sentence 2 remains unaffected. If there is no such information, sentence 1 applies and otherwise paragraph 3.
(5) Faults are classified into four priorities. P1 (critical): complete failure of call answering for at least one location of the Customer, or a security incident with a specific threat to confidentiality, integrity or availability; a security incident is additionally dealt with under A § 14. P2 (high): an essential function of productive operation is significantly impaired, numerous calls are affected and no reasonable workaround exists. P3 (normal): a partial function is impaired, individual calls are affected or a reasonable workaround exists. P4 (low): general enquiry, question about the documentation, purely cosmetic error or request for change without impairment of operation.
(6) The following response times and recovery targets apply:
| Priority | Response time | Recovery target |
|---|---|---|
| P1 | at most 4 support hours | at most 24 hours from the start of the period |
| P2 | at most 1 business day | at most 3 business days |
| P3 | at most 2 business days | at most 10 business days |
| P4 | at most 5 business days | by agreement; no fixed target |
A support hour is a clock hour within the support time under paragraph 2 sentence 2. A business day is Monday to Friday except statutory public holidays in Lower Saxony, time zone Europe/Berlin. The response time is binding (paragraph 3 sentence 2). Recovery targets are target values; they end with the restoration of essential operation or the provision of a reasonable workaround, and the final remedy of the cause may take place later.
(7) If a report of priority P1 or P2 remains without a qualified response beyond the response time, the Customer may, via the support channel, stating the case and with the subject “ESKALATION” (escalation), demand that the management of RR42 deal with it. RR42 confirms the escalation within the current support time, otherwise within the next, and names a contact person. Irrespective of the Customer's demand, RR42 involves the management in the case of a fault of priority P1 without foreseeable restoration, in the case of a security incident with significant risk and in the case of repeated outages with the same cause.
A § 10 Changes to the Service; beta functions
(1) RR42 may change the Service to the extent this is necessary (a) to comply with statutory or official requirements, in particular of data protection, telecommunications and AI law, (b) to avert or remedy security risks, (c) because a telecommunications, language model, speech recognition or speech synthesis provider used by RR42 ceases to exist, changes or is replaced, or (d) to adapt to the state of the art of the language models, speech recognition and speech synthesis used, and the change is reasonable for the Customer having regard to the interests of RR42. A change is reasonable only if the core functions described in A § 5 para. 12 sentence 2 (call answering and dialogue, structured capture of requests, transfer to the forwarding destination) are retained, the protective mechanisms are not weakened and the relationship between performance and remuneration is not shifted to the Customer's detriment.
(2) RR42 announces to the Customer in text form, at least six weeks before they take effect, changes that cause agreed functions to lapse, restrict them substantially or significantly increase the risk profile of the Service for the Customer. Urgent changes under paragraph 1 letters a and b may be made at shorter notice; RR42 informs the Customer without undue delay, stating the reason. A change of language model, speech recognition or speech synthesis provider is always announced at least 30 calendar days in advance and is additionally governed by § 11 of the Data Processing Agreement (Annex B1); the rights of objection regulated there remain unaffected.
(3) In the event of a change that RR42 has announced under paragraph 2, or has made under paragraph 2 sentence 2 at shorter notice, the Customer may terminate the contract in text form within four weeks of receipt of the announcement or of the subsequent information. At the Customer's choice, the termination takes effect at the time the change takes effect or at the end of the current billing period; if the change has already taken effect, the termination takes effect upon receipt. In every announcement and in every subsequent information, RR42 points out this right, the period and its start; if the notice is omitted, the period does not begin to run. RR42 refunds within 14 days remuneration already paid in advance for the time after the end of the contract. The Customer's rights on account of an impairment caused by the change (A § 15, A § 20) remain unaffected.
(4) Measures that do not reduce the agreed scope of performance and impair the Customer not at all or only insignificantly — in particular bug fixes, security updates, improvements in response quality and additional functions that do not take the place of existing functions — may be taken by RR42 at any time without announcement; paragraph 1 sentence 2 also applies to them. If a measure impairs the Customer more than insignificantly contrary to sentence 1, it is governed by paragraphs 1 to 3. For the language model, speech recognition and speech synthesis, RR42 uses exclusively models that it has tested and approved under its model governance procedure (model portfolio); RR42 notifies the Customer in text form on request, within ten business days, which providers and which models the portfolio comprises. A change of a model within the model portfolio is not a change within the meaning of paragraph 2 and is neither announced to the Customer individually nor justified individually, provided paragraph 1 sentence 2 is observed and the change does not measurably worsen the quality of speech recognition, of the answers and of the recognition of emergency indications; RR42 checks this before a model is admitted to the portfolio and before each change by means of a documented test procedure, and provides the Customer with its result in text form on request within ten business days. RR42 bears the burden of presentation and proof that a model change has not measurably worsened the quality stated in sentence 4. If a change leads to such a deterioration, it is governed by paragraphs 1 to 3. The admission of a provider to the model portfolio is a change within the meaning of paragraph 2 sentence 3 and is governed by that provision and by § 11 of Annex B1. If, within eight weeks of a model change, the Customer notifies a significant deterioration in the quality of answers or recognition, RR42 examines the connection and, at the Customer's request, restores the previous state to the extent this is possible and reasonable for it; the Customer's rights under A § 15 remain unaffected. § 11 of Annex B1 remains unaffected.
(5) Functions that RR42 labels to the Customer in the customer account, upon their first provision, as “Beta”, “Preview” or “Pilot” and whose trial character RR42 points out to the Customer in text form before first use are not part of the performance owed; they are provided free of charge for trial purposes, may be changed or discontinued, and may not be used for safety-critical or supply-critical processes. The label may not be applied to functions that are shown in the plan overview, in the order flow or in the order as a feature of the plan ordered; A § 5 para. 9 remains unaffected. If RR42 charges a separate fee for a labelled function, paragraphs 1 to 3 apply to it. RR42 announces, where possible two weeks in advance, the discontinuation of a labelled function that the Customer uses productively. A subsequent labelling of a function previously provided without labelling and without the notice under sentence 1 does not change its classification; its restriction or discontinuation is governed by paragraphs 1 to 3. This paragraph does not apply to functions that are not labelled. A § 15 and A § 20 remain unaffected also for labelled functions.
A § 11 Customer's cooperation; forwarding destination, availability, content, safeguards
(1) The Customer keeps the following up to date in the customer account: the forwarding destination, opening and standby hours including special and public-holiday arrangements, the knowledge base, the greeting text, the notification address, the invoicing details, and contact persons for subject-matter and technical questions. The Customer is responsible for the accuracy, currency and lawfulness of the content that it provides or approves. Where the Service reproduces the content provided or approved by the Customer accurately as to substance, the output is attributed to the Customer, as between the parties, as its own declaration to callers. RR42 bears the burden of presentation and proof that an output reproduces the Customer's content accurately as to substance; at the Customer's request, it shall for this purpose produce in text form within ten working days the transcript of the call concerned, the wording of the system prompt applicable at that time and the revision status of the tool set (A § 14 para. 1 sentences 3 and 4). Where an output departs in substance from the content provided by the Customer, reproduces it in abridged or distorted form, or supplements it with information that has not been stored, it is not a declaration of the Customer; in that respect A § 5 para. 4, A § 15 and A § 20 apply, and the Customer has no obligation to indemnify under A § 21 para. 2 letter a. RR42 is responsible for the standard content it provides, the system prompt, the tool set and the safeguards, to the extent that the Customer has not modified them.
(2) Before go-live and before setting up the call diversion, the Customer shall store an actually reachable telephone number of its business, or of a person it has engaged, as the forwarding destination and keep it up to date. An example number pre-filled by the system is not a forwarding destination; until the Customer has stored its own number, it may not divert its line to the Service.
(3) The Customer determines in the customer account whether transfers also take place outside the stored opening hours. This release is deactivated in the default state; RR42 shall draw the Customer's attention to this in text form during onboarding and before go-live and shall display the applicable setting permanently in the customer account. Without this release, the Service does not transfer calls outside opening hours; it then only takes down requests and, in the case of emergency indications under A § 6 para. 3, refers callers to public emergency call channels. The Customer shall ensure that this setting complies with its statutory and professional-law availability obligations (for pharmacies and practices: B § 7). If the notice under sentence 2 is not given, RR42 cannot hold the missing release against the Customer; in that case the Customer's rights under A § 15 and A § 20 and the indemnification under A § 21 para. 2 letter b depend on the share of causation and fault of both parties.
(4) During the times when transfers are released, the Customer shall keep staff capacity available to receive forwarded calls and shall promptly review, through authorised personnel, matters marked as emergencies or otherwise recognisable as critical, as well as captured requests. It does not owe constant monitoring of every call. If the Customer identifies an incorrect or potentially harmful output, it shall take the corrective and informational measures available to it towards callers and shall report systematic errors to RR42.
(5) The Customer shall use the Service only within its intended purpose under A § 5, A § 6 and Annex A5. Where its plan includes the research function (A § 5 para. 14), it shall ensure that its employees do not enter any information there that makes a caller or other person identifiable; transmission of personal data to the literature search service is neither intended nor permitted (A § 5 para. 14 sentence 3, Annex 3 to Annex B1). It may not remove, weaken or circumvent the safeguards. This applies in particular to the replacement or supplementing of the system prompt via the settings of the customer account insofar as this removes the identification as an AI assistant, the subject-matter response limit or the emergency rule, and to instructions that cause the Service to give diagnoses, dosage, therapy, stock or price information, to assess the urgency of a request, or to assess callers by personal characteristics. A breach of sentences 2 and 3 is a material breach of contract if it is capable of endangering callers or third parties or of exposing RR42 to liability or to action by an authority; in all other respects, termination for good cause and suspension are governed by A § 24 and A § 25. Where there are concrete indications of a breach, RR42 shall first call upon the Customer, setting a deadline, to remedy it. Only after unsuccessful expiry of the deadline or, in the case of a concrete danger to callers or to the security of the Service, immediately, may RR42 reset the contested setting to the default and temporarily restrict the function directly affected; the measure must be necessary and proportionate and must be lifted as soon as its reason has ceased to exist. Before any reset, RR42 shall back up the previous configuration and restore it to the Customer on request. RR42 shall inform the Customer in advance or, in the case of danger to callers, without undue delay afterwards, stating the reason, scope and expected duration. RR42 shall not make any further interventions in the Customer's configuration; if the measure was not justified, RR42 shall refund the remuneration attributable to the period, and the Customer's rights under A § 15 and A § 20 remain unaffected. For the measures under sentences 5 to 8, A § 25 para. 4 sentences 4 to 6, para. 5 and para. 6 apply mutatis mutandis; in particular, to the extent that the danger situation allows, RR42 shall give the Customer an opportunity to comment beforehand, shall decide in text form no later than ten working days later whether to lift the measure or to terminate under A § 24, the base fee shall lapse pro rata for the duration of a restriction unless it is based on a circumstance for which the Customer is responsible, the Customer may terminate the contract without notice period if the restriction lasts longer than five working days, and RR42 bears the burden of proof that the conditions of sentences 5 and 6 are met. The suspension of call acceptance is governed exclusively by A § 25.
(6) Where the Customer uses its own SIP/VoIP server, or one operated by a third party it has engaged (hybrid operation, A § 7 para. 7), it is responsible for its operation, connection, network and security, as well as for the reachability of the control interface from the cloud. The Customer shall protect its systems, end devices, accounts, access credentials and interfaces in line with the state of the art reasonable for it (paragraph 11).
(7) The Customer shall inform callers on its own channels (website, notice, announcement before the diversion, insofar as its telecommunications provider permits this) that an AI assistant takes calls, that call content is processed as a text transcript and that the emergency number is to be dialled in emergencies. RR42 provides text templates (A § 12 para. 7); their use and adaptation to the actual processing are the Customer's responsibility.
(8) The Customer shall review the configuration before go-live and after every change to opening hours, forwarding destination or transfer release by means of representative test calls, including transfer and emergency indication, and shall report material deviations to RR42. It shall report malfunctions, faults, unexpected call outputs and security incidents without undue delay via the support channel with the information specified in A § 8 para. 8. The further cooperation and operator obligations follow from paragraphs 10 to 12 and from Annex A5.
(9) If RR42 does not render a service, or does not render it on time or in full, because of missing, late or defective cooperation by the Customer, the time limits affected, in particular response and recovery targets, are suspended only for the duration and to the extent that the missing cooperation demonstrably prevents the service; RR42 shall point out the obstacle to the Customer as soon as it becomes apparent. If the Customer is prevented from exercising its right of use for a reason lying in its own person, it remains obliged to pay the remuneration (section 537 para. 1 sentence 1 BGB (German Civil Code)); this does not apply to circumstances that neither lie in its person nor are attributable to it. The Customer's rights under A § 15 remain unaffected. RR42 may charge additional effort caused to it by missing cooperation only after prior notice in text form and only at an hourly rate that was shown to the Customer before conclusion of the contract in the plan overview or in the order; if no hourly rate is shown, RR42 cannot charge additional effort separately. A breach of cooperation duties does not exclude RR42's liability to the extent that RR42 contributed to causing the damage.
(10) Before go-live, the Customer shall name to RR42 at least one contact person responsible for subject-matter matters and one for technical matters and shall keep the details up to date (paragraph 1 sentence 1). Before productive use and thereafter as occasion requires, it shall brief all employees who operate or configure the Service, take over calls or evaluate records, at least on the functioning, the intended use and the recognisable limits of the Service, on the permitted use cases and the prohibited subject-matter assessments, on the takeover, escalation and emergency procedures, on the data-protection-compliant handling of call, transcript and contact data, and on the reporting of malfunctions and security incidents. It shall document the time, participants and essential contents. RR42 provides an information sheet in text form for this purpose (B § 10 para. 2). The Customer does not owe constant monitoring of every call (paragraph 4 sentence 2).
(11) The Customer shall protect its systems, end devices, accounts, access credentials and interfaces in line with the state of the art reasonable for it. It shall use personal accounts, assign permissions only to the extent required, activate the multi-factor authentication offered for accesses with extended rights, keep access credentials secret, change them without undue delay on suspicion of compromise, and review permissions regularly and upon role changes and the departure of employees. It shall ensure that only authorised persons gain access to call data and settings.
(12) The Customer shall retain, in appropriate form, evidence of the contact persons named, of the briefing under paragraph 10, of releases granted, of the review under paragraph 8 sentence 1 and of the handling of matters marked as critical, and shall produce it to RR42 on reasoned request insofar as this is necessary to meet a contractual or statutory duty of proof. RR42 provides the Customer with the corresponding evidence from its sphere (A § 29 para. 4). Further rights of proof and audit are governed exclusively by A § 29 para. 1 and § 15 of Annex B1.
A § 12 Data protection; data processing agreement; processing of the call; information to callers
(1) Insofar as RR42 processes personal data on behalf of the Customer in providing the Service, the Customer is the controller and RR42 is the processor within the meaning of Art. 4 no. 7 and 8 GDPR (DSGVO). The parties shall conclude the Data Processing Agreement (Annex B1 in the version applicable under A § 3 para. 2), including its annexes, before processing begins. Without a validly concluded Data Processing Agreement, RR42 shall not assign a target number to the Customer and shall not accept calls for it; this also applies to the trial period.
(2) The Data Processing Agreement applies to all data protection questions, in particular instructions, confidentiality, technical and organisational measures, sub-processors, transfers to third countries, assistance with data subject rights and with the obligations under Art. 32 to 36 GDPR, notification of personal data breaches, evidence and audits, and erasure and return. In the event of conflicts between these AGB and the Data Processing Agreement, the Data Processing Agreement prevails in the data protection questions named in sentence 1, but only insofar as it does not fall short of the commitments in these AGB; the precedence of the more favourable provision under A § 3 para. 1 sentence 8 remains unaffected, and A § 3 para. 1 otherwise applies. These AGB do not extend RR42's rights in personal data beyond the Data Processing Agreement. Data protection audits by the Customer are governed by § 15 of Annex B1; for the costs of an audit, A § 29 para. 1 sentences 4 to 6 apply, which in this respect also take precedence over § 15 para. 4 of Annex B1. The Customer's claim to the information from the area for which RR42 is responsible that is necessary to meet its contractual, professional-law and regulatory duties of proof (A § 11 para. 12), as well as its claim to the information and documents necessary to pursue claims against RR42, remain unaffected; RR42 shall provide them in text form within 20 working days.
(3) The Customer determines the purposes and legal bases of the processing, fulfils the information obligations under Art. 13 and 14 GDPR towards callers and employees and carries out the data protection impact assessment required under Art. 35 GDPR; RR42 provides for this purpose the template named in § 14 para. 2 of Annex B1 and product-related information. The Customer shall not transmit to RR42 any data whose processing is not covered by the documented instruction.
(4) RR42 treats instructions of the Customer that materially change or extend the scope of services defined in A § 5 para. 12 and in the approved configuration as a request for a change of services (§ 5 para. 4 of Annex B1). Instructions that restrict, discontinue or end a processing are not a change of services; RR42 carries them out free of charge. The Customer's right to give instructions under Art. 28 para. 3 sentence 2 letter a GDPR and RR42's duty to notify under Art. 28 para. 3 sentence 3 GDPR remain unaffected. Before execution, RR42 shall indicate to the Customer in text form whether and in what amount remuneration on a time-and-effort basis is incurred for this; it is governed by the hourly rate shown to the Customer before conclusion of the contract in the plan overview or in the order and lapses if no hourly rate is shown. The Customer may then confirm, amend or withdraw the instruction. The performance of the obligations under the Data Processing Agreement is not separately remunerated. RR42 provides the following in particular without remuneration: assistance in responding to requests of data subjects under Art. 28 para. 3 sentence 2 letter e GDPR including access, rectification, erasure, restriction and data portability; assistance under Art. 28 para. 3 sentence 2 letter f GDPR with the obligations under Art. 32 to 36 GDPR, including the provision of the template and the product-related information for the data protection impact assessment; forwarding of data subject requests; erasure or restriction on instruction; the erasure confirmation; the data export under A § 26; the notification of incidents under A § 14; and cooperation in audits under § 15 of Annex B1. Remuneration on a time-and-effort basis comes into consideration only insofar as the Customer requests assistance that, by its nature and extent, manifestly goes beyond the cooperation required by law and RR42 has previously indicated this under sentence 2.
(5) The Service processes the audio signal of the automated call with the AI assistant exclusively transiently for speech recognition, dialogue management and speech output; RR42 neither generates nor stores an audio file from it and provides no playback facility. A recording function for the Customer is not part of the Service and cannot be activated by the Customer. RR42 does not set up or provide the Service over telephony routes on which sound recordings of call segments are made at the telephony provider; no recording is made either on handover to the forwarding destination or of messages left. At the Customer's request, RR42 shall demonstrate in text form that no sound recording is generated on the telephony route used for it. If a sound recording is nevertheless made or stored, this is a defect of the Service and at the same time a security incident under A § 14; RR42 shall erase the recording, including all copies held by subcontractors, without undue delay and shall demonstrate the erasure in text form, and the Customer may terminate the contract without notice period, the remuneration for the current billing period being refunded pro rata; further claims remain unaffected.
(6) To be distinguished from the audio signal are the transcript, handover summary, structured requests, call metadata, the caller profile together with the suggestions generated from it (A § 5 para. 12, B § 12 para. 1) and the queries of the research function together with their results. RR42 shall erase them no later than upon expiry of the following agreed maximum periods, counted from the end of the call and, for the research function, from the last follow-up question put on the query and, if no follow-up question was put, from the query: transcript and handover summary 30 calendar days, caller profile and suggestions generated from it 30 calendar days, structured request including callback number 90 calendar days, call metadata without reference to content 12 months, queries of the research function together with result 180 calendar days; RR42 shall erase production data no later than 30 calendar days after the end of the contract (§ 16 of Annex B1). For the transcript and handover summary and for the caller profile and the suggestions generated from it, the Customer may set a shorter period of at least seven calendar days in the customer account and may delete there individual research threads and individual entries of a thread; for the other stocks named in sentence 2, RR42 sets a shorter period on the Customer's instruction in text form, and for all stocks named in sentence 2 the Customer may at any time demand early erasure, which RR42 carries out within ten working days and confirms in text form. An extension of the periods under sentence 2 requires an agreement in text form. The Customer shall not use transcripts for performance, conduct or employee monitoring unrelated to the purpose (Annex A5 no. 8), shall observe section 26 BDSG (Federal Data Protection Act) and the participation rights of the employee representation body in this regard, and shall restrict access to authorised persons; its authority to have authorised personnel evaluate transcripts and captured requests to fulfil its obligations under A § 11 para. 4 and its professional-law and regulatory duties remains unaffected. For the period after the end of the contract, retention, retrieval, export and erasure are governed exclusively by A § 26 para. 1 to 3 and para. 6; the duration of the transition period and of the retrieval period provided for there, including their extension and suspension, and the subsequent erasure period take precedence over sentence 2, last clause, and § 16 of Annex B1. If, before expiry of a period under sentence 2, the Customer requests provision under A § 26 para. 1, the erasure of the data concerned is suspended until 14 calendar days after complete provision. RR42 shall point out to the Customer prominently in the customer account and in the confirmation under A § 4 para. 4 that transcripts and handover summaries are erased 30 calendar days and structured requests 90 calendar days after the call and must therefore be exported on an ongoing basis; if this notice is not given, RR42 cannot hold the erasure of this data against the Customer. The billing data kept separately under A § 16 para. 5 sentence 7 are not subject to sentence 2; the retention periods stated there apply to them, they contain no telephone numbers and no call or research content and are processed exclusively for the retention purpose. Their retention does not justify keeping the stocks named in sentence 1 beyond the periods of sentence 2.
(7) At the start of each call in which the Service interacts with callers, it outputs a short notice specified by RR42: the identification as an AI assistant, the indication that the call is transcribed and stored for handling by the Customer's staff, and the indication that callers may object to the storage; RR42 does not use the word “recording” or equivalent expressions in the short notice, because no sound recording is made (paragraph 5). If a caller objects, the caller continues to be served and, where configured, transferred; the Service stores neither a transcript nor a handover summary for this call, and RR42 shall erase text data already generated without undue delay, at the latest within 24 hours; a matter already formed in the same call before the objection is also covered. If the caller subsequently provides, of its own accord in the same call, information for the handling of a request, or corrects or confirms such information, the Service stores the matter formed from it including the associated transcript; the change is documented in the call log. The objection takes effect only for storage; the transient processing required to conduct the call and the connection metadata under A § 5 para. 12 remain unaffected. If a call is put through directly to the forwarding destination without involvement of the assistant, the Service outputs a notice about the processing before putting it through. RR42 ensures the technical implementation of sentences 2 to 5 and demonstrates it to the Customer on request. RR42 provides the Customer with the model texts of document C3 for its own channels as well as text modules for the data protection notices under Art. 13 GDPR, which the Customer adapts to its processing and publishes on its channels; the short notice and text modules do not replace the Customer's own review of whether they describe its processing completely and correctly. The Customer may not remove the short notice and may not word its greeting text in such a way that the short notice is not output; supplementary information in its greeting text is left to the Customer. If the Customer uses its own greeting text, output of the short notice is omitted only insofar as that text contains all the information under sentence 1 including the possibility of objection; RR42 checks this before go-live and, in case of doubt, additionally outputs the short notice; a greeting text of the Customer that mentions the storage without naming the possibility of objection does not suppress the short notice. RR42 uses the same wording of the short notice for all product variants and sectors and inserts into it only the designation, applicable to the Customer, of the body that handles the request.
(8) Data subject requests from callers are to be addressed to the Customer; RR42 shall forward requests received by it without undue delay and shall assist the Customer in accordance with § 13 of Annex B1.
(9) Annex B1 and its annexes are incorporated in the version applicable under A § 3 para. 2. RR42 shall actively notify the Customer of changes to the sub-processor list (Annex 3 to Annex B1) in accordance with § 11 of Annex B1; a mere reference to an online list does not replace the notification.
A § 13 Rights of use, Customer data, use of data, feedback, open source, AI outputs
(1) RR42 and its licensors retain all rights in the Service, software, models, system prompts, documentation, interfaces, methods and further developments. For the contract term, the Customer receives the non-exclusive, non-transferable and non-sublicensable right to use the Service in accordance with the contract for its own business purposes via the customer account and the target number. Own use includes use for all establishments, branches and locations of the Customer in accordance with the number of locations and target numbers specified in the order, and the fulfilment of the Customer's statutory or professional-law obligations regarding representation, out-of-hours service, standby and networks, including where requests concerning another professional are handled in the process. Making the customer account available to third parties and operating the Service for third parties not covered by sentence 3 are not permitted unless agreed in text form.
(2) The Customer retains all rights in Customer data. RR42 processes Customer data exclusively to provide the Service, to ensure security and operation, for support at the Customer's request and to fulfil statutory obligations, in each case in accordance with the Data Processing Agreement. The Customer grants RR42 the rights of use required for this and warrants that it is entitled to do so.
(3) RR42 does not use audio signals, transcripts, prompt and output data or other call content for training, fine-tuning or evaluating AI models. RR42 shall contractually oblige the providers of language models, speech recognition and speech synthesis that it uses likewise not to use this data for such purposes, and shall demonstrate to the Customer on request within 20 working days in text form that and in what form this obligation exists (§ 9 of Annex B1). Storage of call content by a subcontractor for purposes other than providing the Service for the Customer, in particular for abuse monitoring, is permitted only if it is shown in Annex 3 to Annex B1 stating provider, purpose, place of processing and storage period and the Customer has separately agreed to it before use, in text form or via a field of the customer account provided for this purpose and not pre-selected; silence of the Customer does not count as agreement. Towards Customers to whom Part B applies, such storage is in addition permitted only if the subcontractor is obliged in text form to confidentiality under B § 2 para. 5 and the conditions of B § 2 para. 6 are met. If the Customer does not agree, RR42 shall not use the provider for it or shall provide it with a processing route without such storage; if RR42 can do neither, it shall inform the Customer of this in text form, and either party may terminate the contract without notice period, the remuneration for the current billing period being refunded pro rata. If RR42 uses a provider that does not enter into the obligation under sentence 2, it shall replace the provider or inform the Customer before use; in this case the Customer may terminate under A § 10 para. 3.
(4) RR42 uses anonymised or aggregated call content only if the Customer has previously agreed to this separately in text form and re-identification is excluded (§ 9 para. 3 of Annex B1). The agreement is not a condition of the conclusion of the contract and may be revoked at any time with effect for the future. Irrespective of this, RR42 may, as its own controller, process billing, usage and security metadata of the customer account that have no reference to an individual call and contain no telephone numbers of callers (in particular the number of calls and call minutes per billing period and error, load and security events of the platform), exclusively for billing, capacity planning, ensuring the security and stability of the Service and fulfilling statutory obligations. Use of this data for the development, training, fine-tuning or evaluation of AI models or other products and services does not take place (§ 9 para. 1 of Annex B1). RR42 shall describe the processing under sentence 3 in its own privacy notice, which it makes available to the Customer before conclusion of the contract.
(5) RR42 may use voluntary feedback from the Customer on the Service free of charge to improve the Service; paragraphs 2 to 4 and A § 14 remain unaffected.
(6) The Service contains components under open-source licences. The respective licence terms apply to them and RR42 shall identify them on request; they do not affect the Customer's use of the Service.
(7) Rights in the transcripts, summaries and captured requests generated by the Service belong to the Customer, insofar as they are protectable. RR42 does not promise that individual outputs are unique or that identical or similar outputs are not also generated for other Customers. The Customer's rights on account of defects in title (section 536 para. 3 BGB), the indemnification under A § 21 para. 3 and liability under A § 20 remain unaffected; responsibility for erroneous outputs as to content is governed by A § 5 para. 4 and A § 15.
A § 14 Confidentiality; information security; security incidents; contact points
(1) “Confidential Information” means all information that one party makes accessible to the other in connection with the contract and that is marked as confidential or whose confidentiality follows from the circumstances. For RR42 this includes in particular system prompts, escalation and security logic, interface descriptions, unpublished prices and security information; for the Customer in particular configurations, knowledge base, transcripts, requests, telephone numbers, employee data and all information subject to a statutory duty of confidentiality of the Customer. At the Customer's request, RR42 shall make available to it in text form the content applicable to it of the identification as an AI assistant, the subject-matter response limit, the emergency rule and the other safeguards (A § 2 no. 17) as well as a description of the tool set and its revision status, insofar as the Customer needs this information to fulfil its obligations as deployer under the AI Act (KI-VO), to fulfil its obligations as controller including the data protection impact assessment, or to pursue claims against RR42. In a dispute about an erroneous output, RR42 shall additionally produce the wording of the system prompt applicable for the period concerned, insofar as this is necessary to establish whether the safeguards were complied with. The Customer shall treat this information as confidential in accordance with paragraphs 2 to 4; disclosure to advisers bound to confidentiality, professional chambers and competent supervisory authorities remains permitted to it.
(2) Each party shall use the other party's Confidential Information only to perform the contract, shall protect it with at least the care it applies to its own comparable information, but no less than with reasonable measures within the meaning of section 2 no. 1 letter b GeschGehG (Trade Secrets Act), and shall make it accessible only to those persons who need it for performing the contract and who are bound to confidentiality in text form or by law. RR42 may make the Customer's Confidential Information accessible to the sub-processors approved under Annex B1 insofar as this is necessary to provide the services.
(3) Information is not confidential if it is or becomes publicly known without breach of this contract, was demonstrably already known to the recipient, was developed independently by the recipient or was lawfully obtained from third parties without a confidentiality obligation. Disclosures required by law or ordered by an authority are permitted; the other party shall, insofar as legally permitted, be informed in advance.
(4) The obligations under this paragraph apply during the contract term and for five years thereafter; for trade secrets within the meaning of section 2 no. 1 GeschGehG for as long as they remain trade secrets, and for personal data and information subject to a statutory duty of confidentiality, without time limit. Section 5 GeschGehG remains unaffected.
(5) RR42 maintains a level of security appropriate to the risk and the state of the art in accordance with the technical and organisational measures (Annex 2 to Annex B1). The naming of standards does not mean certification unless such certification is expressly demonstrated. Neither party shall make security information or vulnerabilities of the Service publicly known before the other party has had an opportunity to remedy them, but no longer than 90 calendar days after being notified of the vulnerability at the contact point under paragraph 7; in the case of a continuing significant danger to callers or to data, this period is shortened to 30 calendar days. The following are not disclosure within the meaning of sentence 3: informing employees, advisers bound to confidentiality, insurers and professional chambers; informing data subjects; any communication to a supervisory or law enforcement authority; and information that a party is required by law to provide. Section 5 GeschGehG remains unaffected.
(6) RR42 shall notify the Customer of a personal data breach affecting Customer data without undue delay after becoming aware of it, in accordance with § 14 and Annex 6 to Annex B1, at the contact point named by the Customer; it shall in doing so transmit the information available to it and shall supply missing information without undue further delay. The Customer shall report suspected security or data protection incidents affecting the Service to RR42 without undue delay in accordance with A § 11 para. 8 sentence 2 and no. 9 of Annex A5, at the contact point under paragraph 7 sentence 1 letter b, and shall refrain from measures that alter evidence or hinder remediation. For notifications under sentences 1 and 2, the receipt rule of A § 9 para. 2 sentence 3 does not apply; they take effect upon receipt. The notification is not an acknowledgement; the decision on notifications under Art. 33 and 34 GDPR lies with the Customer.
(7) RR42's contact points are: a) for contract and support matters, info@rr42.de; b) for security incidents and personal data breaches, security@rr42.de; c) as data protection contact, datenschutz@rr42.de. If one of these addresses is temporarily unreachable, a notification addressed to info@rr42.de with the subject “Sicherheitsvorfall” (security incident) or “Datenschutz” (data protection) is deemed to have been received at the respective contact point. RR42 has appointed an external data protection officer; RR42 shall communicate the name and contact details to the Customer in text form no later than upon activation, shall keep them up to date in the customer account and shall publish them under Art. 37 para. 7 GDPR. RR42 shall notify the Customer in advance in text form of changes to the contact points. The Customer shall name in the order or in the customer account a contract contact, a notification address and a contact point for security incidents; until it does so, the notification address stored in the customer account applies.
A § 15 Warranty
(1) If the Service departs from the agreed quality (defect), RR42 shall remedy the defect within a reasonable period by rectification. Until rectification, RR42 may provide a workaround if it is reasonable for the Customer and preserves the core functions described in A § 5 para. 12 sentence 2; the provision of a workaround does not remedy the defect and leaves the Customer's rights under paragraphs 3 to 6 unaffected. If the agreed quality has not been restored 30 calendar days after receipt of the notice of defect, the defect is deemed not remedied; the Customer's rights under section 536 para. 1, section 536a para. 1 and section 543 para. 2 sentence 1 no. 1 BGB remain unaffected. A workaround that permanently changes the scope of services is a change to the Service and is governed by A § 10. The response and recovery targets follow from A § 9 para. 6.
(2) The Customer shall notify RR42 of defects and faults without undue delay via the support channel and describe them as precisely as it can (section 536c BGB). A defect need not be reproducible. To clarify a defect notified by the Customer, RR42 may consult the transcripts and records of the matter concerned insofar as necessary for the clarification; the notice of defect is deemed in this respect a documented instruction within the meaning of § 5 para. 1 and para. 2 of Annex B1. RR42 shall restrict access to the persons authorised for this purpose, log it in accordance with § 6 of Annex B1 and produce the log to the Customer in text form on request. For Customers under Part B, B § 2 para. 3 and B § 12 additionally apply. There is no preclusion period for notices of defect.
(3) If the Service is not usable or only usable to a limited extent as a result of a defect, the remuneration is reduced by operation of law (section 536 para. 1 BGB). The Customer may not deduct the reduction amount from ongoing payments. If the defect is undisputed, acknowledged by RR42 or finally established by a court, RR42 shall refund or set off the reduction amount no later than with the next invoice. The Customer's right to reclaim overpaid remuneration (section 812 BGB) exists independently of a finding by RR42 and remains unaffected. Insignificant reductions in fitness are disregarded. For set-off and retention, A § 18 applies.
(4) RR42's liability, irrespective of fault, to pay damages for defects that already existed when the Service was made available (section 536a para. 1 alt. 1 BGB) is excluded; this does not apply to damage from injury to life, body or health and not in the other cases of A § 20 para. 1. Sentence 1 further does not apply to departures that RR42 knew of at the conclusion of the contract and did not disclose under A § 5 para. 11. Liability for defects for which RR42 is responsible, and for delay in remedying defects, is governed by A § 20. If RR42 has fraudulently concealed a defect, RR42 cannot rely on the limitations in this paragraph (section 536d BGB).
(5) Claims on account of a defect do not exist insofar as the defect is due to the Customer having configured or used the Service contrary to these AGB or Annex A5, in particular having switched off safeguards, to content provided by the Customer being incorrect or incomplete, or to disruption of systems, connections or networks operated by the Customer or by a third party engaged by it (A § 11 para. 6). This does not apply insofar as RR42 is also responsible for the cause. Disruptions at RR42's subcontractors are not attributed to the Customer.
(6) The Customer's right to terminate for good cause (A § 24), in particular in the event of persistent non-provision of use (section 543 para. 2 sentence 1 no. 1 BGB), remains unaffected.
A § 16 Fees, billing period, measurement, plan change, value added tax
(1) The amount of the base fee, the included allowance per billing period, the price per additional minute and, where the plan includes the research function (A § 5 para. 14), the number of included queries per billing period and the price per additional query follow from the plan chosen at the time of the order, in the plan overview displayed in the Customer's order process at that time. No set-up fee is charged. An individually agreed plan is displayed to the Customer in the Customer's order process and becomes part of the contract with the order; no further agreement in text form is required for this. Unlimited minute allowances require an agreement in text form. RR42 does not charge any fees other than those expressly stated in the plan overview, in the order or in these AGB; in particular, no set-up, processing, dunning, returned-debit, blocking, unblocking, export or switching fees are charged, unless they are stated and agreed pursuant to A § 11 para. 9 sentence 4, A § 12 para. 4 sentence 4 or A § 16 para. 7.
(2) The billing period is one month. The first billing period begins with the subscription start; each further billing period begins immediately upon the end of the preceding one. RR42 states the start and end of the current and of the following billing period as a date in the customer account and names them in every invoice. If RR42 does not state this information or it is contradictory, a billing period ends at the end of the day that precedes, in the following month, the calendar day of the subscription start; if this calendar day does not exist in the following month, it ends at the end of the last day of the following month. Only the Customer may rely on sentence 4. RR42 will not postpone the start of a billing period without the Customer's agreement in text form; a postponement that is to the Customer's disadvantage, in particular by changing the billing cycle held at the payment service provider, has no effect vis-à-vis the Customer. A base fee is in no case charged for more than one billing period per month; if a billing period is shortened, the base fee is charged for it only pro rata temporis and the included allowance is not reduced. The base fee is charged in advance at the start of each billing period. Additional minutes are charged retrospectively with the next invoice after the end of the billing period in which they were incurred. If the contract ends, RR42 settles the additional minutes incurred up to the end of the contract with a final invoice designated as such; the final invoice is issued within 14 calendar days after the end of the contract. A charge to the stored payment method after the end of the contract is permitted only on the basis of this final invoice and only within 14 calendar days after its receipt; thereafter, outstanding amounts are to be paid against invoice. After the end of the contract, no further base fees arise; RR42 will promptly refund base fees already collected for periods after the end of the contract.
(3) For each call accepted by the Service, RR42 records the call duration to the second. The measurement begins when the Service accepts the call and ends with the end of the automated conversation or, in the case of transferring the call, with the start of the transfer (A § 7 para. 5 sentence 3); times of call set-up and ringing before acceptance are disregarded, and started seconds are disregarded. Calls that the Service does not accept and connections that end before acceptance are not counted. Likewise not counted are times in which the Service renders no performance because of a disruption for which RR42 is responsible; RR42 deducts these times as soon as they become known to it. The Customer may demand the deduction in text form within eight weeks after receipt of the relevant invoice, stating the date and approximate time of the calls concerned; this period is not a preclusion period. RR42 decides on the demand in text form within two weeks and refunds or offsets the amount at the latest with the next billing. If RR42's operating, platform or incident data (A § 8 para. 2) show an impairment for the period stated by the Customer, RR42 bears the burden of presentation and proof that the billed call duration does not include any disruption time. The duration of a transferred call is disregarded from the start of the transfer (A § 7 para. 5 sentence 3); no separate connection fee is charged. The call durations of all calls accepted within a billing period are added up per billing period. A call that was accepted before the start of a billing period and ends only in it is attributed as an additional minute neither to this nor to the preceding billing period; it remains uncharged. The measurement method under sentences 2 to 10 is part of the fee agreement; RR42 may change it only pursuant to A § 19 para. 2. A § 10 and A § 27 do not apply to the measurement method.
(4) The plan's included allowance (in seconds) is deducted from the result under paragraph 3. The remainder is rounded down to full minutes; only these full minutes are charged as additional minutes at the plan price. Unused included minutes lapse at the end of the billing period and are not carried over.
(4a) If the ordered plan includes the research function (A § 5 para. 14), RR42 counts the queries triggered by the Customer per billing period. Every query that results in a response from the Service is counted; queries that remain without a result because of a disruption, an error or a missing response are not counted. The plan's included queries are deducted from the total; only the remaining queries are charged as additional queries at the price per additional query. Unused included queries lapse at the end of the billing period and are not carried over. The Customer can view the number of queries taken into account in the customer account; at the Customer's request, RR42 excludes an additional query from billing if it has remained without a usable result. Paragraph 3 sentences 5 to 7 and paragraph 5 apply to additional queries accordingly. If the plan overview states, for the Customer's plan, neither a number of included queries nor a price per additional query, queries are not charged separately.
(5) The basis of billing is the call durations recorded by the Service under paragraphs 3 and 4. The consumption and cost values continuously displayed in the customer account are a non-binding approximation; they may deviate from the billing, in particular because additional minutes are billed only after the end of the billing period. The amount payable is the amount stated in the invoice issued by the payment service provider in the name of RR42; the invoice contains no confirmation of facts, does not give rise to a presumption of its correctness and does not change the statutory burden of proof. If the invoice deviates from the recorded call durations, the recorded call durations prevail; RR42 corrects the invoice and promptly refunds or offsets any amount collected in excess, at the latest with the next billing. If the Customer disputes the billed duration or the number of calls taken into account, RR42 must present and prove them. On request in text form, RR42 provides the Customer, free of charge, for each billing period with an itemised statement of the calls taken into account, with date, time of start, recorded call duration and allocation to the billing period and, where additional queries have been charged, an itemised statement of the queries taken into account, with date and time. RR42 retains the billing data required for this (call identifier, date, time of start, recorded call duration, identifier and time of queries taken into account, allocation to the billing period), without telephone numbers and without call or research content, separately from the other call data, for the duration of the statutory retention periods (section 147 para. 1 no. 4 and para. 3 AO, section 14b para. 1 UStG, section 257 HGB), but at least until the expiry of three months after receipt of the invoice in which the respective call was included and, where the Customer has raised objections, until these have been finally resolved; the erasure periods for the other call data under A § 26 and Annex 4 to Annex B1 remain unaffected. If RR42 cannot provide the itemised statement for a billing period, it cannot rely on the recorded call durations for that period and cannot assert the additional minutes charged for it; it will promptly refund amounts already paid. The Customer should notify objections to an invoice in text form within eight weeks after receipt; this period is not a preclusion period, and the Customer's statutory claims remain unaffected.
(6) The Customer may demand a change of plan in text form. If the demand reaches RR42 no later than seven calendar days before the end of the current billing period, RR42 implements the change with effect from the start of the following billing period; if it arrives later, with effect from the start of the billing period after that. RR42 confirms the change and the time at which it takes effect to the Customer in text form. The base fee, included allowance and price per additional minute of the new plan apply from that time; the current billing period is not recalculated pro rata. In the case of a change to a higher plan, RR42 activates the higher included allowance promptly, at the latest within two working days after receipt of the demand, already in the current billing period, without an additional base fee being incurred for this; for additional minutes of this billing period, the more favourable of the two prices per additional minute for the Customer then applies, and the higher base fee is charged only from the following billing period. A change to a lower plan always takes effect only at the start of the billing period that is relevant under sentence 2. A change of plan via the customer portal is not possible.
(7) The Customer selects the voice used in the Service in the customer account. If, according to the plan overview, the ordered plan provides a higher price per additional minute for additional minutes rendered with a premium voice (A § 2 no. 29), RR42 states this price in the customer account at the place where the Customer selects the voice, before the Customer confirms the selection. The higher price applies only if the Customer has selected the premium voice themselves, and only for additional minutes from the start of the billing period following the selection; for the current billing period, the previous price remains. If the Customer again selects a standard voice, the lower price applies from the start of the following billing period. As long as RR42 has not stored the changed price with the payment service provider, the previous, lower price is charged; RR42 does not demand a subsequent charge of the difference for past billing periods. If RR42 changes the voice on its own initiative, in particular as a result of a change under A § 10, this does not lead to a higher price per additional minute. In all other respects, any change to the price per additional minute is governed exclusively by A § 19.
(8) All fees are net, plus the applicable statutory value added tax. If the tax rate changes, the gross amount changes accordingly, without any announcement being required. For the group of customers and the value added tax treatment of Customers with their seat outside Germany, A § 1 para. 3 applies.
(9) If the Customer orders the Service for several locations or several target numbers, a single contract with one billing period exists. The base fee and included allowance are determined by the order; if separate base fees are stated there for several locations or target numbers, the associated included allowances are combined for the billing period and the call durations of all locations and target numbers are billed together under paragraphs 3 and 4. If the order does not state separate base fees, the base fee is incurred only once. The Customer may cancel individual locations or target numbers subject to the notice period of A § 23 para. 2; the base fee and the included allowance are then reduced, from the following billing period, by the share stated for them in the order.
A § 17 Payment, invoice, default, returned debit
(1) Payment is made via the payment service provider engaged by RR42 by credit card or SEPA direct debit; the Customer stores the payment method in the order process and manages it in the customer portal. RR42 offers payment against invoice outside the payment service provider only to the extent that it is expressly designated as available and agreed in the order; in this case, the invoice amount is to be paid without deduction, within 14 calendar days after receipt of the invoice, to the account stated in the invoice, and paragraph 3 does not apply.
(2) RR42 issues invoices. RR42 transmits them to the Customer electronically as structured electronic invoices (EN 16931, ZUGFeRD) to the stored e-mail address and makes them available for retrieval in the customer account. Receipts of the payment service provider are payment receipts and not invoices. The Customer agrees to the transmission of invoices in an electronic format that does not meet the requirements for an electronic invoice (other invoice, section 14 para. 1 sentence 4 and sentence 5 UStG). Where RR42 is legally obliged to issue an electronic invoice (section 14 para. 2 sentence 2 no. 1 in conjunction with section 14 para. 1 sentence 3 and sentence 6 UStG), RR42 provides the invoice in a structured electronic format that conforms to the standard under Directive 2014/55/EU; on request, the Customer notifies RR42 of the receiving data required for this. The Customer keeps the company name, billing address and VAT identification number up to date in the customer portal.
(3) Fees fall due upon receipt of the notification under sentence 2. RR42 announces to the Customer each charge, stating the amount and the debit date, to the stored e-mail address; the announcement takes place at the latest at the same time as the charge to the stored payment method (advance notification) and may be transmitted by the payment service provider in the name of RR42; RR42 transmits the invoice under para. 2 separately. In the case of payment by credit card, the charge may take place at the same time as the transmission of the notification under sentence 2; RR42 points this out to the Customer prominently in the order summary. In the case of payment by SEPA direct debit, the charge takes place no earlier than three bank working days after receipt of the advance notification; the notification additionally contains the creditor identifier and the mandate reference. For recurring direct debits of constant amount, a single notification that states the amounts and the due dates suffices; if the amount changes, RR42 announces the direct debit again in accordance with sentence 4. Sentences 2 to 5 apply to all contracts irrespective of the ordering channel; C § 5 para. 2 repeats and supplements them for the online order without deviating from them, and if a deviation nevertheless arises, then, notwithstanding A § 1 para. 5 sentence 3 and A § 3 para. 1, the provision that is more favourable to the Customer applies. A charge before the due date and a charge by SEPA direct debit without advance notification given in due time under sentence 4 are unjustified; paragraph 5 does not apply in this respect, RR42 refunds the amount promptly, a block under A § 25 para. 1 cannot be based on such a collection attempt, and default does not occur before receipt of a renewed, timely notification; the fee claim itself remains unaffected. As long as RR42 does not technically ensure the advance notification under sentence 4 and has not demonstrated this to the Customer in text form, it does not offer SEPA direct debit.
(4) The statutory provisions apply to default, in particular section 286 para. 3 and section 288 paras 2 and 5 BGB. RR42 may demand default interest at nine percentage points above the base rate and the lump sum of EUR 40; the lump sum is credited against a claim for damages to the extent that the latter is based on the costs of legal enforcement. Both parties reserve the right to prove higher or lower damage. The Customer's rights in respect of default against RR42, for example in the case of late refund, are not restricted.
(5) If a direct debit collection fails or a card payment is charged back and the Customer is responsible for this, in particular because of insufficient funds, because of a lapse of the mandate for which the Customer is responsible or because of incorrect payment data, the Customer reimburses RR42 for the fees actually charged by the payment service provider or by the account-holding institution for this and demonstrated to the Customer. There is no obligation to reimburse to the extent that the collection was wholly or partly unjustified, was based on an incorrect invoice or on a collection without the advance notification required under paragraph 3 sentence 2, or is based on a circumstance for which RR42 or the payment service provider is responsible. The Customer's right to demand from their payment service provider the refund of an authorised direct debit under section 675x para. 2 BGB remains unaffected; its exercise leaves RR42's claim unaffected. RR42 does not charge its own processing costs; no dunning, returned-debit or blocking lump sums are levied. The Customer reserves the right to prove that no damage or less damage has arisen.
A § 18 Set-off and retention
(1) The Customer may set off against claims of RR42 only with claims that are undisputed, ready for decision or finally determined by a court. This does not apply to counterclaims of the Customer arising from the same contractual relationship; the Customer may set off with these without this restriction. For this purpose, all components of the contract under A § 3 para. 1, including the Data Processing Agreement (Annex B1) with its annexes and Parts B and C, are deemed one contractual relationship. In particular, claims for defects of the Service, for repayment of overpaid fees, for damages under A § 20 and for indemnification and compensation under A § 21 are covered. The prohibition of deduction in A § 15 para. 3 sentence 2 concerns only the unilateral reduction of ongoing payments by a reduction amount determined by the Customer themselves; it does not preclude a set-off under sentences 2 to 4 or the assertion of the claim for repayment.
(2) The Customer may exercise a right of retention only on account of counterclaims arising from the same contractual relationship; paragraph 1 sentence 3 applies accordingly to the concept of the contractual relationship. The defence of non-performance of the contract (section 320 BGB), the Customer's right to withhold payment because of non-performance for which RR42 is responsible, and the Customer's rights under section 536 BGB and under A § 15 remain unaffected.
(3) Paragraphs 1 and 2 apply accordingly to RR42 vis-à-vis the Customer. However, RR42 has no right of retention or to refuse performance with regard to the provision, retrieval and export of Customer data under A § 26 para. 1, para. 2 and para. 6, the return or erasure of Customer data under A § 26 para. 2 sentence 7 and para. 3, the confirmation of erasure under A § 26 para. 3, the itemised statement under A § 16 para. 5 sentence 6, the support with requests of data subjects and the execution of instructions under Annex B1. RR42 makes these services dependent neither on the payment of outstanding fees nor on any other consideration; section 273 BGB is excluded in this respect. Sentence 2 also applies during a block under A § 25, during a suspension of call acceptance and after the end of the contract.
A § 19 Price change
(1) During a minimum term agreed under A § 23 para. 5, the fees agreed at the conclusion of the contract remain unchanged.
(2) In all other respects, RR42 may change the base fee, the included allowance, the price per additional minute and the measurement method under A § 16 para. 3 subject to the following sentences. RR42 notifies the Customer in text form of an intended change at least six weeks before the start of the billing period from which it is to apply, stating the previous and the new fee and the previous and the new included allowance. The notification points out separately and in typographically emphasised form that the change takes effect with the start of this billing period if the Customer does not object to it beforehand, as well as the right of objection, its informality and that it is free of charge to exercise. The Customer may object to the change in text form until the start of the billing period referred to in sentence 2, without any reason being required. RR42 may additionally provide a function of the customer account for the objection; an objection declared via this function is effective if the function can be operated with a single, non-preselected input and RR42 promptly confirms receipt of the objection to the Customer in text form. If the Customer objects in due time, the previous conditions continue to apply; in this case, RR42 may terminate the contract with ordinary notice under A § 23 para. 3. If the Customer does not object in due time, the new conditions are deemed accepted from the start of the billing period referred to in sentence 2. RR42 bears the burden of presentation and proof that the notification under sentence 2 with the notice under sentence 3 reached the Customer in due time; if it cannot do so, the change has not taken effect, the previous conditions continue to apply, and RR42 promptly refunds amounts collected in excess.
(3) Changes in value added tax remain unaffected (A § 16 para. 8). Changes to the scope of services are governed by A § 10; a reduction of the included allowance and any other change that shifts the relationship between performance and remuneration to the Customer's disadvantage is excluded under A § 10 para. 1 sentence 2 and can be changed only under paragraph 2. Changes to these AGB are governed by A § 27.
(4) If the Customer orders additional locations, target numbers or plans, the plan overview displayed to the Customer at the time of this order applies to this additional order. The fees, included allowances and prices per additional minute agreed for existing subscriptions remain unaffected; they can be changed only under paragraph 2. A § 3 para. 5 does not give rise to any change in the fees, included allowances or terms of existing subscriptions.
A § 20 Liability
(1) RR42 is liable without limitation for damage arising from injury to life, body or health, for damage based on intent or gross negligence on the part of RR42, its legal representatives or its vicarious agents, for damage arising from the breach of a guarantee expressly designated as such by RR42, in the case of fraudulent concealment of a defect, as well as under the Product Liability Act and in other cases of mandatory statutory liability.
(2) For damage based on simple negligence, RR42 is liable only in the event of a breach of an essential contractual obligation. Essential contractual obligations are obligations whose fulfilment makes the proper performance of the contract possible in the first place and on whose observance the Customer may regularly rely; these include in particular the acceptance of incoming calls, the forwarding and capture of requests according to the Customer's configuration, the provision of the captured data in the customer account, the operation of the protective mechanisms and the preservation of confidentiality and data protection. The availability commitment under A § 8 para. 1 does not limit the scope of essential contractual obligations; A § 8 para. 5 sentence 3 remains unaffected. In this case, liability is limited to compensation of the damage that was foreseeable at the conclusion of the contract as a typical consequence of the breach of duty for this type of contract.
(3) Liability under paragraph 2 is also limited in amount. The following applies:
a) A contract year is the period of twelve months from the subscription start (A § 2 no. 24, A § 23 para. 1 sentence 2) and each following period of twelve months; a trial period preceding the subscription start is attributed to the first contract year. If no subscription comes into being, the first contract year is the period of twelve months from the start of the trial period under C § 3 para. 1 sentence 5 or, in the case of an order in text form, under A § 4 para. 5; for the trial period, C § 3 para. 2 remains unaffected.
b) A loss event is the event giving rise to liability. Several events that are based on the same cause or on several similar, related causes are deemed one loss event. For the allocation to a contract year, the occurrence of the respective damage is decisive; damage that occurs in different contract years is allocated to the contract year of its occurrence even if it is based on the same cause. A separate maximum amount under letters c and d applies for each contract year in which damage occurs. Sentence 2 does not result in damage that occurred in a later contract year being attributed to an earlier contract year and thereby being covered by its already exhausted maximum amount.
c) For all loss events of a contract year in total, RR42 is liable at most up to the higher of the following amounts: the net remuneration that the Customer paid or was to pay for the Service in the twelve months before the occurrence of the first loss event of this contract year, or EUR 50,000. In the case of a shorter contract duration, the net remuneration is extrapolated to twelve months; during the trial period and for periods without a base fee, the base fee of plan tier 1 of the respective sector is used as the basis. RR42 has oriented this maximum amount to the typical operating size of the customers it addresses and to the coverage amount of its liability insurance under letter e, and assumes that it covers the damage that was typical for this type of contract and foreseeable at the conclusion of the contract. If the Customer proves that the damage typical for this type of contract and foreseeable at the conclusion of the contract exceeds this amount, RR42 is liable under paragraph 2 up to the amount of this damage; if the Customer has drawn RR42's attention in text form before the conclusion of the contract to a higher damage potential and RR42 has not objected to this in text form before the conclusion of the contract, this proof is deemed provided.
d) Notwithstanding letter c, RR42 is liable for damage arising from the breach of obligations relating to data protection, confidentiality or the preservation of professional secrecy, as well as for the loss or damage of Customer data, for all loss events of a contract year in total up to EUR 250,000; for Customers to whom Part B applies, up to EUR 500,000.
e) RR42 maintains, for the duration of the contract, liability insurance for financial loss, data loss and cyber damage with a coverage amount per insurance year that at least reaches the maximum amounts under letters c and d. On request, once per contract year, RR42 evidences the existence of the insurance and the coverage amount to the Customer in text form within two weeks. If the insurance does not exist or RR42 does not provide the evidence in due time, the maximum amounts under letters c and d do not apply to loss events that occur in the period in which the insurance is lacking or the evidence is outstanding; liability is then governed by paragraph 2.
The maximum amounts under this paragraph apply only within the scope of paragraph 2; paragraph 1 remains unaffected by them.
(4) In all other respects, RR42's liability for simple negligence is excluded. Paragraph 1 remains unaffected; liability for damage arising from injury to life, body or health, for damage arising from the breach of a guarantee expressly designated as such by RR42, in the case of fraudulent concealment of a defect, under product liability law and in other cases of mandatory statutory liability is neither excluded nor limited by this paragraph even if it is based on simple negligence.
(5) A § 5 para. 10 applies to data backup. The Customer backs up data that they have exported or downloaded from the Service in their own systems in accordance with the state of the art. For data that was not available to them for export in a format that permits a backup, the Customer is under no duty to back up; contributory fault for a failure to back up is not to be considered in this respect. For the loss or damage of Customer data, RR42 is liable under paragraphs 1 to 4; the maximum amount of paragraph 3 letter d, which is set for data protection, confidentiality and data loss damage, applies.
(6) Paragraphs 1 to 5 apply to all contractual and non-contractual claims of the Customer against RR42 arising from or in connection with this contract and likewise for the benefit of the legal representatives, employees and vicarious agents of RR42, but only to the same extent as for the benefit of RR42 itself. The settlement between the parties in the internal relationship under Art. 82 para. 5 GDPR (DSGVO) is governed by the share that each party bears in the responsibility for the damage. For the claim for settlement against RR42, the maximum amount of paragraph 3 letter d applies; it does not apply to the extent that RR42 has caused and is responsible for the damage alone or predominantly, nor in the cases of paragraph 3 letter e sentence 3. § 20 para. 1 of Annex B1 remains unaffected to the extent that it is more favourable to the Customer. Claims of data subjects under Art. 82 paras 1 to 4 GDPR, the joint and several liability under Art. 82 para. 4 GDPR and, in all other respects, mandatory Union law remain unaffected; paragraphs 1 to 5 limit neither a party's external liability nor the share for which a party can be held liable in the external relationship. A fine is borne by the party against which it is imposed to the extent that it is itself responsible for the sanctioned breach of duty; it cannot demand indemnification from the other party for this fine. If the fine is based wholly or partly on a breach of duty by the other party, the party concerned may demand compensation under the general provisions to the extent that the fine is recoverable under the applicable law; paragraphs 1 to 5 apply. The parties promptly inform each other of regulatory proceedings that have been initiated and coordinate statements to the extent legally permissible.
(7) The Customer remains responsible for professional decisions and for compliance with their obligations under professional and data protection law. The scope and limits of the Customer's duties of review and supervision follow conclusively from A § 11; the Customer does not owe constant monitoring of the calls. Whether and to what extent contributory fault on the part of the Customer reduces RR42's liability is governed by section 254 BGB; contributory fault is considered only to the extent that the Customer has breached a duty incumbent on them under A § 11 and this breach has become causal for the damage. This paragraph does not limit RR42's liability for its own breaches of duty and does not give rise to a reversal of the burden of proof to the Customer's disadvantage.
A § 21 Third-party claims; indemnification; settlement in the internal relationship
(1) The statutory liability of RR42 and of the Customer towards callers and other third parties, in particular under section 823 BGB, under the Product Liability Act and under Art. 82 GDPR, is neither excluded nor limited by this contract. The provisions of this section concern exclusively the relationship between RR42 and the Customer.
(2) The Customer indemnifies RR42 against justified claims of third parties, including the costs of a reasonable legal defence, to the extent that the claim is based on the Customer having
a) provided or released incorrect, outdated or unlawful content,
b) not configured, incorrectly configured or not kept up to date the forwarding destination, the opening and availability hours or the forwarding release,
c) removed, weakened or circumvented protective mechanisms or used the Service for use cases prohibited under these AGB or Annex A5,
d) breached a duty to provide information, a duty of supervision or a duty of cooperation incumbent on the Customer under these AGB or under Annex A5, or a professional duty applicable to the Customer; a breach of availability obligations gives rise to indemnification only to the extent that the Customer has left unchanged or changed the forwarding release under A § 11 para. 3 contrary to the notice given to the Customer under A § 11 para. 3 sentence 2, or
e) given RR42 unlawful instructions,
and the Customer is responsible for this. The indemnification lapses to the extent that RR42 has contributed to causing the claim; in this case, the parties bear the damage in proportion to their shares of causation and fault. If the Customer's breach of duty is based on simple negligence, the Customer's indemnification and compensation obligations under this paragraph and under B § 11 para. 4 are limited together to EUR 50,000 for all claims of a contract year in total, including the costs of legal defence; this limitation does not apply to intent and gross negligence, contract year and loss event are determined in accordance with A § 20 para. 3 letters a and b, A § 20 para. 3 does not otherwise apply to this limitation, and RR42 has oriented the amount to the basic amount up to which it itself is liable under A § 20 para. 3 letter c.
(3) RR42 indemnifies the Customer against justified claims of third parties, including the costs of a reasonable legal defence, to the extent that the claim is based on RR42 having
a) culpably failed to provide or operate the protective mechanisms owed by it,
b) culpably failed to execute the Customer's configuration in accordance with the contract,
c) culpably processed personal data outside the Customer's instructions or contrary to the Data Processing Agreement (Annex B1), the Acceptable Use Policy (Annex A5) or Part B, in particular recorded or stored call audio contrary to A § 12 para. 5, or
d) infringed third-party intellectual property rights in Germany through the unchanged use of the Service in accordance with the contract.
In the case of letter d, RR42 will primarily procure the necessary rights of use or change the Service so that the infringement ceases; such a change must observe the limits of A § 10 para. 1 sentence 2. If both measures are impossible for RR42 or possible only with disproportionate effort, RR42 may discontinue the affected part of the Service; it announces this in text form at least 30 calendar days in advance, unless a court decision or an official order requires a shorter period, which RR42 will then communicate to the Customer. In this case, RR42 refunds pro rata temporis the prepaid remuneration relating to the time after the discontinuation. If a core function under A § 10 para. 1 sentence 2 is thereby eliminated or substantially restricted, the Customer may terminate the contract as a whole without observing a notice period with effect from the time of discontinuation; the defect rights under A § 15, termination for good cause under A § 24 and claims for damages under A § 20 remain unaffected. The indemnification under sentence 1 lapses to the extent that the Customer has contributed to causing the claim; in this case, the parties bear the damage in proportion to their shares of causation and fault. The liability limitations of A § 20 apply to the indemnification under this paragraph; for the Customer's indemnification obligation, the last sentence of paragraph 2 applies.
(4) To the extent that a party is liable to a natural person under product liability law or under Art. 82 GDPR, the settlement between the parties is governed by paragraphs 2 and 3 and otherwise by the share in which each party has caused and is responsible for the damage. For the claim for settlement against RR42, A § 20 para. 3 applies with the proviso that the maximum amounts stated there do not apply to the extent that the damage to be settled is based on injury to life, body or health or to the extent that RR42 or a person whose conduct RR42 is responsible for has caused the damage intentionally or with gross negligence; in this respect, RR42 bears the damage in the internal relationship without limitation according to its share of causation and fault. A § 20 para. 1 remains unaffected. Liability towards the injured person remains unaffected by this paragraph (paragraph 1).
(5) The party to be indemnified promptly informs the other party in text form of claims asserted and transmits to it the information required for the defence, to the extent that statutory duties of confidentiality and Part B do not preclude this; it cooperates in the defence to a reasonable extent. It makes no admission of liability as to the basis or amount of the claim without the consent of the indemnifying party; statutory duties of reporting, notification, information, rectification and documentation, in particular under Articles 12 to 16, 33 and 34 of the General Data Protection Regulation, as well as professional duties remain unaffected and are not deemed an admission. The indemnifying party may take over the defence of the claim at its own expense. If it does not declare within a reasonable period, as a rule two weeks from the notification, that it takes over the defence, or if leaving the defence to it is unreasonable for the party to be indemnified, in particular because that party is itself being claimed against or professional or data protection duties preclude it, the party to be indemnified conducts the defence itself; the indemnifying party bears the reasonable costs, and the party to be indemnified may then admit or settle the claim to the extent that a prudent businessperson would do so. Settlements that create obligations for the respective other party require its consent; the consent may not be withheld without objective reason. If a party breaches an obligation under this paragraph, the indemnification lapses or is reduced only to the extent that the breach has demonstrably impaired the defence of the claim.
(6) For professional secrecy holders, B § 11 para. 4 applies in addition.
A § 22 Force majeure
(1) Neither party is liable for non-performance of its obligations to the extent that it is based on an event that lies outside its sphere of influence and whose occurrence or consequences it could not have averted even by applying the utmost care reasonably to be expected in the circumstances, but at least the care required in the ordinary course of business (section 276 para. 2 BGB (German Civil Code)) (force majeure). Payment difficulties and disruptions of the systems, networks and security precautions for which the respective party is itself responsible are not force majeure. Disruptions at subcontractors of RR42 are force majeure only if they themselves are based on an event under sentence 1; the selection and management of the subcontractors remain the responsibility of RR42. The burden of presentation and proof for the existence of force majeure lies with the party relying on it.
(2) The affected party shall inform the other party without undue delay, mitigate the effects and resume performance as soon as the event has ceased. Payment claims for services already rendered remain in place. The base fee is reduced for the duration and to the extent of the impairment; the reduction takes effect by operation of law (section 536 para. 1 BGB), does not require RR42 to be at fault, and also applies in the case of a mere reduction in suitability. RR42 shall refund or offset the reduction amount no later than with the next billing. The Customer's rights under A § 15 remain unaffected; the exclusion of force majeure in A § 8 para. 1 (there letter d of the list of excluded periods) relates exclusively to the calculation of availability and does not exclude these rights. Double compensation for the same disadvantage is excluded.
(3) If the event lasts longer than 60 calendar days and impairs essential services, either party may terminate the contract with immediate effect. The right of either party to terminate for good cause (A § 24, section 314 BGB), the Customer's right to terminate without notice period for non-provision or withdrawal of the use in accordance with the contract (section 543 para. 2 sentence 1 no. 1 BGB) and its right to ordinary termination under A § 23 para. 2 remain unaffected; the period in sentence 1 neither postpones nor excludes them, and force majeure does not preclude the existence of good cause. RR42 shall refund remuneration paid in advance for the time after the end of the contract pro rata within 14 calendar days.
(4) Paragraph 1 excludes only compensation for damage that is based on force majeure. The Customer's rights under sections 536, 543 BGB and under A § 15 as well as the termination rights under A § 10 para. 3, A § 23 and A § 24 remain unaffected.
A § 23 Term and ordinary termination
(1) The contract for a subscription is concluded for an indefinite period. The subscription start is the time of the conclusion of the contract (A § 4 para. 3, C § 4 para. 3); if a later start of performance has been agreed or is decisive under A § 4 para. 3 sentence 5, that time takes its place. RR42 states the subscription start in the confirmation under A § 4 para. 4 and shows it in the customer account. The billing period is one month and begins with the subscription start (A § 16 para. 2).
(2) The Customer may terminate the contract at any time without observing a notice period, with effect from the end of the current billing period. The termination is in time if it reaches RR42 by 24:00 (time zone Europe/Berlin) on the last day of the billing period. RR42 shows the start and end of the respective billing period in the customer account in the same time zone in accordance with A § 16 para. 2 sentence 3; if it is doubtful whether a termination was still received within the current billing period, it is deemed to have been received in time. Notwithstanding section 130 para. 1 sentence 1 BGB, a termination given via the termination function of the customer account or of the customer portal is deemed received at the time of the input logged there, and a termination transmitted by e-mail to the address specified in A § 30 para. 5 is deemed received upon its arrival on the mail server of RR42, including outside normal business hours and on Saturdays, Sundays and public holidays; delays or disruptions in transmission caused by a body used by RR42 are not at the Customer's expense. If the termination is received only after the time specified in sentence 2, it takes effect at the end of the billing period in which it is received by RR42; no further binding of the Customer arises. RR42 bears the burden of proof for a later receipt than that stated by the Customer. Until the end of the contract the Service remains usable; base fees already paid for the current billing period are not refunded.
(3) RR42 may terminate the contract with one month's notice to the end of a billing period; A § 23 para. 5 sentence 4 remains unaffected.
(4) Termination requires text form. The Customer may declare it via a termination function offered in the customer account or in the customer portal or by e-mail to the address specified in A § 30 para. 5; for contracts via the customer account, C § 6 applies in addition. There is no special requirement of receipt. RR42 shall confirm to the Customer in text form, within three working days, the receipt of its termination and the date of the end of the contract, to the contract contact and to the notification address, and shall in doing so refer to the cancellation of the call diversion (paragraph 6). The effectiveness of the termination does not depend on the confirmation; if it is not forthcoming, the Customer may prove receipt by any suitable means. If RR42 terminates under paragraph 3, under A § 19 para. 2 sentence 6, under A § 24 or under A § 27 para. 4 sentence 3, the declaration of termination states the date of the end of the contract and contains the same notice; C § 8 para. 2 applies accordingly.
(5) A minimum term applies only if it has been individually negotiated between the parties, has been designated in the order separately and typographically highlighted as a deviation from paragraph 2, and has been confirmed by both parties in text form. Before the order is placed, RR42 shall point out to the Customer separately and prominently that the Service is otherwise terminable monthly without a notice period. The minimum term begins with the start of the first billing period subject to a charge (A § 16 para. 2) and is at most twelve months. During the minimum term, ordinary termination is excluded for both parties; paragraph 3 does not apply to RR42 either in this respect. Either party may terminate with one month's notice to the end of the minimum term. If no termination is given, the contract continues for an indefinite period and may be terminated under paragraphs 2 and 3; an extension by fixed periods does not take place. During the minimum term, A § 19 para. 1 applies. The Customer's rights to terminate for good cause (A § 24) and under A § 10 para. 3, A § 27 para. 2 sentence 5 and para. 4 and A § 32 para. 2 remain unaffected by the minimum term; if the contract ends for one of these reasons or for any other reason for which RR42 is responsible, the minimum term also ends, and RR42 shall refund charges paid in advance for the time after the end of the contract pro rata. The selection between pre-formulated term indications, in particular via a tick box, a selection list or a default setting in the ordering process, is not negotiation within the meaning of sentence 1 (section 305 para. 1 sentence 3 BGB); for a conclusion of the contract via the customer account (Part C), no minimum term applies.
(6) Upon the end of the contract, RR42 no longer accepts calls. The Customer shall cancel the call diversion to the target number at the latest by the end of the contract (A § 7 para. 9). A § 26 applies to data export and erasure.
A § 24 Termination for good cause
(1) The right of each party to terminate the contract for good cause without observing a period (section 314 BGB) remains unaffected. If the good cause consists in the breach of a contractual obligation, termination is permissible only after the unsuccessful expiry of a reasonable period set for remedy or after an unsuccessful warning, unless setting a period or giving a warning is dispensable under section 314 para. 2 sentences 2 and 3 BGB. In the cases of paragraph 2 letters c and d, termination always requires a prior request, with a reasonable period, to eliminate the cause; in the case of paragraph 2 letter e, whether a request is dispensable is governed by section 314 para. 2 sentences 2 and 3 BGB.
(2) There is good cause for RR42 in particular if the Customer
a) is in default with the payment of the base fee for two consecutive billing periods or of a not insignificant part of the remuneration, or, over a period extending over more than two billing periods, is in default with an amount that reaches the base fee for two billing periods, and in both cases the arrears amount to at least EUR 100 net; RR42 has previously reminded the Customer of the arrears in text form and set a payment period of at least two weeks (paragraph 1 sentence 2);
b) despite a warning again seriously violates A § 11 para. 5 or Annex A5, in particular removes or misleadingly designs the labelling of the Service as an AI system or cancels, through the configuration, the professional answer limit and the emergency rule;
c) uses the Service for purposes that would constitute a high-risk AI system under Annex III of the AI Act (KI-VO) and does not end such use within a set period;
d) despite a request with a reasonable period set, refuses altogether the conclusion or continued validity of an agreement required under Art. 28 GDPR (DSGVO) or, as a professional secrecy holder, refuses altogether the acceptance of Part B and of the undertaking declaration (Annex 5 to Annex B1) or revokes altogether an undertaking already given, without offering an equivalent agreement. The exercise of rights under Annex B1 or under the General Data Protection Regulation, in particular the objection to a sub-processor, the issuing of instructions, the demand for evidence or audits and the refusal to agree to a change of Annex B1 proposed by RR42, is not good cause; in these cases the rights under § 11 of Annex B1 and under paragraph 3 remain in place;
e) at the time of making its declaration under A § 1 para. 2 knew, or deliberately closed its mind to the realisation, that it is not concluding the contract in the exercise of its commercial or self-employed professional activity. If, without such conduct, it turns out that the Customer is a consumer, this is not good cause within the meaning of this section; in this case the termination of the contract is governed exclusively by A § 1 para. 4, in particular by the period of two weeks regulated there, by the restriction of immediate effect to the cases of A § 1 para. 4 sentence 2 and by the continuation of call answering and the notice on the cancellation of the call diversion under A § 1 para. 4 sentence 3. In both cases paragraph 4 sentence 3 does not apply; RR42 shall refund charges paid in advance for the time after the end of the contract pro rata within 14 days. Mandatory rights of the Customer, in particular under sections 312 et seq. and 355 BGB, remain unaffected in any case.
(3) The list in paragraph 2 is not exhaustive and does not increase the requirements of section 314 para. 1 BGB. There is good cause for the Customer in particular if
a) call answering fails for more than 24 consecutive hours due to a circumstance for which RR42 is responsible, or RR42 falls materially short of the agreed availability in two consecutive calendar months, and in both cases fails to provide a remedy despite a period being set;
b) RR42 uses a sub-processor to which the Customer has validly objected under the Data Processing Agreement, without a reasonable alternative being found;
c) compliance with the duties of confidentiality under Part B is not ensured (B § 2 para. 8);
d) contrary to A § 12 para. 5, audio recordings of calls are produced or stored and RR42 does not demonstrate the deactivation and erasure within a reasonable period set by the Customer;
e) RR42 does not carry out the erasure under A § 26 para. 3 or provide the erasure confirmation within a reasonable period set by the Customer, or does not carry out an instruction of the Customer under Annex B1 despite a period being set;
f) a personal data breach occurs that concerns call content, health data or information subject to professional secrecy, and RR42 does not take without undue delay the measures required for remedy.
A § 8 para. 2 applies to the proof of unavailability.
(4) If the contract is terminated for good cause, the Customer must pay the remuneration until the termination takes effect. RR42 shall refund base fees paid in advance for the time after the termination takes effect, irrespective of who declared the termination and who is responsible for the cause, pro rata within 14 days; usage-based charges are billed until the termination takes effect. If the termination is based on a circumstance for which the Customer is responsible, RR42 may claim compensation for the damage thereby incurred by it in accordance with the statutory provisions; saved expenses and other earnings are to be credited, and the Customer expressly remains entitled to prove that no damage, or only lesser damage, has arisen. Further statutory claims of both parties remain unaffected.
A § 25 Suspension
(1) If the Customer falls into default with the payment of due charges (section 286 BGB) and the arrears reach the amount of the base fee for one billing period, but at least EUR 100 net (A § 24 para. 2 letter a), RR42 may temporarily cease accepting calls for the Customer (suspension) if RR42 has previously threatened the suspension to the Customer in text form to the notification address on file and to the contract contact, has set a payment period of at least two weeks and has in doing so pointed out the consequences of the suspension for the calls diverted to the target number and the possibility of seeking judicial legal protection (A § 7 para. 8). Before the suspension, the payment service provider carries out the provided repeat collection attempts; during this time call answering is not ceased. The suspension always requires a separate declaration by RR42 under sentence 1. In calculating the arrears under sentence 1, amounts are disregarded that the Customer has disputed with substantiation and that RR42 has not substantiated by the itemised statement under A § 16 para. 5 sentence 6 or in another way, as well as amounts based on an incorrect invoice, on a circumstance from the sphere of responsibility of RR42 or of the payment service provider, or on a reduction that has occurred by operation of law. If the arrears remaining on that basis do not reach the threshold of sentence 1, a suspension is excluded. If the Customer disputes the claim only after the threat or after the start of the suspension and the remaining arrears thereupon fall below the threshold of sentence 1, RR42 shall lift a suspension already carried out without undue delay, at the latest within one working day after receipt of the dispute; RR42 bears the burden of proof for the conditions of sentence 1 and for the amount of the arrears relevant under sentence 4. For Customers to whom Part B applies, the additional conditions of B § 7 para. 5 apply.
(2) The suspension is limited to call answering. The Customer's access to the customer account, to call records, transcripts, requests and to the export function remains in place. During the suspension, callers hear exclusively the announcement: "This line is currently unavailable. Please try again later." If RR42 is exceptionally unable to play this announcement on the telephony route used for the Customer, it shall inform the Customer of this in text form in the threat under paragraph 1; the connection then ends without an announcement. Calls arriving at the target number during the suspension are not calls accepted by the Service within the meaning of A § 16 para. 3; their duration is not recorded and not charged. RR42 shall not disclose to callers the reason for the suspension, the name of the Customer, the payment status or the status of the customer account; a different announcement requires the Customer's prior agreement in text form. In the threat under paragraph 1, RR42 shall state to the Customer the earliest possible start and the expected duration of the suspension and point out to it that it should cancel the call diversion for the duration of the suspension.
(3) RR42 shall lift the suspension without undue delay, at the latest within one working day after receipt of the full arrears. If the suspension is based on a payment default for which the Customer is responsible and the conditions of paragraph 1 are met, the Customer remains obliged to pay the base fee; RR42 must credit the expenses that it saves as a result of the suspension, and the Customer remains entitled to prove that RR42 has saved more. The obligation under sentence 2 exists for ten working days at most from the start of the suspension. Periods of a suspension justified under paragraph 1 are, to the extent that the Customer is responsible for the cause, not creditable downtime minutes within the meaning of A § 8 para. 1 (there sentence 6 letter e) and do not give rise to a reduction under A § 15 para. 3; section 537 para. 1 sentence 1 BGB applies accordingly (A § 11 para. 9 sentence 2). In the case of sentence 6, sentence 4 does not apply; the time of the suspension is then a creditable downtime minute within the meaning of A § 8 para. 1, and the reduction under A § 15 para. 3 remains unaffected. If it turns out that the conditions of paragraph 1 were not met in whole or in part, in particular because the claim did not exist or did not exist in the amount asserted, because the threat, the payment period or the notice under paragraph 1 were missing, or because a ground of exclusion under paragraph 1 sentence 4 existed, the base fee lapses pro rata for the duration of the suspension; RR42 shall refund amounts already paid at the latest with the next invoice. RR42 bears the burden of proof for the existence of the conditions of paragraph 1. At the latest upon expiry of the period of sentence 3, RR42 shall decide whether it lifts the suspension or terminates the contract under A § 24, and shall inform the Customer of the decision in text form to the contract contact and to the notification address. If RR42 neither lifts the suspension nor terminates the contract, the base fee lapses pro rata for the time after expiry of the period; RR42 shall refund charges already paid with the next invoice, at the latest within 14 calendar days. If a suspension under paragraph 1 lasts longer than ten working days, the Customer may terminate the contract without observing a period; A § 24 para. 4 applies accordingly. Claims of RR42 to the charges accrued until the start of the suspension and during the period of sentence 3, to default interest and to compensation for default damage remain unaffected. Further rights of the Customer, in particular the reduction under A § 15 para. 3 and damages under A § 20, remain unaffected insofar as they are not based on a suspension justified under paragraph 1 (sentence 4). No suspension or reactivation flat fee is charged. The right to terminate for good cause (A § 24) remains unaffected.
(4) Irrespective of paragraph 1, RR42 may temporarily suspend individual functions or call answering to the extent necessary to avert a concrete danger to the security or integrity of the Service, to data of the Customer or of third parties or to callers, or to comply with a statutory or official obligation. In the case of a suspicion of misuse under the version of Annex A5 incorporated at the conclusion of the contract, based on concrete facts to be communicated to the Customer, a suspension is permissible only if the violation is serious and the danger cannot be averted by a milder means; milder means to be considered are in particular a warning with a reasonable period for remedy, the resetting of the objected configuration under A § 11 para. 5, and the restriction of the affected function alone. The suspension of call answering is always the last resort. RR42 shall inform the Customer without undue delay, where possible in advance, of the reason, scope and expected duration, shall give it, to the extent the danger situation allows, an opportunity to comment within a reasonable period before the suspension, shall limit the measure to the necessary extent and shall lift it without undue delay, at the latest within one working day after the reason has ceased. At the latest after ten working days, RR42 shall decide on lifting the measure or on a termination under A § 24 and shall inform the Customer of the decision in text form. If a suspension under this paragraph lasts longer than five working days, the Customer may terminate the contract without observing a period. A suspension does not release RR42 from responsibility for causes attributable to RR42 or one of its subcontractors.
(5) For the duration of a suspension under paragraph 4, the Customer's obligation to pay the base fee lapses pro rata, unless the suspension is based on a circumstance for which the Customer is responsible; RR42 shall refund charges already paid with the next invoice. If it turns out that the conditions of paragraph 4 were not met, sentence 1 always applies; further claims of the Customer remain unaffected. RR42 bears the burden of proof for the existence of the conditions of paragraph 4.
(6) If a suspension under paragraph 1 or paragraph 4 is carried out rightfully, and RR42 limits it to the necessary extent and lifts it without undue delay after the reason has ceased, at the latest within one working day, it is not a breach of duty by RR42; RR42 is in this case not responsible for the disadvantages typically associated with the temporary cessation of call answering. For damage from an unjustified suspension as well as for damage from the manner in which a suspension is carried out, in particular from a suspension beyond the necessary extent, from a missing or inadequate threat under paragraph 1 and from a delayed lifting under paragraph 3, RR42 is liable in accordance with A § 20. A § 20 para. 1 and the responsibility under paragraph 4 last sentence remain unaffected in all cases; liability for damage from injury to life, body or health, for intent and gross negligence, and liability under mandatory law, in particular under Art. 82 GDPR (DSGVO) and under product liability law, is neither excluded nor limited by this paragraph. The claims under paragraph 5 remain unaffected. RR42 bears the burden of proof that the conditions of the suspension were met and that the suspension, as to threat, scope and duration, complied with paragraphs 1 to 4.
(7) Call answering is ceased because of payment default exclusively in accordance with paragraphs 1 to 3. For other reasons it is ceased or suspended only in the cases expressly regulated in these AGB, in particular under paragraph 4, under A § 12 para. 1 sentence 3, under B § 1 para. 2, B § 2 para. 5 and para. 6, B § 3 para. 1 and under C § 9 para. 5, also in conjunction with A § 3 para. 6; for each such measure, paragraph 4 sentences 4 to 6 and paragraphs 5 and 6 apply accordingly, insofar as nothing more favourable for the Customer is provided there. Events at the payment service provider, in particular a change of the subscription status, the failure of a collection, the end of the repeat attempts and the termination or deletion of the subscription held there, are neither a suspension nor a termination and do not end the contract; the contract ends only by a termination under A § 23 or A § 24. If RR42 ceases call answering without the conditions of paragraphs 1 to 4 or one of the circumstances mentioned in sentence 2 being met, it shall resume it without undue delay, at the latest within one working day after becoming aware, shall inform the Customer in text form of the start, end and cause of the cessation and shall refund the base fee pro rata for the duration of the cessation; further claims of the Customer, in particular under A § 15 para. 3, A § 20 and A § 24 para. 3, remain unaffected. RR42 shall configure the settings of the payment service provider so that, after unsuccessful repeat attempts, the subscription is not terminated but merely marked as unpaid, and so that call answering can be ceased solely by a decision of RR42 under paragraph 1. Suspensions and restrictions of call answering and of individual functions of the Service are governed exclusively by these AGB; deviating or supplementary powers of suspension and restriction in the Annexes, in particular no. 10 of Annex A5, do not apply. For the restriction or suspension of individual functions, paragraph 4 sentences 2 to 7 and paragraphs 5 and 6 apply accordingly, unless A § 11 para. 5, B § 11 para. 3 or another provision of these AGB provides something more favourable for the Customer.
A § 26 End of the contract, data export, erasure, switching
(1) During the contract term, the Customer may at any time retrieve call records per call in the customer account as a PDF file. RR42 keeps the machine-readable version of the call record (JSON) available for the Customer to retrieve per call in the customer account; if a call generates a request, RR42 additionally sends it as an attachment to the notification to the notification address on file. There is no operating mode that restricts the notification to a notice without content referring to the customer account: if the transmission of call content by e-mail is not permissible for the Customer (B § 2 para. 5 sentence 7), it shall not file a notification address; without one, the sending is omitted, and the matter and the call record are available to it in the customer account. RR42 shall point this out to the Customer in text form before going live. Upon request in text form, RR42 shall make the Customer's customer data available to it as a whole, in a structured, commonly used and machine-readable format by a secured route, namely as a JSON file and additionally as a CSV file in accordance with RFC 4180, in each case together with a field description, within ten working days after receipt of the request; RR42 shall communicate the scope, format and retrieval route in text form. Customer data in this sense are the configuration including opening hours, forwarding rules and priority and block lists, the knowledge base, the call records with transcripts and metadata, the captured requests, the user list and the usage and billing records; data of third parties in which the Customer has no rights are not covered. The claim covers only customer data that, under A § 12 para. 6, are still stored at the time of the request. If complete provision is exceptionally not possible within the period, RR42 shall inform the Customer of this before the period expires, stating the reason and a new date; the period is extended by a further ten working days at most. If the Customer requests the provision during the retrieval period under paragraph 2, the latter is suspended until 14 calendar days after complete provision. If RR42 does not provide it on time, it shall not erase the affected data until complete provision; further rights of the Customer remain unaffected. RR42 charges no fee for the provision under this paragraph; the format is governed by sentence 3 and by § 16 para. 5 of Annex B1. RR42 shall also provide the same output, upon the Customer's request in text form, filtered to the data of a data subject designated by it, so that the Customer can respond to that person's request under Art. 15 or Art. 20 GDPR (DSGVO) (Art. 28 para. 3 sentence 2 letter e GDPR (DSGVO)); the periods of sentences 3 and 6 and the free-of-charge provision under sentence 9 apply accordingly.
(2) The retrieval period begins with the end of the contract, in the case of paragraph 6 with the expiry of the transition period regulated there, and is at least 30 calendar days; if several points in time come into consideration for its start, the later one is always decisive. Upon request of the Customer in text form, RR42 shall extend the retrieval period once by up to 30 calendar days. During the retrieval period, RR42 keeps the customer data available for retrieval and export under paragraph 1; the customer account remains accessible to the Customer to the extent required for viewing, retrieval and export, as does the export function; call answering remains ceased. There is no separate read-only state of the customer account; RR42 ensures accessibility during the retrieval period organisationally and makes the provision under paragraph 1 available to the Customer at any time within the period stated there. For the duration of the retrieval period, including an extension, a suspension under paragraph 1 and a transition period under paragraph 6, the period of § 16 para. 2 of Annex B1 is extended accordingly; notwithstanding A § 3 para. 1, paragraphs 1 to 3 and 6 of this section take precedence over Annex B1 insofar as they are more favourable for the Customer. RR42 shall point out to the Customer, at the latest on the first day of the retrieval period and again at the latest ten calendar days before its expiry, in text form to the contract contact and the notification address, the start and end of the retrieval period, the possibility of extension and, prominently, that RR42 will erase the data after expiry if the Customer does not communicate otherwise by then. If the notice under sentence 5 is omitted, the retrieval period begins only upon receipt of the notice given belatedly. The Customer shall inform RR42 in text form by the end of the retrieval period whether it wishes the return or erasure of its data; RR42 shall confirm receipt of the communication. RR42 charges no separate fees for termination, export, retrieval, notice and erasure. RR42 shall not make export, retrieval, notice, return, erasure and erasure confirmation dependent either on payment of outstanding charges or on the settlement of a dispute about charges (A § 18 para. 3 sentence 2). Support with transfer to another system that goes beyond the provision under paragraph 1 is provided by RR42 under a separate agreement.
(3) After expiry of the retrieval period, RR42 shall irrevocably erase the customer data in its production systems and in the systems of the subcontractors used, as well as all copies existing outside the backup copies, within 14 calendar days, and shall confirm the erasure to the Customer, notwithstanding § 16 para. 4 of Annex B1, unprompted and without special request in text form; notwithstanding A § 3 para. 1, this paragraph takes precedence over Annex B1 in this respect. The confirmation states the time of erasure, the data types affected and storage locations, including the systems of the subcontractors used, in particular the telecommunications providers, and the time at which the backup copies will have been overwritten. RR42 shall erase any audio or voice recordings made at a telephony provider within the same period and shall demonstrate this separately. Backup copies are overwritten after the period set in Annex 4 to Annex B1, but at the latest 180 calendar days after the erasure under sentence 1; until then they are not used productively and are kept exclusively for restoration in the event of a disruption. If customer data are restored from a backup copy after the erasure under sentence 1, RR42 shall erase them again within three working days and inform the Customer of this in text form. Statutory retention obligations and billing records without call content remain unaffected; RR42 shall name in the confirmation the data covered by this, the legal basis and the retention period; restricted data are processed only for the retention purpose. If, before expiry of the retrieval period, a party has raised objections to a billing or asserted a claim under this contract and has requested retention in text form, the erasure of those data that are necessary for clarification is suspended, at the longest until the final or amicable conclusion of the dispute; the suspension is limited to the date, start and recorded call duration of the calls taken into account as well as to the billing records, and does not cover call content, transcripts, summaries or callers' telephone numbers. RR42 shall process these data exclusively for this purpose, shall mark them as restricted, shall name them in the confirmation under sentence 1 and shall erase them without undue delay once the purpose ceases. The claim to the itemised statement under A § 16 para. 5 sentence 6 continues to exist for the duration of the suspension.
(4) Upon the end of the contract, the use of the target number ends; it reverts to RR42 (A § 7 para. 9). The target number is a technical endpoint that callers do not dial; the Customer keeps its own telephone number with its provider. RR42 does not owe a transfer of the target number to the Customer or to another provider; a statutory claim to number portability remains unaffected in the event that the Service is to be classified as a telecommunications service (A § 7 para. 8). The Customer shall cancel the call diversion at the latest by the end of the contract. Irrespective of the ordering route, RR42 shall inform the Customer in text form, to the contract contact and to the notification address, of the time at which call answering ends and of the need to cancel the call diversion; the information is given at least ten calendar days before this time if RR42 already knows it at that time, otherwise without undue delay after becoming aware, in the case of a termination by the Customer at the latest with the confirmation under A § 23 para. 4 sentence 4, and in the case of a termination by RR42 with the declaration of termination under A § 23 para. 4 sentence 6; C § 8 also applies accordingly to contracts concluded in text form under A § 4 para. 3. RR42 shall not assign the target number to another Customer for a period of six months after the end of the contract and shall not use it for the Service during that time (quarantine period). A renewed assignment additionally requires that RR42 has monitored the target number for incoming traffic over a continuous period of at least 30 calendar days immediately before the assignment and that no call has arrived in that period; RR42 shall document the result of the monitoring and present it to the former Customer upon request in text form. The monitoring is carried out solely on the basis of the fact of an incoming call; sentence 11 applies to it accordingly. Calls arriving at the target number during the quarantine period are not processed; callers hear exclusively the announcement: "This line is no longer in service." If RR42 is exceptionally unable to play this announcement on the telephony route used, it shall inform the Customer of this in text form together with the information under sentence 5; the connection then ends without an announcement. RR42 does not record, store or use the content, telephone numbers and connection data of such calls and does not forward them. If RR42 assigns the target number to another Customer contrary to sentences 6 and 7, RR42 bears responsibility for the resulting disclosure; it shall indemnify the Customer against claims of third parties and reimburse it for the necessary costs of legal defence and of defence in professional-law, chamber-law, supervisory-law and administrative-fine proceedings that are based on the assignment. A § 20 para. 6 sentence 6 (bearing of a fine by the party against which it is imposed) remains unaffected and does not preclude reimbursement of the procedural costs. The provisions of this paragraph on the target number apply to every target number assigned to the Customer (A § 7 para. 1, A § 16 para. 9).
(5) RR42 is not obliged to hand over its own software, its models, the general system instructions developed by it, its security configurations or rights of third parties. Not covered by this and to be handed over under paragraph 1 are all content entered, uploaded or initiated by the Customer, in particular the configuration, the knowledge base, customer-specific instruction texts including an override of the system instruction made by the Customer, priority and block lists, and the call and request data. The obligations of confidentiality, data protection and observance of professional secrecy under Part B and under the undertaking declaration (Annex 5 to Annex B1) continue to apply without limit in time and regardless of the reason for the end of the contract. The provisions on liability, remuneration and rights of use continue to apply after the end of the contract insofar as their purpose so requires.
(6) RR42 shall not obstruct a switch to another provider or to the Customer's own infrastructure. The Customer need not announce a switch separately; termination under A § 23, for which no notice period applies to the Customer (A § 23 para. 2), suffices. If a minimum term has been agreed under A § 23 para. 5, the announcement period is at most two months. The transition period, during which RR42 supports the switch by the provision under paragraph 1, is 30 calendar days from the end of the contract; at the Customer's request in text form it is extended by the period required due to technical infeasibility, but to no more than seven months. The retrieval period under paragraph 2 follows the transition period under sentence 4; the erasure under paragraph 3 begins at the earliest upon its expiry. RR42 shall inform the Customer in text form of the start and end of the transition period and of the retrieval period as well as of the earliest possible erasure date, determined by calendar date, with the notice under paragraph 2 sentence 5. As long as RR42 has not communicated these dates determined by calendar date, it shall not erase the customer data. RR42 does not charge switching charges.
(7) Paragraphs 1 to 6 apply irrespective of whether the Service is a data processing service within the meaning of Art. 2 no. 8 of Regulation (EU) 2023/2854. Insofar as this Regulation is applicable to the Service, its mandatory provisions take precedence. RR42 keeps the information on the data structures and data formats of the export under paragraph 1 and on the jurisdiction to which the ICT infrastructure used for processing is subject available and up to date at https://www.rr42.de/agb/datenformate; this address is separate from the version archive under A § 3 para. 2 because the register is updated while the archived versions remain unchanged. RR42 shall state the address in the confirmation under A § 4 para. 4. Paragraphs 1 to 6 apply unchanged to the trial period (C § 3, A § 4 para. 5). RR42 does not rely on Art. 31 para. 2 of the Regulation because the Service is provided, also in the trial period, as a production-ready version and with the same standard of care (C § 3 para. 2 sentence 5, para. 3 sentence 1); a notification under Art. 31 para. 3 of the Regulation is therefore not required.
A § 27 Amendment of these AGB
(1) RR42 may amend these AGB and Annex A5 with effect for existing contracts only to the extent necessary to (a) implement changes in statutes, supreme-court case law or requirements of public authorities, in particular in data protection, telecommunications and AI law, or (b) reflect a change to the Service that is permissible under A § 10, and provided the amendment does not shift the relationship between performance and remuneration to the Customer's detriment. Where a provision of these AGB has not become part of the contract or is invalid, only A § 32 para. 5 applies; replacement by RR42 under this section does not take place. This section governs the amendment of these AGB and of Annex A5 exhaustively. Amendment provisions in the Annexes, in particular in the amendment clause of Annex A5, and references in that Annex to the amendment provisions of a Master Service Agreement, do not apply; RR42 has no unilateral right to amend an Annex without the consent under paragraph 4, including for editorial, clarifying or mandatory statutory adjustments. RR42 may make purely editorial corrections without substantive effect, in particular the correction of obvious typographical errors and incorrect cross-references; it shall notify the Customer of them with the next notification under paragraph 3.
(2) Amendments to the principal performance obligations, to the agreed quality including availability under A § 8 para. 1, to the fees, to the provisions on term and termination, to the liability provisions, to the Data Processing Agreement, to Part B including the undertaking under B § 13, to the provisions on the exclusion of emergency calls (A § 6) and on the protective mechanisms (A § 5, A § 11 para. 5), and to this section are excluded to the Customer's detriment. Likewise excluded are amendments to Annex A5 that extend or tighten the Customer's obligations or that extend the grounds entitling RR42 to a block under A § 25 or to termination for good cause under A § 24; for the application of A § 24 para. 2 letter b and A § 25 para. 4, the version of Annex A5 incorporated at the conclusion of the contract shall always prevail unless the Customer has expressly agreed to an amendment. Paragraphs 3 and 4 do not apply to the amendments excluded under sentences 1 and 2; they require an express agreement. Changes to the scope of services are governed by A § 10, changes to Annex B1 by the procedure provided for there. Where a mandatory statutory or regulatory requirement necessitates the amendment of a provision excluded under sentences 1 and 2, RR42 shall offer it to the Customer for express acceptance in accordance with paragraph 4; if the Customer does not accept the offer, either party may terminate the contract without notice period as of the time the statutory requirement takes effect, RR42, however, not before the expiry of a minimum term agreed under A § 23 para. 5. RR42 shall refund remuneration paid in advance for the period after the end of the contract pro rata within 14 days; A § 26 applies.
(3) RR42 shall notify the Customer of the intended amendment at least six weeks before the planned effective date in text form, to the e-mail address of the contract contact stored in the customer account and, if stored, to the second address under A § 30 para. 3. The notification shall contain the amended provisions set against the previous version, the statement of the reason under paragraph 1, the date of the planned effective date and the prominent notice that the amendment will take effect only with the Customer's express consent.
(4) The amendment takes effect when the Customer expressly consents to it in text form or, where RR42 provides a function of the customer account for this purpose, through that function, at the earliest at the start of the second billing period following receipt of the notification; the following applies to such a function: consent declared through it is effective only if, before the declaration is made, the function displays the previous and the new version of the affected provisions side by side, the declaration requires a separate, not pre-selected field, and RR42 confirms the consent to the Customer in text form without undue delay. The Customer's silence does not constitute consent. If the Customer does not consent, the previous version continues to apply; in this case RR42 may terminate the contract by ordinary termination under A § 23 para. 3, but not before the expiry of a minimum term agreed under A § 23 para. 5. On the occasion of the notification, the Customer may terminate the contract until the planned effective date without notice period as of that date; RR42 shall refund remuneration paid in advance for the period after the end of the contract pro rata.
(5) The version currently in force and all earlier versions of these AGB and of the Annexes shall be kept available for retrieval, with version number, date and checksum, at the address stated in A § 3 para. 2.
A § 28 References and publicity
(1) Neither party may publicly use the name, company name, logo or trade marks of the other party as a reference without its prior consent in text form. Information required by law remains permissible.
(2) The Customer may separately permit RR42 in text form to name the Customer's name and logo in customer lists on RR42's website and in presentations. The permission is not a condition for the conclusion of the contract, does not cover any statements about content, key figures or experiences from the cooperation, nor any naming towards the Customer's patients, customers or clients, and may be revoked at any time with effect for the future in text form. After revocation or the end of the contract, RR42 shall cease the naming without undue delay and remove it from all media controlled by RR42 within 14 days. From receipt of the revocation, RR42 shall no longer produce new documents, publications and presentations containing the naming. Materials printed before the revocation may be used up for no longer than three months; if the revocation is based on a ground under professional, data protection, competition or trade mark law or on an objection by a public authority or professional chamber, the use-up period does not apply and RR42 shall withdraw the materials from circulation without undue delay. Where the naming by RR42 has reached third-party media, RR42 shall work towards its removal and shall inform the Customer on request which third parties it has contacted.
(3) Case studies, quotations and testimonials require a separate agreement. The Customer's professional-law restrictions on advertising remain unaffected.
A § 29 Evidence, audits, legal compliance, sanctions
(1) RR42 shall provide the Customer with appropriate evidence of the agreed security and data protection measures, primarily by means of control descriptions, standardised information and, where available, audit reports or certificates. Certifications are owed only if expressly agreed; the obligations under Art. 28 para. 3 letter h GDPR (DSGVO) remain unaffected. Audits by the Customer are governed by § 15 of Annex B1. Each party bears its own costs arising from an audit. By way of derogation, RR42 shall reimburse the Customer for the reasonable and documented costs of an audit if it reveals a material breach of this contract, of Annex B1 or of the General Data Protection Regulation, or if it became necessary because RR42, despite a request setting a reasonable deadline, failed to provide the evidence owed under sentence 1 and under Art. 28 para. 3 letter h GDPR (DSGVO). Further claims for damages remain unaffected.
(2) Each party shall comply with the laws applicable to it. RR42 shall support the Customer, to the contractually agreed extent, with product-related information on the GDPR (DSGVO), on the AI Act (KI-VO) and on the agreed protective mechanisms. RR42 does not owe overall legal compliance of the Customer's operations; RR42 does not provide legal, medical, pharmaceutical or tax advice.
(3) The Customer declares that, to its knowledge, neither it nor the persons holding, directly or indirectly, more than 25 per cent of its shares or controlling it (section 3 GwG) are, at the time of the conclusion of the contract, named on a sanctions list of the European Union under Art. 215 TFEU or on a sanctions list of the United Nations Security Council. It shall verify this before the conclusion of the contract with reasonable effort and shall notify RR42 in text form without undue delay as soon as it becomes aware of any listing. The Customer does not assume any liability going beyond its knowledge. RR42 makes the same declaration for itself and for the persons holding a corresponding interest in it, and ensures that the subcontractors it uses are not subject to any sanctions measure that stands in the way of the performance of the services in accordance with the contract. Each party may terminate the contract for good cause if its continuation would actually violate sanctions or export control law; A § 24 para. 4 applies with the proviso that remuneration paid in advance shall in every case be refunded pro rata.
(4) The Customer shall retain evidence of the controllers it has designated, of the training of the persons dealing with the Service, of approvals granted, of relevant checks and of the handling of escalated matters under A § 11 para. 12 for three years from the end of the calendar year in which the respective matter was concluded; the Customer's statutory retention periods remain unaffected. On request, the Customer shall inform RR42 of the existence and content of this evidence and shall produce it to the extent RR42 needs it to comply with its own statutory or regulatory duty of proof or to defend a claim asserted against it by a third party. There is no duty of production for the defence of claims by the Customer against RR42; the statutory provisions on the burden of presentation and proof and on the production of documents in court proceedings remain unaffected. The Customer shall not produce information that is subject to a duty of confidentiality under section 203 para. 1 StGB (German Criminal Code) or to a statutory right to refuse to give evidence; it shall provide it redacted or in summarised form without personal reference. RR42 shall reimburse the Customer for the reasonable expense associated with the production, and is subject to the same duty of disclosure and production towards the Customer under the same conditions.
A § 30 Form, declarations, notifications
(1) Declarations by the parties in connection with this contract, in particular terminations, notices of defects and objections, require text form (section 126b BGB (German Civil Code)), unless a stricter form is prescribed by law. E-mail suffices. Where the customer account or the customer portal offers a function for the respective declaration, the Customer may also make it there. Annex B1 applies to the Customer's instructions; instructions that, in order to avert a specific risk to the rights and freedoms of data subjects, brook no delay may also be given by the Customer in text form directly to the contact point under A § 14 para. 7 sentence 1 letter c. RR42 shall accept such an instruction, record it in text form with time, content and the declaring person, make it available to the Customer and carry it out without undue delay; the receipt rule of A § 9 para. 2 sentence 3 does not apply to its receipt, and it takes effect upon receipt (section 130 BGB). A human standby service outside support hours exists only to the extent expressly agreed in the order (A § 9 para. 2 last sentence); instructions given outside support hours shall be carried out by RR42 without undue delay after it becomes aware of them, and until then the Customer may at any time itself end the taking of calls for it by cancelling the call diversion to the target number.
(2) Amendments and supplements to the contract require text form. Individually agreed arrangements take precedence over this provision and over these AGB irrespective of their form (section 305b BGB).
(3) The contract contact is the person named by the Customer in the order or in the customer account for contractual and billing matters, together with that person's e-mail address (A § 2 no. 25); if the Customer names no such person, the notification address stored in the customer account takes its place, and if there is none either, the e-mail address of the holder of the customer account. RR42 communicates with the Customer by e-mail to this address. In addition, RR42 may display notifications in the customer account. Legally significant declarations by RR42, in particular terminations, threats of a block, amendment offers under A § 19 and notifications under A § 10 and A § 27, shall always be transmitted by RR42 by e-mail to the address of the contract contact and additionally to a second address named by the Customer, provided it has stored one. A fiction of receipt is not agreed; receipt is governed by section 130 BGB, and RR42 bears the burden of proof for receipt.
(4) The Customer shall keep the contact data stored in the customer account, in particular the e-mail address of the contract contact, the notification address and the billing address, up to date and notify RR42 of changes without undue delay. It shall use reasonable means to ensure that messages from RR42 are not held back by filter or security settings within its sphere of responsibility. These duties of the Customer neither establish an obligation of result as to technical deliverability nor a fiction or presumption of receipt; receipt is governed by section 130 BGB. A fiction or presumption of receipt is not established even in the event of a breach of the duties under sentences 1 and 2; receipt is governed exclusively by section 130 BGB, and RR42 bears the burden of proof. Where the Customer has frustrated receipt in breach of good faith, in particular by leaving RR42 with an address known to it to be no longer reachable or by deliberately blocking messages from RR42, it cannot rely on the lack of receipt under section 242 BGB; simple negligence is not sufficient for this. If RR42 receives a non-delivery notification or has other indications that a legally significant declaration has not reached the Customer, it shall repeat the transmission without undue delay by another means known to it; until then, time limits arising from that declaration do not run.
(5) Declarations by the Customer to RR42 are to be addressed to: RR42 UG (haftungsbeschränkt), Marienstraße 4, 31832 Springe, e-mail: info@rr42.de.
A § 31 Governing law, place of jurisdiction, dispute resolution
(1) The law of the Federal Republic of Germany applies to this contract and to all disputes arising out of or in connection with it, excluding the United Nations Convention on Contracts for the International Sale of Goods (CISG) and the rules of private international law that would lead to the application of another legal system.
(2) If the Customer is a merchant, a legal entity under public law or a special fund under public law, the Amtsgericht Springe (local court) has exclusive jurisdiction for actions by the Customer against RR42 arising out of and in connection with this contract; if the amount in dispute exceeds its jurisdiction under section 23 no. 1 GVG or if the Landgericht (regional court) has subject-matter jurisdiction, the Landgericht Hannover takes its place (section 38 para. 1 ZPO). RR42 may, at its choice, bring an action before these courts or at the Customer's general place of jurisdiction. If a Customer who is not a consumer has its seat in another Member State of the European Union, sentence 1 also applies where it is not a merchant; to that extent the agreement is based on Art. 25 of Regulation (EU) No 1215/2012, the formal requirement of which is satisfied by the electronic consent under C § 1 para. 3 and C § 4 para. 1 and the storage of the contract text under C § 4 para. 4 (Art. 25 para. 2 of the Regulation). If the Customer satisfies neither the requirements of sentence 1 nor those of sentence 3, the statutory places of jurisdiction remain; this applies in particular to physicians, dentists, lawyers, tax advisers and other members of the liberal professions who are not merchants (section 1 HGB (German Commercial Code)). Mandatory statutory places of jurisdiction remain unaffected. A § 1 para. 3 applies to Customers with their seat outside the Federal Republic of Germany.
(3) The parties do not agree on a contractual place of performance.
(4) RR42 is neither willing nor obliged to participate in dispute resolution proceedings before a consumer arbitration board within the meaning of the Consumer Dispute Resolution Act (Verbraucherstreitbeilegungsgesetz). No arbitral tribunal is agreed.
A § 32 Assignment, transfer of the contract, language, interpretation, severability clause
(1) The Customer may assign, pledge and transfer for collection monetary claims of the Customer against RR42 without consent; section 354a HGB remains unaffected. In this case, the protection of RR42 as debtor is governed by sections 404, 406 to 410 BGB. Otherwise, the Customer may transfer its position as a contracting party, the rights of use arising from this contract and its legal position under the Data Processing Agreement to third parties only with the prior consent of RR42 in text form. RR42 shall decide on the consent within two weeks after receipt of the request in text form; consent may be refused only for a material reason, in particular if the third party does not enter into the obligations under this contract and under the Data Processing Agreement or, in the case of Part B, does not give the undertaking under B § 13. If RR42 does not object in text form, stating its reasons, within the time limit, the consent is deemed given. In the case of a transfer of the contract by universal succession and in the context of the takeover of the Customer's business, practice, pharmacy or law firm by a successor, the consent is deemed given as soon as the successor has declared to RR42 in text form its entry into the obligations under this contract and under the Data Processing Agreement and, in the case of Part B, the undertaking under B § 13; the Customer shall notify RR42 of the transfer in text form without undue delay. Paragraph 2 applies to a transfer by RR42.
(2) RR42 may transfer the contract as a whole to the legal successor in the context of a conversion or other universal succession. A transfer by way of singular succession, in particular in the context of a transfer of the business operations, requires the Customer's consent in text form; consent may not be unreasonably refused. In both cases, RR42 shall notify the contract contact and, if stored, the second address under A § 30 para. 3 of the transfer in text form at least six weeks in advance, shall name the transferee with company name, address and register, and shall in the same notification point out to the Customer, in a prominent manner, its right of termination under sentence 6, the time until which it may be exercised and the pro rata refund of remuneration paid in advance. The transfer requires that the transferee enters into the obligations under this contract and under the Data Processing Agreement and that, before any access by the transferee to the Customer's data, RR42 demonstrates to the Customer that the transferee complies with the technical and organisational measures at least to the previous extent. If the Customer is a professional secrecy holder, the transferee may obtain access to secrets only after the Customer has obliged it in text form to secrecy under section 203 para. 4 sentence 2 no. 1 StGB; until then access remains blocked. The Customer may terminate the contract until the transfer takes effect without notice period as of the time of transfer; RR42 shall refund remuneration paid in advance pro rata. RR42 remains liable, alongside the transferee, for breaches of duty established before the transfer. If the notice under sentence 3 is omitted or is incomplete or not prominent, the period under sentence 6 does not begin to run; in this case the Customer may still terminate the contract without notice period within four weeks after receipt of a notice supplied subsequently that meets the requirements of sentence 3, but at the latest until the expiry of six months after the transfer. In this case too, RR42 shall refund remuneration paid in advance for the period after the end of the contract pro rata within 14 calendar days.
(3) The contract language is German. If RR42 provides translations of these AGB or of the Annexes, they serve for information only; in the event of discrepancies, the German version prevails.
(4) The headings of these AGB serve for overview; they neither extend nor restrict the content of the respective provision. Section 305c paras. 1 and 2 BGB remain unaffected.
(5) If individual provisions of this contract have not become part of the contract or are invalid, the contract remains effective in all other respects. The statutory provisions take the place of the provision that has not been incorporated or is invalid (section 306 para. 2 BGB). Section 306 para. 3 BGB remains unaffected.
Part B – Special Terms for Professional Secrecy Holders
B § 1 Scope of application and precedence
(1) This Part B applies if the Customer or the persons for whom it uses the Service are subject to a statutory duty of confidentiality under section 203 para. 1 StGB, in particular pharmacies, medical and dental practices, medical care centres, members of other state-regulated healthcare professions, lawyers, patent attorneys, tax advisers, tax agents, auditors, sworn auditors and their professional practice companies (“professional secrecy holders”). The Service is not offered to notaries; RR42 asks about this during set-up under C § 1 para. 3 and rejects the order. If the Customer selects the sector “Apotheke” (pharmacy) in the customer account, the query is omitted; this does not change the exclusion. If a contract with a notary nevertheless comes into being, either party may terminate it on two weeks' notice; RR42 shall refund the base fee paid for the current billing period pro rata. Until termination, this Part B applies without restriction.
(2) Part B applies as soon as and for as long as the conditions of paragraph 1 are objectively met; RR42's knowledge is irrelevant. Before activation, the Customer shall inform RR42 whether it is a professional secrecy holder and shall notify any later change without undue delay; this notification is an obligation of the Customer in its own interest and not a condition for the applicability of this Part B. If it is not given, RR42's obligations under B § 2 nevertheless remain in place; the obligations under B § 3 arise in that case only upon knowledge. If RR42 recognises or must recognise that the Customer is a professional secrecy holder, it shall apply Part B even without notification and shall obtain the obligation under B § 2 and the declaration under Annex 5 to Annex B1 without undue delay; if the Customer does not cooperate in this within two weeks of a request, RR42 may suspend the taking of calls after prior notice in text form. For this suspension, A § 25 para. 4 sentences 4 to 6 and A § 25 paras. 5 and 6 apply accordingly (A § 25 para. 7 sentence 2); in particular, RR42 shall decide in text form within ten working days at the latest on lifting the measure or on termination under A § 24, the Customer may terminate the contract without notice period if the suspension lasts longer than five working days, whereby remuneration paid in advance shall be refunded pro rata, and RR42 bears the burden of proof that the conditions are met. The base fee lapses pro rata for the duration of the suspension, unless it is based on a circumstance for which the Customer is responsible; its pro rata lapse takes the place of a reduction under A § 15 para. 3, and a suspension whose reason the Customer is responsible for is not a countable minute of downtime within the meaning of A § 8 para. 1 (A § 8 para. 1 sentence 6 letter e). The brand under which the Service is ordered and the sector selected in the customer account are irrelevant for the applicability of this Part B; the sector alone determines whether RR42 makes the query under paragraph 1.
(3) Part B takes precedence over Part C and Part A. The Data Processing Agreement (Annex B1) takes precedence over Part B for all data protection questions within the meaning of A § 12 para. 2; the undertaking (Annex 5 to Annex B1) takes precedence over Part B for the content, form and proof of the confidentiality obligation. However, both take precedence over Part B only to the extent that they do not fall short of the commitments in this Part B; if they fall short of them, the provisions of this Part B apply, and RR42 cannot rely on the deviating version of the Annex. In all other respects, Part B takes precedence over the Annexes; this applies in particular to the description of the Service, its intended purpose and its limits (B § 5 to B § 8), to the statements on the AI Regulation (B § 10) and to the statements on sound recordings (B § 12 para. 3). If an Annex contains a deviating or more extensive statement on these matters, the provision of this Part B applies; RR42 shall align the Annexes without undue delay. For Customers who fall under this Part B, Annex B1 shall always be concluded including its section on professional secrecy and including Annexes 5, 5a and 5b; a version of Annex B1 in which these provisions are missing, apply only conditionally or are described as dispensable shall not be used towards professional secrecy holders.
B § 2 Confidentiality and obligation under section 203 StGB
(1) In providing the Service, RR42 acts as another person contributing to the service within the meaning of section 203 para. 3 sentence 2 StGB. RR42 hereby undertakes towards the Customer not to disclose without authorisation, and not to exploit without authorisation, third-party secrets that become known to it or its employees in the exercise of, or on the occasion of, this activity. This obligation is unlimited in time and continues beyond the end of the contract.
(2) RR42 has been instructed that unauthorised disclosure under section 203 para. 4 sentence 1 and para. 6 StGB and unauthorised exploitation under section 204 StGB are punishable offences. The wording of sections 203 and 204 StGB is attached as Annex 5b to Annex B1.
(3) RR42 shall obtain knowledge of third-party secrets only to the extent necessary for the performance of this contract. Access by RR42's employees to call content takes place only on specific occasions, for the remedying of faults or on the Customer's instruction. RR42 shall record each such access with time, accessing person, matter concerned and reason, and shall, on request, produce the records concerning the Customer to the Customer in text form within ten working days free of charge. As long as the recording under sentence 3 is technically not carried out throughout, RR42 shall inform the Customer of this in text form before activation and thereafter without undue delay, shall document each access in another way, shall name the time of the technical implementation and shall produce the documentation under sentence 3; in this case the Customer may terminate the contract without notice period, and the remuneration for the current billing period shall be refunded pro rata. Use of call content for RR42's own purposes, in particular for the training or improvement of AI models, for analysis purposes or for disclosure to third parties, does not take place.
(4) RR42 shall oblige all employees who may obtain access to secrets, in text form, to secrecy and shall instruct them on the criminal-law consequences of a breach of duty before they obtain access.
(5) RR42 is entitled to engage subcontractors and further persons contributing to the service to perform the contract; for this purpose it shall use exclusively providers that are identified in Annex 3 to Annex B1 with company name, seat, place of processing, subject matter of the service and extent of possible access to secrets. RR42 shall keep Annex 3 complete and up to date; in particular, it shall also list there the providers via which call content, structured requests or handover summaries are sent, delivered or temporarily stored, as well as all providers used for the language model, speech recognition and speech synthesis. If RR42 uses a provider not identified in Annex 3, this is a material breach of contract. Before the first access, RR42 shall oblige each subcontractor and each further person contributing to the service who may obtain access to secrets, in text form, to secrecy and shall instruct them on the criminal-law consequences of a breach of duty; the obligation must correspond at least to paragraphs 1 to 3 and must bind the authority to engage further persons to the same obligation (section 43e para. 3 sentence 1 no. 3 BRAO (Federal Lawyers' Act), section 62a para. 3 sentence 1 no. 3 StBerG (Tax Advisers Act)). The status of the obligation per subcontractor and per further person contributing to the service is shown with date in Annex 5a to Annex B1. As long as the obligation of such a person is not available in text form or the person is not identified in Annex 3, RR42 shall not use that person for Customers under B § 1; if the provision of the Service is not possible without that person, RR42 shall not activate the Customer and shall not take calls for the Customer, and for an already activated Customer RR42 shall discontinue the processing concerned without undue delay or replace the person with an identified and obliged person. RR42 shall transmit call content, structured requests and handover summaries by e-mail only via services identified in Annex 3 and obliged under sentence 4; otherwise it shall limit the notification to a content-free notice referring to the customer account. A decision by the Customer on the use of a person who is not identified or not obliged is not agreed; a notice from RR42 replaces neither the inclusion in Annex 3 nor the obligation and does not release RR42 from its duties under section 203 para. 4 sentence 2 no. 2 StGB. If RR42 breaches this paragraph, the Customer may terminate the contract without notice period; the remuneration for the current billing period shall be refunded pro rata, and further claims remain unaffected. For a discontinuation or suspension of the taking of calls under sentence 6, A § 25 para. 4 sentences 4 to 6 and A § 25 paras. 5 and 6 apply accordingly (A § 25 para. 7 sentence 2); the base fee lapses pro rata for its duration. If the measure is based on RR42 having failed to create the conditions of this paragraph, it shall always be deemed to be attributable to RR42; in this case the Customer may additionally claim damages under A § 20.
(6) RR42 shall use subcontractors and further persons contributing to the service outside the European Union and the European Economic Area only if they are identified in Annex 3 to Annex B1 with company name, seat, specific place of processing and transfer instrument, and if RR42 has, before use, examined and documented that the protection of the secrets existing there is comparable to the protection in Germany. As long as any of this information is missing for a provider or is marked in Annex 3 only as to be confirmed, RR42 shall not use that provider for Customers under B § 1; paragraph 5 sentence 6 applies accordingly. Before activation and before any change, RR42 shall provide the Customer, unprompted and in text form, with: company name, seat, place of processing, categories of accessible data, transfer instrument including supplementary measures, the transfer impact assessment, the status of the obligation under paragraph 5, and the result of its examination under sentence 1 with the principal considerations. The Customer's own duty of examination and documentation under section 43e para. 4 BRAO or section 62a para. 4 StBerG remains unaffected to the extent it applies to the Customer; it does not relieve RR42, does not limit RR42's responsibility under paragraphs 1 to 5 and under A § 20, and does not establish contributory fault of the Customer to the extent its decision is based on incomplete, late or incorrect information from RR42. If the Customer requests in text form that secrets be processed exclusively within the European Union and the European Economic Area, RR42 shall inform it in text form within ten working days whether and on what conditions it can offer this; if it cannot, the Customer may terminate the contract without notice period, and the remuneration for the current billing period shall be refunded pro rata. For a discontinuation or suspension of the taking of calls under sentence 2 in conjunction with paragraph 5 sentence 6, A § 25 para. 4 sentences 4 to 6 and A § 25 paras. 5 and 6 apply accordingly (A § 25 para. 7 sentence 2); the base fee lapses pro rata for its duration, and the measure shall always be deemed to be attributable to RR42 if it is based on RR42 having failed to create the conditions of this paragraph.
(7) RR42 shall notify the Customer in text form of the addition or replacement of a subcontractor at least 30 calendar days before it takes effect, naming company name, seat, place of processing, subject matter of the service, transfer instrument, the extent of possible access to secrets and the status of the obligation under paragraph 5 (§ 11 of Annex B1). The Customer's right to raise justified objections is governed by § 11 of Annex B1 and is not curtailed by this Part B; grounds under professional law, in particular a missing obligation under paragraphs 4 and 5 or a non-comparable protection of secrets under paragraph 6, are always a justified objection. After an objection, RR42 shall not use the subcontractor concerned for that Customer as long as the objection has not been resolved, to the extent technically possible; it shall set out to the Customer in text form without undue delay whether, and with what effort, the Service can be provided without the subcontractor concerned. If no reasonable solution is found within 30 calendar days after receipt of the objection, the Customer may terminate the contract without notice period. In this case, RR42 may terminate only under A § 23 para. 3, unless it has demonstrated with reasons under sentence 3 that continued operation without the subcontractor is technically not possible; in that case RR42 too may terminate with effect as of the time of the change. In all cases, the remuneration for the current billing period shall be refunded pro rata.
(8) On request, RR42 shall produce to the Customer the undertakings under paragraphs 4 and 5 and the register under Annex 5a to Annex B1 and shall provide the information necessary for the examination under section 43e para. 2 BRAO and section 62a para. 2 StBerG. If compliance with paragraphs 1 to 6 is not ensured, the Customer may terminate the contract without notice period; the remuneration for the current billing period shall be refunded pro rata.
(9) RR42 shall disclose the Customer's secrets to authorities, courts and other bodies only to the extent it is obliged to do so under the law of the European Union or of a Member State. RR42 shall comply with a demand of an authority or court of a third country only to the extent that an international agreement within the meaning of Art. 48 GDPR (DSGVO) supports it; no voluntary disclosure takes place. RR42 shall inform the Customer of every request for information, disclosure or seizure without undue delay, at the latest within 24 hours of becoming aware of it, unless it is prevented from informing by an order under the law of the European Union or of a Member State; in that case it shall inform the Customer as soon as the obstacle ceases to apply and shall document the obstacle. RR42 shall point out the Customer's duty of confidentiality to the requesting body, shall assert existing rights to refuse to give evidence and prohibitions of seizure (sections 53, 97 StPO (German Code of Criminal Procedure)), shall apply, where possible, for suspensive effect and shall give the Customer the opportunity to assert its rights itself; RR42 bears the costs of these measures. RR42 shall oblige its subcontractors and the further persons contributing to the service accordingly. If RR42 breaches sentences 1 to 5, this is a breach of an essential contractual obligation; A § 21 para. 3 applies accordingly to third-party claims based thereon, and the Customer's rights under A § 15 and A § 20 remain unaffected.
(10) The obligation under this section is confirmed by the declaration under Annex 5 to Annex B1 signed by RR42. It exists alongside and independently of the obligations under Annex B1.
(11) Compliance with professional secrecy under paragraphs 1 to 6 is an essential contractual obligation within the meaning of A § 20 para. 2 sentence 2. Losses of the Customer arising from its breach, in particular claims by the persons whose secrets were disclosed, costs of notification under Art. 34 GDPR (DSGVO), costs of legal defence and costs of professional-law and supervisory proceedings, are foreseeable consequences typical of the contract within the meaning of A § 20 para. 2 sentence 4. For them, the maximum amount of A § 20 para. 3 letter d, separately determined for Customers to whom this Part B applies, applies; it is set so that it covers the loss foreseeable and typical for the contract, and is to be reconciled with the scope of cover of RR42's liability insurance (A § 20 para. 3 letter e). The maximum amounts of A § 20 para. 3 do not apply to the extent RR42 has engaged a subcontractor or a further person contributing to the service contrary to paragraph 5 without identification in Annex 3 to Annex B1 or without an obligation in text form, or has disclosed secrets contrary to paragraph 9. A § 20 para. 1 and para. 6 remain unaffected.
B § 3 Time of the obligation; activation
(1) RR42 will not assign a target number to the Customer or accept calls until the Customer has accepted this Part B and the Data Processing Agreement (Annex B1), including Annex 5, in text form and RR42 has provided the declaration pursuant to Annex 5 countersigned. This also applies to the trial period.
(2) The Customer will not set up the call diversion to the target number before the conditions of paragraph 1 are met.
(3) RR42 records the acceptance pursuant to paragraph 1 with the version, the time and the declaring person, and makes the documents available to the Customer, together with the confirmation pursuant to A § 4 para. 4, as printable and storable files so that the Customer can furnish its proof pursuant to section 203 para. 4 sentence 2 no. 1 StGB (German Criminal Code) and, where applicable, section 43e para. 2 BRAO (Federal Lawyers' Act) or section 62a para. 2 StBerG (Tax Advisers Act).
B § 4 Professional-law responsibility of the Customer
(1) The Customer remains responsible for compliance with its professional rules, in particular for preserving its duty of confidentiality, for the careful selection and supervision of RR42 as service provider, for assessing the necessity of the disclosure (section 203 para. 3 sentence 2 StGB, section 43e para. 1 BRAO, section 62a para. 1 StBerG) and for documenting its selection decision. RR42 owes no legal advice and no professional-law advice to the Customer. RR42's duties to inform, to submit documents and to provide information pursuant to B § 2 para. 3, para. 5, para. 6 and para. 8, pursuant to B § 10 para. 1 and para. 2 and pursuant to A § 12 para. 2 last sentence remain unaffected; RR42 shall make available to the Customer in text form, unprompted, before activation and thereafter upon every change, the information from its area of responsibility that the Customer needs for its decision on selection, supervision and documentation, and shall answer queries in this regard in text form within 20 working days. The Customer's responsibility pursuant to sentence 1 does not limit RR42's liability and does not give rise to any contributory fault on the part of the Customer insofar as the Customer's decision is based on incomplete, late or incorrect information from RR42.
(2) The Customer shall ensure that callers whose secrets become accessible to the Service are informed about the use of the Service in accordance with the rules applicable to the Customer. RR42 provides sample texts for this purpose (A § 12 para. 7; document C3 section 13), the use of which is the Customer's responsibility.
(3) Where the use of the Service serves a single client matter directly, the Customer shall obtain the required consent of the client (section 43e para. 5 BRAO, section 62a para. 5 StBerG). The Service is designed as general operational infrastructure that accepts the calls of the entire business.
(4) The Customer shall examine on its own responsibility whether the use of the Service is compatible with its obligations under professional law, pharmacy law, statutory health insurance physician law and chamber law, and shall reflect the use in its quality management insofar as its professional rules so require.
B § 5 No pharmaceutical, medical, legal or tax advice
(1) The Service accepts calls, answers organisational questions from content approved by the Customer (opening hours, address, accessibility, approved standard notices), captures enquiries as non-binding requests and forwards calls to the forwarding destination. It does not provide information or advice on medicinal products or medical devices within the meaning of section 20 ApBetrO (Pharmacy Operation Ordinance), no medical advice or treatment, no legal services and no assistance in tax matters.
(2) The Customer shall not use or configure the Service in such a way that it makes statements on the effect, use, dosage, side effects or interactions, suitability, interchangeability, reimbursement or dispensing of medicinal products, on diagnoses, symptoms or therapies, or on individual legal or tax questions. Such enquiries are captured and passed to the Customer's authorised personnel or marked with a callback notice.
(3) The Customer organises information and advice through its pharmaceutical or otherwise professionally authorised personnel itself; for pharmacies this follows from section 20 para. 1 and section 3 para. 5 ApBetrO, and for the other professional secrecy holders from the professional rules applicable to them in each case. Callers bear no costs for the Customer's advice beyond the usual connection charges; the target number is not a special-rate number.
(4) Requests captured by the Service, in particular prescription, pre-order, referral, appointment and courier service requests, are requests to the Customer. They do not constitute acceptance, reservation, or a promise of delivery or dispensing. The examination of prescriptions (section 17 para. 5 ApBetrO) and the decision on dispensing, courier service and substitution are made exclusively by the Customer. The cross-check carried out by the Service of recognised medicinal product names is a check of the speech recognition, not a professional examination.
(5) The research function (A § 5 para. 14) is addressed exclusively to the Customer's professionally authorised personnel and is not part of the conversation with callers. It reproduces the content of published literature with a source reference and makes no statement on the individual case; it replaces neither the advice pursuant to paragraph 3 nor the professional examination by the Customer's personnel, and the Customer does not pass on its result to callers as information from the Service. The outputs of the research function are based on a probabilistic method (A § 5 para. 4); RR42 does not promise that every source reference is relevant, complete or correctly reproduced.
B § 6 Statements on stock, availability and prices; Medicinal Products Advertising Act
(1) Subject to paragraph 5, the Service does not state or confirm stock levels, delivery availability, delivery times or prices of medicinal products or medical devices. Questions about these are captured as a request and passed to the Customer's personnel. Approval of such information requires a separate agreement in text form, a connected data source and a prior professional and advertising-law review.
(2) RR42 shall ensure that its advertising and its pre-contractual information do not hold out information pursuant to paragraph 1, and shall draw the Customer's attention to paragraph 1 prominently and in text form before the Customer places its order. If the Customer concluded the contract in reliance on a statement by RR42 holding out information excluded under paragraph 1, the Customer may terminate the contract without observing a notice period within four weeks of becoming aware of it; remuneration already paid will be refunded pro rata temporis. A § 5 para. 9 sentence 2 and sentence 3 remain unaffected and take precedence over this paragraph; statutory claims of the Customer on account of incorrect pre-contractual information likewise remain unaffected.
(3) The Customer is responsible for the content it provides and approves (knowledge base, greeting, standard notices) and shall ensure that it complies with the provisions of the Medicinal Products Advertising Act (Heilmittelwerbegesetz), medicinal product pricing law and competition law as well as its professional rules; in particular, it shall not store any content that extols medicinal products, treatments or procedures, advertises prescription-only medicinal products to callers (section 10 HWG) or is misleading (section 3 HWG). RR42 is responsible for the standard content it provides, for the system prompt it specifies, for the tool set and for the protective mechanisms, as well as for Customer content that RR42 has altered without the Customer's approval; A § 11 para. 1 sentences 4 to 6 apply without restriction also to Customers subject to this Part B. If the Service reproduces approved content of the Customer in abridged form, with its meaning distorted or supplemented by information that has not been stored, the output is not a declaration of the Customer; the Customer's responsibility pursuant to sentence 1 does not extend to such outputs.
(4) The answering of a specific organisational enquiry by a caller from approved content remains unaffected.
(5) Paragraph 1 does not preclude the reproduction of general operating procedures of the Customer's business that the Customer has approved, for example the time by which orders or prescriptions received are regularly made ready for collection on the same day, or a note that the Customer will send further details by e-mail (Annex A5 no. 7 paragraph 4). The Service reproduces such statements as a general rule of the Customer and not as a promise, confirmation or information about a specific order, a specific prescription or a specific medicinal product; it continues to take up questions about the status of a specific order or the availability of a specific medicinal product as a request (paragraph 1 sentence 2). The Customer words such statements as a general rule without any guarantee for the individual case and ensures in accordance with paragraph 3 sentence 1 that they comply with the provisions mentioned there.
B § 7 Readiness for service and out-of-hours service (pharmacies); accessibility of medical practices
(1) The Service does not replace the pharmacy's readiness for service pursuant to section 23 ApBetrO or the personal accessibility of the pharmacy manager or a person authorised to act as deputy. During readiness for service, in particular during out-of-hours service, the Customer shall take the measures possible and reasonable for it so that callers can reach the pharmacy on duty and the responsible person; for this purpose it maintains the standby times in the configuration, approves forwardings for these times (A § 11 para. 3) and keeps the forwarding destination staffed, or it cancels the call diversion for the duration of the readiness for service. RR42 is responsible for the Service executing approved forwardings within the configured standby times, and shall draw the Customer's attention to this paragraph in text form before activation and upon every change to the opening-hours configuration. The Customer has no duty to be liable for disruptions of the Service; A § 21 para. 2 applies in this respect only to a breach of the duty pursuant to sentence 2. No assurance is given that no call will be lost.
(2) The Customer is advised that the Service forwards calls only within the configured opening and standby times or where approved pursuant to A § 11 para. 3. Outside these times the Service tells callers that the Customer is not available, takes down their concerns and, in the case of emergency indications pursuant to A § 6 para. 3, refers them to public emergency call channels; it does not name any particular out-of-hours pharmacy.
(3) A Customer operating a medical practice, a medical care centre or a comparable facility shall take the measures possible and reasonable for it so that callers outside consultation hours are referred to the medical on-call service (116117) and, in emergencies, to the rescue service (112); for this purpose, the greeting text, the maintenance of consultation and standby times, the forwarding approval pursuant to A § 11 para. 3, the cancellation of the call diversion and its own channels are available to it. RR42 is responsible for the Service issuing these notices according to the logic described in A § 6 para. 3, and shall inform the Customer in text form before activation and upon every change in which call flows the Service does not issue the notices. The Customer has no duty to be liable beyond sentence 1 for the content, timing and completeness of the Service's announcements; A § 21 para. 2 applies in this respect only to a breach of the duty pursuant to sentence 1.
(4) The Customer reflects the use of the Service, including the taking over of captured requests, the review of transcripts before pharmaceutical or medical actions and the switching for readiness for service, in its quality management system (section 2a ApBetrO) or in accordance with the requirements applicable to it.
(5) A suspension of call acceptance pursuant to A § 25 para. 1 additionally requires, in relation to Customers to whom this Part B applies, that RR42 announces the start of the suspension, after expiry of the payment period, at least five working days in advance in text form to the contract contact and to the notification address, and in doing so points out the effects on the accessibility of the business and the need to cancel the call diversion. The start of the suspension is not placed at a time at which, according to the times stored in the customer account, a readiness for service, an emergency service or an on-call service exists; it is postponed to the next time outside these times. If no such times are stored, the suspension begins at the earliest on a working day at 18:00. A suspension pursuant to A § 25 para. 4 remains permissible but must be limited to the specific danger; in this case RR42 shall inform the Customer without undue delay by telephone and in text form. In all other respects A § 25 applies unchanged.
B § 8 Emergencies and urgency
(1) The Service is not intended to assess or classify emergency calls, to alert, dispatch or prioritise emergency or rescue services, or to rank callers by urgency, severity or need for treatment. It is not an emergency call system and does not establish a connection to rescue services (A § 6 para. 1).
(2) The Service may mark a handover as an emergency if the language model recognises in callers' statements indications of an acute danger to life, limb or mental well-being (A § 6 para. 2). This marking has the sole effect that the forwarding to the forwarding destination is initiated without follow-up questions and regardless of the high-load mode. It is not a medical assessment, does not establish any order between callers and does not trigger any alert. The marking is based on a probabilistic method (A § 5 para. 4); it may not occur or may be set incorrectly. RR42 does not promise that every emergency will be recognised or that every marking will be correct; the Customer may not rely on the marking as the sole safeguard and shall set up the same human follow-up process for marked and unmarked handovers. If forwarding is not possible because the Customer has not approved forwarding for the relevant time, the Service names to callers, in accordance with A § 6 para. 3 sentence 1, the public body provided for the situation described (telephone counselling service, rescue service 112 or medical on-call service 116117) and asks them to dial it themselves. If a handover marked as an emergency does not materialise for any other reason, in particular because the forwarding destination is not reached, the person reached there refuses to take over the call (A § 7 para. 5 sentence 6), no forwarding destination or no reachable forwarding destination is stored, or the connection used technically does not support forwarding, the Service nevertheless names to callers the public body provided for under sentence 6 and asks them to dial it themselves; only thereafter does it tell them that it cannot transfer the call, and captures the concern (A § 6 para. 3 sentence 3). If the emergency marking is absent or a forwarding does not materialise for one of the reasons named in sentence 7, the Service tells callers that it cannot transfer the call, points out to them, irrespective of the emergency marking and irrespective of the course of the conversation, that in an emergency they can themselves dial the emergency number 112 and, if the Customer operates a pharmacy, a medical practice or another facility of medical or dental care, outside consultation hours the medical on-call service 116117, and captures the concern; naming a particular body relating to the situation described pursuant to sentence 6 is not owed in this case (A § 6 para. 3 sentence 4). A § 6 para. 3 sentences 5 and 6 and A § 20 para. 1 remain unaffected.
(3) The Customer shall configure a reachable forwarding destination and set up a human follow-up process for handovers marked as an emergency. In its own communication to callers (website, notice, greeting text, announcement before the diversion) it shall not create the impression that the Service assesses the urgency of a concern, always puts urgent calls through, or replaces an emergency call. The same duty applies to RR42 for the announcements and standard content it specifies and for its advertising; it shall amend statements that contradict this paragraph without undue delay after becoming aware of them. The Customer may use the Service during an emergency or on-call service only if forwardings are approved for that time and the forwarding destination is staffed (B § 7 para. 1).
B § 9 Health data, legal basis, data protection impact assessment
(1) The Customer is the controller within the meaning of the GDPR (DSGVO); RR42 is the processor in accordance with Annex B1. The accrual of health data and of data subject to professional secrecy is the normal case with this Service.
(2) The Customer determines the legal basis for the processing of special categories of personal data itself. For pharmacies, medical and dental practices, medical care centres and members of other state-regulated healthcare professions, Article 9 para. 2 letter h GDPR in conjunction with section 22 para. 1 no. 1 letter b BDSG (German Federal Data Protection Act) will regularly come into consideration; for lawyers, patent attorneys, tax advisers, tax agents, auditors and sworn accountants, Article 9 para. 2 letter f GDPR and the special provisions applicable to them in particular come into consideration. These notes are not legal advice and do not bind the Customer. If a legal basis chosen by the Customer requires that the processing be carried out by persons, or under the responsibility of persons, who are subject to a duty of secrecy, RR42 establishes this duty of secrecy by B § 2 and the declaration pursuant to Annex 5 to Annex B1; RR42 guarantees that the conditions of B § 2 para. 4 and para. 5 are met for all persons and bodies involved in the processing, and shall demonstrate this to the Customer in text form upon request.
(3) The Customer is advised that the use of an AI system to control interaction with callers regularly requires a data protection impact assessment under no. 11 of the Data Protection Conference list on Article 35 para. 4 GDPR (version 1.1 of 17.10.2018) and, in the case of health data, under Article 35 para. 3 letter b GDPR. Performance and responsibility lie with the Customer. RR42 provides a pre-filled working template and the product-related information required for the assessment (section 14 para. 2 of Annex B1).
B § 10 AI Act: roles, competence, transparency
(1) The Service is an AI system within the meaning of the AI Act (KI-VO). RR42 is the provider, the Customer the deployer (Article 3 nos. 3 and 4 AI Act). RR42 has assessed the Service on the basis of the intended purpose described in these AGB and does not classify it as a high-risk AI system under Article 6 in conjunction with Annex III of the AI Act; RR42 shall provide the Customer with the classification and its rationale in text form before activation and thereafter upon request. For as long as this classification applies and the Customer uses the Service within the intended purpose, the deployer obligations of Articles 26 and 27 AI Act do not apply to the Customer. RR42 reviews the classification upon every change to the intended purpose, the Service or the legal position, and shall inform the Customer of a changed classification without undue delay in text form. If the review or a decision of an authority shows that the Service is a high-risk AI system, RR42 shall provide the Customer without undue delay and at no additional charge with the information required to fulfil the deployer obligations; in this case the Customer may terminate the contract without observing a notice period with effect from the time the change takes effect, and the remuneration for the current billing period will be refunded pro rata temporis. Claims of the Customer on account of an incorrect statement under this paragraph are governed by A § 20. The classification does not replace the Customer's assessment of whether its own use of the Service is covered by the intended purpose (B § 11).
(2) The Customer takes measures to promote the AI literacy of the persons who operate, configure or evaluate the Service for it (Article 4 AI Act) and documents them (A § 11 para. 10). For this purpose RR42 shall provide the Customer, at the latest upon activation, with an information sheet in text form that describes the functioning, performance limits, known error patterns, the intended use and the configuration limits pursuant to B § 11 and deals with the research function (A § 5 para. 14) in a separate section or in a separate version; it shall update it upon material changes to the Service and transmit the version in force to the Customer in text form. RR42 additionally makes the information sheet permanently available in the customer account and includes its handover as a mandatory step in onboarding. If RR42 does not provide the information sheet within two weeks of a request in text form, the Customer may terminate the contract without observing a notice period; the remuneration for the current billing period will be refunded pro rata temporis. RR42 does not owe training of the Customer's employees. The information sheet supports the Customer in its measures pursuant to Article 4 AI Act; whether these measures suffice overall is for the Customer to judge, and RR42 does not promise this.
(3) At the beginning of the automated conversation the Service informs callers that they are interacting with an AI system (Article 50 paras. 1 and 5 AI Act). The Customer may not remove, shorten, delay or make misleading this notice and may not give callers the impression that they are speaking with a human being. In the case of a direct forwarding set up by the Customer without the Service conducting the conversation (forwarding of all calls; priority numbers), no notice is given because no AI system interacts with the caller. Compliance with the duty pursuant to sentence 1 is incumbent on RR42 as provider (Article 50 paras. 1 and 5 AI Act). If a competent authority or a court, deviating from sentence 3, assesses that an AI system also interacts with the caller on these paths, RR42 shall implement the notice there as well and bears the resulting costs and consequences; there is in this respect no duty of the Customer to indemnify under B § 11 para. 4. The Customer's duty pursuant to sentence 2 is a contractual one. The Service does not trigger the Customer's own transparency duties under Article 50 paras. 3 and 4 AI Act; it does not recognise emotions, does not carry out biometric categorisation and does not generate content within the meaning of Article 50 para. 4 AI Act.
(4) RR42 examines and documents whether and how synthetic speech outputs of the Service can be marked in a machine-readable manner pursuant to Article 50 para. 2 AI Act, and shall implement a marking as soon as an effective, interoperable and robust method for telephony connections is available in accordance with the state of the art. A machine-readable marking is currently not part of the Service.
(5) The Customer shall report to RR42 without undue delay malfunctions, misleading outputs and incidents that affect the security or lawfulness of the operation. The Customer maintains priority and block lists for telephone numbers itself. In addition, the Service evaluates call behaviour per telephone number: if a call from the same telephone number has been handed over to the Customer's personnel three times within 90 calendar days, the Service no longer offers this telephone number its own capture of the concern and suggests to the Customer that it be added to the priority list. RR42 performs this evaluation; it is based exclusively on the telephone number and the number of handovers and assesses no personal characteristics. Only the criteria and thresholds named in sentence 3 are decisive and are hereby disclosed. A change of the criteria or thresholds is governed by A § 10 and will be announced to the Customer in text form at least six weeks in advance. RR42 additionally reflects the evaluation in A § 5 para. 12 and in Annex 1 to Annex B1; if one of these descriptions deviates from sentence 3, sentence 3 prevails. A suggestion takes effect only when the Customer adopts it; the Customer is responsible for the adoption and its consequences. The Customer uses neither the lists nor the suggestions to assess personal characteristics of callers and reflects the evaluation in its information to callers pursuant to A § 11 para. 7 and A § 12 para. 3.
B § 11 Prohibition of change of purpose; configuration limits; indemnification
(1) The Customer uses the Service only within its intended purpose pursuant to B § 5, B § 8, A § 5 para. 12 and Annex A5. It may not configure, instruct or use the Service in such a way that it (a) assesses or classifies emergency calls, dispatches or prioritises emergency or rescue services, or triages patients (Annex III no. 5 letter d AI Act), (b) makes professional assessments, diagnoses, or statements on dosage or therapy, (c) assesses callers by personal characteristics, or (d) circumvents or switches off protective mechanisms, transparency notices, content limits, escalation rules or logging. This applies in particular to the editing of the system prompt and the knowledge content via the customer account settings (A § 11 para. 5). The intended use of functions and settings that RR42 provides to the Customer in the customer account is not a breach of sentence 2; this applies in particular to the forwarding of all calls, to priority numbers, to block lists and to the high-load mode. If such a function results in the notice pursuant to B § 10 para. 3 being omitted or a protective mechanism not taking effect, RR42 is responsible for this; it shall point out to the Customer, prominently in the customer account before activation, this effect and the resulting duties of the Customer towards callers.
(2) The Customer is advised that a change of the intended purpose makes it the provider of the Service under Article 25 para. 1 letter c AI Act only if the Service thereby becomes a high-risk AI system within the meaning of Article 6 AI Act; it is then subject to the provider obligations of Article 16 AI Act, and RR42 is, under Article 25 para. 2 sentence 1 AI Act, no longer deemed the provider of this system in that respect. A change of the intended purpose below this threshold does not have this consequence but remains a breach of paragraph 1. RR42 hereby clearly stipulates that the Service may not be converted into a high-risk AI system (Article 25 para. 2 sentence 3 AI Act); there is therefore no duty to hand over the documentation pursuant to Article 25 para. 2 sentence 2 AI Act.
(3) If there are specific indications, to be communicated to the Customer, that a configuration breaches paragraph 1, RR42 shall first request the Customer in text form, setting a reasonable deadline, to remedy it. Only after fruitless expiry of the deadline or, in the case of a specific danger to callers or to the security of the Service, immediately, may RR42 reset the objected setting to the default and temporarily restrict the directly affected function; the measure must be necessary and proportionate, must be limited to the objected setting and must be lifted as soon as its reason ceases to apply. The cessation of call acceptance is always the last resort; for it, A § 25 paras. 4 to 6 and, in the case of default in payment, A § 25 paras. 1 to 3 and B § 7 para. 5 apply, in each case including the provisions there on remuneration, burden of proof and liability. Before any reset RR42 backs up the previous configuration and restores it at the Customer's request. RR42 shall inform the Customer in advance, and in the case of a specific danger to callers without undue delay afterwards, in text form stating the reason, scope and expected duration, and shall, insofar as the danger situation permits, give the Customer the opportunity to comment within a reasonable period before the measure. At the latest after ten working days RR42 shall decide on lifting the measure and shall inform the Customer of the decision in text form. If the measure was not justified, RR42 shall refund the remuneration attributable to the period pro rata temporis; the Customer's rights under A § 15 and A § 20 remain unaffected. The burden of proof that the conditions of sentences 1 and 2 were met and that the measure was necessary in scope and duration lies with RR42. In all other respects A § 11 para. 5 applies also to Customers subject to this Part B; if its provision is more favourable to the Customer in an individual case, it takes precedence.
(4) If the Customer culpably breaches paragraph 1, it shall indemnify RR42 against justified claims of third parties based on this breach, including the reasonable costs of legal defence. If an order or prohibition by an authority is issued against RR42 on account of such a breach that is based directly on the Customer's breach, the Customer shall reimburse RR42 for the necessary expenses incurred as a result. If the breach is based on simple negligence of the Customer, the indemnification pursuant to sentence 1 and the claim for reimbursement pursuant to sentence 2 are limited by the maximum amount of A § 21 para. 2 last sentence, which applies to the obligations under that provision and under this paragraph together. Fines and other sanctions imposed on RR42 on account of the breach of its own obligations are borne by RR42 itself (A § 20 para. 6 sentence 6). The indemnification lapses insofar as RR42 has contributed to causing the claim or the measure or is also responsible for it; in this case the parties bear the loss in proportion to their shares of causation and fault (section 254 BGB (German Civil Code)). It does not cover claims and measures that are based on a breach of duty by RR42, nor those that are based on RR42 having provided a function or opened up a setting option whose intended use brings about the objected state (paragraph 1 sentence 4 and sentence 5). RR42 shall inform the Customer without undue delay of every claim asserted and every measure by an authority, shall make no acknowledgement, and shall give the Customer the opportunity to comment and to participate in the defence; A § 21 para. 5 applies accordingly. The burden of proof for the breach of paragraph 1, for the Customer's fault and for causation lies with RR42.
B § 12 Call data, transcripts, surrender
(1) The Service generates text transcripts, handover summaries and structured requests. In addition, RR42 keeps for each calling telephone number a caller profile containing the name given, if any, the time of the name query and the number of handovers to the Customer's personnel within the last 90 calendar days, as well as the suggestions to the Customer generated from it (B § 10 para. 5). RR42 erases this data at the latest 30 calendar days (transcript, handover summary, caller profile and suggestion) or 90 calendar days (structured request) after its creation; the Customer may set shorter periods in the customer account or by instruction in text form, and longer periods require an agreement in text form. For the time after the end of the contract, retention, retrieval, export and erasure are governed exclusively by A § 26 paras. 1 to 3 and para. 6; the duration of the transition period and the retrieval period provided for there, including their extension and suspension, and the subsequent erasure period take precedence, in derogation of A § 3 para. 1, over the periods of this paragraph, A § 12 para. 6 sentence 2 last half-sentence and section 16 of Annex B1. If Annex 4 to Annex B1 provides for shorter periods, these apply; if it contains no periods or only periods marked as provisional, the periods of this paragraph apply directly. RR42 shall confirm the erasure to the Customer in text form upon request and shall provide in the customer account a function with which individual cases and the data of a data subject can be erased without undue delay. Caller profiles and suggestions are subject to the same confidentiality, access and erasure rules as the other call data. Only persons authorised by the Customer and RR42 within the scope of B § 2 para. 3 have access.
(2) The Customer shall not use transcripts for an extraneous monitoring of the behaviour or performance of employees (A § 12 para. 6 sentence 5) and shall have captured requests reviewed by authorised personnel before any professional action. Its authority to have transcripts and captured requests evaluated by authorised personnel to fulfil its obligations pursuant to A § 11 para. 4 and its obligations under professional, supervisory and quality-assurance law (B § 7 para. 4) remains unaffected; section 26 BDSG and the participation rights of the employee representation must be observed, and A § 12 para. 6 sentence 5 applies accordingly, without being displaced by this paragraph. The Customer shall restrict access to persons authorised for this purpose (paragraph 1 last sentence). RR42 shall not derive any contributory fault of the Customer from an evaluation permissible under sentences 1 to 3 (A § 20 para. 7 sentence 3).
(3) Whether and to what extent audio recordings are made is governed by A § 12 para. 5. RR42 is responsible for the announcement and notice texts issued to callers correctly describing the actual processing, and shall adapt them before any change to the processing. If an announcement or notice text specified by RR42 deviates from the actual processing, this is a breach of duty by RR42; the Customer need not have the deviation attributed to it, and RR42 may in this respect set up against the Customer neither contributory fault nor a breach of its information duties pursuant to B § 4 para. 2 or A § 11 para. 7. RR42 shall inform the Customer in text form before activation, and thereafter without undue delay upon every change, whether, at which point of the call flow, on which telephony path, at which subcontractor, at which place of processing and for what duration audio recordings are generated or stored, and by what route they are erased. This information is subject to no reservation; if, pursuant to A § 12 para. 5, no audio recordings are made, it is limited to that statement. For as long as RR42 has not provided it, it shall not assign a target number to the Customer and shall not accept calls for the Customer (B § 3 para. 1). If audio recordings are made that A § 12 para. 5 does not provide for, this is a defect of the Service and at the same time a security incident pursuant to A § 14; RR42 shall erase the recordings without undue delay, including copies stored at subcontractors, shall demonstrate the erasure in text form, and the Customer may terminate the contract without observing a notice period, whereby the remuneration for the current billing period will be refunded pro rata temporis. Further claims of the Customer remain unaffected.
(4) RR42 treats requests for surrender from authorities and courts in accordance with B § 2 para. 9. RR42 contributes to the Customer's professional activity pursuant to section 53a para. 1 sentence 1 StPO (German Code of Criminal Procedure); it asserts towards the ordering body that call data in its custody is not subject to seizure pursuant to section 97 para. 1 nos. 1 to 3, para. 2 sentence 1 and para. 3 StPO, and refuses to testify. The Customer decides on the exercise of the right to refuse to testify (section 53a para. 1 sentence 2 StPO); if its decision cannot be obtained in time, RR42 shall refuse to testify and object to the measure. In the event of a search, securing or seizure, RR42 shall voluntarily surrender nothing, shall object to the review of the material, shall demand sealed custody until the court decision (section 110 paras. 1 and 2 StPO), shall apply for the court decision pursuant to section 98 para. 2 sentence 2 StPO and shall inform the Customer pursuant to B § 2 para. 9 sentence 3; RR42 bears the costs of these measures. RR42 does not physically resist an effective and enforceable order; it shall not alter or erase the data concerned on the occasion of the order, and the periods of paragraph 1 continue to run unless an order requires their retention, about which RR42 shall inform the Customer. RR42 does not promise that a seizure will not take place; the protection presupposes that the contribution pursuant to section 53a para. 1 sentence 1 StPO is affirmed in the individual case, and lapses pursuant to section 97 para. 2 sentence 2 StPO in particular where the suspicion is directed against the Customer itself. The Customer remains responsible for exercising rights to refuse to testify and rights of protection against seizure; RR42 supports it with the information available to it.
B § 13 Declaration of undertaking (Annex 5 to Annex B1)
(1) Annex 5 to Annex B1 forms part of the contract. It contains the declaration signed by RR42 pursuant to B § 2 para. 1, the instruction pursuant to B § 2 para. 2, the restriction of knowledge pursuant to B § 2 para. 3 and the stipulation on the involvement of further persons pursuant to B § 2 para. 5 with the duty to bind them to secrecy in text form (section 43e para. 3 sentence 1 nos. 1 to 3 BRAO, section 62a para. 3 sentence 1 nos. 1 to 3 StBerG).
(2) Annex 5a contains the register of the bound employees and subcontractors with the date and status of the undertaking; Annex 5b contains the wording of sections 203 and 204 StGB. RR42 shall provide the Customer with Annex 5 countersigned and with Annexes 5a and 5b in text form at the latest upon activation, and keeps Annex 5a up to date in the customer account.
(3) If Annexes 5, 5a or 5b are missing or do not contain the stipulations named in paragraph 1 in full, the undertaking pursuant to B § 2 paras. 1 and 2, the restriction of knowledge pursuant to B § 2 para. 3, the binding of further persons pursuant to B § 2 para. 5 and the duties to submit documents and to provide information pursuant to B § 2 para. 8 apply directly as contractual stipulations within the meaning of section 43e para. 3 sentence 1 nos. 1 to 3 BRAO and section 62a para. 3 sentence 1 nos. 1 to 3 StBerG. If RR42 does not provide the Annexes within two weeks of a request in text form, the Customer may terminate the contract without observing a notice period; the remuneration for the current billing period will be refunded pro rata temporis.
Part C – Special Terms for Online Orders
C § 1 Scope of application; registration and activation of the customer account
(1) This Part C applies to contracts concluded via the customer account and the order process of the payment service provider. It supplements Part A and, for professional secrecy holders, Part B; in the event of conflict, Part B takes precedence.
(2) Registration takes place via the waiting list of the customer account. By registering, the Customer does not make a declaration of intent to conclude a contract; the Customer expresses interest and acknowledges the privacy notices for the customer account. RR42 decides on the activation of the customer account; there is no entitlement to activation. Activation is not an acceptance of an offer (A § 4 para. 1).
(3) After activation, the Customer goes through the set-up on first login. In doing so, the Customer makes the declarations pursuant to C § 2, agrees to these AGB and to the Data Processing Agreement, stating the version number and date, by clicking a separate box that is not pre-selected for each, and receives the documents as files that can be printed and saved. Professional secrecy holders additionally accept Part B and Annex 5 to Annex B1 pursuant to B § 3. Before the set-up is completed, RR42 activates neither the trial period nor call answering.
C § 2 Business customer declaration; "Einzelunternehmer" plan
(1) During set-up and separately with each order, the Customer declares by clicking a box that is not pre-selected that the Customer orders the Service as a business customer within the meaning of section 14 BGB (German Civil Code) for the business, practice, pharmacy or law firm named by the Customer, and acknowledges the notice that the Service is not offered to consumers and that consumer protection rights such as a right of withdrawal do not exist for business customers. The declaration is a declaration of the Customer; it is not a confirmation of facts to the Customer's detriment and does not change the statutory burden of proof.
(2) The "Einzelunternehmer" plan is open only to natural persons who use the Service for their own commercial or independent professional activity. The Customer declares this separately when ordering this plan and provides a VAT identification number, tax number, register number or chamber membership; RR42 may require proof. RR42 stores the declaration together with the time, the declaring person and the version of these AGB.
(3) If RR42 has specific indications that the requirements of paragraph 2 are not or are no longer met, it will notify the Customer thereof in text form, stating the facts on which it relies, and give the Customer an opportunity to comment and to prove that the requirements are met within two weeks. If the requirements are then not met, RR42 may switch the Customer, with effect from the start of the billing period after next, to the lowest regular plan of the Customer's sector; RR42 will announce the switch in text form at least four weeks before it takes effect and will state therein the new plan, the base fee, the included allowance and the price per additional minute. Until the switch takes effect, the Customer may choose a different plan or terminate the contract pursuant to A § 23 para. 2; if the Customer terminates, the previous plan remains in place until the end of the contract. No retroactive additional charge for past billing periods will be made, unless the Customer made the declaration under paragraph 2 against better knowledge. If the Customer is at the same time a consumer, A § 1 para. 4 remains unaffected; RR42's right to terminate for good cause pursuant to A § 24 also remains unaffected.
(4) The button with which the Customer orders a subscription subject to a charge is labelled with the words "zahlungspflichtig bestellen" ("order with obligation to pay"). On the pricing pages and in the order summary, RR42 points out prominently that the offer is addressed exclusively to business customers, freelancers, legal entities under public law and special funds under public law, and that all prices are net prices plus statutory value added tax.
(5) RR42 does not display a withdrawal notice in the order process. A right of withdrawal under sections 312g para. 1, 355 BGB exists only for consumers; the Service is not offered to consumers (A § 1 para. 2), and neither these AGB nor the order process grant the Customer a contractual right of withdrawal. If it turns out that a Customer has acted as a consumer contrary to the Customer's declaration under paragraph 1, RR42 will inform the Customer without undue delay after becoming aware, in text form, of the Customer's statutory right of withdrawal using the model in Annex 1 to Article 246a § 1 para. 2 sentence 2 EGBGB (Introductory Act to the German Civil Code), will provide the Customer with the model withdrawal form pursuant to Annex 2 to Article 246a § 1 para. 2 sentence 1 no. 1 EGBGB, and will at the same time draw the Customer's attention to A § 1 para. 4; in this case the withdrawal period begins only with this information (section 356 para. 3 sentence 1 BGB). In this case RR42 does not demand compensation for value for the services provided up to the withdrawal.
C § 3 Trial period
(1) After the set-up has been completed (C § 1 para. 3), RR42 makes the Service available to the Customer free of charge for 14 calendar days for trial purposes (trial period). The contract for the trial period is concluded when RR42 makes the Service available. The trial period runs on plan tier 1 of the relevant sector with its included allowance; no additional minutes are incurred. A payment method is not required. The start of call answering requires RR42 to assign a target number; RR42 assigns it within five working days after the set-up has been completed, and the trial period begins with the assignment. If the assignment does not take place within ten working days after the set-up has been completed, the Customer may end the contract for the trial period without observing a notice period; if the Customer has already ordered a subscription subject to a charge, the first billing period begins only with the assignment, and until then no base fee is incurred. The Customer makes the offer to conclude the contract for the trial period upon completing the set-up pursuant to C § 1 para. 3; RR42 accepts it by making the Service available, without the acceptance having to be declared to the Customer (section 151 sentence 1 BGB). RR42 confirms the conclusion of the contract without undue delay pursuant to A § 4 para. 4.
(2) The trial period is granted free of charge. During the trial period, RR42 is liable without limitation in the cases of A § 20 para. 1 and for intent and gross negligence. For damage based on simple negligence, RR42 is liable during the trial period only in the event of a breach of an essential contractual obligation within the meaning of A § 20 para. 2 sentence 2, limited to the typical contractual damage foreseeable at the start of the trial period and, in amount, to EUR 10,000 for all cases of damage of the trial period in total; for damage arising from the breach of obligations relating to data protection, confidentiality or the preservation of professional secrecy, in particular under B § 2 and Annex B1, A § 20 para. 2 and para. 3 letter d apply unchanged. In all other respects, RR42's liability for simple negligence is excluded during the trial period. The standard of care to be observed by RR42 is not lowered by the fact that the trial period is free of charge; RR42 operates the Service, its protective mechanisms and the processing of personal data during the trial period with the same care as in the subscription subject to a charge. Sections 599 and 690 BGB do not apply. A particular availability is not owed during the trial period; support is provided pursuant to A § 9 subject to available capacity. RR42 uses the call content processed during the trial period exclusively to provide the Service to the Customer; consideration from the Customer, in particular consent to advertising or data use, is not a condition of the trial period.
(3) Because the Service also answers real calls during the trial period, these AGB including Annex A5, the Data Processing Agreement and, for professional secrecy holders, Part B including the undertaking pursuant to B § 2 apply without restriction. The Data Processing Agreement and the undertaking must be concluded before the first call is answered (A § 12 para. 1; B § 3). During the trial period, the Customer does not use the Service as the sole communication channel for processes critical to supply or safety and maintains the Customer's existing reachability.
(4) RR42 informs the Customer pursuant to C § 8 para. 2, at least three calendar days before the end of the trial period, in text form of the expiry date and of the obligation to cancel the call diversion. The trial period ends at the end of the 14th day of the trial period (paragraph 1 sentence 5), but at the earliest three calendar days after receipt of the information pursuant to sentence 1 and in any case at the latest at the end of the 30th day of the trial period; no termination is required, no payment obligation arises, and no automatic transition into a subscription takes place. If RR42 has not provided the information pursuant to sentence 1 in good time, it continues to answer calls free of charge until the expiry date resulting from sentence 2 and promptly supplies, in text form, the information on the expiry date and on the obligation to cancel the call diversion; C § 8 para. 1 sentences 5 and 6 and C § 8 para. 2 last sentence remain unaffected, and RR42 bears the burden of proof for receipt of the information pursuant to sentence 1. After the end of the trial period, RR42 no longer answers calls for the Customer; calls that continue to arrive at the target number are rejected. Callers hear exclusively the announcement pursuant to C § 8 para. 1 sentence 2; the Customer nevertheless cancels the call diversion before the end of the trial period if the Customer does not continue the Service (C § 8). Access to the customer account and to the data captured during the trial period remains available for the retrieval period pursuant to A § 26 para. 2; thereafter RR42 erases the data pursuant to A § 26 para. 3.
(5) A subscription subject to a charge comes into existence exclusively pursuant to C § 4. If the Customer completes the order process during the trial period, the ordered plan is activated upon conclusion of the contract pursuant to C § 4 para. 3; however, the first billing period subject to a charge begins only upon expiry of the trial period, and until then no base fee is incurred. In the order summary, the Customer may expressly choose that the first billing period subject to a charge begins already upon conclusion of the contract; in this case RR42 points out prominently to the Customer before the order that the remaining trial period lapses, and states the number of days that lapse. If this notice or the choice option is missing, sentence 2 applies.
(6) The trial period is granted once per Customer and business. If RR42 has specific indications that an account was set up solely to circumvent this rule, it will notify the Customer of the material facts in text form and give the Customer an opportunity to comment within five working days. If the indications are confirmed, RR42 may end the free-of-charge provision for this account and terminate the contract for the trial period without observing a notice period; it will notify the Customer thereof in text form and point out the need to cancel the call diversion (C § 8). This rule has no effect on subscriptions subject to a charge of the same Customer; for the blocking of call answering, A § 25 applies exclusively. RR42 bears the burden of proof for the requirements of sentence 3.
C § 4 Ordering a subscription via the customer account
(1) The presentation of the plans on the website and in the customer account is not an offer but an invitation to the Customer to make an offer. The Customer makes the Customer's offer by selecting a plan in the customer account, checking the order summary, making the declarations pursuant to C § 2, declaring agreement to the current version of these AGB and of the Data Processing Agreement, and clicking the button "zahlungspflichtig bestellen" ("order with obligation to pay"). Before clicking the button, the Customer can identify and correct the Customer's entries via the "Back" button or by changing the selection in the order summary; the order process can be cancelled at any time until then. If the Customer in fact completes the order process by another route, in particular directly in the order flow of the payment service provider, that completion is also the Customer's offer; RR42 cannot rely against the Customer on the absence of an order summary, of a request for agreement or of a button labelled in accordance with sentence 2, and in this case the contract is concluded in accordance with the statutory provisions; for the incorporation of these AGB, A § 3 para. 2 last sentence applies.
(2) The technical steps to the conclusion of the contract are: (a) registration and activation of the customer account and set-up pursuant to C § 1; (b) selection of the plan in the customer account; (c) checking the order summary with plan, base fee, included allowance, price per additional minute, value added tax, billing period and terminability; (d) making the declarations and giving the agreements pursuant to paragraph 1; (e) clicking the button "zahlungspflichtig bestellen"; (f) storing a payment method and the invoicing details with the payment service provider. Decisive for the incorporation of these AGB is exclusively the agreement pursuant to paragraph 1 and C § 1 para. 3; if the order process of the payment service provider additionally requests the agreement, C § 9 para. 3 applies. RR42 confirms receipt of the order without undue delay, at the latest within one working day, by e-mail to the address stored in the customer account; the confirmation states the ordered plan and the current version of these AGB and the Annexes with version number and date, contains these documents as an attachment, points out that acceptance takes place separately pursuant to paragraph 3, and contains no statement suggesting that the Service has been activated. The confirmation of receipt is not an acceptance.
(3) The contract is concluded when RR42 accepts the order. Acceptance takes place by a confirmation in text form designated as such, which states the ordered plan, the start of performance and the current version of these AGB and the Annexes with version number and date, or by RR42 activating the ordered plan in the customer account. If the payment service provider collects the first base fee before one of these declarations exists, acceptance is deemed declared upon the collection. If RR42 does not accept the order within five working days after its receipt and no collection has taken place by then either, the Customer is no longer bound by the Customer's offer; any amount nevertheless collected will be refunded without undue delay.
(4) RR42 stores the contract text (order summary, the version of these AGB and the Annexes applicable at the time of the order with version number and date, the Data Processing Agreement and the Customer's declarations). Attached to the confirmation of receipt, as a file attachment in a reproducible format, are the version of these AGB applicable at the time of the order, the Data Processing Agreement and a plan sheet with the figures of the ordered plan, the version number and the date of the contractual documents. The Customer can retrieve and save the order summary and the Customer's declarations at any time in the customer account under "Verträge" ("Contracts"); the aforementioned documents are also available to the Customer there. A § 3 para. 2 remains unaffected.
(5) The contract language is German. RR42 has not submitted to any code of conduct within the meaning of Article 246c no. 5 EGBGB. The obligations under section 312i para. 1 sentence 1 nos. 1 to 4 BGB are not waived.
(6) The subscription start within the meaning of A § 2 no. 9 and no. 24, A § 16 para. 2, A § 20 para. 3 letter a and A § 23 para. 1 is the time of conclusion of the contract pursuant to paragraph 3. If the first billing period subject to a charge begins only upon expiry of the trial period pursuant to C § 3 para. 5 sentence 2, the period from the subscription start until expiry of the trial period forms the first billing period, which is free of charge; it may be shorter than one month, and no base fee is incurred for it. The first billing period subject to a charge begins upon expiry of the trial period; each further one begins immediately upon the end of the preceding one (A § 16 para. 2 sentence 2). A termination pursuant to A § 23 para. 2 that the Customer declares during the trial period takes effect upon expiry of the trial period. The period in A § 16 para. 6 sentence 2 and the minimum term pursuant to A § 23 para. 5 sentence 3 are linked to the first billing period subject to a charge. RR42 states the subscription start, the expiry of the trial period and the start and end of the first billing period subject to a charge, determined by calendar date, in the confirmation pursuant to A § 4 para. 4 and shows them in the customer account pursuant to A § 16 para. 2 sentence 3; if this information is missing or contradictory, A § 16 para. 2 sentences 4 and 5 apply, and in all other respects the point in time more favourable to the Customer is decisive.
C § 5 Payment via the payment service provider; SEPA direct debit
(1) Payment is made exclusively via the payment service provider pursuant to A § 17. In the order process, the Customer stores a payment method (credit card or SEPA direct debit), the billing address and, where available, the Customer's VAT identification number, and manages these details in the customer portal.
(2) If the payment service provider offers SEPA direct debit in the order process and the Customer chooses it, the Customer thereby issues a SEPA direct debit mandate in favour of RR42; RR42 has it obtained and managed by the payment service provider and identifies in the mandate text RR42 as payee, its creditor identification number and the mandate reference. RR42 announces each direct debit that falls due at least three banking days before the debit date; what is decisive is receipt of the announcement by the Customer. The announcement is made by e-mail to the stored e-mail address and contains the amount, debit date, creditor identification number and mandate reference of RR42; RR42 transmits the invoice under A § 17 para. 2 separately. For recurring direct debits of constant amount, a single announcement that states the amounts and the due dates suffices; if the amount changes, RR42 announces the direct debit again pursuant to sentence 2. The Customer ensures that the account has sufficient funds. If the announcement is omitted or does not reach the Customer in good time, the debit is unauthorised and will be refunded without undue delay; if the collection fails for that reason, RR42 additionally bears the charges incurred for this. A § 17 para. 5 does not apply in this respect, a block pursuant to A § 25 para. 1 cannot be based on such a collection attempt, and default does not occur before receipt of a renewed announcement made in due time; the claim for payment itself remains unaffected (A § 17 para. 3 sentence 7).
(3) The amount to be paid is the amount shown in the invoices of RR42 (A § 17 para. 2); A § 16 para. 5 applies. The display in the customer account is an approximation (A § 16 para. 5). Invoices are available for retrieval in the customer account.
(4) If the collection fails, the payment service provider repeats the collection in accordance with its rules; A § 17 paras. 4 and 5 and A § 25 apply.
C § 6 Termination in the customer portal
(1) The Customer may terminate the contract at any time via a termination function offered in the customer portal, with effect from the end of the current billing period (A § 23 para. 2). Termination by e-mail to the address stated in A § 30 para. 5 remains possible in addition; there is no special requirement as to receipt.
(2) RR42 confirms to the Customer receipt of the Customer's termination and the date of the end of the contract within three working days in text form to the contract contact and to the notification address, and in doing so points out the cancellation of the call diversion; A § 23 para. 2 and para. 4 apply without restriction to terminations pursuant to this paragraph. Until the end of the contract, the Service remains usable. Before the end of the contract, the Customer cancels the call diversion (C § 8).
(3) A change of plan is not possible via the customer portal; the Customer may request it in text form pursuant to A § 16 para. 6. If the Customer requests a change to a higher plan, RR42 activates the higher included allowance without undue delay, at the latest within two working days after receipt of the request, already for the current billing period, without an additional base fee being incurred for this; for additional minutes of this billing period, the more favourable to the Customer of the two prices per additional minute applies, and the higher base fee is charged only from the following billing period. A change to a lower plan takes effect at the start of the billing period determined under A § 16 para. 6 sentence 2. RR42 confirms the change and the time at which it takes effect in text form.
C § 7 User accounts, team, access credentials
(1) The holder of the customer account may invite further users from the Customer's business and assign roles to them. The Customer is responsible for all actions taken via user accounts of the Customer's customer account, to the extent that the Customer is responsible for them, and ensures that only authorised persons gain access to call data and settings (A § 11 para. 11).
(2) The Customer uses personal accounts, keeps access credentials secret, activates a multi-factor authentication that is offered for privileged access, withdraws authorisations without undue delay upon departure or change of role, and notifies RR42 without undue delay of any suspected compromise; RR42 may then temporarily block the accounts concerned (A § 25 para. 4).
(3) Authentication takes place via the identity provider named in Annex 3 to Annex B1; RR42 does not obtain knowledge of the Customer's passwords.
C § 8 End of call answering; advance information; call diversion
(1) If call answering ends because the trial period expires, a block pursuant to A § 25 begins or the contract ends, the Service no longer answers calls that continue to be diverted to the target number. Callers hear exclusively an announcement that reveals neither the Customer's name nor the reason for the end, the payment status or the status of the customer account; it reads, during a block pursuant to A § 25 para. 2 sentence 3, after the end of the contract and during the grace period pursuant to A § 26 para. 4 sentence 9, and otherwise: "Dieser Anschluss ist derzeit nicht erreichbar. Bitte versuchen Sie es später erneut." ("This line is currently unavailable. Please try again later."). If RR42 exceptionally cannot play the announcement on the telephony route used, it will notify the Customer of this in text form together with the information pursuant to paragraph 2, and the connection ends without an announcement; this applies equally to all order routes. RR42 does not capture, store or exploit the content, numbers and connection data of such calls and does not forward them. The Customer cancels the call diversion by the end of call answering; this obligation exists only once the information pursuant to paragraph 2 stating the time of the end has been received by the Customer. Contributory fault of the Customer on account of a continuing call diversion comes into consideration only to the extent that this information was received by the Customer in good time; in the case of a block pursuant to A § 25 para. 4 that takes effect without prior announcement, contributory fault is excluded.
(2) RR42 informs the Customer of the impending end of call answering in text form at the notification address stored in the customer account and, where the Customer has named a contract contact in the order or in the customer account, additionally at that contact; the information contains the time of the end and the instruction to cancel the call diversion. It is given, upon expiry of the trial period, at least three calendar days beforehand, in the case of a block with the warning pursuant to A § 25 para. 1, and, upon the end of the contract, at least ten calendar days before the end of the contract, provided RR42 already knows the time of the end of the contract at that point (A § 26 para. 4 sentence 5). If fewer than ten calendar days lie between receipt of the Customer's termination and the end of the contract, RR42 informs the Customer without undue delay, at the latest within one working day after receipt of the termination and in any case at the latest with the confirmation of termination pursuant to A § 23 para. 4 sentence 4; no longer period applies to RR42 in this case. If RR42 itself terminates, the information is given with the declaration of termination pursuant to A § 23 para. 4 sentence 6. For contracts concluded in text form pursuant to A § 4 para. 3, this paragraph applies accordingly pursuant to A § 26 para. 4 sentence 5. If the information is not given for reasons for which RR42 is responsible, RR42 is liable pursuant to A § 20 for damage incurred by the Customer from the continuing diversion; the Customer's obligation pursuant to paragraph 1 remains in place.
C § 9 Proof of incorporation; contract text; existing customers
(1) RR42 logs every agreement pursuant to C § 1 para. 3, C § 2 and C § 4 in an audit-proof manner with the time (UTC), user and tenant identifier, version and checksum of the accepted documents, text of the declarations made, state of the agreement boxes and the dispatch and delivery status of the confirmations. RR42 additionally logs the IP address and the browser identifier of the device from which the declaration was made. For the logging pursuant to sentences 1 and 2, RR42 is the controller within the meaning of Article 4 no. 7 GDPR (DSGVO); the legal basis is Article 6 para. 1 subparagraph 1 point (f) GDPR, with the purpose of proving the conclusion of the contract and incorporation. RR42 uses the logs exclusively for this purpose, does not evaluate them in any other way and does not pass them on to third parties unless it is legally obliged to do so. RR42 retains the logs for the duration of the contract and until expiry of the regular limitation period after its end; it erases the details pursuant to sentence 2 at the latest twelve months after the end of the contract. The retention is aligned with the erasure concept. RR42 informs the data subjects pursuant to Article 13 GDPR in the privacy notices for the customer account and provides the Customer with these notices for forwarding to the Customer's users.
(2) The Customer can view and save the Customer's agreements and the associated document versions at any time in the customer account under "Verträge" ("Contracts").
(3) If the order process of the payment service provider additionally requests agreement to these AGB and to the Data Processing Agreement in the respective version indicated, this agreement is an additional confirmation; it does not replace the agreement pursuant to C § 1 para. 3 and C § 4 para. 1. Decisive for the incorporation of these AGB and for being bound to a version is exclusively the agreement pursuant to C § 1 para. 3 and C § 4 para. 1 and its logging pursuant to paragraph 1. No objection to incorporation follows from the absence of a request at the payment service provider.
(4) For Customers whose customer account was activated before these AGB entered into force, RR42 presents these AGB, the Data Processing Agreement and, for professional secrecy holders, Part B and Annex 5 to Annex B1 for agreement at the next login pursuant to C § 1 para. 3 and at the same time sends them to them in text form with a period of at least four weeks for a declaration. If the Customer does not agree, the previously agreed terms remain applicable to the existing contractual relationship and otherwise the statutory provisions; in this case RR42 can terminate the contractual relationship only with the notice period of A § 23 para. 3 and offer the Customer continuation on these AGB. Until such a termination takes effect, agreement is not a prerequisite for continued use of the Service; the presentation pursuant to sentence 1 therefore contains, in addition to the agreement box, an equally prominent button with which the Customer can decline or postpone the agreement and continue to use the Service unchanged. Silence, inaction and continued use of the Service do not count as agreement; no deemed-consent mechanism is agreed. The transmission pursuant to sentence 1 designates the documents as new contract terms, states the material deviations from the previous contractual basis, in particular regarding liability (A § 20), term and termination (A § 23) and place of jurisdiction (A § 31 para. 2), and points out the consequences of non-agreement pursuant to sentence 2; the four-week period begins upon its receipt. RR42 logs declining and postponing pursuant to paragraph 1 in the same way as an agreement. Before the presentation pursuant to sentence 1, RR42 corrects towards each existing Customer, in text form, those of its public statements that deviate from the owed quality of the Service, stating the previous and the correct statement; if the correction is not made, the previous statements remain decisive for the existing contractual relationship pursuant to A § 5 para. 9 sentence 3.
(5) For professional secrecy holders for whom an undertaking pursuant to B § 2 is not yet in place, RR42 declares it without undue delay and unilaterally in text form and makes the declaration pursuant to Annex 5 to Annex B1 available to them, countersigned; no agreement by the Customer to these AGB is required for this. If the Customer refuses the Data Processing Agreement required under Article 28 para. 3 GDPR or acceptance of the undertaking, RR42 suspends call answering; it announces the suspension in text form at least two weeks beforehand and points out that the Customer must cancel the call diversion (C § 8). For the duration of the suspension, the base fee lapses pro rata temporis; either party may terminate the contract without observing a notice period, and the remuneration for the current billing period is refunded pro rata temporis. The pro rata lapse of the base fee pursuant to sentence 3 takes the place of a reduction pursuant to A § 15 para. 3; a suspension pursuant to sentence 2, the reason for which the Customer is responsible, is not a countable outage minute within the meaning of A § 8 para. 1 (A § 8 para. 1 sentence 6 letter e). In all other respects, A § 25 para. 4 sentences 4 to 6 and A § 25 para. 5 and para. 6 apply accordingly to the suspension (A § 25 para. 7 sentence 2).
(6) If a personal data breach affecting Customer data occurred before these AGB entered into force, RR42 will notify the Customer concerned thereof without undue delay in text form in accordance with A § 14 para. 6 sentence 1 and Article 33 para. 2 GDPR, even if at the time of the breach the contract existed without effectively incorporated terms. The notification states the nature, time and duration of the breach, the categories of data concerned and the remedial measures taken. The decision on notifications pursuant to Article 33 para. 1 and Article 34 GDPR lies with the Customer.
Index of Annexes
This index designates the Annexes; which version of an Annex applies to the Customer is determined by A § 3 para. 2. Decisive in this regard is the version that RR42 transmits to the Customer pursuant to A § 4 para. 4 with version number, date and checksum and evidences in the version archive. Each Annex is made available to the Customer before the order for retrieval, saving and printing and is transmitted again with the confirmation pursuant to A § 4 para. 4. The Annexes apply to all product variants of the Service.
| Abbreviation | Document | Rank under A § 3 para. 1 | Remark |
|---|---|---|---|
| B1 | Data Processing Agreement pursuant to Article 28 GDPR (DSGVO) with Annexes 1 (description of the processing), 2 (technical and organisational measures; executed as document B2), 3 (sub-processors), 4 (erasure and return specifications), 5 (undertaking to professional secrecy) with 5a (list of the persons and sub-processors bound) and 5b (text of sections 203 and 204 StGB (German Criminal Code)) and 6 (reporting form) | c | mandatory before processing begins; for professional secrecy holders always including the section on professional secrecy and Annexes 5, 5a and 5b (B § 1 para. 3) |
| A5 | Acceptable Use Policy | g | Number 6 follows A § 6 para. 3, number 7 follows A § 5 para. 13, number 8 follows A § 12 para. 6 sentence 5; sanctions under number 10 are governed exclusively by A § 25, changes under number 11 exclusively by A § 27. No independent powers to block or to change exist |
Not part of the contract but referred to are documents C3 (Transparency and Purpose Limitation Policy; model texts pursuant to A § 12 para. 7 and B § 4 para. 2), C4 (Prompt Governance; A § 10 para. 4), C5 (Model Steering Procedure; A § 10 para. 4 and § 11 para. 7 of Annex B1), B4 (Erasure Concept; A § 26 para. 3) and the input for the Customer's data protection impact assessment (§ 14 para. 2 of Annex B1), in each case in the current version. Likewise not part of the contract is the Annex "Known Limitations" (list of the deviations known to RR42 between the owed and the actually provided quality pursuant to A § 5 para. 11): it is pre-contractual information, does not take part in the order of precedence of A § 3 para. 1 and does not change the owed quality; the Customer's rights on account of a defect remain unaffected alongside it.