Privacy: what Revue stores and sends

Revue runs on your Mac and keeps your reviews there. It talks to GitHub, to the AI tools you run, and to two servers of its own, for updates and for usage reports. This page says what goes where. The two lists below are the ones in Help › What Revue Stores and Sends, word for word.

Stored on this Mac

~/.revue/: The database with snapshots, local comments, settings and review results. Partial copies of the GitHub repositories you open. A GitHub token, only if Revue signed you in itself rather than through the GitHub CLI. The Claude Code plugin’s files once you install it. Revue’s log. The install ID, the key that makes its codes for your repositories, your reporting choices and reports waiting to be sent.
~/Library/Application Support/Revue Native/: Your windows and tabs, recent folders, layout and Inbox read history. Comment drafts, viewed marks and images waiting to be attached. The list of agent sources, without their tokens. What onboarding has shown you, and the tour’s sample repository while a tab has it open.
~/Library/Caches/Revue/: Images from comments and syntax colouring, which Revue can fetch or work out again.
Keychain: Agent source tokens.
Elsewhere, only if you ask: Worktrees for stack layers, in a folder beside the checkout named after it with .worktrees on the end. The revue command, in /usr/local/bin. The Claude Code plugin’s registration, in Claude Code’s own settings. Git hooks installed with revue hooks. A lock file in ~/.claude/ide while a terminal tab runs Claude Code.

Files and folders lists what’s inside each folder.

Sent from this Mac

GitHub: While you are signed in, requests for your Inbox and the pull requests you open, with their reviews, checks and stacks. The Inbox asks about once a minute while it is open. The reviews, comments and replies you submit, and what you push. Git fetches of the repositories you open. People’s avatars, and images in comments unless you turn them off in Settings › Diff and review.
Your AI provider: The change, and the files of its repository the tool reads while it works, through your own Claude Code or Codex, when you run AI review, ask about lines or draft a pull request description. Not otherwise, unless you turn on automatic review.
An agent source: Nothing until you add one. Then requests for the pull requests it reviewed and the ones you open, what you do with its findings, and the reviews you ask it for. Local work reporting, only if you turn it on for that source: the name of this Mac, and for each repository you allow, the names, commit subjects and sizes of your unmerged branches. Their code only when a review of one is requested.
GitHub, through your browser: Only if you turn on live updates in Settings › Live updates. Revue then reads your GitHub session cookie from Chrome, Brave or Firefox to hear about changes as they happen. Off by default.
updates.ryc.sh, for updates: After you allow it, about every hour, and when you choose Check for Updates: a request for the newest version. It carries the version you have and an update access code that every copy shares, and no account. Like any web request, it carries your IP address.
usage.ryc.sh, for usage and crash reports: Unless you turn them off in Settings › Updates: counts of the features you use and the settings you change, how long launches, sessions and diffs take, when Revue stops responding, and the errors and crashes Revue meets, by error code, with paths, addresses, logins, tokens and the names of the repositories, branches and folders Revue knows taken out first. Repositories, branches and pull requests are counted by codes made on this Mac, which no one can turn back into names, and the size of a stack or diff only in ranges. They carry a random install ID, the versions of Revue and macOS, the kind of processor and the update access code. Never your code, comments or prompts. Like any web request, it carries your IP address.

Pictures in comments are turned off with Load images in comments, in Settings › Diff and review › Comments. Live updates are turned on in Settings › Live updates, which Settings › Accounts links to.

Usage statistics and crash reports

The first time you open Revue, a notice says “Revue sends usage statistics and crash reports to help improve it.” Nothing is sent before that. Its What is sent button, and What Revue sends in Settings › Updates, list every field. In short:

When: about every five minutes while you use Revue, and when you quit, to usage.ryc.sh.
Who you are: a random install ID made on this Mac, the versions of Revue and macOS, and whether the Mac has Apple silicon or an Intel processor. No account and no name.
What happened: launches, sessions and how long they lasted, the features you used and how you reached them, the settings you changed, timings such as diff loads, and when Revue stopped responding.
What it was about: repositories, branches and pull requests appear only as 12-character codes made with a key that never leaves your Mac, and sizes only as ranges, such as 21 to 100 lines.
Errors and crashes: an error code such as GIT-012, and the error’s sentence with paths, names, logins, tokens and the names of repositories and branches taken out first.
Never: your code, comments, prompts or file contents, or the longer text under an error.

On macOS 27 and later, each report is signed with a key made for this install, so the server can tell it came from a genuine copy of Revue. Like any web request, a report carries your IP address.

Turn sending off

To stop	Do this
Usage statistics	Turn off Share usage statistics in Settings › Updates.
Error and crash reports	Turn off Send error and crash reports in Settings › Updates.
Update checks	Turn off Check for updates automatically in Settings › Updates. Revue › Check for Updates still checks when you ask.
Your AI provider	Don’t run AI review, Ask AI or drafts, and leave Review new snapshots automatically off in Settings › AI review.
Live updates	Leave them off in Settings › Live updates. They’re off unless you turn them on.
An agent source	Remove it in Settings › Agent sources.

Turning a report switch off sends one last count saying so, and nothing of that kind after it. Reset ID, in Settings › Updates, makes a new install ID and a new key, so earlier reports can’t be matched with later ones.

Copy Diagnostics

When you ask for help, Help › Copy Diagnostics puts a report on the clipboard. Nothing is sent until you paste it somewhere yourself. It holds your Revue and macOS versions, where Revue runs from, the update status, the tools Revue found and the PATH it uses, how GitHub is connected, data sizes and the last 200 lines of the log. Tokens, the update code, email addresses, repository names and your home folder are left out. See Get help.