Reviso — Privacy Policy

Last updated: October 2026

This policy covers Reviso, the open-source (Apache-2.0) code review plugin for Claude Code and Codex, installed from github.com/Vyttle-LLC/reviso.

The Short Version

Vyttle collects nothing automatically. Reviso runs on your machine, inside Claude Code or Codex, on your own account. There is no Reviso account, no signup, and no telemetry. Your code never passes through Vyttle LLC infrastructure. The only thing that reaches us is a feedback report you choose to file.

How Reviso Works

Reviso is a set of review commands that run inside your AI coding host. It reads your branch's changes from your local git repository and reviews them through the Claude Code or Codex session you are already using. It reports findings and never edits your files.

What We Collect

Nothing automatically. Reviso has no servers of its own and sends no usage data, analytics, or "anonymous" metrics. Its only outbound write is a feedback report you approve, filed as a GitHub issue (see Feedback Reports below).

AI Provider Data

The review itself is done by your AI host, so the code it reads is handled the same way as anything else you do in Claude Code or Codex. That handling is governed by your agreement with Anthropic or OpenAI. We recommend reviewing their privacy policies and data retention settings.

Web Lookups (Opt-In)

One feature reads the public web: the best-practices lens, which runs only when you add --web to a style review. No repository file, environment variable, or setting can turn it on. When it runs:

• A search contains only ecosystem facts: the language, framework, library names and versions, and the names of third-party symbols on changed lines.
• A search never contains your code, diff text, your own identifiers, file paths, commit messages, branch names, or ticket IDs.
• Each run is capped at twelve searches. Every finding cites its source, and --explain prints every query and URL.
• Nothing fetched is stored.

Searches go through your AI host's web tools, not through Vyttle. The full rules are in the web lookup contract.

Feedback Reports

After a review, Reviso can offer to report a wrong finding. Nothing is ever sent automatically: a report exists only because you said yes to that report.

• Metadata report (default). A script builds it from a fixed list of fields: which lens or detector produced the finding, its severity and confidence bucket, why you judged it wrong (chosen from a fixed list), the command, the plugin version, and the model. It never includes file paths, code, finding text, branch names, or free text. You see the exact payload before it is sent.
• Code-context report (optional). Reviso opens a prefilled issue form in your browser. You add, edit, or redact anything and submit it yourself.

Both are filed as public GitHub issues on the Reviso repository, from your own GitHub account, so your GitHub identity is attached just as it is for any issue you file by hand. GitHub's privacy statement governs that data. The full rules are in the feedback contract.

Feedback issues stay open until we have looked at them, then they are closed. We delete feedback issues a year after they are filed. If you want one deleted sooner, email privacy@vyttle.com with a link to the issue and we will delete it. Because these issues are public, copies made before deletion, such as search-engine caches or GitHub notification emails, may remain outside our control.

Third-Party Services

Reviso is installed and updated from GitHub, so GitHub's privacy statement applies to those downloads. Reviso has no other third-party services.

Changes to This Policy

If we make changes, we will update the "Last updated" date above.

Contact

Questions? Contact us at privacy@vyttle.com