Skip to content

Legal

Terms of Service

These terms govern the use of Lynx Heartbeat, the server and website monitoring service of CATAMA Software. The service is offered to businesses only.

1. Scope and provider

1.1 Lynx Heartbeat is provided by Agentur 404Media, Inhaber Stefan Pingel, Am Jungfernsee 21, 14469 Potsdam, Germany ("provider", "we" or "us"), who is your contracting party. Lynx Heartbeat is a service of CATAMA Software. You can reach us by email at info@catama.de and by phone on +49 38791 80926.

1.2 These Terms of Service ("terms") apply to every contract for the use of Lynx Heartbeat between the provider and the customer – to the free trial as well as to a booked plan.

1.3 Lynx Heartbeat is offered exclusively to entrepreneurs within the meaning of section 14 of the German Civil Code (BGB), to legal entities under public law and to special funds under public law. Consumers within the meaning of section 13 BGB cannot use Lynx Heartbeat. By signing up you confirm that you are acting in the course of your trade, business or profession.

1.4 If you enter into the contract on behalf of a company or another organisation, you warrant that you are authorised to do so. The customer makes sure that every user it gives access to its account complies with these terms.

1.5 Deviating, conflicting or supplementary terms of the customer do not become part of the contract, even if we do not expressly object to them.

1.6 The Data Processing Agreement under Art. 28 GDPR (/dpa) forms part of the contract. In matters of data protection it takes precedence over these terms.

2. Conclusion of the contract and trial

2.1 The presentation of Lynx Heartbeat on the website is not a binding offer. The contract for use is concluded when you sign up, accept these terms and confirm your email address with the code we send you. The account is only created upon confirmation. If we set up access at your request, the contract is concluded when the access is provided; these terms apply in that case too.

2.2 A free trial of 7 days starts with the account. During the trial every feature is available, limited to 10 servers, 50 monitors and 3 published status pages. No payment details are needed. The trial does not turn into a paid plan by itself.

2.3 When the trial ends, you decide: you book a plan or you delete the account. If you signed up yourself and do not book a plan, monitoring is paused when the trial ends and the account is deleted with all its data 14 days after the end of the trial. We will tell you by email beforehand, the last time at least 3 days before the deletion.

2.4 A paid contract is only concluded when the owner of the account chooses a plan on the "Billing" page and completes the booking with the payment service provider (section 7). Before you complete it, you see the chosen plan, the billing period and the price.

2.5 You provide true information about your business when signing up and while using the service, and you keep the owner's email address up to date. We send notices about the contract, billing and operation to that address.

2.6 The contract languages are German and English. If the language versions of these terms differ, the German version prevails.

2.7 We record which version of these terms and of the Data Processing Agreement the customer accepted at sign-up or at booking, in which language and when. The owner of the account sees these entries on the "Billing" page.

3. What Lynx Heartbeat provides

3.1 Lynx Heartbeat is software that we provide over the internet (software as a service). It monitors the customer's servers and services reachable over the internet and notifies the customer when something is wrong. Depending on the booked plan, the service includes in particular:

  • monitoring of Linux servers by the Lynx agent, a program the customer installs on its servers and which sends metrics and check results to Lynx;
  • monitors: checks from outside, for example of websites, certificates and reachability, from check locations in Nuremberg, Helsinki, Ashburn (USA) and Singapore, and heartbeat monitors for recurring jobs;
  • alerts and notifications through the channels the customer sets up;
  • incidents with their history, security notices about installed packages, status pages and the weekly report;
  • optionally, AI help with the customer's own Anthropic key and read-only MCP access (section 6).

3.2 The exact scope is described on the website (the "Features" and "Pricing" pages) and in the Lynx Heartbeat interface as current from time to time. The quantities and features of each plan are listed on the Pricing page.

3.3 We keep developing Lynx Heartbeat and may change, add to or replace features with equivalent ones as far as this is reasonable for the customer. A change is reasonable in particular if it is needed because of a change in the law, for reasons of security or data protection, because of the state of the art or because of changes to third-party services, or if the agreed service essentially remains the same. If an essential feature of a booked plan is removed without replacement, we announce this at least one month in advance; the customer may then terminate with effect from the date of the change.

