Privacy Policy

How InfraNest collects, uses and protects your data — in plain language.

Last updated: 25 October 2026.

The short version: InfraNest brings your domains, DNS, servers, certificates and monitoring into one place. To do that we handle some personal data — your account details, what you connect, and how you use the service. We don't sell it, we don't run advertising trackers, and we use a small set of trusted providers to run everything. The details are below, in plain language.

Who we are

InfraNest is run by Jaspar Steenman, Hansaring 79, 50670 Köln, Germany. We are the "data controller" for the personal data described here — meaning we decide how and why it's used. Any privacy question, or to exercise your rights: privacy@infranest.io.

What this policy covers

This applies to the InfraNest marketing site (infranest.io) and the InfraNest app and API (app.infranest.io). When you connect a third-party provider (a registrar, DNS host or cloud), that provider has its own privacy policy for the data it holds.

What we collect, and why

When you visit the site

Analytics — we run Umami, self-hosted on our own servers and cookieless. It tells us which pages get visited and roughly where from — an approximate city and country, worked out from your IP address, which we do not store — with no cross-site tracking. With your consent — and only with it — we also record how pages are used on this website: mouse movement, clicks and scrolling, so we can see where the site confuses people. Those recordings are made by our own software and stay on our own servers alongside the rest of our analytics, and you can change your mind at any time under Cookie settings at the foot of any page. Recording is limited to this website; it is not switched on in the app you sign in to. Signed in to the app, those numbers can carry an account id and a broad role (member, admin) so we can tell one person's journey from another's — never your email address, and never your organisation's name.
Product analytics (PostHog) — alongside Umami we use PostHog, hosted in its EU data centre in Frankfurt, to understand how people find their way around the website and the app. Without your consent it works like Umami: nothing is stored in your browser, and visits are counted with a short-lived, one-way code that PostHog calculates on its servers from your IP address and browser details; your IP address itself is not stored. With your consent — Analytics under Cookie settings — PostHog sets a cookie so it can recognise you across pages and visits, keeps session replays of this website with everything you type masked, and, if you go on to create an account, links those earlier visits to it. In the app, PostHog records which features are used, linked to your account id, your role and your organisation's id and plan — never your email address, never your organisation's name, and never the domains, servers or other data you manage — so we can see where people get stuck. For this it stores nothing in your browser unless you have allowed Analytics. Session replay is not switched on in the app.
The contact form — your name, email and message, so we can reply. With your agreement — the box you tick before sending — we also keep the enquiry in our CRM (HubSpot, hosted in the EU), together with the page you wrote from and any campaign link that brought you there, so we can follow up properly.
Email updates — if you ask for new articles and product news: your email address, your language and the page you signed up from. We confirm every sign-up by email first, so nothing is sent unless you click that link, and every message carries an unsubscribe link. This runs on your consent, which you can withdraw at any time.
Asking for an integration — the provider you asked us to support and, if you leave one, your email address, so we can tell you when it is ready.
Support chat — if you message us, the conversation (handled by Intercom, in the US). Unless you allow marketing cookies, the chat only loads when you click the bubble, so nothing reaches Intercom until you start a conversation. If you do allow them, the messenger loads with the page so it can offer help on what you are reading — which means Intercom sees the pages you visit while it is running. You can change that at any time under Cookie settings at the foot of any page. An AI assistant (Intercom's Fin) may answer first; you can ask for a human at any time.

When you have an account

Account details — your name, email, password (stored only as a secure hash) and organization.
Signing in with Google or GitHub — if you choose this, that provider confirms your identity and shares your basic profile (name, email, avatar) under its own privacy policy. We use it only to create and access your account; you can use email + password instead.
Avatars — if avatar images are enabled, we show a Gravatar based on a hash of your email. We fetch it server-side, so Gravatar sees only the hash, never your browser or IP. You can turn this off.
Files you upload — such as avatars, logos and screenshots, and the profile picture Google or GitHub shares if you sign in with them. We keep them so we can show them where you use them — in the app, or on your status pages. From 26 October 2026 they are stored in Cloudflare R2, in the EU.
Billing — handled by Stripe. We never see or store your full card number.
What you manage — the domains, DNS records, servers, certificates, monitors and watchlists in your account, plus the provider credentials and API tokens you connect. These are encrypted at rest, access is strictly limited to the parts of our system that need them to carry out what you ask for — including any automations you set to run on a schedule — and we don't use them for anything else. You can revoke them at any time.
Technical data — IP address, browser/device information and server logs, which we need for security and reliability. We work out an approximate country from your IP — locally, on our own servers — to flag unusual sign-ins.
Error diagnostics — via Sentry, so we can find and fix bugs. We send only a pseudonymous account id, never your email or other personal details.

Monitoring — when you set up a monitor, our probe servers contact the target you chose to check whether it's up. To verify DNS changes and certificates, we also query public DNS-over-HTTPS resolvers and certificate-transparency logs using your domain names.

Alerts and automations — when you connect an alert channel (Slack, Teams, Discord, Telegram, PagerDuty or email) or build an automation, we send the events you asked for to the destination you chose. Those messages describe the object involved — a domain, a certificate, a server, a monitor — and, where a person triggered the action, that person's name and email. Secrets are never included: passwords, tokens, API keys and private keys are stripped from every automation payload before it is sent. A calendar feed works the same way — the link you add to Google, Apple or Outlook Calendar carries your domain and certificate expiry dates to that provider. Except for email and our shared Telegram bot, the destination receives that data under your own agreement with whoever runs it, not ours.

API and connected tools — when you or your organisation connect a script, an integration or an AI assistant to InfraNest with an API token (for example through our MCP server), that tool receives the data its token can read. That can include team members' names and email addresses, for example in the audit log. The tool receives this data at your organisation's direction and under its own agreement with whoever runs the tool, not ours.

AI assistants (Claude, ChatGPT and others) — you can connect an AI assistant to InfraNest. You start the connection, choose one organisation and approve what it may see. The assistant can only read; it cannot change anything. When you ask it a question, InfraNest sends the answer — for example monitor status, DNS records or domain names in that organisation — to the assistant's provider, which processes it under its own privacy policy. InfraNest never sends secrets such as transfer codes, private keys or tokens. We store only the connection itself (which app, which organisation, what it may see) and record its use in your organisation's audit log. You can end it at any time under My account → Authorized apps. Questions: support@infranest.io.

Status-page subscribers

When someone subscribes to one of our customers' public status pages to receive incident and maintenance alerts, the organisation that runs that status page is the controller for the contact details they give — an email address, or a Slack webhook — because it decided to offer the subscription, and we process those details on its behalf. Email sign-ups are confirmed by double opt-in, the details are used only to send that page's status notifications, and unsubscribing at any time deletes them. Email sign-ups that are never confirmed are deleted after 7 days.

Our agreement with that organisation allows it to use those details for that page's status notifications and nothing else — a status-page subscription is not a marketing opt-in — and lets it see and manage its own subscriber list. If you subscribed to one of our customers' status pages and want to know what is held about you, or want it erased, ask that organisation; if you write to us at privacy@infranest.io, we will pass your request on and help them answer it.

One thing we keep as controller ourselves: if an email to an address bounces or is reported as spam, we put that address on a suppression list so we stop sending to it. That protects our email delivery for every customer (our legitimate interest); the list is ours rather than the organisation's, and unsubscribing does not remove an address from it — write to privacy@infranest.io if you want it removed.

Performing our contract with you — to provide your account, run the service and handle billing.
Our legitimate interests — keeping the service secure, preventing fraud, understanding usage in aggregate, monitoring errors, improving InfraNest, and answering your messages.
Legal obligations — for example, keeping invoices for tax purposes.
Your consent — only where we specifically ask for it (such as optional emails, or the fuller website analytics described above). You can withdraw it at any time.

Cookies and local storage

We keep this simple, and we don't use any advertising or cross-site tracking cookies. The few cookies in play are strictly necessary:

Stripe sets a cookie during checkout, for payment security and fraud prevention.
Cloudflare, which delivers and protects our sites, sets a cookie for spam and bot protection.
Beyond that, we use your browser's local storage (not cookies) to remember your language and light/dark theme on the site, and to keep you signed in to the app.
Umami analytics is cookieless.
PostHog is cookieless too, unless you allow Analytics: then it sets a cookie, and uses local storage, to recognise you across pages and visits — including in the app at app.infranest.io.
Intercom sets cookies to keep your support chat conversation together — once you open the chat, or with the page if you have allowed marketing cookies.

When something needs your consent, we ask before it runs — today that is session recording and PostHog's fuller analytics, and marketing cookies: HubSpot's tracking code and the chat loading with the page. Nothing else. Your answer is remembered in your browser's local storage — and in a small cookie on infranest.io holding the same choice, so that our app at app.infranest.io respects it too — so that we only ask once, and you can change it at any time under Cookie settings at the foot of any page.

Marketing cookies are set only if you allow them, never otherwise, and you can change your answer at any time under Cookie settings at the foot of any page. We never sell your data.

Who else processes your data (sub-processors)

We use a small set of trusted providers to run InfraNest:

Hetzner (Germany, EU) — hosting for the app, back-office systems, database and marketing infrastructure.
Cloudflare (EU / global) — hosting and CDN/security for the marketing site, and bot protection (Turnstile); transactional email delivery (alerts, receipts and account messages); and, from 26 October 2026, storage of files uploaded to InfraNest (such as avatars, logos and screenshots) in Cloudflare R2, held in the EU.
Umami — self-hosted on our own Hetzner infrastructure, so analytics data stays with us.
PostHog (EU — Frankfurt; US company) — product analytics for the website and the app, as described above. Our PostHog project is hosted in PostHog's EU data centre in Frankfurt.
OVH — servers that run our monitoring probes in regions worldwide. You choose which regions check your services, so monitoring data is only processed outside the EU if you enable a non-EU region.
Sentry — error tracking and diagnostics.
Stripe — payment processing.
Backblaze B2 (EU region, US company) — off-site storage of our database backups.
Telegram (outside the EU) — delivering alert notifications to the Telegram chats you connect. This applies only if you set up a Telegram alert channel; we operate the bot that sends them.
Gravatar / Automattic (US) — avatar images, fetched by a hash of your email, when avatars are enabled.
Intercom (US) — our support chat and contact form. From the website: the messages you send us, your name and email address, and the page you wrote from. When you are signed in to the app: your name, email address, language, your role and which organisation you belong to, and that organisation's plan. The messenger loads when you open the chat, or with the page if you have allowed marketing cookies.
HubSpot (EU — Frankfurt; US company) — our CRM: your contact details, the message you sent us, your language, the page and campaign that brought you to us, and a record of our correspondence, so we can follow up properly and know who we have already spoken to. Our HubSpot account is hosted in HubSpot's EU data centre in Frankfurt. We send this from our own servers when you submit a form. If you allow marketing cookies, HubSpot's tracking code also runs on this website and sets cookies (__hstc, hubspotutk, __hssc) which let it connect the pages you read to your enquiry when you contact us. If you decline, only what you type into a form ever reaches HubSpot.

International transfers

Most of our providers are based in the EU/EEA (Hetzner). Some — Stripe, Sentry, Cloudflare, Intercom, Telegram and Gravatar — may process data outside the EU, including in the United States. Backblaze stores our backups in its EU region, HubSpot hosts our CRM and PostHog our analytics in their EU data centres in Frankfurt; all three are US companies, so US access is possible in principle. From 26 October 2026, files uploaded to InfraNest are stored in Cloudflare R2 under EU jurisdiction, which keeps them in EU data centres; as Cloudflare is a US company, US access is possible in principle there too. And because our monitoring probes (OVH) run in regions worldwide, if you choose to monitor your services from a region outside the EU, those checks are processed there too. Where they do, the transfer is protected by appropriate safeguards such as the EU Standard Contractual Clauses.

How long we keep your data

We keep personal data only as long as we need it. Account data is kept while your account is active; when you close it, we delete or anonymise your data — except where the law requires us to keep certain records longer (for instance, invoices must be kept for up to 10 years under German tax law). Aggregate analytics and technical logs are kept for a short period (PostHog session replays are deleted after 30 days), and support messages for as long as needed to help you.

Your rights

Under the GDPR you can ask us to access your data, correct it, delete it, restrict or object to how we use it, or provide it in a portable format — and you can withdraw consent at any time. Email privacy@infranest.io and we'll respond within the timeframe the law sets. You also have the right to complain to a data-protection authority; ours is the State Commissioner for Data Protection and Freedom of Information North Rhine-Westphalia (LDI NRW).

How we protect your data

Everything travels over encrypted connections (HTTPS/TLS). Provider credentials and other secrets are stored encrypted, access is limited to what's needed, and two-factor authentication is available on your account.

Children

InfraNest isn't intended for anyone under 16, and we don't knowingly collect their personal data.

Changes to this policy

We'll update this page whenever our practices change and revise the date at the top. For significant changes, we'll let account holders know.

Contact

Jaspar Steenman · Hansaring 79, 50670 Köln, Germany · privacy@infranest.io