Data Processing Agreement

Data Processing Agreement under Art. 28 GDPR. Part of the Sonar Terms of Service.

Last updated: November 17, 2026

1) Parties, Subject and Duration

This Data Processing Agreement ("DPA") is an annex to and part of the Terms of Service. It applies between you as the operator of a Minecraft server ("Customer", controller) and us, the entity named in our Imprint ("Sonar", processor).

Sonar processes personal data of the players who connect to the Customer's servers, on behalf of the Customer and only to provide the Service: detecting and blocking bots, VPNs and proxies, and showing the Customer statistics about the server and its players.

This DPA applies for as long as Sonar processes such data for the Customer. It ends with the deletion of the data under Section 10.

2) Nature and Purpose, Types of Data, Data Subjects

Data subjects: players who connect to a server that runs the Sonar plugin, and players the Customer adds to an exclusion list.

Data processed in transit only: the IP address and the username of a connecting player, sent by the plugin for real-time verification. This data is evaluated on the fly and is not written to any database.

Data stored: player events (joins and the results of verification: passed, failed, captcha, in-game challenge, blocked by country, as VPN or proxy, or by the blacklist). Each event holds the player's username, Minecraft protocol version, the hostname the player connected to, country and continent derived from the IP address, the network (AS number and operator), whether the IP address is a known VPN or proxy, the bot score, and the client brand if the plugin sends it. Also the entries of the Customer's VPN exclusion list (IP addresses, IP ranges, AS numbers, usernames).

Purpose: protection of the Customer's server against bot attacks and abuse, and statistics for the Customer. Sonar does not use this data for its own purposes, does not sell it and does not build profiles of players across customers.

3) Instructions

Sonar processes the data only on documented instructions from the Customer. The Terms of Service, this DPA and the Customer's settings in the dashboard and through the Sonar API are the Customer's complete instructions. Further instructions can be given in writing or by e-mail to the address in our Imprint.

Sonar informs the Customer without delay if it considers an instruction to infringe data protection law. Where Union or Member State law requires Sonar to process data otherwise, Sonar informs the Customer before processing, unless that law prohibits it.

4) Confidentiality

Sonar ensures that every person authorised to process the data has committed to confidentiality or is under an appropriate statutory obligation of confidentiality.

5) Security of Processing

Sonar takes the technical and organisational measures required by Art. 32 GDPR. They are described in Annex 1. Sonar may adapt them to technical progress as long as the level of protection does not fall.

6) Sub-processors

The Customer gives general authorisation for Sonar to engage the sub-processors listed in Annex 2. Sonar informs the Customer by e-mail at least 30 days before adding or replacing a sub-processor. The Customer may object within that period for a reasonable data protection reason. If the parties cannot agree, the Customer may terminate the affected part of the Service.

Sonar imposes the same data protection obligations as in this DPA on every sub-processor by contract, and remains liable to the Customer for the sub-processor's performance.

7) Data Subject Rights

Taking into account the nature of the processing, Sonar assists the Customer by appropriate technical and organisational measures in answering requests of players to exercise their rights under Chapter III GDPR. If a player contacts Sonar directly, Sonar forwards the request to the Customer without delay and does not answer it on the Customer's behalf unless instructed.

8) Assistance and Personal Data Breaches

Sonar assists the Customer in meeting its obligations under Art. 32 to 36 GDPR (security, notification of breaches, data protection impact assessments, prior consultation), taking into account the nature of the processing and the information available to Sonar.

Sonar notifies the Customer without undue delay, and where feasible within 24 hours, after becoming aware of a personal data breach that affects the Customer's data. The notification contains the information required by Art. 33(3) GDPR as far as it is available.

9) Retention

Stored player events are deleted automatically after the retention period of the Customer's plan: 7 days without a subscription, 14 days on Basic, 30 days on Premium, 90 days on Business and 180 days on Enterprise. A subscription pause extends the period by the length of the pause. Events of a deactivated or paused server are reduced to the last 30 days. Independent of the plan, no event is kept longer than 365 days.

Exclusion list entries are kept until the Customer removes them, at the latest until the account is deleted. Earlier values of a server's configuration stay in its change log for 180 days.

10) Deletion and Return at the End

When the Customer deletes a server, its analytics data is deleted. When the Customer deletes the account, all data, including the change logs, is deleted 30 days later; during these 30 days the account can be restored on request.

Before deletion the Customer can download its account data and server configurations in the account settings, and player events as a CSV file in the server analytics where the plan includes it. Sonar keeps no copy unless Union or Member State law requires storage.

11) Information and Audits

Sonar makes available to the Customer all information necessary to demonstrate compliance with Art. 28 GDPR and allows for and contributes to audits, including inspections, by the Customer or an auditor mandated by the Customer. Audits are announced at least 30 days in advance, take place during business hours, and must not disclose data of other customers or trade secrets. The Customer bears its own costs.

12) Transfers to Third Countries

Sonar processes and stores player data, including its backups, only in Germany (Annex 2). A transfer to a third country takes place only where the requirements of Chapter V GDPR are met.

13) Conclusion, Changes and Precedence

This DPA is part of the Terms of Service and is concluded together with them, in electronic form (Art. 28(9) GDPR).

Sonar informs the Customer by e-mail of any change to this DPA before it takes effect. In case of conflict, this DPA prevails over the Terms of Service in matters of data protection.

Annex 1: Technical and Organisational Measures

  • Encryption in transit: connections between the dashboard, the web application and the verification service use TLS.
  • Encryption at rest: secrets and selected account fields are encrypted at the application level.
  • Access control: dashboard access requires a sign-in; two-factor authentication is available. Team members see only the servers they were invited to, with the role the owner gave them. Sonar API keys are stored only as one-way hashes; credentials for the metrics export are stored encrypted.
  • Separation: every record is bound to the customer's account and server; queries are always scoped to them.
  • Data minimisation: IP addresses sent for verification are processed in memory and not stored. Stored events are deleted by plan (Section 9).
  • Abuse protection: rate limiting protects sign-up, sign-in and the API; sign-up and sign-in also require a proof-of-work challenge.
  • Logging: changes to a server's configuration are recorded with the account or API key that made them and the IP address, and deleted after 180 days.
  • Availability: regular backups at the hosting provider and monitoring with alerting.

Annex 2: Sub-processors

Sonar engages these sub-processors. Player data is processed only by the first; the second is listed for completeness.

  • dataforest GmbH, Taunusstraße 52, 65830 Kriftel, Germany: hosting of the server that runs the application, the databases and the verification service, and of the backups, in a data center in the Frankfurt am Main area, Germany.
  • Proton AG, Route de la Galaise 32, 1228 Plan-les-Ouates, Switzerland: delivery of e-mails to account holders. These e-mails contain no player data. Switzerland is recognised by the European Commission as providing an adequate level of data protection.