3.4 Installation, set-up, consulting, training and custom adaptations are not owed unless expressly agreed. The customer's internet connection, its servers and the software needed there are not part of our service.

4. Availability, maintenance and limits of monitoring

4.1 We operate Lynx Heartbeat with the care of a diligent provider and aim to keep the service reachable around the clock. We do not promise a specific availability; uninterrupted availability is not owed.

4.2 The service may be unavailable in whole or in part from time to time for maintenance, updates and to avert security threats. Where possible we schedule plannable work for times of low use and announce it if it noticeably restricts the service.

4.3 Lynx Heartbeat is an aid. It does not replace the customer's own care in operating its systems. In particular:

  • We do not promise that every fault, outage or vulnerability is detected, nor that a notification arrives in time or at all. Notifications depend on networks and services we do not operate (email, messengers, push services, webhooks).
  • Security notices are based on publicly available sources. They may be incomplete and do not replace a security audit.
  • Forecasts, analyses and the answers of the AI help are assessments. Lynx Heartbeat does not execute anything on the customer's servers; the customer decides what to do.
  • The customer sets up and tests its own alert rules and channels and keeps additional safeguards of its own for systems whose failure would have serious consequences.

4.4 Lynx Heartbeat is not intended for uses in which a failure or an undetected fault can endanger life or health.

5. Duties of the customer

5.1 The customer uses Lynx Heartbeat only in accordance with the law and these terms.

5.2 The customer only monitors its own systems and addresses or those it is entitled to monitor. Monitors must not be used to probe third-party systems, to put load on them or to impair their availability. Agencies make sure that their clients agree to the monitoring.

5.3 The customer installs the agent on its servers at its own responsibility. It keeps installation tokens, credentials, recovery codes and secret keys confidential, gives them only to authorised persons and changes or revokes them if an unauthorised person may have obtained them. We recommend switching on the second factor for all users.

5.4 The customer is responsible for all actions taken through its accesses to the extent it is at fault. It informs us without undue delay if it suspects misuse of its account or a security breach.

5.5 The customer refrains from anything that impairs the operation or security of Lynx Heartbeat, in particular from attempts to circumvent safeguards, to access other customers' data or to put more than ordinary load on the service.

5.6 The customer alone is responsible for the content it publishes or sends through Lynx Heartbeat – in particular on status pages and in messages to their subscribers.

5.7 If the customer culpably breaches this section, we may block access in whole or in part as far as this is necessary to stop the breach. We announce the block in advance unless there is imminent danger, and lift it as soon as the breach has ended.

6. Third-party services chosen by the customer

6.1 The customer may connect Lynx Heartbeat to third-party services, such as Telegram, Slack, Microsoft Teams, a webhook of its own, the push services of browser vendors or the Anthropic API. These services are not part of our service. They are subject to the terms of the respective provider; the customer contracts with that provider itself.

6.2 By setting up such a channel, the customer instructs us to send the content of notifications there. We are not responsible for the availability, security or data processing of these services.

6.3 The AI help is switched off until the owner of the account agrees to it and stores an Anthropic key of its own. Anthropic bills the costs directly to the customer. Lynx Heartbeat shows which data is transmitted before it is switched on. MCP access only allows a Claude application of the customer to read, and only after the owner has approved it.

7. Plans, prices and payment

7.1 The prices stated at the time of booking on the "Billing" page and on the Pricing page apply. At the date of this version of the terms these are, per month:

PlanBase price per monthServers includedMonitors includedEach further server per month
Start€9310€3.00
Team€291550€2.00
Agency€7950200€1.50

7.2 All prices are net prices in euros plus statutory value added tax. VAT is calculated at the time of booking and shown separately on the invoice.

7.3 Payment is made monthly or yearly in advance. With yearly payment the price is 10 times the monthly price; this applies to the base price and to each further server.

