New: temperature, fans, power supplies and SSD health per server. View hardware health

Try it free

Data processing agreement

Deutsche Fassung

This English version is a convenience translation. The German version is legally binding.

Data processing agreement pursuant to Art. 28 of the EU General Data Protection Regulation (GDPR; German: DSGVO) for the “PeakNode” product
Last updated: November 2026

between the customer (hereinafter “Controller”) and Nelpx GmbH, Heininger Str. 9, 71554 Weissach im Tal, represented by the managing director Mandeep Singh (hereinafter “Processor”).

Responsible for the PeakNode platform and contact person of the Processor: Serge Efremov, Head of Strategy, Nelpx GmbH, email: privacy@peaknode.de

§ 1 Subject matter and duration #

(1) This agreement governs the processing of personal data by the Processor on behalf of the Controller in connection with the use of the PeakNode monitoring platform as software-as-a-service (hereinafter “Main Contract”, consisting of the terms and conditions and the booked plan).

(2) This agreement forms part of the Main Contract and takes effect upon its conclusion. It applies as long as the Processor processes personal data of the Controller, and at least for the term of the Main Contract.

(3) In the event of conflicts, this agreement takes precedence over the provisions of the Main Contract insofar as the protection of personal data is concerned.

§ 2 Nature, purpose, types of data and data subjects #

(1) The subject matter of the processing is the operation of PeakNode for the Controller: receipt, storage, evaluation and display of the data that the agent sends from the Controller’s servers, uptime, heartbeat, DNS and certificate checks, sending of notifications to the channels set up by the Controller, operation of status pages, reports and teams.

(2) The sole purpose is the provision of these services. No processing for the Processor’s own purposes takes place.

(3) The types of data, categories of data subjects and retention periods are set out in Annex 1.

(4) Data that the Processor processes as a controller in its own right (account, contract, billing, security of the portal) is not the subject of this agreement; the Privacy policy applies to it.

§ 3 Instructions #

(1) The Processor processes the data only on documented instructions from the Controller, including with regard to transfers to third countries, unless it is required to do so by Union or Member State law. In such a case, it informs the Controller of that legal requirement before processing, unless that law prohibits such information.

(2) The instructions are defined by the Main Contract, this agreement and the settings that the Controller makes in the portal (for example enabling NodeGuard per server, selecting notification channels, publishing status pages, inviting team members, deleting monitors). The Controller issues further instructions in text form to privacy@peaknode.de.

(3) If the Processor is of the opinion that an instruction infringes data protection provisions, it informs the Controller without delay. It may suspend the execution until the Controller confirms or changes the instruction.

§ 4 Confidentiality #

The Processor only deploys persons who have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. They are given access to the data only to the extent necessary for the service.

§ 5 Technical and organizational measures #

(1) The Processor takes the technical and organizational measures pursuant to Art. 32 GDPR described in Annex 2.

(2) It may adapt the measures to technical progress, provided that the level of protection is not reduced. It documents material changes.

§ 6 Sub-processors #

(1) The Controller approves the sub-processors listed in Annex 3.

(2) The Processor informs the Controller by email at least four weeks before engaging or replacing a sub-processor. The Controller may object within this period for an important reason under data protection law. If the parties cannot reach an agreement, the Controller may terminate the Main Contract as of the date of the change.

(3) The Processor contractually binds each sub-processor to the obligations of this agreement (Art. 28 (4) GDPR).

(4) Services that the Controller selects itself and to which PeakNode transmits data on its instruction do not constitute sub-processing, in particular the notification channels Microsoft Teams, Slack, Telegram, Discord, the recipients’ email mailboxes and webhook targets, as well as fonts that the Controller loads from Google for a status page. The Controller is responsible for these services.

(5) Furthermore, the comparison of package lists with OSV.dev does not constitute sub-processing, since only the package name, version and distribution are transmitted without any reference to the Controller.

§ 7 Rights of data subjects #

The Processor assists the Controller with appropriate technical and organizational measures in fulfilling the rights of data subjects under Chapter III GDPR. The Controller can implement many rights itself in the portal (access, export via the API, rectification, deletion of monitors, channels, members and subscribers). If a data subject contacts the Processor directly, the Processor forwards the request to the Controller without delay and does not answer it itself.

§ 8 Assistance, notification of breaches #

(1) Taking into account the nature of the processing and the information available to it, the Processor assists the Controller in complying with the obligations under Art. 32 to 36 GDPR (security, notification and communication of breaches, data protection impact assessment, prior consultation).

(2) The Processor notifies the Controller of a personal data breach without delay after becoming aware of it, to the email address of the account. The notification contains, to the extent known, the information pursuant to Art. 33 (3) GDPR; missing information will be provided subsequently.

(3) For assistance services that are not based on a breach by the Processor and go beyond the usual extent, the Processor may demand reasonable remuneration.

§ 9 Deletion and return #

(1) During the term, the Controller can delete data itself at any time and retrieve it via the API and the export functions of the portal.

(2) After the end of the services, the Processor deletes the data in accordance with the rules in Annex 1, at the latest upon deletion of the account, unless there is an obligation to store it under Union or Member State law. Data in backups is deleted when these expire in the regular course.

§ 10 Evidence and audits #

(1) Upon request, the Processor makes available to the Controller all information necessary to demonstrate compliance with the obligations under Art. 28 GDPR.

(2) It allows for and contributes to audits, including inspections, by the Controller or an auditor mandated by the Controller who is bound to confidentiality and is not a competitor of the Processor. Audits are announced with reasonable notice, usually four weeks, and are carried out during business hours. Evidence may also be provided by current audit reports or certificates.

§ 11 Place of processing, third countries #

