Legal
Data Processing Agreement
This agreement under Art. 28 GDPR governs how we process personal data that a customer has monitored by Lynx Heartbeat. It forms part of the contract for the use of Lynx Heartbeat.
1. Parties, subject matter and duration
1.1 This Data Processing Agreement ("DPA") is concluded between the customer as controller and Agentur 404Media, Inhaber Stefan Pingel, Am Jungfernsee 21, 14469 Potsdam, Germany, as processor ("we" or "us"). It is concluded together with the contract for the use of Lynx Heartbeat under the Terms of Service (the "main contract").
1.2 Its subject matter is the processing of personal data that arises when the customer's servers and services are monitored by Lynx Heartbeat. Annex 1 describes the nature and purpose of the processing, the types of data and the categories of data subjects.
1.3 The DPA applies for the term of the main contract and beyond it for as long as we process the customer's data on its behalf.
1.4 Processing takes place in member states of the European Union (Annex 3). It is only moved to a country outside the European Union and the European Economic Area if the requirements of Art. 44 et seq. GDPR are met, and after prior notice to the customer in accordance with section 6.
1.5 If the customer is itself a processor – for example an agency monitoring its clients' servers – we act as a further processor. The customer makes sure that it is entitled to engage us and passes its principals' instructions on to us.
2. Instructions
2.1 We process the data only on documented instructions from the customer, unless the law of the European Union or of a member state requires us to process it otherwise; in that case we inform the customer of that requirement before processing, unless the law prohibits this.
2.2 The customer's instructions follow from the main contract, from this DPA and from the settings the customer and its users make in Lynx Heartbeat – for example which servers and monitors are monitored, who is notified and whether the AI help is switched on. The customer gives further instructions in text form to info@catama.de.
2.3 If we consider an instruction unlawful, we inform the customer without undue delay. We may suspend carrying it out until the customer confirms or changes the instruction.
2.4 We do not process the customer's data for our own purposes.
3. Duties of the processor
3.1 Persons with access to the data on our side are bound to confidentiality or are subject to a statutory duty of confidentiality. The duty continues after their work has ended.
3.2 We take the technical and organisational measures under Art. 32 GDPR that Annex 2 describes. We may develop them further as long as the level of protection does not fall.
3.3 We assist the customer by appropriate measures in answering requests from data subjects (section 7) and in meeting its obligations under Art. 32 to 36 GDPR, as far as the nature of the processing and the information available to us allow.
3.4 The contact person for data protection is Stefan Pingel, who can be reached at the postal address in section 1.1 and at info@catama.de.
4. Duties of the customer
4.1 The customer is responsible for the lawfulness of the processing, in particular for being allowed to monitor the servers and services and for informing the data subjects where necessary.
4.2 The customer decides which systems it monitors and which features it switches on. Lynx Heartbeat is designed to process technical metrics. The customer does not use it to deliberately process special categories of personal data (Art. 9 GDPR).
4.3 The customer informs us without undue delay if it finds errors or irregularities in the processing.
5. Services the customer connects itself
5.1 If the customer connects Lynx Heartbeat to a service of its choice – such as Telegram, Slack, Microsoft Teams, a webhook of its own, push notifications in the browser or the Anthropic API for the AI help – we transmit the data needed for that to this service on the customer's instruction.
5.2 The providers of these services are not our sub-processors. The customer contracts with them itself and checks itself whether the transfer is permitted – including where the provider processes data outside the European Union.
5.3 The AI help stays switched off until the owner of the account agrees and stores an Anthropic key of its own. Lynx Heartbeat shows beforehand which data is transmitted.
6. Sub-processors
6.1 The customer gives us general authorisation to engage further processors. Annex 3 lists those engaged at the time of conclusion.
6.2 If we intend to add or replace a sub-processor, we notify the owner of the account by email at least 30 days in advance. The customer may object to the change in text form within that period for good cause. If we do not find a solution, either party may terminate the main contract with effect from the date of the change.
6.3 We bind every sub-processor by contract to obligations that essentially correspond to those of this DPA, and we answer to the customer for it.
7. Rights of data subjects
7.1 If a data subject contacts us with a request under Art. 15 to 22 GDPR and the request recognisably concerns the customer's data, we forward it to the customer without undue delay and do not answer it ourselves.
7.2 The customer can view, correct and delete most data in Lynx Heartbeat itself – for example servers, monitors, notification recipients and subscribers of a status page. Where that is not enough, we assist on request.
8. Personal data breaches
8.1 If we become aware of a personal data breach affecting the customer's data, we report it to the owner of the account by email without undue delay.
8.2 As far as known, the report states the nature of the breach, the data and persons affected, the likely consequences and the measures taken or proposed. We supply missing details later.
8.3 We take without undue delay the measures needed to remedy the breach and mitigate its consequences, and we assist the customer with its obligations under Art. 33 and 34 GDPR.
9. Evidence and audits
9.1 On request we give the customer the information needed to demonstrate compliance with this DPA.
9.2 The customer may check compliance itself or through an auditor bound to confidentiality. Audits are first carried out on the basis of documents and information. If that is not sufficient for objective reasons, on-site audits are possible after reasonable notice during normal business hours, without unreasonably disturbing operations and while preserving confidentiality towards other customers.
9.3 The data centres are operated by our sub-processor. Audits there are subject to its conditions; we give the customer the evidence we receive from it.
9.4 For audits that go beyond one per calendar year and are not prompted by an incident or by an order of an authority, we may charge reasonably for our effort.
10. Deletion and return
10.1 After the end of the main contract we delete the customer's data according to the rules of the main contract (sections 2.3 and 10 of the Terms of Service), unless there is a statutory duty to store it. The owner of the account may also delete the account with all its data at any time.
10.2 During the term, the retention periods in Annex 1 apply. The customer can delete servers, monitors and other entries itself at any time; the related measurements are then removed.
10.3 Deleted data may still be contained in encrypted backups for up to 30 days. It is no longer processed there and is deleted when the backup expires.
10.4 If, before deletion, the customer asks for data to be handed over beyond the views and extracts available in Lynx Heartbeat, we agree the form and effort with the customer.
11. Liability and final provisions
11.1 Liability between the parties is governed by the main contract. Art. 82 GDPR remains unaffected.
11.2 In the event of conflict between this DPA and the main contract, this DPA prevails in matters of data protection.
11.3 Changes to this DPA are governed by section 18 of the Terms of Service. The law and place of jurisdiction of the main contract apply.
Annex 1: Subject matter of the processing
Nature and purpose
Collecting, storing, analysing, displaying, transmitting and deleting data in order to monitor the customer's servers and services reachable over the internet, to detect anomalies, to notify the customer and the recipients it names, to provide status pages and to produce reports, and, where the customer switches it on, to analyse access to the customer's websites (usage, origin, share of automated traffic, error pages).
Types of data
| Area | Data |
|---|---|
| Servers with the Lynx agent | metrics (such as CPU, memory, disks, network, state of services), check results, installed packages, system information (operating system, versions, services, network addresses of the server); names of the processes with the highest usage; for open ports the name of the process and of the user account; the number of failed SSH logins and of open sessions |
| Monitors | addresses of the websites and services checked, check settings, results and response times |
| Notifications | recipients and destinations (email addresses, chat IDs, webhook addresses, push endpoints), content and delivery history |
| Status pages | content of the page, messages; for subscribers the email address and the times of entry, confirmation email and confirmation |
| Incidents | history, cause, severity and who acknowledged an incident |
| AI help (only if switched on) | what was sent to Anthropic and the answer, for the customer to read back |
| Web traffic (only if the customer switches it on for a server) | counts condensed on the server from the web server's access log, per minute and page: page path without query, kind of origin, device type, human or machine, number of hits and visits, bytes transferred, status codes, response times. IP addresses, user agent strings and single requests do not leave the server; visits are counted with a daily changing key held only on the server. |
The Lynx agent never transmits file contents, command lines or environment variables. Failed logins are only counted – without IP addresses, user names or log lines. Databases are asked for counters, never for contents.
Categories of data subjects
- employees and agents of the customer, as far as their names occur in system information (for example as the name of a user account on a server) or they are entered as recipients of notifications;
- clients of the customer, as far as an agency monitors their servers;
- subscribers of the customer's status pages;
- visitors to the customer's websites, where the customer has switched on the analysis of access logs.
Retention during the term
- check results: at one-minute resolution for 90 days, then as hourly values for two years;
- server metrics: at one-minute resolution for 30 days, then as hourly values for 400 days;
- web traffic: at one-minute resolution for 90 days, then as hourly and daily values for at most two years; deleted at once on request when it is switched off;
- incident history: one year;
- unconfirmed subscribers of a status page: seven days.
Annex 2: Technical and organisational measures
Access
- Operation on servers in Hetzner data centres in Germany; the operator of the data centres is responsible for protecting the buildings and facilities.
- Sign-in with a password; passwords exist only as an Argon2id hash. Ten failed attempts lock the sign-in for 15 minutes.
- Second factor with an app code (TOTP) and recovery codes for every user; the owner of an account can make it mandatory.
- Sessions end after 12 hours. Four roles determine who may read and who may change.
- Tokens for invitation, password reset and installation are valid once and for a limited time; only their hash is stored.
- Secret keys the customer stores are kept encrypted (AES-256-GCM).
Separation of customers
- Each customer sees only its own data. The separation is enforced in the database (row-level security in PostgreSQL); the application signs in with a role that cannot bypass these rules.
- Agencies get a sub-tenant per client; the agency sees its clients, never the other way round.
- Public status pages show no server details, no versions, ports or causes.
Transmission
- Browser and agent talk to Lynx Heartbeat exclusively over HTTPS.
- The agent only opens outgoing connections on port 443; no port is opened on the customer's server.
The agent on the customer's server
- It runs under a user of its own without root privileges, refuses to start as root and needs no sudo rule.
- The service is confined by systemd (read-only file system, limited CPU time and limited memory).
- Agent updates carry a signed manifest (Ed25519); the agent verifies the signature and checksum before installing. New versions are rolled out in stages; a version that does not start cleanly is rolled back automatically.
Data minimisation
- The agent sends metrics and system information, no contents (see Annex 1).
- The AI help is switched off until the owner agrees; on request, names and addresses are replaced before sending.
Availability and recovery
- Daily backup of the database; an encrypted copy is kept at a second site (Falkenstein) for 30 days. Restoring from it has been tested.
- A second, independent monitoring service (the Lynx watchdog) checks whether Lynx Heartbeat itself is working.
Traceability and review
- Changes to settings are recorded in the change log; the delivery of every notification is logged.
- The web server's access and error logs are kept for 14 days and are then deleted.
- Automated checks run before each release of a new version, including checks of the separation of customers.
Annex 3: Sub-processors
| Sub-processor | Service | Place of processing |
|---|---|---|
| Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany | Lynx Heartbeat servers, encrypted backup, check locations | Germany (Nuremberg, Falkenstein), Finland (Helsinki), USA (Ashburn), Singapore |
| webhostone GmbH, Rheinvogtstraße 17, 79713 Bad Säckingen, Germany | mailbox and delivery of notifications, reports and status page messages by email | Germany |
Agreements under Art. 28 GDPR are in place with both.
The payment service provider Stripe (Stripe Payments Europe, Limited, Ireland) is not a sub-processor: it receives no monitoring data. Stripe only processes billing details for which we are the controller, and also acts as a controller in its own right when handling payments (see the Privacy Policy).