Allgemeine Abonnementbedingungen

Annex 1 to the Hellobot General Subscription Terms · version 1.0

This is an English translation provided for information only. The Polish version is binding.

§ 1. Parties and subject matter

  1. This Data Processing Agreement is concluded between the Client as the data controller (the "Controller") and Hellobot S.A., with its registered office in Wrocław (53-135), ul. Januszowicka 5, Poland, KRS 0000735214, tax ID (NIP) 634-292-71-63, as the processor (the "Processor").

  2. This Data Processing Agreement forms an integral part of the agreement concluded on the basis of the Order and the GST and is concluded together with the Order. Capitalised terms have the meaning given to them in the GST.

  3. The Controller entrusts the Processor with the processing of personal data to the extent and for the purpose set out in this Data Processing Agreement, and the Processor undertakes to process it in accordance with Regulation (EU) 2016/679 (the "GDPR"), national law and this Data Processing Agreement.

§ 2. Scope, nature and purpose of processing

  1. The purpose of processing is to provide the Service to the Controller, in particular handling conversations and communication through AI Agents, integrating with the Controller's systems, making results available in the Panel and providing technical support.

  2. The nature of processing includes in particular collecting, recording, transcribing, analysing, storing, making available to the Controller and deleting data, using artificial intelligence systems.

  3. The categories of data subjects, types of data and processing period are set out in Appendix A. The Order may specify additional categories of data relevant to a given Scenario.

  4. If a Scenario involves special categories of data (e.g. health data), the Controller indicates this in the Order or in documentary form before the Scenario goes live.

  5. Processing continues for the term of the Order and for the period necessary to fulfil the obligations referred to in § 10.

§ 3. Obligations of the Processor

  1. The Processor:

  • a) processes data only on documented instructions from the Controller. Instructions include in particular the Order, the GST, this Data Processing Agreement, the Scenario configuration and instructions given in documentary form or in the Panel;

  • b) promptly informs the Controller if, in its opinion, an instruction infringes the GDPR or other data protection laws;

  • c) ensures that persons authorised to process the data have committed themselves to confidentiality;

  • d) applies the technical and organisational measures referred to in Article 32 GDPR, described in Appendix C;

  • e) does not use the data for purposes other than providing the Service to the Controller, in particular not to train artificial intelligence models or to create or improve AI Agents of other clients;

  • f) maintains a record of categories of processing activities referred to in Article 30(2) GDPR.

  1. If the law requires the Processor to process data to a different extent, the Processor informs the Controller before processing begins, unless the law prohibits it.

§ 4. Sub-processors

  1. The Controller gives general authorisation for the Processor to engage sub-processors. The list of sub-processors on the date the Order is concluded constitutes Appendix B.

  2. The Processor informs the Controller in documentary form of any intended addition or replacement of a sub-processor at least 30 days in advance.

  3. The Controller may object within 30 days of receiving the notice. The Parties will then attempt to agree on a solution. If no solution is agreed before the planned change, the Controller may terminate the Order with effect from the date of the change, without having to pay the early termination fee referred to in § 16(7) of the GST.

  4. The Processor imposes on each sub-processor data protection obligations no less stringent than those under this Data Processing Agreement and is liable to the Controller for their performance as for its own acts.

§ 5. Location of processing

  1. The Processor processes data, including through sub-processors, exclusively within the European Economic Area.

  2. If a sub-processor is established outside the EEA or provides service access from outside the EEA, the transfer is safeguarded by standard contractual clauses adopted by the European Commission or by an adequacy decision.

§ 6. Personal data breaches

  1. The Processor notifies the Controller of a personal data breach without undue delay and no later than 24 hours after becoming aware of it.

  2. The notification includes, to the extent the information is available: a description of the breach, the categories and approximate number of data subjects and records, the likely consequences, the measures taken and proposed, and the contact person's details. Information not available at the time of notification is provided promptly once obtained.

  3. The Processor promptly takes action to mitigate the effects of the breach and cooperates with the Controller in investigating it, reporting it to the supervisory authority and notifying data subjects.

§ 7. Assistance to the Controller

  1. Taking into account the nature of processing, the Processor assists the Controller, as far as possible:

  • a) in responding to requests from data subjects. Any request addressed directly to the Processor is promptly forwarded to the Controller;

  • b) in complying with the obligations under Articles 32–36 GDPR, including data protection impact assessments (DPIA) and prior consultation with the supervisory authority.

  1. Assistance is provided within the pools of hours referred to in § 6 of the GST and, once they are used up, charged in Man Days according to the Price List. Assistance related to a breach attributable to the Processor is free of charge.

§ 8. Audits

  1. The Processor makes available to the Controller the information necessary to demonstrate compliance with the obligations under Article 28 GDPR, primarily in the form of documentation, answers to a security questionnaire and a summary of penetration test results.

  2. If the information referred to in section 1 is insufficient, the Controller may carry out an audit, including an inspection, itself or through an auditor bound by confidentiality who is not a competitor of the Processor. The audit:

  • a) takes place no more than once a year, subject to section 3;

  • b) is announced at least 30 days in advance, together with its scope;

  • c) is carried out on Business Days, in a way that does not disrupt the Processor's business or the security of other clients' data;

  • d) is carried out at the Controller's expense.

  1. The frequency limit does not apply to an audit following a personal data breach or an audit required by a supervisory authority.

