Our commitments
These are current policy, not perpetual promises. The distinction is the honest one, and is what makes the rest of this page believable.
How changes work
Any material change to anything on this page takes effect at least 90 days after notice by email, and applies only to future renewals. Billing is monthly, so a change can be declined by leaving before it takes effect. Notice plus a short billing cycle is the part worth relying on. A notice period with an exit attached is worth more than a promise of “never”, because a notice period can be acted on.
Where things run
Current since 2 September 2026. Last changed 2 September 2026.
Nameservers and the database run on EU-headquartered providers, and customer data at rest lives in EU datacentres. The full inventory, updated as it changes, is on the privacy page, including the two places where a non-EU company is involved and exactly what reaches them.
Query logs
Current since 2 September 2026. Last changed 2 September 2026.
DNS query logging is off. Aggregate counters remain: how many queries per nameserver, never who asked what. Data never collected is data nobody can lose, leak, or be compelled to produce.
If we wind down
Current since 2 September 2026. Last changed 2 September 2026.
- 90 days notice, or the most notice circumstances permit if a legal requirement makes 90 impossible.
- One-click zone export in BIND format, available from day one of the notice period, and already available today from the dashboard.
- No charges in the final 60 days.
- DNS keeps answering, read-only, through to the end.
A sale or change of owner is not a wind-down. If the service continues under someone else, this section does not apply. The 90-day notice rule above still does, so a new owner changing the hosting posture has to announce the change before it takes effect.
Founding pricing
Current since 2 September 2026. Last changed 2 September 2026.
Accounts created during the founding period keep €4/month for their labels. Like everything else here, the rate is policy with 90 days notice attached, and survives a change of owner as an attribute of the account.
Each label is a separate boundary
Current since 2 September 2026. Last changed 2 September 2026.
A label belongs to one customer, and labels are sold to unrelated parties. Credentials are scoped to a single label, so no customer can publish a record inside another customer's namespace, and certificate challenges are writable only at the label apex. The separation is enforced by the service rather than promised by policy. How the boundary works.
What we will not do
- Carry customer traffic. The service answers DNS and stores TXT records. Packets stay none of our business.
- Hold private keys. Certificates are issued to, and stay on, customer hardware.
- Track people. No third-party analytics, no pixels, no open or click tracking in email.
- Let one customer reach another customer's namespace. The boundary is structural, not a setting.