Skip to content

Privacy

Short version: disensor collects nothing. Nothing you do with the CLI, the GitHub Action or the Claude plugin reaches the author of disensor. The only data that leaves your machine goes where you send it: to the reviewer you registered and consented to, and to the package index and GitHub when you install or scaffold.

Static pages served by Cloudflare Pages, with no analytics, no cookies and nothing on the page that sends data. Cloudflare, as the host, handles the HTTP requests under its own privacy policy; this site adds nothing on top.

disensor runs on your machine and has no telemetry. It makes network requests in exactly these cases:

  • pip install or pipx install fetch the package from PyPI, as with any Python package.
  • disensor init and disensor pin ask the GitHub API which commit a release tag points at, to pin the CI gate. It is a public request, without authentication.
  • disensor round runs the reviewer CLI you registered with disensor reviewer add, and that CLI sends the package under review (the brief, the diff or the plan, and the preamble) to its provider, under that provider’s terms. This happens only after the repository owner ran disensor reviewer consent for that repository, that recipe and that executable; a different command or binary needs a new consent. A reviewer that runs the model on your machine sends nothing. The CLI treats ollama as one and asks for no consent for it, but Ollama can also serve cloud models (names ending in :cloud), whose prompts go to Ollama’s servers, and OLLAMA_HOST can point its client at a server on another machine.
  • Everything else works offline.

What the round produces stays in your repository: the declaration in .residue/, which you commit; the reviewer’s report, in a private temporary directory you control. The minimized profile exists for repositories that must not expose paths or prose in the declaration; it narrows the surface, it does not close it, and the reference says which fields still carry free text.

The gate runs in your CI, reads the declarations committed in the pull request and posts the result as a comment with the token your workflow gives it. It calls no service other than GitHub, and it installs no code beyond the Action itself and its dependencies from PyPI.

The plugin is a set of skills: text that tells Claude how to run the CLI. It bundles no executable, hook or server, and it sends nothing anywhere. Its setup skill installs the CLI from PyPI only after you approve the command, and its round skill drives the round described above; the consent to send material to a reviewer stays yours to give. For a listing in Anthropic’s directory, Anthropic shows the plugin’s author aggregate usage figures (installs, versions, runs per skill, error rates) under Anthropic’s own terms; disensor receives nothing else.

Questions about this page: open an issue in the repository.