Privacy Policy

Monitorable is a server-monitoring service. To run it, we hold two kinds of data: a little about you (your account) and a lot about your servers (the metrics the agent sends). This page says exactly what that is, in plain language. Where it links to the docs, the docs are the detailed, maintained source.

Who is responsible

The controller of the personal data described here is the individual entrepreneur who operates Monitorable, identified in full — name, registration number and address — in the Terms of Service. For anything in this policy, write to hello@monitorable.io.

What we collect about you

Account data. When you sign in with Google or GitHub we receive your email address, display name, and avatar from the provider — nothing else, and we never see your password there. When you sign in by email we hold your email address and send it a one-time link and code. Your account is created on first sign-in; there is no separate registration form.

Organization and team data. Organization names, member roles, and the email addresses you invite.

Notification destinations. The addresses and endpoints you configure for alerts — an email address, a Telegram chat, a Discord, Slack, ntfy, or PagerDuty target, or a webhook URL.

Billing data. If you take a paid plan, Creem — our merchant of record — handles the purchase, your card details and your invoices; we never receive card numbers. We store the plan you are on, its status, and Creem’s identifiers for your customer record and subscription.

Session and security data. A short-lived access token (60 minutes) kept in your browser, a refresh token (30 days) set as a cookie, and the time and address of sign-ins. Nothing we run carries advertising trackers.

Website and dashboard analytics. On this website, its docs and the dashboard we count visits with HitKeep, an analytics tool we host ourselves, so no analytics company receives this data. For each page view it records the page, the page you came from, campaign tags in the link (utm_*), your browser’s user-agent string and language, an approximate location (country, and where available region and city) and network provider looked up from your IP address. It also records clicks on links to other sites, file downloads, and form submissions — which form and where it was sent, never what you typed. Your IP address is used for that lookup and for spam filtering; it is not stored. No cookies are set: an anonymous session ID is kept in your browser’s session storage, which is cleared when you close the tab. If your browser sends Do Not Track, nothing is recorded. In the dashboard, page views are not linked to your account: nothing that identifies you or your organization is sent. A dashboard page’s address can include the number of one of your servers or alert templates; invitation links are never recorded.

Support correspondence. Whatever you send to hello@monitorable.io.

What we collect from your servers

The agent you install sends one batch a minute over HTTPS, plus an empty hourly check-in over IPv4 and over IPv6 that carries only the server’s key, and nothing else. The full field list is on What is collected; in summary:

• Host metrics — CPU, memory, swap, disk usage and I/O, network throughput, load, uptime, temperatures.
• Server details — hostname, OS and kernel version, and CPU model. The public IPv4 and IPv6 addresses the agent connects from are recorded and looked up against an offline geolocation database on our own servers; they are not sent to any third party.
• Docker containers — container ID, name, image, state, health, exit code, and per-container resource use.
• systemd services — unit names, states, and per-unit resource use.
• Listening ports — the TCP port numbers a server listens on, their service names, whether each is local or exposed, and connection counts per port. No addresses, process names, or UDP.
• Disk health (SMART) — drive model and serial number, health status, temperature, wear indicators.

The agent never reads process lists, command lines, environment variables, file contents, or logs. It runs as an unprivileged user, opens no listening ports, and its source is public so you can check this yourself.

You are responsible for what your servers contain. If a hostname, container name, or unit name on your servers includes personal data about someone else, that data reaches us as part of the metrics you chose to send.

Why we process it

• To provide the service you signed up for (contract): accounts, metrics storage, dashboards, alert evaluation, and delivering alerts to the destinations you configured.
• To keep the service secure and working (legitimate interest): sign-in records, abuse prevention, error logs, capacity planning.
• To improve this website and the docs (legitimate interest): which pages are read and where visitors come from.
• To bill you (contract and legal obligation) on paid plans.
• To answer you when you write to us (legitimate interest).

We do not sell personal data, use it for advertising, or train models on your metrics.

Where it lives

The platform — the database, the metrics store, the dashboard backend, and website analytics — runs on dedicated servers we operate in France, in the European Union. Downloads of the agent are served from EU-jurisdiction object storage.

We use a small number of processors and independent providers to run the service:

Alert messages contain the server name, the rule that fired, and the measured value. Configuring a destination is your instruction to send those messages there.

Metrics traffic from your servers to ingest.monitorable.net goes directly to our servers in France and does not pass through Cloudflare.

How long we keep it

• Metrics are stored at two levels of detail: per-minute data for 35 days and hourly summaries for 400 days, after which they expire automatically (see Metrics history). Each plan states the metric-history period it offers on the pricing page.
• Server details and snapshots (containers, services, disk health) are kept for as long as the server exists in your account.
• Removing a server revokes its API key and deletes its details and snapshots immediately; there is no undo. Its metric history is no longer reachable from the dashboard and is not purged at that moment — it is deleted when the retention period above ends.
• Account data is kept while the account exists.
• Refresh tokens expire after 30 days; expired tokens are purged.
• Billing records are kept for as long as tax law requires.
• Website analytics are kept for 3 months, then deleted.

Your rights

Under the GDPR and comparable laws you can ask us to access, correct, export, restrict, or delete your personal data, and you can object to processing based on legitimate interest. To delete your account and everything in it, email hello@monitorable.io from the account’s address; we confirm the deletion in writing. You can also lodge a complaint with your local data-protection authority.

Metrics and server metadata are yours: you can see them in the dashboard at any time and ask us for a copy in an open format. Removing a server takes it out of your account at once and its metric history expires on the schedule above; deleting your account removes everything from ours.

Cookies

The dashboard sets one cookie, holding the refresh token that keeps you signed in. It is HttpOnly, Secure, and is cleared when you sign out. This website sets none of its own, and our analytics set none anywhere; they keep only the session-storage ID described above. Cloudflare may set the strictly necessary cookies it uses to protect the site. There are no analytics, advertising, or cross-site tracking cookies.

Security

Metrics travel over TLS. API keys are stored hashed. Tenancy is enforced on every query, not only at the edge. The agent runs unprivileged and its requirements and permissions are documented. If you find a vulnerability, please follow the security policy.

Children

Monitorable is a business tool and not directed at children under 16. We do not knowingly collect their data.

Changes

When this policy changes in a way that matters, we will note it here with a new date and, for significant changes, tell account holders by email before the change takes effect.