Privacy

Last updated 2026-09-10

The short version

runlocal is a hardware-fit calculator. It doesn't need your data to work, and by default it collects none. Everything below is opt-in and off until you say yes.

CLI telemetry (opt-in, off by default)

The first time you run any runlocal command interactively, it asks once whether to share anonymous usage. If you say no — or you're running non-interactively, in CI, or with --no-telemetry / RUNLOCAL_TELEMETRY=0 / DO_NOT_TRACK=1 — nothing is ever sent.

If you opt in, a run may send: a random anonymous id (no account, no email), a coarse hardware bucket (e.g. "Apple M3 Ultra 128GB"), the platform, and — when you check or install a model — its catalog id, variant, quant, and fit tier. If you run a search that doesn't match anything in the catalog, the query text itself is sent as a demand signal, unless it looks like a filesystem path (those are dropped, never sent). Post-install/bench runs may also send a measured tokens/sec datapoint next to what runlocal predicted, to improve future estimates.

Never collected: prompts, chat content, file paths, model weights, your name, or anything else that could identify you beyond the random anonymous id.

Site analytics (opt-in at deploy time, DNT-respecting)

runlocal.sh may use privacy-respecting, cookie-free analytics (no third-party ad trackers). When enabled, it records page views and outbound link clicks against a random id stored in your browser's local storage — never a cookie, never cross-site. It checks your browser's Do Not Track setting first and sends nothing if it's on.

What we don't do

We don't sell your data. We don't share it with anyone beyond the processor that runs the analytics above, and only in the anonymized form described here. There's no ad network, no cross-site tracking pixel, no PII in any payload runlocal sends.

Questions

Open an issue on GitHub or reach out via the links in the footer.