RuleReceipt is a command-line tool that runs on your own computer. This page explains, plainly, what that means for your data.
Nothing, by default. RuleReceipt reads your rules files (CLAUDE.md, AGENTS.md, and Cursor/Copilot/Windsurf rules) and your local agent session transcript on your machine, and prints a report to your terminal. None of that content — no rule text, no file paths, no session content — is ever sent to us, stored by us, or seen by us. Plain rulereceipt check makes no network calls unless you opt in (--share/--email/--llm/--telemetry/--check-updates).
The shareable report is written locally, not uploaded. Passing --html writes a single self-contained file into your working directory and nothing else — no upload, no network call, no copy kept anywhere. That file does contain your rule text and evidence quoted from your session, because that's what makes it useful to send. It goes only where you choose to send it, and it's worth knowing what's in it before you forward it to someone.
Anonymous install count: pass rulereceipt check --telemetry and it sends one random ID — generated once per machine, stored locally, never tied to your name or email — so we can count real distinct installs instead of guessing. That's the entire payload: one ID, nothing else. Off by default; even with the flag, DO_NOT_TRACK=1 or RULERECEIPT_NO_TELEMETRY=1 in your environment forces it back off. A raw HTTP request inherently exposes your IP and the request time to whatever server receives it (ours or anyone's) — we don't store or use that, but we're not going to pretend it isn't technically visible either.
For rules that need judgment rather than a local check, RuleReceipt calls the Claude API using your own Anthropic API key, only when you pass --llm — the same way Claude Code itself already does. That call goes directly from your machine to Anthropic. We don't proxy it, log it, or see it.
Running rulereceipt check --share is opt-in and off by default. If you use it, it sends aggregate pass/fail/unclear counts — never rule text, file paths, or session content.
This landing page uses PostHog for anonymous analytics only: how many people visit each page, how far down the page they scroll, and which buttons and links they click (recorded by a fixed name, like “github” or “copy install command”). We never record your screen, and never send anything you type, paste, or drop — no rule text, no session content, no results, and never your email address (the signup event records only that a submission happened). In the interactive demo, the rules files and session logs you check run entirely in your browser and are never sent to PostHog or anywhere else; at most we record a coarse size bucket like “>10k characters” or “1–10MB”, never the content. Session recording and autocapture are turned off and all text is masked. The RuleReceipt CLI itself contains no analytics and never contacts PostHog; by default it makes no network calls unless you opt in (--share/--email/--llm/--telemetry/--check-updates). No cross-site tracking, no ad networks, and we don't sell or share this data.
If you submit your email on this site (to get notified before pricing changes), we store it in a database (hosted by Upstash) so we can send you that one update. We don't sell it, share it with anyone else, or use it for anything beyond what you signed up for. There's currently no automatic expiry — it stays until you remove it.
To remove your email at any time, use the unsubscribe page or just email us (see below) — either way it's deleted immediately, not just marked inactive.
Email hello@rulereceipt.dev.