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, sends no telemetry, and makes no update check — the interface itself has no network access at all, enforced by a content security policy in the application.

Two things are written to your own machine and nowhere else:

• Display preferences — theme, page size, column widths, which namespace you were last looking at. The interface keeps these in its own local storage rather than beside the history below.
• 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. It is written to the per-user application directory your operating system provides, readable only by you.

Neither is transmitted anywhere. Uninstalling removes the application; brew uninstall --zap --cask podsteer removes both of them with it.

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.