Processing takes place in Germany. A transfer to a third country by the Processor or a sub-processor only takes place if the requirements of Art. 44 et seq. GDPR are met. Transfers that the Controller itself initiates by selecting notification channels or fonts (§ 6 (4)) are the responsibility of the Controller.

§ 12 Liability and final provisions #

(1) Art. 82 GDPR applies to liability. Otherwise, the liability rules of the Main Contract apply.

(2) Amendments to this agreement require text form. § 11 of the terms and conditions applies accordingly to amendments.

(3) Should individual provisions be invalid, the remainder of the agreement remains valid.

(4) For the on-premise version, this agreement only applies insofar as the Processor obtains access to personal data in the course of support services. Otherwise, the Processor does not process any data of the Controller in the case of the on-premise version.

Annex 1: Types of data, data subjects, retention periods #

AreaTypes of dataData subjectsRetention period
Measurement data of the agentutilization, hardware values, operating system; processes on GPUs with process ID, name and user name; serial numbers of drives and GPUs; names of servers and monitors assigned by the Controlleremployees and other users of the Controller’s serversretention period of the plan (14 days in the Proof of Concept plan, one year in Premium and Enterprise); incidents until deletion of the monitor
NodeGuard (only if enabled per server, Linux only)SSH sign-in lines with user name and source IP address or host name; open ports with local address and process name; package list and checksums of system files; from the web server access logs: IP addresses with attack patterns, many failed requests or a very high request rate, and a few truncated request lines with masked parameter values; at a CPU utilization of 90% or more, the five processes with the highest load including their ownerpersons who sign in or attempt to sign in via SSH; visitors to the Controller’s websites whose requests are identified as suspicious; employees of the Controller as owners of processesevents according to the retention period of the plan, at least one day; findings marked as resolved at least eight days; the most recent NodeGuard status of a server as long as the monitor exists
NodeCarenotices on components with findings and valuesas for measurement dataopen notices until resolved; completed notices 400 days
Uptime, heartbeats, DNS, domains and SSLchecked addresses, response times, response codes, certificate and registration data of domainsowners and operators of the checked targets, insofar as they are natural personsretention period of the plan; incidents until deletion of the monitor
Notificationschannel details (email addresses, webhook addresses, identifiers for Teams, Slack, Telegram, Discord); content of the messagesrecipients of the notificationschannels until deleted by the Controller
Status pageswhen accessed, only the technically necessary access data of the web server (as in section 3 a) of the privacy policy), no visitor statistics; email addresses and confirmation time of subscribersvisitors and subscribers of the status pagesaccess data as for the web server log files; subscribers until unsubscription or deletion
Teams and change logname, email address and permissions of the members; who created, changed or deleted what and when; acknowledgments and comments on incidentsemployees and agents of the Controllermembers until removal; change log according to the retention period of the plan

When a paid plan ends, the longer retention period continues to apply for 30 days. If the account is deleted, all data of the account is deleted. Special categories of personal data pursuant to Art. 9 GDPR are not the subject of the processing; the Controller does not set up monitors in such a way that such data is transmitted.

Annex 2: Technical and organizational measures #

Confidentiality

  • physical access control to the data centers: by the hosting provider in accordance with its evidence (Annex 3)
  • access to the portal: personal accounts, two-factor authentication via authenticator app (can be enforced by the Controller for team members), lockout after failed attempts per IP address and per account, password reset links valid once and for 60 minutes, passwords stored only as a hash
  • access of the agents: separate access token per server monitor with 192 bits of randomness, transmitted in the Authorization header and compared in constant time; a token only permits submitting data for exactly this monitor
  • access control in the portal: data is assigned to the account; team members receive permissions per area; access control enforced on the server side
  • administrative access of the Processor to the portal and the servers: limited to one named person (Serge Efremov, Head of Strategy, Nelpx GmbH, responsible for the PeakNode platform); administrative access is logged and the log is retained for 13 months
  • separation: processing separated per account; the on-premise version runs entirely at the customer’s site

Integrity

  • transmission exclusively via TLS; the agent verifies the certificate (no insecure connection), HSTS including subdomains
  • receipt only as JSON up to 1 MB with strict validation of numerical values; invalid values are stored as unknown
  • protection of all forms against cross-site request forgery; cookies with HttpOnly, Secure and SameSite; browser policies against embedding in third-party pages and content type sniffing
  • uptime checks and webhooks only to public targets, checked after DNS resolution, including for redirects
  • uploaded files only according to an allowlist, with random names, without script execution
  • change log: who created, changed or deleted what and when
  • the agent does not accept commands and does not open a port; it is available in plain text and can be reviewed by the Controller

Availability and resilience

  • operation in the IONOS data center in Frankfurt am Main
  • automated, redundant data backups on IONOS servers at three locations in Germany (Frankfurt am Main, Cologne and Berlin)

Procedures for regular review

  • review of the entire source code for security vulnerabilities (shell calls, SQL, authentication, CSRF, access control, uploads, XSS, SSRF, headers), most recently in October 2026; findings implemented
  • data minimization: the agent only sends NodeGuard data for servers for which the Controller has enabled NodeGuard; the agent does not send file contents, passwords, keys, environment variables or command lines

Annex 3: Sub-processors #

Sub-processorServicePlace of processing
IONOS SE, Elgendorfer Str. 57, 56410 Montabaurhosting of portal and database; server for the probe nodes used for uptime, DNS and certificate checks (own server of Nelpx GmbH at IONOS); sending of email via the IONOS mail server; automated, redundant data backupsGermany: hosting in Frankfurt am Main, probe nodes in Frankfurt am Main, data backups in Frankfurt am Main, Cologne and Berlin

Stripe (payment processing) and Cloudflare (protection against automated requests with Cloudflare Turnstile) do not process any data on behalf of the Controller; they are used by the Processor under its own responsibility (see Privacy policy).