Known Limitations
Statement pursuant to A § 5 paragraph 11 of the General Terms and Conditions of RR42 UG (haftungsbeschränkt)
| Document | Details |
|---|---|
| Provider | RR42 UG (haftungsbeschränkt), Marienstraße 4, 31832 Springe · Local Court (Amtsgericht) Hannover HRB 230929 |
| Applies to | AI telephone assistant for incoming calls, in all product variants, brands and sectors. Where a statement applies only to pharmacies, medical practices or other professional secrecy holders, this is stated |
| Document type | Pre-contractual information pursuant to A § 5 paragraph 11 of the AGB. Not part of the contract: this statement does not take part in the order of precedence under A § 3 paragraph 1 and does not change the owed quality of the Service |
| Version | Version 1.4.0, as of 9 November 2026 |
| Provision | Highlighted and in text form before the order is placed. Published at the fixed address /agb/einschraenkungen of the Service's website, where it is available with version, date and SHA-256 checksum for retrieval, printing and saving. RR42 keeps the statement up to date in the customer account and informs the Customer without undue delay in text form of every newly added deviation |
| Reference | The AGB together with Annex A5 (Acceptable Use Policy) and Annex B1 (Data Processing Agreement) with its annexes, including B2 (technical and organisational measures) and the sub-processor list (Annex 3); also document C3 (Transparency and Intended Purpose Policy), the contribution to the data protection impact assessment and the online register of data formats — in each case in the version in force |
| Review | Upon every change to the Service that affects a statement in this document, and otherwise at least annually |
1. How to read this statement
It describes the state of the Service that applies at the start of performance. Statements in the present tense describe what the Service then does; where something is added only later, the point in time is stated.
The statement lists three kinds of limitations side by side without distinguishing them from one another, because the distinction would be of no use to the Customer: services that the Service does not owe under the AGB in the first place; limits that follow from the technology; and deviations between what the AGB promise and what the Service actually does. Where a statement belongs in the last group, this is expressly said.
2. What the Service is intended for
The Service accepts incoming calls that the Customer diverts from its own line to the target number, conducts an automated conversation with callers, answers questions from the opening hours, address data and knowledge base stored by the Customer, captures requests in a structured way, and can transfer the call to a forwarding destination named by the Customer.
It is an administrative communication tool and not an instrument of pharmaceutical, medical or other professional care. The full intended purpose and the excluded uses are set out in section 2 of document C3 and in no. 3 of Annex A5; the following numbers repeat from them only what is relevant to the decision whether to place an order.
3. No connection to merchandise management, practice management or pharmacy systems
The Service is not connected to any system of the Customer. There is no connection to merchandise management, practice management or pharmacy systems, to appointment calendars, to cash register or billing systems, or to any other data source of the Customer (A § 5 paragraph 13). The Service reads nothing from such systems and writes nothing to them.
It follows in particular that:
- An appointment request is captured as a request but is not booked, reserved or confirmed. The same applies to orders, prescription requests, pre-orders and callback requests (A § 5 paragraph 7).
- The Service does not check a prescription against the systems of the payers and makes no decision on dispensing, supply, courier delivery or substitution (A § 5 paragraph 13, B § 5 paragraph 4).
- The Service does not know the processing status of a matter at the Customer's premises. It does not answer questions about the status of a prescription, an order or a delivery, but captures them as a request with a callback request.
- Everything the Service knows about the Customer's business comes from the Customer's own configuration and knowledge base. If it is out of date, the Service reproduces the out-of-date state; the Customer is responsible for its accuracy and currency (A § 11 paragraph 1).
A connection to a data source of the Customer is owed only once it has been expressly agreed in text form, technically implemented, assessed under data protection law and from a professional standpoint, and taken into account in the protection and escalation rules (A § 5 paragraph 5).
4. No information on stock, availability, delivery times and prices
The Service neither states nor confirms stock levels, delivery availability, delivery times or prices. It takes up enquiries on these as requests and makes them available to the Customer for answering by its staff (A § 5 paragraph 5, Annex A5 no. 7; for professional secrecy holders B § 6).
Both halves are meant: the Service does not of its own accord state any such information, and it also does not confirm any that a caller states to it. This applies expressly even where corresponding information is stored in the Customer's knowledge base. The Customer may not enter such information there (Annex A5 no. 7); the Service's instructions additionally prohibit its output, independently of what is in the knowledge base. For pharmacies, this applies in particular to the question whether a specific medicinal product is in stock or available for delivery.
To be distinguished from this is a general operating procedure of the Customer, for example the time by which orders received are regularly made ready for collection on the same day. The Customer may store it and the Service may reproduce it as a general rule, but not as a promise for a specific order (Annex A5 no. 7 paragraph 4, B § 6 paragraph 5).
Furthermore, the Service does not determine which pharmacy is on out-of-hours duty or on standby. It names no specific out-of-hours or standby pharmacy, no address and no further telephone number. Outside the configured opening and standby times, it can point out that a pharmacy out-of-hours service is in place, without designating a specific pharmacy (Annex A5 no. 7, B § 7 paragraph 2).
5. No pharmaceutical, medical, legal or tax advice
The Service provides no information or advice on medicinal products or medical devices within the meaning of section 20 ApBetrO (Pharmacy Operating Regulation), no medical advice or treatment, no legal services and no assistance in tax matters (A § 5 paragraph 5, B § 5).
In particular, it makes no statements on the effect, use, dosage, side effects or interactions, suitability, interchangeability or reimbursement of a medicinal product, on diagnoses, symptoms or therapies, or on legal or tax questions in an individual case. Such requests are captured and handed over to the Customer's authorised staff or provided with a callback note.
A configuration that instructs the Service to give such information is prohibited for the Customer under no. 3.3 of Annex A5; the Service's instructions maintain the limit additionally and independently of the configuration. No assurance that every single output complies with this limit is associated with this — no. 7 applies to that.
If the Service declines a professional question, it tells the caller where an answer can be obtained — in the Pharmacy and Medical Practice product variants, via a physician and, outside consultation hours, via the out-of-hours medical service 116117.
6. Not an emergency call system; what happens on emergency indications
The Service is not an emergency call system and does not replace an emergency call. It establishes no connection to emergency call answering points (112, 110), to the out-of-hours medical service (116117) or to poison control centres, alerts no rescue or standby services and cannot trigger calls (A § 6 paragraph 1). It does not assess or classify emergency calls, does not dispatch or prioritise emergency or rescue services, and does not rank callers by urgency, severity or need for treatment (A § 6 paragraph 4, B § 8 paragraph 1).
The emergency flag. If the language model recognises in callers' statements indications of an acute danger to body, life or mind, it flags the handover as an emergency. This flag has the sole effect that the transfer to the forwarding destination is initiated without asking for the name, without the offer of the Service's own capture and without deferral because of the high-load mode, and that in the cases named below the Service names the public bodies designated there. It has no further effects (A § 6 paragraph 2).
It is a probabilistic procedure. It has two states and no gradation; it is not a medical assessment, not triage, not a ranking and not a prioritisation relative to other callers, and it triggers no emergency call and no alerting of third parties. It may be absent, and it may be set incorrectly. RR42 does not promise that every emergency will be recognised or every flag will be correct. The Customer may not rely on it as the sole safeguard and sets up the same human follow-up process for flagged and for unflagged handovers (B § 8 paragraph 2).
If a handover flagged as an emergency is not established — because the Customer has not released forwarding for that time, because the forwarding destination is not reached, because the person reached there declines to take over, because no forwarding destination is stored, or because the connection used technically does not support forwarding —, the Service names to the caller the public body designated for the situation described and asks the caller to dial it themselves: in the case of mental distress the telephone counselling service (Telefonseelsorge), in the case of a physical emergency the rescue service 112, and otherwise the out-of-hours medical service 116117. Only then does it state that it cannot transfer the call, and captures the request (A § 6 paragraph 3).
If the emergency flag is absent and forwarding is not established, the Service says so and, irrespective of the course of the conversation, points out that in an emergency 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 out-of-hours medical service 116117 are to be dialled by the caller themselves. Naming a specific body relating to the situation described is not owed in this case.
A limit to be aware of: in the case of a handover flagged as an emergency that is not established, and in the case of forwarding that is not possible, the Service itself speaks the bodies and telephone numbers; their wording is thus fixed. In the other cases — in the case of deferral because of the high-load mode and outside the times at which forwarding is permitted — the notice is output via the language model; it is given, but its wording may differ from conversation to conversation.
The Service does not name a specific out-of-hours pharmacy, a poison control centre, an address or a further telephone number (A § 6 paragraph 3 sentence 2).
The Customer's responsibility remains. That callers reach a human in emergencies lies within its sphere: a reachable forwarding destination, release of forwarding outside opening hours, staffing capacity in the released times, a human follow-up process for flagged handovers, and a reference to the emergency number on its own channels (A § 6 paragraph 5, A § 11 paragraphs 2, 3 and 7).
7. Limits of speech understanding and of outputs
The Service generates speech and text outputs using machine-learning methods that work probabilistically. Individual outputs may be incomplete, misleading or factually incorrect, even if RR42 complies with all protective mechanisms. The freedom from error of every individual output is not owed (A § 5 paragraph 4).
In detail:
- The Service is conducted in German. Speech recognition, speech output and the dialogue specifications are set up in German. Callers who speak another language are not reliably understood. A foreign-language version is not part of the Service.
- RR42 does not promise that the Service understands every utterance, every proper name, every medicinal product name and every dialect variant correctly (A § 5 paragraphs 4 and 13). The telephone connection transmits a narrowband signal; names and digits are particularly susceptible on it. The Service asks again where something is unclear or has it spelled out, and reads back a stated callback number once, digit by digit; a mishearing cannot be ruled out in this way.
- The transcript is a machine speech recognition output and not a verbatim record.
- In the Pharmacy and Medical Practice product variants, the Service cross-checks a recognised medicinal product name through a second, professionally tuned speech recognition. This cross-check is a check of the speech recognition and not a professional check (B § 5 paragraph 4); it costs a short pause in the conversation. In the other product variants it does not take place.
- The Service invents nothing. It answers exclusively on the basis of the knowledge base and the standard content provided by RR42. What is not stored there it does not answer, but captures as a request.
- Interruption of the output by the caller is available only to the extent that the telephony route used for the Customer supports it (A § 5 paragraph 12).
- Form of address. The Service uses "Herr" or "Frau" only where the gender is known with certainty and otherwise speaks without a form of address.
Whether an erroneous output constitutes a defect is determined by the statutory provisions and the agreed quality; the above statements do not restrict the statutory concept of defect (A § 5 paragraph 4). On request, RR42 provides the Customer in text form with the evaluations available to it on recognition and handover errors from the Customer's conversations.
8. Behaviour in the event of failure of the language model and of other processing
The Service depends on providers for the language model, speech recognition, speech synthesis and telephony. If one of them fails, the conversation does not break off into silence; the caller is in every case addressed.
| What fails | What the caller experiences |
|---|---|
| Language model (conduct of the dialogue) | The Service states the fault and connects to a human. If no forwarding destination is stored or the connection cannot forward, it asks the caller to put the question again straight away |
| Speech recognition | The Service says that it currently does not understand and connects to a human; without a forwarding option it asks for repetition |
| Speech synthesis | The Service states the fault. Forwarding is not promised in this case |
| Forwarding fails | The Service says so, names the emergency number 112 and, in the Pharmacy and Medical Practice product variants, additionally the out-of-hours medical service 116117, and continues the conversation itself |
| A processing step takes unusually long | After about two seconds the Service gives a short waiting notice, and after about six seconds it aborts a hanging operation |
| The caller is silent | The Service asks twice whether the caller is still there and then says goodbye |
The route to the language model is restricted to places of processing in the Union and is set up fail-closed: if no endpoint in the Union is available, the request fails instead of leaving the Union. The failure is intended in this case; it keeps the conversation content in the Union. What the caller then experiences is set out in the first row of the table.
A forwarded conversation is removed from processing by the Service. From the start of the transfer it is with the Customer; the Service cannot absorb faults on the Customer's side.
9. How many calls are accepted at the same time
The Service accepts several calls per Customer at the same time. The number is nevertheless limited, and at two levels:
- Per target number. For each target number, a number of simultaneously conducted conversations is set on the telephony account. Which number applies to the Customer is shown in the order summary; RR42 additionally notifies the Customer of it in text form before go-live.
- Per telephony server. On the server on which the Customer's target number is operated, the number of simultaneously conducted conversations is additionally limited across all telephone numbers operated there; the value set is currently eight. This limit takes effect before the limit per target number. RR42 queries the utilisation of each server automatically every half minute and is notified as soon as capacity becomes scarce; a further server and the distribution of the telephone numbers to it are then set up by hand. There is no automatic expansion, and no assurance that the limit will never be reached is associated with this.
Limitations triggered by the Customer. In the customer account, a high-load mode can be activated in which forwardings, with the exception of emergency flags, are treated as busy; the Service then takes up the requests itself. The forwarding of a conversation flagged as an emergency is deferred neither because of utilisation nor because of the high-load mode (A § 5 paragraph 6).
Load peaks at providers. In load peaks at the telecommunications and AI providers used, calls may be accepted late or put through late. This does not limit the agreed availability.
10. Forwarding to a human
- Exactly one forwarding destination. The Service connects a running conversation to exactly one telephone number stored by the Customer. There is no selection among several destinations, no sequence, no fallback number and no distribution across several lines. Special-rate numbers and lines that themselves divert to the Service are not permitted (A § 7 paragraph 5).
- The first request for a human is deferred once. If a caller asks for an employee early in the conversation, the Service promises that it will connect and, in the same sentence, names what it could do itself immediately. It asks no question about this. If the caller does not accept this — and likewise in the case of silence or an unclear answer —, the call is connected. A caller who asks for a human later in the conversation is connected without this offer. A handover flagged as an emergency is never deferred.
- The Service counts handovers per telephone number over 90 calendar days. From the third handover of the same telephone number, it asks once for the name before forwarding and proposes to the Customer the inclusion in the priority list; from the same handover onwards, it no longer offers this telephone number to capture the request itself first, but connects immediately. Both effects occur at the same value — three handovers —, as B § 10 paragraph 5 sentence 3 conclusively discloses. A proposal takes effect only once the Customer adopts it (A § 5 paragraph 12, B § 10 paragraph 5).
- Outside the times for which the Customer has released forwardings, no forwarding takes place. The Service says so, takes up the request and, in the case of emergency indications, refers to the public routes (B § 7 paragraph 2).
- The announcement before the handover has a time budget. About eight seconds are available for speech synthesis and playback together, of which at most three seconds for the synthesis. If the budget expires, the handover is carried out even if the caller has not heard the sentence to the end — the promised forwarding takes precedence over the announcement.
- If the Service does not reach the forwarding destination or the person reached there declines to take over, it says so and continues the conversation itself in accordance with the released configuration. It does not end the connection without such a notice (A § 7 paragraph 5).
- A prompt to leave a voice message is not part of the Service, and no recording function exists (A § 7 paragraph 5, A § 12 paragraph 5).
- The test call in the customer account and the demonstration in the browser on the website run without a telephone connection and therefore cannot forward to a human. The Service says so there and names it as a limit of this version, not as a limit of the Service on the telephone.
11. Telephony, target number and caller number display
- RR42 provides no telephone line, allocates no telephone numbers to the Customer and enables no outgoing calls (A § 7 paragraph 4). The Customer sets up the call diversion itself with its telecommunications provider and bears that provider's charges (A § 7 paragraph 3).
- The target number is a technical endpoint of RR42 and is not allocated to the Customer. There is no entitlement to a particular area code; the target number has no relation to the Customer's local network. It may not be published or given to callers as a contact number (A § 7 paragraph 1).
- Number portability to RR42 does not take place, and the target number cannot be ported to another provider (A § 7 paragraph 6).
- The display of the callers' telephone number at the forwarding destination is not assured. It depends on the telecommunications providers involved; on one of the routes used, the provider replaces the displayed number with the target number. The display may also be suppressed (A § 7 paragraph 5).
- If the Customer's provider does not transmit the callers' telephone number or callers suppress it, the functions based on it — pre-filling of the callback number, priority and block lists, display on transfer — are not available or only available to a limited extent. In this case the Service asks for a callback number during the conversation (A § 7 paragraph 3).
- If the target number lies outside the German numbering space, the display of the callers' telephone number is to be suppressed on handover (section 120 para. 4 sentence 2 TKG (Telecommunications Act)), and the Customer's provider may charge international fees. RR42 points this out separately before the order and obtains the Customer's agreement (A § 7 paragraph 1).
- One telephony route is active per Customer. RR42 states which one in text form on request (A § 5 paragraph 12).
- There is no fallback route. A Customer is permanently assigned to a voice server; if this server or the upstream telecommunications provider fails, calls are not switched over to another route. Monitoring detects the failure and reports it; it does not remedy it. For the Customer this means: during such a fault the Service accepts no calls, and the calls diverted to the target number reach nobody — RR42 therefore points out that the call diversion should be cancelled for the duration of the fault. This notice is the reason why this line appears here: the call diversion lies with the Customer's provider, and only the Customer can cancel it (A § 7 paragraph 3, A § 8 paragraph 6).
- Notification in the event of a fault. RR42 notifies the Customer of an ongoing fault in text form at the stored notification address as soon as it is detected, stating the start, the known extent and — as far as foreseeable — the expected duration. Outside the support hours under A § 9 paragraph 2 there is no standby service; the notification is then sent automatically, and handling begins with the next support time.
12. Further limits of the conversation
- At most one successful capture of a request is provided for per conversation (A § 5 paragraph 12). If a caller states two mutually independent requests, they are combined in one case; a later correction changes this case and does not create a second one.
- A conversation has a maximum duration. It can be set in the customer account between one and thirty minutes; without its own setting it is five minutes. When it is reached, the Service says goodbye and ends the connection.
- The Service makes no outgoing calls, no advertising calls, no surveys and no sequential dialling (Annex A5 no. 3.2). A callback provided for by a request is a matter for the Customer.
- The Service does not evaluate personal aspects of callers, builds no profiles beyond the counting of handovers described in A § 5 paragraph 12 and B § 12 paragraph 1, and makes no statements on creditworthiness (section 2.3 of document C3).
- Notification and webhook. Captured requests are available in the customer account. In addition, the Service notifies the stored address and, where configured, triggers a webhook of the Customer. RR42 is not responsible for the delivery and availability of the Customer's systems.
13. Availability, maintenance and updates
- 99.5 % monthly availability is agreed per component (call acceptance and speech processing, customer account). In a calendar month this arithmetically allows around three and a half hours of unavailability without the promise being missed. The Customer's rights in respect of individual outages remain unaffected to the extent that the impairment is not insignificant (A § 8 paragraphs 1 and 5).
- Scheduled maintenance takes place in the regular maintenance window on Tuesdays from 02:00 to 04:00 (Europe/Berlin) and is announced at least 48 hours in advance. Within the window and outside the window together, it may not exceed four hours per calendar month; of this, no more than two hours may be attributable to maintenance outside the window. Maintenance outside the window is permissible only if it is technically not feasible within the window, requires its own announcement with the same notice period and may not fall within the period from 07:00 to 20:00 on working days.
- Emergency maintenance to avert a concrete security or stability risk is permissible at any time and without prior notice. RR42 informs of this, where possible in advance and otherwise without undue delay afterwards, and states the reason and duration.
- Maintenance times totalling at most four hours per calendar month are disregarded in calculating availability — of this, at most two hours for maintenance outside the window and at most two hours for emergency maintenance. Maintenance times in excess of this count as an outage, and maintenance may not be used to fall below the agreed availability. Maintenance is refrained from during times that the Customer has indicated in text form as emergency, standby or out-of-hours service times, unless it cannot be postponed (A § 8 paragraph 3).
- An update of the speech processing ends conversations that are running at that moment. RR42 therefore treats such an update as maintenance within the meaning of A § 8 paragraph 3, with the windows and notice periods regulated there. Software updates that do not interrupt running conversations are not maintenance and are not announced.
- The subject matter of availability is call acceptance together with the start of speech processing, as well as reachability of and login to the customer account. Not subject matter are the quality of an individual conversation, the substantive quality of an output, the content maintained by the Customer and the reachability of the forwarding destination (A § 8 paragraph 7).
- RR42 determines availability for a component only to the extent that it operates a measurement procedure for that component. RR42 notifies in text form which components these are, on what basis the determination rests and what significance it has, before go-live, upon every change and on request. The absence of a measurement procedure is not at the Customer's expense: the agreed 99.5 % remains owed for every component, and if the Customer conclusively demonstrates an unavailability on the basis of its own records — for example the call logs of its telecommunications provider — and RR42 cannot refute it, the Customer's demonstration is decisive (A § 8 paragraph 2).
- How the availability figure comes about — and what it does not say. It is derived from the outcomes of the calls that reached RR42 and is not measured externally. It says how these calls ended, not whether the line was up: a call that never reached RR42 leaves no trace, and a dead line generates zero calls and thus no outage in this calculation. An abort before the end of a conversation is missing from the count, because the call record is created only at the end; the fault rate therefore tends to turn out too favourable. Cases that may lie with RR42 or with the other side count only towards the lower bound. The absence or weakness of the measurement is not at the Customer's expense (A § 8 paragraph 2): the 99.5 % remain owed, and if the Customer conclusively demonstrates an unavailability on the basis of its own records, its demonstration is decisive if RR42 cannot refute it.
- Excluded minutes are calculated per Customer. Times of a justified block or suspension are excluded minutes under A § 8 paragraph 1 sentence 6 letter e, but only to the extent that the Customer is responsible for the reason; if this has not been decided or is denied, the time remains countable. The formula of A § 8 applies per Customer: across several practices or locations, the sum of excluded minutes is not a denominator, and the report therefore additionally shows it per practice. The excluded minutes do not change the fact that the figure is derived from call outcomes and not measured externally.
- A fallback route that puts calls through directly to the forwarding destination in the event of a fault in call acceptance is not available on every telephony route. RR42 notifies in text form, before go-live and upon every change, whether it exists for the Customer; where it is available, RR42 uses it (A § 8 paragraph 6).
- Model change. For the language model, speech recognition and speech synthesis, RR42 uses exclusively models from a vetted and approved portfolio. A change within this portfolio is neither announced individually to the Customer nor individually justified; it may not measurably worsen the quality of the speech recognition, of the answers and of the detection of emergency indications, and RR42 bears the burden of proof for this. RR42 states on request which providers and models the portfolio comprises (A § 10 paragraph 4).
- A model change takes effect for all Customers of a product variant at the same time. There is no staged rollout per Customer.
14. Support: hours, no on-call duty
- The support channel is an e-mail address or a channel named in the order. Telephone support is not part of the Service.
- Human support is available on working days from 09:00 to 17:00 (Europe/Berlin). A working day is Monday to Friday except for public holidays in Lower Saxony (A § 9 paragraphs 2 and 6).
- There is no human standby service outside these hours, unless it is expressly agreed in the order (A § 9 paragraph 2). A fault that begins on a Friday evening, at the weekend or on a public holiday is handled only in the next support time. The response time for a critical fault of at most four support hours runs exclusively within the support time.
- Automated monitoring outside the support time covers only the components for which RR42 operates a monitoring procedure. RR42 notifies in text form which these are, before go-live and on request. Automated monitoring does not give rise to any promise that an outage outside the support time will be detected or remedied (A § 9 paragraph 2).
- Irrespective of this, RR42 notifies of every fault known to it that wholly or partly prevents call acceptance without undue delay after becoming aware of it, and the agreed availability remains owed regardless of whether RR42 has noticed an outage (A § 8 paragraph 6, A § 9 paragraph 2).
- Recovery targets are target values. A particular time to remedy a fault is not owed; only the response time is binding (A § 9 paragraph 3).
- Not subject matter of support are training, maintenance of the knowledge base, legal, medical, pharmaceutical or tax information, and assistance with the Customer's systems (A § 9 paragraph 1).
15. Audio recordings, transcripts and erasure periods
- No audio recording of the conversation is made. The audio signal is processed solely transiently; a text transcript is stored. A recording function is not part of the Service and cannot be activated by the Customer — not on request and not for a fee either (A § 5 paragraph 5, A § 12 paragraph 5). Anyone who needs an audio recording cannot obtain it with this Service.
- At the start of every conversation the Service outputs a brief notice: the identification as an AI assistant, the notice of transcription and storage for processing by the Customer's office, and the notice of the possibility to object. The Customer may not remove it and may not word its greeting text in such a way that it is omitted (A § 12 paragraph 7).
- If a caller objects, the caller continues to be served and, where configured, forwarded; for this conversation neither transcript nor handover summary is stored, and RR42 erases text records already generated without undue delay, at the latest within 24 hours; a case already formed in the same conversation before the objection is also covered. If the caller subsequently, in the same conversation, of their own accord provides information for the processing of a request, or corrects or confirms such information, the case formed from it is stored together with the associated transcript; the change is documented in the call log (A § 12 paragraph 7). A conversation with an objection therefore yields no transcript to the Customer.
- For the brief cross-check of recognised medicinal product names, the Service in the Pharmacy and Medical Practice product variants holds a sliding window of at most 90 seconds of audio in working memory. It is not stored, cannot be retrieved via any interface and ends with the conversation.
- RR42 sets a shorter period per customer account on request. The data storage maintains a separate value per customer account for the transcript window and the case window, and the nightly erasure run enforces it. The user interface of the customer account does not yet show a control for this; until then a request in text form suffices, and RR42 sets the value. RR42 sets a longer period than the default only on the Customer's documented instruction (Annex 4 to Annex B1).
- The data stocks are erased after fixed maximum periods: transcript and handover summary as well as caller profile and the suggestions generated from it after 30 calendar days, the structured request including callback number after 90 calendar days, call metadata without reference to content after 12 months, queries of the research function together with the result after 180 calendar days; production data at the latest 30 calendar days after the end of the contract (A § 12 paragraph 6). Anyone who needs conversation content for longer must export continuously.
- For data erased from the production stock, there is a run-off period in the backups of at most 180 calendar days until the affected backup state has lapsed through regular overwriting (Annex B2 no. 5.2, Annex 4 to Annex B1).
- A restoration from a backup resets the state as a whole and thereby also brings back data erased in the meantime. It is therefore carried out only after prior assessment; the restored data stocks are erased again within three working days and the affected Customer is informed (A § 26 paragraph 3, Annex B2 no. 5.2).
16. Places of processing
The language model, speech recognition and the evaluation of the research question are processed in the Union; the route to the language model is restricted to serving stacks in the Union and is set up fail-closed (no. 8).
Speech synthesis takes place outside the Union. What is transmitted is the text to be spoken, which may contain names and medicinal product designations that are read back. Standard contractual clauses and a transfer impact assessment are in place; processing in the Union is being sought.
Where the Customer has stored a notification address, the content of the call leaves the Union with the notification via the dispatch service. The Customer decides on this and switches the route off by not storing an address; the case and the transcript are in any event available to the Customer in the customer account.
There is no notification limited to a content-free notice. If a notification address is stored and a call has generated a request, the notification always goes out with the complete call record as an attachment — as a PDF file and in machine-readable form. The Service does not check whether the transmission of call content by e-mail is permissible for this Customer (B § 2 para. 5 sentence 7); this decision is taken by the Customer alone, and it is expressed in whether the Customer stores an address. Anyone who may not receive call content by e-mail does not store a notification address.
For Customers to whom Part B of the AGB applies, the requirements of B § 2 paras. 5 and 6 apply in addition: RR42 uses only providers identified in Annex 3 to Annex B1 and bound to confidentiality in text form, and, before activation, provides without being asked the particulars stated there. If the Customer requires processing exclusively in the Union, RR42 will inform the Customer within ten working days whether and on what conditions it can offer this; if it cannot, the Customer may terminate without notice period.
Which providers are used for which function and in which places they process follows from Annex 3 to Annex B1 and from the online register of data formats.
17. Data security and data backup
The technical and organisational measures are set out in Annex B2. It discloses for itself what it does not deliver; for the decision on an order, the following points are of particular importance:
- Transcripts are not separately encrypted field by field beyond the encryption of the storage. To that extent, protection rests on access and authorisation control and on tenant separation.
- A loss of zero data is not promised. For stored call and request data, RR42 aims for a recovery point of no more than 24 hours; this is a target value and not a measured property. A particular recovery time and a particular frequency of data backup are not owed unless they are agreed in text form (A § 5 para. 10, A § 8 para. 9).
- Where RR42 operates no backup procedure for a component, it points this out to the Customer separately and prominently before the Customer's order and, until the procedure has been set up, makes the provision under A § 26 para. 1 available at any time, without a time limit and without a limit on quantity (A § 5 para. 10).
- Archiving beyond the erasure periods and a backup of data in the Customer's systems are not owed by RR42.
- Access by RR42 to call content takes place only on a case-by-case basis to remedy a fault or on the Customer's instruction; it is logged and evidenced to the Customer on request (B § 2 para. 3, Annex B2 nos. 3.3 and 4.2).
- The connector for an AI assistance system of the Customer is set up only by the holder of the customer account, granted only after sign-in, and limited to the data for which the signing-in user is authorised. The provider of this assistance system is not a sub-processor of RR42; the Customer decides on the transmission to that provider and is responsible for it. There is no unauthenticated access to call data (A § 5 para. 12).
18. Research function (Evidenz-Check)
The research function is available only in the product variants Apotheke and Arztpraxis and only in the plans that list it.
- It is aimed exclusively at the Customer's professionally authorised staff and is not part of the conversation with callers (B § 5 para. 5).
- It reproduces the content of published literature with a citation. It is not a professional assessment of the individual case, does not replace advice from the Customer's staff, and its result must not be passed on to callers as information from the Service.
- Its outputs are based on a probabilistic method. RR42 does not promise that every citation is relevant, complete or correctly reproduced (A § 5 para. 14, B § 5 para. 5).
- The Customer does not enter any details that make a calling or other person identifiable. RR42 points this out to the Customer in the customer account. Before transmission to the literature search, the application additionally checks the question mechanically for direct identifiers — form of address with a name, telephone number, e-mail address, long sequence of digits, IBAN, full date — and rejects it instead of sending it. This check is not a promise of completeness: a surname without a form of address, an address, or a medical history so rare that it makes a person identifiable will pass through it. The question itself is stored at RR42 in the Union.
- There is no erasure route for an individual research history. The stored data knows two routes: the period of 180 calendar days from the last entry and the erasure of the entire customer account. A selection with which an individual history or an individual entry could be erased exists neither in the customer account nor via the interface, because a research query is not bound to any telephone number or to any call. A request that relates to a person named in free text is carried out by RR42 by hand until then, and RR42 records the execution.
- The function cannot be switched on or off by the Customer. It is accessible within the product variants Apotheke and Arztpraxis as soon as the access required for it has been set up; only RR42 can switch it off, per customer account.
- The number of queries included per billing period is shown in the plan overview; queries beyond that are charged separately (A § 16).
19. Export, switching and handover of data
The Customer can retrieve call records at any time as a PDF file and in machine-readable form and can request its Customer data in full; RR42 provides them within ten working days and makes no charge for this (A § 26 para. 1). RR42 does not charge switching fees.
Three particulars in this regard that a Customer must know before ordering:
- Controls in the customer account exist so far only for the PDF version. The machine-readable version per call, the retrieval of the Customer data in full and the extract filtered to a named data subject can be retrieved via the authenticated interface of the customer account; the user interface does not yet show a button for this. Until one is added, RR42 generates the retrieval on request in text form, within the period of A § 26 para. 1 and free of charge.
- The retrieval in full has a quantity limit. Above a number of calls set operationally, it declines and refers to provision in text form; the period of ten working days then continues to run. A data stock that exceeds this limit is not output directly.
- The procedure around the export is organisational and is not stored in the system. For provision on request, the Service keeps no case and no deadline: receipt of the request, the ten-working-day period, the notification in text form about scope, format and retrieval route, the notice of extension before the period expires (A § 26 para. 1 sentence 6) and the erasure stop until complete provision (sentence 8) are handled and documented by the operational point of contact. The Customer's claims remain unaffected; this statement discloses what their observance relies on.
- After the end of the contract there is no separate read-only state of the customer account. The retrieval period under A § 26 para. 2 is maintained organisationally: the account remains accessible, and RR42 provides the provision under paragraph 1 within the period stated there. A technically enforced state of "open for reading, call acceptance off" does not exist.
- Research queries of the Evidenz-Check are not in the person extract. A research question is not bound to any telephone number or to any call; the extract filtered to a named person therefore does not capture it, and erasure at the request of a data subject draws the same line. They are included in the retrieval in full.
The limitations of this provision — among others, that no audio recording can be handed over, that the readable and the machine-readable versions are not identical in content, that the connector is not an export route and does not replace provision under no. 5 of the register, that RR42 does not owe any conversion into the format of a target system or any import into such a system, that the target number is not transferred and that erased data cannot be provided — are set out in full in no. 9 of the online register of data formats. They apply unchanged and are not repeated here.
20. What RR42 does not otherwise owe
Unless expressly agreed in text form, the following are not part of the subject matter of the performance: individual integrations, data migration and on-site services; the porting or provision of the Customer's telephone numbers; medical, pharmaceutical, legal or tax information or advice; an unlimited number of simultaneously handled calls beyond the number provided (A § 5 paras. 5 and 13).
The following are not part of the subject matter of the performance and cannot become so even by separate agreement: the function of an emergency call system and a recording function that makes audio recordings of calls accessible to the Customer (A § 5 para. 5).
Functions that RR42 labels in the customer account as "Beta", "Preview" or "Pilot" are not part of the performance owed. They are provided free of charge for trial purposes, may be changed or discontinued, and must not be used for safety-critical or supply-critical processes. This labelling must not be applied to functions that are shown as a feature of the service in the plan overview, in the order process or in the order (A § 10 para. 5).
21. Individual notices that exist alongside this statement
The AGB provide for their own notifications at several points. They continue to exist alongside this statement, and the deviations designated there are to be included here at the same time (A § 5 para. 11 last sentence). In detail, these are:
| Purpose | When | Reference |
|---|---|---|
| A component for which RR42 operates no backup procedure | before the order is placed, separately and prominently | A § 5 para. 10 sentence 4 |
| Whether audio recordings are produced on the telephony route used for the Customer | before going live, on request as evidence | A § 12 para. 5, B § 12 para. 3 |
| That transcripts and handover summaries are erased after 30 calendar days and structured requests after 90 calendar days and therefore must be exported on an ongoing basis | in the customer account and in the order confirmation, prominently | A § 12 para. 6 last sentence |
| Whether the recording of every access by RR42 employees to call content is technically complete | before activation and thereafter without undue delay | B § 2 para. 3 sentence 4 |
| Company name, registered office, place of processing, transfer instrument, transfer impact assessment and status of the undertaking for each provider outside the Union | before activation and before any change, without being asked | B § 2 para. 6 sentence 3 |
| Whether and for which of the outputs under A § 6 para. 3 the version of the Service provided does not support the emergency labelling or the notice, respectively | before going live and on every change, prominently | A § 6 para. 3 sentences 5 and 6 |
The first five rows are the individual notices expressly named in A § 5 para. 11 last sentence; the last row is a notification of the same kind and is therefore included here. If one of these notifications is not given, this has the consequences regulated in the relevant provision; this statement does not change that.
22. Updating
RR42 keeps this statement up to date in the customer account. RR42 informs the Customer in text form without undue delay of every newly included deviation (A § 5 para. 11 sentence 1).
Occasions for updating include in particular: a change to the Service under A § 10, a change of a telephony, language model, speech recognition or speech synthesis provider, a change to the places of processing, a change in the number of simultaneously handled calls, and any finding from ongoing operation that makes a statement in this document incorrect or incomplete.
Anyone who notices a deviation that is not stated here should report it via the support channel. RR42 reviews the report and includes the deviation if it is accurate.