Skip to content

Legal

Privacy Policy

This policy explains which personal data we process when you visit this website, create a Lynx Heartbeat account and use the service – and which rights you have.

1. Controller and contact

The controller for the processing of personal data on this website and in Lynx Heartbeat is:

Agentur 404Media, Inhaber Stefan Pingel, Am Jungfernsee 21, 14469 Potsdam, Germany. Email: info@catama.de, phone: +49 38791 80926.

Lynx Heartbeat is a service of CATAMA Software. The contact person for data protection is Stefan Pingel. For any question about data protection and to exercise your rights, you can reach him at the postal address above and at info@catama.de.

2. Two roles: our own processing and processing on behalf

Lynx Heartbeat monitors our customers' servers and websites. We act in two roles:

  • We are the controller for the data we process for our own purposes: when you visit this website, send an enquiry, sign up, for the account and its users and for billing. This policy is about that.
  • We are a processor for the data a customer has monitored by Lynx Heartbeat or processes through it – metrics and system information of its servers, results of its monitors, the recipients of its notifications and the subscribers of its status pages. The customer is the controller for that data. Section 12 gives a summary; the details are governed by the Data Processing Agreement.

How the product is built – data location, agent, separation of customers – is described on the Security and privacy page.

3. Visiting this website

Web server logs

When you open a page, our web server processes the data your browser transmits: the IP address, the time, the address requested, the status code, the amount of data transferred, the page visited before (referrer) and the browser identification. This is technically necessary to deliver the page and serves to keep operation secure, find errors and fend off attacks.

The legal basis is Art. 6 (1) (f) GDPR; our legitimate interest is secure and stable operation. The web server's access and error logs are kept for 14 days and are then deleted. To protect the forms against abuse we count requests per source address in memory for a short time.

Reach measurement

We measure the use of this website with a service of our own, run by CATAMA Software (webservice.catama-software.de). For each page view it processes the address requested, the referring page, the screen size, the type of browser and device, and campaign parameters; the IP address is used only for transmission and to tell visits apart and is not stored permanently. No cookies are set and no data is passed on to third parties. The “Do Not Track” setting of your browser is respected. The legal basis is Art. 6 (1) (f) GDPR; our legitimate interest is improving our offering. There is no reach measurement in the application or on status pages.

Beyond that, this website loads no fonts, scripts or images from third-party servers and uses no advertising tools. No profiles of visitors are created.

4. Cookies

We only set cookies that are necessary for operation or that store a setting you have chosen. There are no third-party cookies and no cookies for analytics or advertising. Consent is not required for this (section 25 (2) no. 2 of the German TDDDG); the legal basis for the related processing is Art. 6 (1) (b) and (f) GDPR.

On the pages of the website no cookie is set as long as you do not submit a form and do not go to the sign-in.

CookiePurposeLifetime
lynx_sessionkeeps you signed in12 hours
lynx_languageremembers the chosen language of the application1 year
lynx_themeremembers the light or dark appearance1 year
lynx_nav, lynx_fleet_viewremember how the navigation and the server list are displayed1 year
lynx_flashshows a notice once after a form60 seconds
lynx_login_step, lynx_invite, lynx_password_resetkeep a step in progress during sign-in, invitation or password reseta few minutes
lynx_invite_link, lynx_install_command, lynx_reinstall_command, lynx_ping_url, lynx_recovery_codesshow a newly created secret exactly onceup to 2 minutes

You can delete or block cookies in your browser. Without the lynx_session cookie you cannot sign in.

5. Access request through the contact form

Through the "Request access" form we process your name, your company, your email address and, if you provide them, the number of your servers and your message. Lynx Heartbeat does not store the form: the details go to our mailbox as an email and are deleted there once the enquiry has been dealt with, unless there is a statutory duty to retain them.

The legal basis is Art. 6 (1) (b) GDPR where your enquiry aims at a contract, otherwise Art. 6 (1) (f) GDPR; our legitimate interest is answering enquiries. The same applies if you write us an email or call us.

6. Sign-up and account

Sign-up

When you sign up we process the name of your company, your name, your email address and your password, and the language of the page. We do not store the password in plain text but only as a hash (Argon2id). We send a code to your address; the account is only created once you enter it. An unconfirmed sign-up is valid for 24 hours and is deleted after seven days at the latest.

To protect against abuse we limit the number of sign-ups per source address, per email domain and per day.

