Security and privacy
Built for data that not everyone should see.
Lynx Heartbeat looks deep into your servers. That is why it collects as little as possible, stores it in Germany and keeps every client apart from the others. Each statement on this page describes how the product is built.

Security and privacy
Where your data is
- The central runs at Hetzner in Germany (Nuremberg).
- The backup is encrypted and stored off-site in Falkenstein; restoring from it has been tested.
- The outside checkers are in Nuremberg, Helsinki, Ashburn (USA) and Singapore. They only fetch the public addresses of your monitors and send the results to the central.
- The agent talks to the central over HTTPS on port 443 — one outgoing connection, no open port on your server.
What the agent sends
- Measurements every minute: CPU, load, memory, disks, network, and the state of MySQL, PHP-FPM and Apache.
- Check results, the installed packages (for security findings) and the facts of the system: operating system, services, pending updates.
- Processes by name only — the ten using the most CPU and the ten using the most memory.
- Listening ports, with the process and the account they belong to.
What the agent never sends
- No file contents and no paths of your customers’ files.
- No command lines and no environment variables — that is where passwords tend to hide.
- No IP addresses of your visitors.
- No database contents: MySQL is asked for status counters, never for rows.
Installed with least privilege
- The agent runs under its own account and refuses to start as root.
- It needs no sudo rule; measurements come from files every account may read.
- The service is confined by systemd: read-only file system, a quarter of one CPU core, 64 MB of memory.
- The enrolment token belongs to the account owner, works once and expires after 24 hours. One command removes the agent again.
Signed updates
- Every agent update comes with a signed manifest (Ed25519); the agent verifies the signature and the checksum of the file before installing it.
- Releases roll out in stages, not to all servers at once.
- A release that does not start cleanly is rolled back automatically and never installed again.
Who gets in
- Second factor with an app code (TOTP) and ten recovery codes, for every user.
- The owner can make it mandatory for the whole team.
- Passwords are stored as Argon2id hashes; ten failed attempts lock the login for 15 minutes.
- Sessions end after 12 hours. Four roles decide who may read and who may change things.
Clients kept apart
- Every tenant only sees its own servers and monitors — enforced in the database with row-level security.
- Agencies get a sub-tenant per client; the agency sees its clients, never the other way round.
- Clients get their own access to their area.
- A public status page shows no server details, versions, ports or causes.
How long data stays
- Check results: every minute for 90 days, then hourly for two years.
- Server metrics such as CPU and memory: every minute for 30 days, then hourly for 400 days.
- The history of incidents: one year.
- After a subscription ends, data is kept for at least 90 days and never deleted automatically.
AI only with your consent
- Switched off until the account owner agrees.
- With your own Anthropic key and your cost limit.
- File contents, command lines, user names and credentials are never sent to the AI.
- MCP access for Claude is read-only and only works after you enable it.
This website
No advertising trackers and no cookies for analytics. We measure the reach of this website with a service of our own, run by CATAMA Software – without cookies and without visitor profiles. At most one technical cookie is set, which remembers the language for the login.
Questions about security and privacy
Where is my data stored?
On servers at Hetzner in Germany (Nuremberg), with the encrypted backup in Falkenstein. The outside checkers are in Nuremberg, Helsinki, Ashburn (USA) and Singapore; they only fetch the public addresses of your monitors and send the results to the central.
What does the agent send from my server?
Only measurements and check results — never file contents, command lines or environment variables. Processes appear by name only.
How long are measurements kept?
Check results are kept every minute for 90 days and then hourly for two years. Server metrics such as CPU and memory are kept every minute for 30 days and then hourly for 400 days.
Which servers does Lynx Heartbeat support?
The agent runs on Ubuntu 20.04 to 26.04 with systemd, on amd64 and arm64. Other distributions are not released yet. Checks from the outside work for any website or service that is reachable from the internet, whatever it runs on.
Does this website set cookies?
No advertising trackers and no cookies for analytics. We measure the reach of this website with a service of our own, run by CATAMA Software – without cookies and without visitor profiles. At most one technical cookie is set, for the language of the app, and only when you go to the login.
Listen to the heartbeat of your servers.
Tell us how many servers and websites you look after — we will set up access for you.