No telemetry. Nothing about you.

The desktop app

It connects only to:

• your clusters, through your kubeconfig, and through them to a cluster’s Prometheus or VictoriaMetrics. The programs your kubeconfig runs to sign in (such as aws, gcloud or kubelogin) are your own, and talk to their own providers;
• Artifact Hub, only when you search it for Helm charts;
• the Helm chart repositories and registries you install charts from, when you install or upgrade one;
• dl.k8s.io, Kubernetes’ own downloads, when a terminal opens for a cluster, to get a kubectl matching the cluster’s version. It’s kept for the next terminals. You can turn this off (View → Match kubectl to Each Cluster), and an organization can turn it off or point it at its own mirror;
• GitHub, to look for new versions, which you can turn off. The copy from the Microsoft Store doesn’t: the Store keeps it up to date;
• GitHub, for newer plugins: only when you open All plugins or press Check now there, and when you install or update one. Nothing about you or your clusters is sent with it, and an organization can turn it off;
• GitHub, for the sponsor card in the sidebar: a small file and the pictures it names, from raw.githubusercontent.com, read 3 seconds after Lumovi starts and then every hour. Nothing about you or your clusters is sent with it, and nothing is counted; like any request, it shows GitHub your IP address and when. It works like the update check, but can’t be turned off. If GitHub can’t be reached, Lumovi keeps the card it last checked, or shows its own.

Your kubeconfig’s credentials stay on your computer, in the app’s main process. Lumovi keeps its settings and its audit log in its own folder on your computer. Clusters you add in Lumovi are kept there too, with their credentials; on macOS and Linux, only your account can read them. Lumovi never writes your kubeconfig.

AI assistants and agents connect only if you turn them on, only from your computer, and with a token of their own. What they read of your clusters goes to the assistant you chose, under its provider’s privacy policy, not Lumovi’s.

Lumovi in your cluster

It runs in your own infrastructure, where you install it. What it keeps (sessions, the audit log and settings) stays there: in your cluster’s Secrets and ConfigMaps, on its volume, or at your audit webhook. None of it goes to Lumovi’s makers.

It reads the sponsor card in its sidebar from GitHub, as the desktop app does: once when it starts and then every hour, for all its pages and everyone using them. A fleet’s hub does the same. Your browser gets the card from Lumovi, never from GitHub. Nothing about your cluster is sent with the request, and nothing is counted. If your cluster can’t reach GitHub, it keeps the card it last checked, or shows Lumovi’s own.

This website and the docs

lumovi.dev has no analytics script, no tracking and no ads, and sets no cookie of its own. It’s hosted on Sevalla, through Cloudflare, which sets one cookie, __cf_bm, to tell people from bots. It expires after 30 minutes. Like any host, they may log requests, such as your IP address, to run and protect the site.

To know how many people visit, Lumovi uses the totals Cloudflare already counts for the domain: requests, approximate unique visitors, which pages, and which countries. They’re aggregated, nothing is added to the page for them, and the daily numbers are kept in a private repository, for the project’s own use.

If you choose light or dark, your browser remembers it on your device. Your browser also fetches the app’s screenshots and the brand’s files from jsDelivr, and the latest version from GitHub, which see those requests under their own policies. The videos come from media.lumovi.dev, Lumovi’s own storage at Cloudflare, which sets no cookie there: a video’s first frame loads as you scroll near it, and the video only when you play it.

docs.lumovi.dev is hosted by Mintlify, under its privacy policy. Lumovi adds no analytics there.

Questions

Write to [email protected], about privacy or to report a security issue. Lumovi is open source, so you can also check all of this in its code.