§ 9. Obligations of the Controller

  1. The Controller represents that it has a legal basis for the processing of the data entrusted to the Processor.

  2. The Controller is responsible for fulfilling information obligations towards data subjects, including informing them about call recording and processing of data by the AI Agent, and for the content of information provided in the Scenario.

  3. The Controller does not transfer to the Service data beyond what is necessary to carry out the Scenario.

§ 10. End of processing

  1. At the Controller's request submitted no later than 30 days after termination of the Order, the Processor provides the Controller with an export of data in accordance with § 11(4) of the GST.

  2. No later than 14 days after the expiry of the period referred to in section 1, the Processor deletes the data, including copies, and provides the Controller with a deletion report, unless the law requires further retention.

  3. Data in backups is deleted in the normal backup rotation cycle. Until deleted, it remains protected and is not processed for any other purpose.

§ 11. Liability

  1. The Parties' liability under this Data Processing Agreement is subject to the rules and limitations set out in § 14 of the GST.

  2. Section 1 does not limit the Parties' liability towards data subjects under Article 82 GDPR.

§ 12. Final provisions

  1. This Data Processing Agreement applies for the term of the Order and until the obligations referred to in § 10 have been fulfilled.

  2. In matters relating to the processing of personal data, this Data Processing Agreement takes precedence over the GST.

  3. The Processor may update Appendices B and C. Changes to Appendix B are made in accordance with § 4. Changes to Appendix C may not reduce the level of data protection.

  4. Contact for data protection matters: admin@hellobot.cx.

Appendix A. Scope of processing

  1. Categories of data subjects: callers who contact the Controller, or whom the Controller contacts, through the AI Agent (in particular the Controller's customers, patients, passengers and business partners); Panel users on the Controller's side; the Controller's staff to whom conversations are transferred.

  2. Types of data: first and last name, phone number, e-mail address, voice recording and transcript of the conversation, content of statements, call metadata (date, time, duration), data relating to cases or bookings (e.g. appointment date, order number, booking reference), data provided by the Controller in import files or through integrations, login data of Panel users.

  3. Special categories of data: only where required by the Scenario and indicated in accordance with § 2(4) (e.g. health information provided by a patient).

  4. Retention period for recordings, transcripts and metadata: the Subscription Term of the Order, unless the Controller specifies a shorter period.

Appendix B. Sub-processors

  • Microsoft Ireland Operations Ltd. (Microsoft Azure, Azure OpenAI): hosting of the application, database, recordings, backups and monitoring; language model. Location: Norway (Norway East), Sweden (Sweden Central).

  • Soniox, Inc.: speech recognition and speech synthesis. Location: EEA (Scandinavia, Germany).

  • Google Cloud EMEA Ltd.: backup speech synthesis, used only if the primary provider fails. Location: EU regions.

  • ElevenLabs: backup speech synthesis, used only if the primary provider fails. Location: EU regions.

  • P4 sp. z o.o. (Play): sending SMS, if the Scenario includes SMS and the Controller has not designated its own provider. Location: Poland.

Microsoft (Azure OpenAI) applies its standard abuse monitoring mechanism and may retain prompts to the model for up to 30 days solely for that purpose, in the EU region, without using them to train models.

The telephone operator and SMS provider designated by the Controller act on behalf of the Controller and are not sub-processors of the Processor.

Appendix C. Technical and organisational measures

  1. Data is processed and stored exclusively in EEA regions. All of the Processor's personnel with access to data work in the EEA.

  2. Encryption of data in transit (TLS 1.2 or higher) and at rest (AES-256).

  3. Logical isolation of each client's data (multitenancy).

  4. User authentication with multi-factor authentication (MFA); access to data based on the principle of least privilege.

  5. Application protection with a web application firewall (WAF); secrets and keys stored in a dedicated key vault.

  6. Regular database backups with point-in-time recovery, encrypted and stored in the EEA.

  7. Event logging and infrastructure monitoring on the Processor's infrastructure in the EEA.

  8. Speech service providers process audio and text only for the duration of speech recognition or synthesis, without storing the data or using it to train models.

  9. Periodic security testing, including penetration testing.

  10. Confidentiality commitments from personnel and a procedure for handling personal data breaches.

Haben Sie Fragen? Kontaktieren Sie uns.

Haben Sie Fragen? Kontaktieren Sie uns.

Haben Sie Fragen? Kontaktieren Sie uns.

Kontakt

T:

+48 739 106 106

E:

hello@hellobot.cx

E:

Gawronów 6, Katowice,Polen

HalloBot

© Alle Rechte vorbehalten 2025

Kontakt

T:

+48 739 106 106

E:

hello@hellobot.cx

E:

Gawronów 6, Katowice,Polen

HalloBot

© Alle Rechte vorbehalten 2025

Kontakt

T:

+48 739 106 106

E:

hello@hellobot.cx

E:

Gawronów 6, Katowice,Polen

HalloBot

© Alle Rechte vorbehalten 2025