Privacy

The application

PodSteer runs entirely on your machine. It reads the kubeconfig you already have and talks to the clusters that file names, using the same client library kubectl uses. It has no account system and sends no telemetry, and the interface itself has no network access at all — that is enforced by a content security policy in the application.

Once a day it asks GitHub whether a newer release exists. That request carries no identifier — no version, platform or machine id — and you can switch it off in Settings, or with PODSTEER_UPDATE_CHECK=false, after which no request is made. Everything else it can connect to, and when, is listed on the security page.

What it writes stays on your own machine:

• Display preferences — theme, page size, column widths, saved views, which namespace you were last looking at. The interface keeps these in its own local storage.
• A settings file — history retention, kubeconfig sources, proxy and per-cluster options — in the per-user application directory your operating system provides.
• Recorded cluster history — capacity figures sampled while the application is open, so the dashboard can draw a trend. Kubernetes reports only the present, so this is the only way to have one. It holds no object names, no logs and no manifests; you choose whether it is kept for a day, a week, a month, or not at all, and choosing "don't record" erases what already exists.
• Your kubeconfig, only when you add a cluster — after writing a backup of it beside the original.
• Files you ask for — a CSV export, an exported settings file, a file copied out of a container — wherever you choose to save them.

None of it is transmitted anywhere. Uninstalling removes the application; brew uninstall --zap --cask podsteer also removes what it wrote to its own application directory.

This website

podsteer.com sets no cookies, runs no analytics, and embeds nothing from another origin — no fonts, no tag managers, no social widgets. Its server keeps standard HTTP logs for operational purposes only.

Downloads

Release binaries are served by GitHub, which applies its own privacy statement to the request. We receive nothing about it.

Contact

Questions about this page, or anything else, belong in the issue tracker.