7.4 A server is a machine with the agent installed that is active in the customer's account. If the customer uses more servers than its plan includes, each further server is charged at the stated price. Lynx Heartbeat reconciles the number of servers regularly; if a server is added or removed during the current billing period, it is charged or credited pro rata. For monitors and status pages the included quantity is the upper limit; for more, the customer moves to a larger plan. For agencies, the servers and monitors of all sub-tenants count towards the agency's plan.

7.5 Payment is handled by the payment service provider Stripe. The payment methods offered at the time of booking are available. The customer receives invoices electronically. The owner of the account manages the payment method, invoices and cancellation in the customer portal, which is reached from the "Billing" page.

7.6 If a payment fails, the payment service provider retries the charge and notifies the customer. If payment is still not made after these attempts, the subscription ends; section 10 then applies. Statutory rights in the event of default remain unaffected.

7.7 The customer may only set off claims that are undisputed or have been finally established by a court. It may only exercise a right of retention for counterclaims arising from the same contract.

7.8 The customer raises objections to an invoice in text form within eight weeks of receipt. Statutory claims in the case of justified objections after that period remain unaffected.

8. Price changes

8.1 We may adjust prices for the future at our reasonable discretion to reflect changes in our costs, for example for the data centre, check locations, delivery services and staff.

8.2 We notify the owner of the account of a price change by email at least six weeks before it takes effect. It applies at the earliest from the next billing period that begins after that notice period; a period already paid for is not affected.

8.3 The customer may terminate the contract with effect from the date the price change takes effect, at any time before that date. We point this out in the notice.

9. Term and termination

9.1 The contract for a plan runs for the chosen billing period (one month or one year) and renews for the same period each time unless it is cancelled beforehand.

9.2 The customer may cancel at any time with effect from the end of the current billing period. Cancellation is made in the customer portal (section 7.5) or in text form to info@catama.de. The plan remains usable until the end of the period paid for.

9.3 We may terminate the contract with one month's notice to the end of the current billing period.

9.4 The owner of an account may also delete the account with all its data at any time (the "Billing" page). A running subscription then ends immediately; a period already paid for is not refunded.

9.5 The right of both parties to terminate for good cause remains unaffected. For us, good cause exists in particular if the customer repeatedly or seriously breaches section 5 despite a warning.

9.6 If the customer changes plan, the quantities and prices of the new plan apply from the time Lynx Heartbeat states before the change is confirmed.

10. Consequences of the end of the contract and deletion of data

10.1 If a subscription ends and the customer does not book again, monitoring continues unchanged for 14 days. After that no notifications are sent and no servers can be added; the data is kept and remains visible. The same applies when the trial of an account that we set up for the customer expires.

10.2 We keep the account's data for at least 90 days after the end. After that we may delete the account with all its data. If the customer books again before then, the account continues with its data.

10.3 Section 2.3 applies to accounts the customer signed up for itself and for which it never booked a plan.

10.4 The customer saves any data it needs beyond the end of the contract in good time. After deletion, data and settings cannot be restored. The customer itself meets retention duties under commercial and tax law for its own records.

10.5 After the end of the contract the customer removes the agent from its servers.

11. Rights of use

11.1 For the term of the contract the customer receives the non-exclusive, non-transferable and non-sublicensable right to use Lynx Heartbeat within the booked plan for its own business purposes. Agencies may also use Lynx Heartbeat for their clients' systems and give those clients access through sub-tenants.

11.2 The Lynx agent may be installed and run on the customer's monitored servers for the term of the contract. Open-source components are subject to their own licences.

11.3 All other rights in Lynx Heartbeat, the website and the documentation remain with us or our licensors. The customer may not rent out or resell Lynx Heartbeat or make it available to third parties outside the scope of section 11.1 and, unless mandatory law permits it, may not reverse engineer it.

11.4 The customer's data remains the customer's data. We process it only to perform the contract.

12. Defects

12.1 We provide our services as described on the website and in the interface. The customer reports defects without undue delay and precisely enough for us to reproduce them.

