Legal

Privacy

Short, because there is very little to describe. RigorRun has no account system, no hosted backend and no analytics, so most of what a privacy policy usually covers does not exist here.

Last updated 10 September 2026.

The software you install

npx rigorrun runs entirely on your machine. Your systems, your credentials, your recordings, your runs and your verdicts are written to ~/.rigorrun and to your operating system's credential store. None of it is transmitted to us, because there is no service to transmit it to.

RigorRun writes a local file, activation.jsonl, containing a stage identifier, a timestamp, a counter and a coarse error class. It records no task content, no tool arguments, no results, no project or record names, no URLs, no commands and no credentials. There is no uploader and no endpoint. If usage reporting is ever added, that is the shape it would take, and it would be opt-in and announced in the changelog.

Three things can make a network request, all because you asked:

  • rigorrun verify downloads the named package from the npm registry.
  • Connecting your own system sends requests to the address you configured, with your credentials.
  • An LLM-backed agent, which exists only if you have set a provider API key, talks to that provider.

None of the three reach RigorRun.

This website

rigorrun.xyz is a set of static files on Cloudflare Pages. There are no cookies, no analytics, no tag manager, no advertising pixels and no third-party embeds. Fonts are served from this origin rather than from a font CDN, so loading a page does not tell anybody else that you did.

Cloudflare, as the host, processes request metadata such as IP address and user agent in order to serve and protect the site. That is described in Cloudflare's privacy policy. We do not receive, store or analyse it.

If you get in touch

Email to an @rigorrun.xyz address is forwarded to a personal mailbox and kept only as long as it is useful to the conversation. Nothing you send is added to a mailing list, because there is no mailing list. erbol@rigorrun.xyz.

Feedback bundles

rigorrun feedback export produces a sanitised bundle you can attach to a bug report. It is written to a file for you to inspect and send yourself. Nothing is uploaded by the command.

Changes

If this ever describes something that collects data, the change will appear in the changelog before it ships, not quietly in this page.