Data Processing Agreement (DPA)
Pursuant to Art. 28 GDPR
octoja GmbH
Version date: 13 October 2026
This is a courtesy translation. The legally binding version is the German original.
Preamble
octoja GmbH (hereinafter the "Processor") processes personal data on behalf of the respective contractual partner (hereinafter the "Controller") in the course of providing the octoja RMM platform. This Data Processing Agreement (hereinafter the "DPA") governs the rights and obligations of both parties with regard to this processing pursuant to Art. 28 GDPR and supplements the main contractual documents existing between the parties (General Terms and Conditions or Terms of Use).
§ 1 Subject Matter and Duration of Processing
(1) The Processor processes personal data on behalf of the Controller exclusively for the provision, operation and maintenance of the octoja RMM platform and the associated support services.
(2) Processing takes place for the duration of the existing main contractual relationship. After termination of the main contract, the provisions on return and deletion pursuant to § 9 of this DPA shall apply.
§ 2 Nature and Purpose of Processing
(1) Purpose of processing: Operation of a Remote Monitoring & Management (RMM) SaaS platform for the administration, monitoring and automation of IT systems by the Controller (MSP/reseller) for its end customers, as well as the provision of the associated support services.
(2) Nature of processing: Collection, storage, transmission, modification, retrieval, use and deletion in the course of platform operation and the associated support services.
(3) Categories of data subjects:
- Employees and user accounts of the Controller (MSP/reseller).
- Employees and IT users of the Controller's end customers.
- Technical contact persons at end customers.
(4) Categories of personal data:
- Account data: Name, email address, username, role, password hash.
- System data of the managed end devices: Device name, IP address, MAC address, hostname, operating system data, installed software, hardware information.
- Connection and access data: Login timestamps, IP addresses, session data.
- Support and communication data: Content of support cases and email communication in the support context.
- Log data (logs): Activity logs, script executions, patch logs.
(5) Special categories of personal data pursuant to Art. 9 GDPR: Processing of special categories of personal data is not intended and must not be carried out by the Controller unless separately agreed in writing.
§ 3 Obligations of the Processor
(1) The Processor processes personal data exclusively on the documented instructions of the Controller – including with regard to the transfer of personal data to a third country – unless it is obliged to process the data under EU or EU Member State law.
(2) The Processor shall inform the Controller without delay if it considers that an instruction infringes the GDPR or other Union or Member State data protection provisions. The Processor is entitled to suspend the execution of the instruction in question until it is confirmed or amended by the Controller.
(3) The Processor ensures that the persons authorised to process personal data have undertaken an obligation of confidentiality or are subject to an appropriate statutory duty of confidentiality and, where relevant, are bound by § 203 of the German Criminal Code (StGB); see § 11.
(4) The Processor takes all measures required pursuant to Art. 32 GDPR. The specific technical and organisational measures are documented in Annex 1 (TOM) to this DPA.
The measures documented in Annex 1 describe the state implemented as of the stated date. The Processor is entitled to further develop and adapt the measures in line with the state of the art, provided that the level of protection agreed under this DPA is not thereby undercut. Such adaptations do not constitute an amendment of this DPA within the meaning of § 12(3). The Processor documents the adaptations and makes the respective current version of Annex 1 available upon request or via the platform. Changes to measures that lower the agreed level of protection require an agreement pursuant to § 12(3). The provisions on the engagement or replacement of sub-processors pursuant to § 5 remain unaffected.
(5) The Processor shall, where possible, support the Controller by appropriate technical and organisational measures in fulfilling its obligation to respond to requests from data subjects pursuant to Chapter III GDPR.
(6) The Processor shall assist the Controller in complying with the obligations pursuant to Art. 32–36 GDPR, in particular with regard to data security, notification obligations and data protection impact assessments.
(7) The Processor shall make available to the Controller all information necessary to demonstrate compliance with the obligations laid down in Art. 28 GDPR and shall allow for and contribute to audits, including inspections, conducted by the Controller or by an auditor engaged by the Controller. Audits must be announced at least four weeks in advance, must be limited to octoja's business hours and may not unreasonably impair business operations. The costs of the audit shall be borne by the Controller. This cost allocation does not apply to incident-related audits following a breach of the protection of personal data for which the Processor is responsible.
§ 4 Obligations of the Controller
(1) The Controller is the controller within the meaning of the GDPR – or, insofar as it processes the data on behalf of its own end customers, their processor – for all personal data that it processes or has processed via the platform. It ensures that a sufficient legal basis exists for each processing activity, including any data processing agreements that may be required with its end customers. In this regard, the Processor acts as a further processor (sub-processor).
(2) The Controller shall issue instructions for processing exclusively in writing or via the functions of the platform provided for that purpose. Oral instructions must be confirmed in writing without delay.
(3) The Controller shall inform the Processor without delay if it identifies errors or irregularities when reviewing the instructions or the processing.
(4) The Controller ensures that it fulfils the information obligations required under data protection law vis-à-vis its end customers and their employees.
§ 5 Sub-processors (Subcontractors)
(1) The Controller hereby grants the Processor a general authorisation to engage sub-processors. The Processor shall inform the Controller, in text form (e.g. by email or notification via the platform), at least four weeks before the intended engagement or replacement of a sub-processor. The Controller may object to the change in text form within two weeks of receipt for an important data-protection-related reason. If, in the event of an objection, no amicable solution is reached, the Controller is entitled to terminate the main contract for cause with effect from the date on which the change takes effect.
(2) Current sub-processors:
| Sub-processor | Registered office / processing details | Processing purpose |
|---|---|---|
| Hetzner Online GmbH | Germany (Nuremberg/Falkenstein) | Hosting, data centre operations, data storage |
| Hetzner Online GmbH (Object Storage) | Germany | Storage of encrypted database backups |
| Supabase Pte. Ltd. | Singapore; data processing exclusively in the EU, Frankfurt am Main region; safeguarded by EU Standard Contractual Clauses | Database for customer management |
| CORDNET OÜ (d/b/a Featurebase) | Estonia (Viimsi, Harju maakond, EU) | Ticket system, customer support |
| Microsoft Ireland Operations Ltd. | Ireland (EU) | Email communication in the context of support; may contain personal data from support enquiries |
| BunnyWay d.o.o. (Bunny CDN) | Slovenia (EU) | Content delivery network, delivery of static platform content |
| Sendinblue GmbH (Brevo) | Germany (Berlin) | Email notifications, transactional emails |
| seven communications GmbH & Co. KG | Germany | Alerting via phone call, SMS and WhatsApp |
When alerting via WhatsApp, phone numbers are transmitted to WhatsApp Ireland Ltd. / Meta. Use of the WhatsApp channel is optional and is activated by the Controller.
(3) Third-party services that the Controller activates and configures on its own responsibility via the platform, for example ThreatDown, Lywand or Acronis, are not sub-processors within the meaning of this DPA. A current overview is available at https://octoja.de/features/integrations. In this respect, the Processor acts solely as a technical integration layer; the data protection responsibility for the use of these services lies with the Controller; see § 8 of the Terms of Use.
(4) All sub-processors are contractually obliged to comply with a level of data protection equivalent to that of this DPA, including the obligations under § 11. In the case of transfers of personal data outside the EU or the EEA, the Processor ensures compliance with the requirements of Chapter V GDPR, in particular through an applicable adequacy decision or appropriate safeguards such as EU Standard Contractual Clauses and, where necessary, supplementary protective measures.
(5) The Processor is liable to the Controller for the fulfilment of the data protection obligations by its sub-processors to the same extent as for its own breaches.
§ 6 Rights of Data Subjects
(1) The Processor shall forward without delay to the Controller any requests from data subjects that are addressed directly to it. The Processor shall not respond to such requests independently unless expressly instructed to do so by the Controller.
(2) The Processor shall support the Controller, upon request, in fulfilling data subject rights, in particular access, rectification, erasure, restriction of processing and data portability, to the extent that this is technically possible and feasible within the scope of platform operation.
§ 7 Notification Obligations in the Event of Personal Data Breaches
(1) The Processor shall notify the Controller without delay of any breach of the protection of personal data within the meaning of Art. 4 No. 12 GDPR affecting data processed on its behalf that comes to its knowledge, as a rule within 24 hours of becoming aware of it. If not all the information required under para. 2 is available at that point in time, a preliminary notification shall be made first; the further information shall be provided without delay.
(2) The notification shall contain at least:
- The nature of the breach and the data categories affected.
- The approximate number of data subjects and data records affected.
- The likely consequences of the breach.
- Measures taken or proposed to remedy the breach.
(3) The Controller is itself responsible for notifying the competent supervisory authority and, where applicable, informing the data subjects pursuant to Art. 33 et seq. GDPR.
§ 8 Data Protection Impact Assessment
If a processing activity of the Controller requires a data protection impact assessment pursuant to Art. 35 GDPR, the Processor shall, upon request, support the Controller by providing the relevant information on platform operation and the technical measures employed.
§ 9 Deletion and Return after Termination of the Contract
(1) After termination of the main contract, the Processor shall delete all personal data of the Controller, unless statutory retention obligations preclude this. Deletion shall take place no later than 30 days after termination of the contract.
(2) Upon request of the Controller, which must be made before expiry of the 30-day period, the Processor shall make the data available in a common export format. The costs of a data export may be invoiced to the Controller.
(3) The Processor shall confirm complete deletion to the Controller in writing upon request.
§ 10 Liability
The liability of the parties under this DPA is governed by the liability provisions of the main contract, in particular § 7 of the General Terms and Conditions or § 6 of the Terms of Use, as applicable. In relation to data subjects, Art. 82 GDPR applies.
§ 11 Professional Secrecy Holders (§ 203 German Criminal Code)
(1) Insofar as the Controller is itself a professional secrecy holder within the meaning of § 203(1) of the German Criminal Code (StGB), or uses the platform for end customers who are professional secrecy holders, in particular tax advisors, auditors, lawyers, physicians and other members of the healthcare professions or insurance undertakings, the Processor acts as another person assisting within the meaning of § 203(3) sentence 2 StGB.
(2) The Processor undertakes to maintain secrecy regarding all third-party secrets that come to its knowledge in the course of providing the services, in particular secrets relating to the personal sphere of life as well as trade and business secrets, and neither to disclose nor to exploit them without authorisation. The Processor shall take note of protected information only to the extent necessary for the proper performance of the contractual service.
(3) The Processor shall, prior to commencement of their activity, bind in writing all persons who are involved in providing the services or who may obtain access to the Controller's data to confidentiality pursuant to § 203 StGB and inform them of the criminal liability for unauthorised disclosure pursuant to § 203(4) StGB. The Processor shall, upon request, provide the Controller with evidence that this obligation has been imposed.
(4) If the Processor engages sub-processors pursuant to § 5 who may obtain access to protected information, it shall bind them in the same manner to confidentiality pursuant to § 203 StGB and ensure that they, in turn, impose a corresponding obligation on the persons working for them.
(5) The Processor is entitled to make a disclosure insofar as it is legally obliged to do so. It shall inform the Controller of this in advance, to the extent permitted by law.
(6) The obligations under this section shall continue to apply without time limit beyond the termination of the main contract.
§ 12 Final Provisions
(1) This DPA is part of the main contract and is subject to the same applicable law, namely German law.
(2) In the event of contradictions between this DPA and the main contract, this DPA shall prevail with regard to data protection matters.
(3) Amendments to this DPA require the agreement of both parties in text form. The Processor shall notify the Controller of proposed amendments in text form at least 30 days before the intended effective date. The mere notification of an amendment or the Controller's silence does not constitute consent. § 5(1) shall apply, by way of derogation, to amendments concerning sub-processors. Further developments and adaptations of the technical and organisational measures pursuant to § 3(4) do not constitute an amendment of this DPA, provided that the agreed level of protection is not thereby undercut.
Annex 1: Technical and Organisational Measures (TOM).