12.2 We remedy defects within a reasonable time. Strict liability for defects that already existed when the contract was concluded (section 536a (1) BGB) is excluded.

12.3 During the free trial we are liable for defects only if we fraudulently concealed them.

12.4 Section 13 applies to damages.

13. Liability

13.1 Our liability is unlimited for intent and gross negligence, for damage arising from injury to life, body or health, under the German Product Liability Act and to the extent of a guarantee we have given.

13.2 In the event of a slightly negligent breach of a material contractual obligation, our liability is limited to the damage that was foreseeable when the contract was concluded and is typical for contracts of this kind. Material obligations are those whose fulfilment makes the proper performance of the contract possible in the first place and on whose observance the customer may regularly rely.

13.3 Otherwise our liability for slight negligence is excluded.

13.4 For loss of data caused by slight negligence we are liable only for the effort that would be needed to restore the data if the customer had made proper and regular backups.

13.5 During the free trial, in deviation from sections 13.2 to 13.4, we are liable only for intent and gross negligence; section 13.1 remains unaffected.

13.6 The rules above also apply to the liability of our legal representatives, employees and vicarious agents.

13.7 The customer's claims for damages become time-barred one year after the statutory start of the limitation period. This does not apply in the cases of section 13.1.

14. Indemnity

If third parties assert claims against us because the customer uses Lynx Heartbeat unlawfully or contrary to these terms – in particular because it monitors third-party systems without authorisation or publishes unlawful content – the customer indemnifies us against these claims and the reasonable costs of legal defence to the extent it is responsible for the breach. We inform the customer of such claims without undue delay.

15. Force majeure

Neither party is liable for failing to perform its obligations to the extent this is due to circumstances beyond its control and for which it is not responsible, such as natural events, official orders, industrial action, attacks on networks or the failure of power, data centres or networks of other operators. The affected party informs the other without undue delay and resumes performance as soon as the circumstance has ceased.

16. Confidentiality

Each party treats confidential information of the other party that it receives in connection with the contract as confidential and uses it only to perform the contract. This does not apply to information that is generally known, that the receiving party developed independently or lawfully obtained from third parties, or that must be disclosed by law or by order of an authority or court. The duty continues for three years after the end of the contract.

17. Data protection and processing on behalf

17.1 The Privacy Policy describes how we process personal data as a controller – for example account and billing details.

17.2 To the extent Lynx Heartbeat processes personal data in the data the customer has monitored, we act as the customer's processor. This is governed by the Data Processing Agreement, which is concluded together with these terms.

17.3 The customer warrants that it is entitled to process the data it has monitored with Lynx Heartbeat and that it informs the data subjects where necessary.

18. Changes to these terms

18.1 We may change these terms for the future if there is an objective reason for doing so – such as a change in the law, new features or the closing of a gap – and the change does not unreasonably disadvantage the customer.

18.2 We notify the owner of the account of changes by email at least six weeks before they take effect. If the customer does not object in text form within that period, the changes are deemed accepted. We point out this consequence in the notice. If the customer objects, the contract continues on the previous terms; either party may then terminate it with effect from the date the change was due to take effect.

18.3 Changes affecting the main services or the prices are governed by sections 3.3 and 8.

19. Final provisions

19.1 The law of the Federal Republic of Germany applies, excluding the UN Convention on Contracts for the International Sale of Goods (CISG).

19.2 The exclusive place of jurisdiction for all disputes arising from or in connection with this contract is Potsdam, Germany, if the customer is a merchant, a legal entity under public law or a special fund under public law, or has no general place of jurisdiction in Germany. We may also sue the customer at its registered office.

19.3 The customer may transfer rights and obligations under this contract to third parties only with our prior consent in text form. Section 354a of the German Commercial Code (HGB) remains unaffected.

19.4 These terms, the Data Processing Agreement and the plan and price details stated at the time of booking form the entire agreement on the use of Lynx Heartbeat. Side agreements must be made in text form.

19.5 If a provision of these terms is invalid in whole or in part, the validity of the remaining provisions is not affected. The statutory provisions take the place of the invalid provision.