We record which version of the Terms of Service and of the Data Processing Agreement you accepted and which version of this policy was shown to you: the document, the date of its version, the language, the time and your name with your email address. The same happens when the owner of an account books a plan. We do not store an IP address for this. The legal basis is Art. 6 (1) (b) and (f) GDPR; our legitimate interest is proof of the conclusion of the contract. The owner sees these entries on the "Billing" page; they are deleted with the account. If an account has booked a plan, we keep this record for three years after the account is deleted (document, version, language, time, name of the account and email address of the accepting person) and then delete it; the legal basis is Art. 6 (1) (f) GDPR, our legitimate interest being the establishment, exercise or defence of legal claims (Art. 17 (3) (e) GDPR).

Account and users

For the account and each user we process name, email address, role, password hash, settings (such as language, appearance, notifications), the second-factor details if used, and current sign-ins (sessions). We store no IP address and no browser identification with a session. Failed sign-ins are counted to prevent passwords from being guessed. Changes to settings are recorded in a change log so that the customer can see who changed what. When the owner switches the analysis of web traffic on or off for a server, we also record which server, when, the name and email address of the person, the version of the Data Processing Agreement and the language in which the declaration was shown; these entries are kept as long as the account exists.

The legal basis is Art. 6 (1) (b) GDPR (performance of the contract for use) and, for security and protection against abuse, Art. 6 (1) (f) GDPR. If a user is invited by the owner of an account, we process that user's data on the basis of our legitimate interest and the customer's interest in giving its staff access.

7. Billing through Stripe

If the owner of an account books a plan, the payment service provider Stripe (Stripe Payments Europe, Limited, Ireland) handles the payment. We transmit the owner's email address and the ID of the account to Stripe; you enter the billing address, VAT ID and payment details at Stripe yourself when booking. We do not receive or store card numbers or bank details, only the link to the customer record at Stripe, the booked plan, the billing period and the state of the subscription. Stripe issues invoices on our behalf; in Stripe's customer portal you manage the payment method, invoices and cancellation.

The legal basis is Art. 6 (1) (b) GDPR and, for the retention of invoices and accounting records, Art. 6 (1) (c) GDPR in conjunction with commercial and tax law. Stripe also processes part of the data as a controller in its own right, for example for fraud prevention and to meet its own legal obligations; see Stripe's privacy policy for details.

8. Emails

We send emails that belong to the contract and to operation: the confirmation of the sign-up, notices about the trial and billing, invitations, password resets, confirmations of changes to your access and notices about material changes to the service or to these texts. The legal basis is Art. 6 (1) (b) GDPR. You cannot unsubscribe from these emails while the account exists.

Alert notifications and the weekly report go to the recipients the customer sets up in Lynx Heartbeat. Every recipient can unsubscribe from the weekly report through a link in the email.

We do not send advertising by email.

9. Recipients and processors

We pass on personal data only as far as the stated purposes require:

RecipientPurposePlace of processing
Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germanyprocessor: operation of the Lynx Heartbeat servers, encrypted backup, check locationsGermany (Nuremberg, Falkenstein), Finland (Helsinki), USA (Ashburn), Singapore
webhostone GmbH, Rheinvogtstraße 17, 79713 Bad Säckingen, Germanyprocessor: mailbox and delivery of our emailsGermany
netcup GmbH, Daimlerstraße 25, 76185 Karlsruhe, Germanyhosting: operation of the CATAMA Software server for the reach measurement of this website (section 3)Germany
Stripe Payments Europe, Limited, Irelandpayment service provider: payment, invoices, customer portalIreland; transfer to the USA possible

Hetzner, webhostone and netcup process data on our behalf; agreements under Art. 28 GDPR are in place with all three. Stripe is not a processor for monitoring data: Stripe only receives the billing details (section 7) and also processes them as a controller in its own right to handle payments. Beyond that we only pass on data if we are legally obliged to or if it is necessary to assert or defend legal claims.

Services a customer connects to Lynx Heartbeat itself – such as Telegram, Slack, Microsoft Teams, a webhook of its own, push notifications in the browser or the Anthropic API for the AI help – receive data only because and to the extent the customer sets this up. They are not service providers engaged by us.

10. Transfers to countries outside the EU

