Data Processing Agreement (DPA)
Agreement on the processing of personal data on behalf of the controller pursuant to Art. 28 GDPR.
This Data Processing Agreement (hereinafter “DPA”) is an integral part of the Software Usage Agreement (SaaS) for “KITALE” (hereinafter “Main Agreement”) and applies uniformly to all customers of the processor. The DPA enters into force automatically upon signing of the Main Agreement and requires no separate signature.
Baumgartner IT (owner: Marc Baumgartner)
Klausenweg 28, 89568 Hermaringen, Germany
(acting for the “KITALE” project)
The respective customer who has concluded the Main Agreement with the processor.
§ 1 Subject matter and duration of processing
- 1.1
This DPA specifies the data-protection obligations of the parties in connection with the processing on behalf pursuant to Art. 28 GDPR that arise from the Main Agreement. It applies uniformly to all customers who conclude the Main Agreement with the processor.
- 1.2
The processor processes personal data on behalf and on the instructions of the controller within the scope of providing the software “KITALE”.
- 1.3
The duration of the processing corresponds to the term of the Main Agreement. Upon termination of the Main Agreement, this DPA also ends, without prejudice to the obligations to return and erase pursuant to § 10 of this DPA.
§ 2 Nature and purpose of processing
- 2.1
Personal data is processed exclusively for the purpose of providing and operating the software “KITALE” for the controller, in particular:
- Administration of child master data and group structures
- Parent and educator communication
- Absence reports and attendance documentation
- Meal ordering, billing and catering management
- Administration of education-and-participation benefits (BuT)
- AI-assisted assistant (chatbot, automation) to support facility administration
- Automatic translation of content (e.g. parent communication)
- Email dispatch (transactional emails, notifications)
- Technical operation, maintenance and support of the software
- Data backup (backups) pursuant to § 5 of the Main Agreement
§ 3 Type of personal data
- 3.1
The following categories of personal data are processed:
Children's data
- Master data (surname, first name, date of birth, gender)
- Group membership and care times
- Attendance and absence data
- Dietary preferences and meal orders
- Health data pursuant to Art. 9 GDPR (e.g. allergies, intolerances, special dietary needs)
- BuT notices and social data pursuant to Art. 9 GDPR (e.g. benefit approvals, funding status)
Data of parents/guardians
- Master data (surname, first name, address)
- Contact details (email address, phone number)
- Communication data (messages, notifications)
- Payment and billing data
Data of educators/staff
- Master data (surname, first name)
- Contact details (work email, phone number)
- Access credentials (username, encrypted password)
- Group assignment and role permissions
§ 4 Categories of data subjects
- 4.1
The processing concerns:
- Children cared for in the controller's facilities
- Parents or guardians of the children cared for
- Educators, pedagogical specialists and other staff of the controller
- Where applicable, further persons authorised by the facility (e.g. persons authorised for pick-up)
§ 5 Obligations of the controller
- 5.1
The controller is solely responsible for compliance with data-protection provisions, in particular for the lawfulness of the data processing and for safeguarding the rights of data subjects.
- 5.2
The controller issues all orders, sub-orders and instructions generally in text form (email is sufficient). Verbal instructions must be confirmed in text form without undue delay.
- 5.3
The controller informs the processor without undue delay if it identifies errors or irregularities in the processing of personal data.
- 5.4
The controller is obliged to obtain the necessary consents of the data subjects (in particular parents/guardians) insofar as consent is the legal basis for the processing. This applies in particular to the processing of special categories of personal data pursuant to Art. 9 GDPR.
- 5.5
The controller names a contact person for the processor for data-protection-related matters.
§ 6 Obligations of the processor
- 6.1
The processor processes personal data exclusively on documented instructions from the controller (“bound by instructions”), unless it is required to process by Union or Member State law to which it is subject. In this case, the processor informs the controller of this legal requirement before processing, unless that law prohibits such notification on important grounds of public interest (Art. 28(3)(a) GDPR).
- 6.2
The processor ensures that persons authorised to process personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality (Art. 28(3)(b) GDPR).
- 6.3
The processor takes all technical and organisational measures (TOMs) required pursuant to Art. 32 GDPR to protect personal data. The current TOMs are documented in Annex A to this DPA.
- 6.4
The processor supports the controller in fulfilling its obligations pursuant to Art. 32–36 GDPR (security of processing, notification of personal data breaches, data protection impact assessments, prior consultation).
- 6.5
The processor informs the controller without undue delay if it considers that an instruction from the controller infringes data-protection provisions. The processor is entitled to suspend the execution of the relevant instruction until confirmation or amendment by the controller.
§ 7 Sub-processors
- 7.1
The controller grants the processor a general authorisation to engage sub-processors pursuant to Art. 28(2) GDPR.
- 7.2
The sub-processors currently engaged are listed in Annex B to this DPA. Annex B is maintained centrally by the processor and published in its respective valid version at https://kitale.de/auftragsverarbeitungsvertrag. Upon conclusion of the Main Agreement, the controller consents to the use of the sub-processors listed in Annex B at the respective time.
- 7.3
The processor informs the controller at least 30 days in advance in text form (e.g. by email) of the intended use of new sub-processors or the change of existing ones and updates Annex B accordingly. The controller may object to the use in writing within 14 days of notification on legitimate data-protection grounds. The provisions of § 8.6 of the Main Agreement apply accordingly.
- 7.4
The processor contractually ensures that the sub-processors comply with the same data-protection obligations as set out in this DPA, in particular with regard to the technical and organisational measures and being bound by instructions.
- 7.5
The processor is liable to the controller for compliance with data-protection obligations by its sub-processors.
- 7.6
The processor engages Degeler Consulting e.U. as a narrowly limited sub-processor to provide support in connection with KITALE. Access by Degeler Consulting e.U. takes place exclusively insofar as this is necessary for product management, project coordination, customer communication, contract handling and data-protection process consulting. Access may in particular cover contract documents, software and administration interfaces, customer and communication data, support data as well as technical operating information such as logs or infrastructure information, in each case only to the extent necessary and exclusively on the instructions of the processor. Processing for its own purposes by Degeler Consulting e.U. is excluded.
§ 8 Rights of data subjects
- 8.1
The processor supports the controller, where possible, with appropriate technical and organisational measures in fulfilling requests from data subjects pursuant to Chapter III of the GDPR (in particular access, rectification, erasure, restriction, data portability, objection).
- 8.2
If a data subject addresses requests directly to the processor, the processor forwards the request to the controller without undue delay and awaits the controller's instruction, unless it is already evident from the request that it is intended to be directed to the controller.
- 8.3
The processor provides the controller with export functions via the software that enable the controller to fulfil data-subject rights independently (e.g. data export for access requests, deletion of individual records).
§ 9 Notification of personal data breaches
- 9.1
The processor notifies the controller of any breach of the protection of personal data (personal data breach pursuant to Art. 33 GDPR) without undue delay, but no later than within 24 hours of becoming aware of it.
- 9.2
The notification contains at least:
- A description of the nature of the personal data breach, where possible indicating the categories and approximate number of data subjects and records concerned
- The name and contact details of the data protection officer or other point of contact
- A description of the likely consequences of the breach
- A description of the measures taken and proposed to remedy and mitigate the breach
- 9.3
The processor supports the controller in fulfilling its notification obligations towards the supervisory authority (Art. 33 GDPR) and the data subjects (Art. 34 GDPR).
- 9.4
Insofar as the personal data breach was caused by the processor or its sub-processors, the processor takes appropriate measures to contain and remedy the breach without undue delay.
§ 10 Erasure and return of personal data
- 10.1
After termination of the Main Agreement, the processor erases all personal data processed on behalf in accordance with the provisions of § 9.4 and § 9.5 of the Main Agreement (30-day transition phase with export option, followed by complete erasure).
- 10.2
The erasure covers all copies of the data, including backups and backup copies, unless a statutory retention obligation exists (e.g. under the German Fiscal Code (AO) or Commercial Code (HGB)). In the case of statutory retention obligations, the relevant data is blocked and erased after expiry of the respective period.
- 10.3
The processor confirms the complete erasure to the controller in writing upon request.
§ 11 Evidence obligations and audit rights
- 11.1
The processor provides the controller with all information necessary to demonstrate compliance with the obligations laid down in Art. 28 GDPR.
- 11.2
The controller is entitled to conduct audits (inspections) or have them conducted by a commissioned auditor bound to confidentiality. The audits may include:
- Review of the technical and organisational measures
- Inspection of relevant documentation and certifications
- On-site inspections of the data centres (insofar as proportionate and taking into account the confidentiality interests of the processor and other customers)
- 11.3
Audits must be announced at least 14 days in advance in text form and carried out during normal business hours. The processor supports the controller in carrying them out. The costs of the audits are borne by the controller, unless the audit reveals material breaches by the processor.
- 11.4
The processor may also provide proof of compliance with its obligations by submitting suitable, current certifications or audit reports (e.g. ISO 27001, SOC 2). Such proof may replace an on-site audit, provided the controller agrees.
§ 12 Data processing in third countries
- 12.1
Personal data is processed exclusively within the European Union or the European Economic Area (EU/EEA). Hosting takes place on servers in Germany (cf. § 1.3 of the Main Agreement).
- 12.2
A transfer of personal data to a third country (outside the EU/EEA) or to an international organisation requires the prior written consent of the controller and is only permissible under the conditions of Art. 44–49 GDPR.
- 12.3
Should a sub-processor process personal data in a third country, the processor ensures that appropriate safeguards exist pursuant to Art. 46 GDPR (e.g. EU Commission standard contractual clauses, adequacy decision).
§ 13 Special categories of personal data
- 13.1
The parties are aware that, in the context of using the software, special categories of personal data pursuant to Art. 9 GDPR may be processed, in particular:
- Health data of children (allergies, intolerances, dietary particularities)
- Social data (BuT notices, funding status)
- 13.2
For these special categories, the processor takes additional protective measures, in particular:
- Encryption of data during transmission (TLS 1.2 or higher) and at rest (AES-256 or comparable)
- Strict access control based on the principle of least privilege
- Logging of all access to special categories of personal data
- Regular awareness-raising and training of staff in handling sensitive data
§ 14 Data protection officer
- 14.1
The processor's data protection officer (or the data-protection point of contact) can be reached at:
- Email: privacy@kitale.de
- 14.2
The controller informs the processor in text form of the contact details of its data protection officer (if appointed) or its data-protection contact person.
§ 15 Final provisions
- 15.1
This DPA is an integral part of the Main Agreement. In the event of contradictions between this DPA and the Main Agreement, the provisions of this DPA take precedence with regard to the protection of personal data.
- 15.2
The processor is entitled to unilaterally amend this DPA as well as Annexes A and B in the event of changes in the legal situation, regulatory requirements or the use of new sub-processors, provided that the level of data protection is not lowered as a result. The controller is informed of material changes at least 30 days before they take effect in text form (e.g. by email). The respective current version of this DPA is available at https://kitale.de/auftragsverarbeitungsvertrag.
- 15.3
Should individual provisions of this DPA be or become wholly or partially invalid or unenforceable, the validity of the remaining provisions shall not be affected.
- 15.4
This DPA is governed by the law of the Federal Republic of Germany, excluding the UN Convention on Contracts for the International Sale of Goods. The place of jurisdiction is – insofar as legally permissible – the registered office of the processor (Hermaringen, Germany).
This DPA requires no separate signature. It is deemed accepted upon signing of the Main Agreement.
Anhang A Technical and organisational measures (TOMs)
pursuant to Art. 32 GDPR — As of 21 Apr 2026
A.1 Confidentiality (Art. 32(1)(b) GDPR)
Physical access control (physical access to data-processing facilities)
- Hosting in ISO-certified data centres in Germany (e.g. Hetzner)
- Access control systems of the data-centre operator (chip cards, biometric systems, video surveillance)
- No physical access by the processor to the servers required (remote administration)
System access control (prevention of unauthorised use)
- Authentication via individual user accounts with a secure password
- Encryption of passwords using modern hashing methods (e.g. bcrypt)
- Automatic session time limit (session timeout)
- Protection of administration access via two-factor authentication (2FA)
Data access control (restriction to authorised data)
- Role-based access control
- Principle of least privilege
- Regular review of access rights
- Logging of access to personal data
Separation control (separate processing for different purposes)
- Logical tenant separation (each customer receives its own data area)
- Separation of production, test and development environments
- No use of real data in test or development environments
A.2 Integrity (Art. 32(1)(b) GDPR)
Transfer control (protection during transmission)
- Encryption of all data transmissions using TLS 1.2 or higher
- Encryption of data at rest (encryption at rest, AES-256 or comparable)
- Use of VPN connections for administrative access
Input control (traceability of data entry)
- Logging of creation, modification and deletion of records
- Assignment of inputs to individual user accounts
A.3 Availability and resilience (Art. 32(1)(b), (c) GDPR)
- Daily automated backups with at least 30 days' retention
- Redundant storage systems in the data centre
- Disaster recovery concept
- UPS protection and emergency power supply in the data centre
- Monitoring of system availability and automated alerting
A.4 Procedure for regular review (Art. 32(1)(d) GDPR)
- Regular review and updating of the TOMs (at least annually)
- Regular security updates and patches
- Awareness-raising and training of staff on data protection and information security
- Incident-response process for personal data breaches
Anhang B List of sub-processors
As of 24 Apr 2026
| Sub-processor | Address / Country | Type of service | Data processed | Safeguards (third country) |
|---|---|---|---|---|
| Hetzner Online GmbH | Industriestr. 25, 91710 Gunzenhausen, Germany | Server hosting, infrastructure (IaaS); AI assistant (Ollama, self-hosted on Hetzner); LibreTranslate (self-hosted, last fallback for translations) | All personal data stored in the software; AI requests and responses; text content to be translated | Not applicable (EU/EEA) |
| DeepL SE | Maarweg 165, 50825 Cologne, Germany | Automatic translations via DeepL API (preferred translation service) | Text content to be translated (e.g. messages, announcements) | Not applicable (EU/EEA) |
| Google Ireland Ltd | Gordon House, Barrow Street, Dublin 4, Ireland | Gemini API (fallback AI assistant); Google Cloud Translation API (fallback translations) | AI requests and responses (only if the primary AI service fails); text content to be translated (only if DeepL fails) | EU standard contractual clauses (SCCs); processing primarily in EU/EEA, where applicable USA on the basis of the EU-US Data Privacy Framework |
| Brevo (Sendinblue SAS) | 106 Boulevard Haussmann, 75008 Paris, France | SMTP service / email dispatch from the backend (transactional emails, notifications) | Email addresses, sender and recipient data, email content | Not applicable (EU/EEA) |
| Stripe, Inc. | 354 Oyster Point Blvd, South San Francisco, CA 94080, USA | Payment processing (wallet top-up via Stripe Checkout); processing of credit card, SEPA and mobile-payment transactions | Name, email address, payment data (credit card, IBAN), IP address, transaction data | EU standard contractual clauses (SCCs); EU-US Data Privacy Framework; Stripe Payments Europe Ltd (Dublin) as EU contracting partner |
| Groq, Inc. | 900 De Guigne Dr, Sunnyvale, CA 94085, USA | AI inference API (fallback AI assistant, 3rd priority after Ollama and Gemini); vision/OCR for document processing | AI requests and responses (only if the primary AI services fail); uploaded images for OCR processing | EU standard contractual clauses (SCCs); EU-US Data Privacy Framework; according to the Groq DPA, data is not used for model training |
| Degeler Consulting e.U. | Bruno-Marek-Allee 5/10/6, 1020 Vienna, Austria | Product management and project coordination; customer communication; contract handling; data-protection process consulting in connection with KITALE | Contract documents; software and administration access; customer, communication and support data; technical operating information such as logs or infrastructure information, in each case only insofar as necessary for the provision of services | Not applicable (EU/EEA) |
This list is maintained centrally by the processor and updated in the event of changes pursuant to § 7.3 of this DPA. The respective current version is available at https://kitale.de/auftragsverarbeitungsvertrag. Customers are informed of changes at least 30 days in advance by email.