Privacy

This website

The marketing pages on this site are static. They set no advertising or cross-site tracking cookies. If you create an account, the session cookie that keeps you signed in is strictly necessary for the dashboard to work and is not used to profile you.

Website analytics

On production domain0.dev (including www.domain0.dev) we use our private Umami instance at analytics.berkant.me to count page views and predefined interactions such as navigation, documentation and GitHub links, primary buttons, demo steps, and successful form submissions. Analytics reports are not publicly shared. Development and preview deployments do not send analytics.

Analytics uses no cookies and respects your browser’s Do Not Track setting. We send only allowlisted page paths and fixed action labels; individual connection paths use a generic route template. We do not send URL query strings or fragments, page titles, referrers, typed values, clipboard contents, email addresses, credentials, API keys, or domain-connection payloads. We do not record sessions, hovering, or mouse movements, and we do not assign account identifiers to analytics visits.

Like any web request, requests to our analytics server expose an IP address and browser request headers to that server. Umami processes request metadata to produce aggregate browser, device, and approximate location statistics. This is separate from the account data needed to operate Domain0. Explicit verification visits are labeled test-activity and use a tab-scoped session-storage flag to keep that label across navigation.

Account data

An account stores the email address and name you supply, and the applications and domain connections you create. Those records exist so the dashboard can show you your own workspace. They are not sold, and they are not shared with third parties for advertising.

Data in a self-hosted deployment

When you self-host Domain0, connection data lives in your own Postgres database and never reaches this site. Domain0 stores what it needs to carry a connection through its states: the domain, the detected provider, the planned and applied records, and the connection's status history. It does not store end-user passwords for DNS providers; provider access is held as a token or credential scoped to the operations the adapter performs.

Changes

This page describes current behaviour rather than a legal commitment, and will be updated as the product changes. For a deployment with regulatory obligations, review the source and the operations documentation rather than relying on this summary.