Lynx Heartbeat is operated in Germany. There are also check locations in Finland, the USA (Ashburn) and Singapore. The checkers there only fetch the public addresses that customers enter as monitors and send the results to the central system in Germany. They do not process personal data of customers. A transfer to a country outside the European Union and the European Economic Area may take place in connection with billing through Stripe. It is then based on an adequacy decision of the European Commission or on appropriate safeguards under Art. 46 GDPR, in particular the European Commission's standard contractual clauses. We will tell you the applicable basis on request.

11. Retention

We store personal data only for as long as the stated purposes require or the law demands:

  • Account and users: for the term of the contract. If the owner deletes the account, the account's data is removed. If a subscription ends, the data is kept for at least 90 days and may be deleted after that. An account you signed up for yourself and for which no plan was ever booked is deleted 14 days after the end of the trial.
  • Record of a deletion: after an account has been deleted we keep a short entry (name of the account, times, reason, a hash of the owner's email address – no address in plain text).
  • Backups: database backups are kept for up to 30 days and then deleted; deleted data may still be contained in them for that long.
  • Billing: invoices and accounting records for the retention periods required by commercial and tax law.
  • Enquiries: until they have been dealt with (section 5).
  • Web server logs: 14 days (section 3).
  • Reach measurement: 365 days (section 3).
  • Accepted terms: for the term of the contract; for accounts that booked a plan, three years beyond the deletion of the account (section 6).

12. Data we process on behalf of our customers

We process the following data not for our own purposes but on behalf of the customer using Lynx Heartbeat. If you have questions about it, please contact that customer first; we support the customer in answering.

  • The customer's servers: the Lynx agent sends metrics (such as CPU, memory, disks, network), check results, the installed packages and system information. Processes appear by name only. For open ports, the name of the process and of the user account it belongs to are transmitted. Failed SSH logins are only counted – without IP addresses, user names or log lines. File contents, command lines and environment variables are never transmitted.
  • Monitors: the addresses of the websites and services checked and the results of the checks.
  • Notifications: the recipients and destinations the customer sets up (such as email addresses, chat IDs, webhook addresses) and the delivery history.
  • Status pages: anyone who subscribes to a customer's status page enters an email address and confirms it through a link (double opt-in). Only the address and the times of entry, confirmation email and confirmation are stored – no IP address and no name. Unconfirmed entries are deleted after seven days; every message contains an unsubscribe link.
  • Web traffic: only if the customer switches the analysis on for a server. The agent condenses the web server's access log on the server into counts per minute and page; IP addresses, user agent strings and single requests do not leave the server.
  • AI help: only if the customer switches it on and stores its own Anthropic key. Then metrics, check results, incident data, system information and process names go to Anthropic – never file contents, command lines, user names or credentials. Anthropic acts on behalf of the customer, not on ours.

How long this data is kept: 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; the incident history for one year.

13. Your rights

Under the GDPR you have the right

  • to obtain information about the data stored about you (Art. 15),
  • to have inaccurate data corrected (Art. 16),
  • to have your data erased where there is no duty or reason to keep it (Art. 17),
  • to have processing restricted (Art. 18),
  • to receive your data in a commonly used, machine-readable format or have it transferred (Art. 20),
  • to object to processing based on Art. 6 (1) (f) GDPR on grounds relating to your particular situation (Art. 21).

To exercise a right, write to info@catama.de or to the postal address in section 1. You can view and change many details yourself in Lynx Heartbeat; the owner of an account can also delete the account completely there.

14. Complaint to a supervisory authority

You may lodge a complaint with a data protection supervisory authority, in particular at your place of residence, your place of work or the place of the alleged infringement (Art. 77 GDPR). The authority responsible for us is:

Die Landesbeauftragte für den Datenschutz und für das Recht auf Akteneinsicht Brandenburg, Stahnsdorfer Damm 77, 14532 Kleinmachnow, Germany.

15. Obligation to provide data, automated decisions

You are not obliged to give us data. Without the details marked as required at sign-up and at booking, however, we cannot create an account or conclude a contract.

There is no automated decision-making including profiling within the meaning of Art. 22 GDPR.

16. Security

The connection between your browser and Lynx Heartbeat is encrypted (HTTPS). Passwords exist only as a hash, a second factor is available to every user, and customers' data is separated from each other in the database. The technical and organisational measures are listed in detail in Annex 2 of the Data Processing Agreement.

17. Changes to this policy

We update this policy when Lynx Heartbeat, the service providers we use or the law change. The version on this page applies; the date at the top shows when it was last updated.