Privacy

Never collected

This is the list that matters for a tool pointed at production clusters. None of the following leaves your machine, in any build, under any setting:

• Anything from your kubeconfig — Context names, cluster URLs, users, certificates, tokens, exec plugins. Read locally, never transmitted, never stored anywhere but on your disk.
• Any data from the Kubernetes API — Namespace, node, workload and resource names, labels, annotations, environment variables, container logs, secrets, events. Zapkube reads them to draw the UI and forgets them when you quit.
• Cluster identifiers, even hashed — Not in analytics events, not in crash reports, not in a support bundle. There is no field anywhere in our telemetry that could hold one.
• Your identity — No name, no email address, no account, no GitHub handle, no license key. There is nothing to sign up for.
• Your machine's identity — No hostname, no computer name, no OS username, no MAC address, no disk or hardware serial.
• Your IP address — Discarded at ingestion, before anything is written down — for the desktop app as well as the website. On the website it is used in transit to resolve an approximate location, then thrown away.
• Keystrokes and file contents — Zapkube is keyboard-driven; it does not log your keys. It does not read files other than your kubeconfig and its own configuration.

What the desktop app sends

Zapkube reports a small, fixed set of anonymous telemetry, so we know which platforms to keep building for and which features are worth keeping. Every event is keyed to a random install id generated on first launch — a UUID tied to nothing else.

The app's events carry no location data at all, not even a country: the geolocation step described further down runs on website traffic only.

• App version — For example v0.4.2. Tells us how quickly people update, and which versions are the ones crashing.
• Operating system and architecture — For example macOS 15 on arm64, or Linux on amd64. Decides which builds we keep shipping.
• Anonymous feature-usage events — Which views are opened and which commands are run, as counts. The event name is all we get — never its arguments, never what you were looking at when you ran it.
• Crash reports — The error type and stack trace when something breaks, so it gets fixed. Stack traces are code paths from inside Zapkube; they can contain a local file path, and never contain cluster data.

All of it can be turned off. Flip the switch in Settings, or set ZAPKUBE_TELEMETRY=0 in your environment if you would rather not rely on a checkbox — the app then sends nothing at all.

What the website collects

zapkube.com is a marketing site, and it is measured like one — so we can tell whether the page explains the product or not.

• Page views and referrer — Which pages you saw, in which order, and which link or search brought you here.
• Device, browser, and approximate location — Browser and OS family, screen size, and a country, region, city and timezone resolved from your IP address before it is dropped. The finer fields a GeoIP database hands back — postal code and coordinates — are stripped during ingestion, so they never reach storage.
• Download clicks — Which platform, architecture, and package format you asked for. This is the number that tells us which builds to keep producing.
• Session recordings — Anonymised replays of website pages — mouse movement, clicks, scrolling, and browser console output. Text you type is masked before it is sent. This runs on the marketing site only, never inside the desktop app, and recordings are deleted after 90 days.
• One first-party cookie — A PostHog cookie holding a random visitor id and session id, so a returning visit is not counted as a new person. No advertising cookies, no cross-site trackers.

Who else touches the data

The full list of third parties involved, and why each one is there:

• GitHubUnited States

  Hosts the releases you download and the public issue tracker. GitHub sees your IP address when you fetch a build or open an issue — that request never passes through us.

• CloudflareGlobal edge

  CDN in front of assets.zapkube.com (screenshots, demos).

• PostHogEU Cloud (Germany)

  Product analytics and session replay for both the site and the app. Ingestion is proxied through a subdomain of zapkube.com, so it stays first-party.

• VercelGlobal edge

  Hosts and serves this website. Keeps short-lived request logs for operations and abuse prevention.

That list is exhaustive as of the date above. If a processor is added, this page changes before the code does.

How long it is kept

• Analytics events — Kept so we can compare this quarter to last. They are anonymous when they arrive and stay that way — there is no profile behind them that grows over time.
• Website session recordings — Deleted 90 days after they are recorded. That is enforced by PostHog, not by us remembering to do it.
• Emails you send us — There is no form and no newsletter on this site, so the only way we ever hold your address is if you write to contact@, security@ or privacy@zapkube.com yourself. Those threads are kept while the conversation is useful, and your address is never added to a mailing list — because there is no mailing list.

Your rights

If you are in the EU or the UK, the GDPR gives you the right to access, correct, export, and delete your personal data, and to object to how it is processed. Zapkube is built so there is almost nothing to exercise those rights against: no account, and no identifier we can trace back to a human.

If you want your telemetry deleted anyway, email privacy@zapkube.com with your install id or website visitor id and we will delete the matching events. Without an id we genuinely cannot find your data in the pile — which is the point of collecting it this way.

The lawful basis for the analytics described above is legitimate interest: understanding whether a product in public beta works, in the least identifying way we could manage. There is no profiling and no automated decision-making.

Who is responsible

Zapkube is built and operated by Matthieu Moquet, an independent developer based in France, who is the data controller for everything on this page.

Questions, deletion requests, or complaints: privacy@zapkube.com. A postal address is available on request by email. If you are not satisfied with our answer, you can complain to your national data protection authority — in France, the CNIL.

Found something on this page that does not match what the app actually does? That is a bug, and we want it reported: https://github.com/zapkube/zapkube/issues.

Changes to this policy

When this policy changes in a way that matters — a new processor, a new kind of data, a telemetry switch finally landing — the date at the top moves and the change is called out in the changelog. We will not quietly widen what we collect and leave the page as it was.