Privacy & data
Guided Review is designed so the product does not phone home. Diff content goes to your AI provider and (for the Chrome extension, optionally) GitHub — not to a Guided Review backend. Short version also lives in the FAQ.
What leaves your machine
| Destination | When | What |
|---|---|---|
| Your AI provider | Annotating / Structure With AI | Prompt built from the diff + schema instructions; API key in the Authorization header — Configure AI provider, How a review plan works |
| GitHub (extension) | Diff fetch, device OAuth, submit review | Diff/patch URLs, OAuth device flow, review API payloads you initiate |
| Guided Review servers | — | None for extension or CLI product paths |
Extension: The background service worker is the only context that holds the API key and performs cross-origin LLM requests. Line-comment drafts are not sent until you explicitly submit.
CLI: The local server binds 127.0.0.1 only. LLM calls go from that process to your provider (or read a coding agent’s local key store). Generate Prompt copies text to your clipboard — Guided Review does not upload it. There is no GitHub OAuth or submit path in the CLI.
What stays local
Chrome extension
- Provider choice, model, and API key (
chrome.storage.local) — Configure AI provider - Active review session: diff, plan, step index (
chrome.storage.session, keyed byowner/repo#number) — Resume later - Draft comments until you submit
- GitHub tokens after Connect GitHub, until you disconnect
Closing the browser session clears session storage; local settings remain until you change or clear them. Session edge cases: Troubleshooting.
CLI
- Provider / model / agent prefs in
~/.config/guided-review/config.json(or$XDG_CONFIG_HOME/GUIDED_REVIEW_CONFIG_DIR) - Active review session and line notes in memory for the running server — gone when you Ctrl+C
- Coding-agent keys stay in that agent’s own store when you use Use My Subscription; Guided Review does not copy them into its config file
Clear data and disconnect
Chrome extension
| Goal | How |
|---|---|
| Remove the API key | Options → AI Provider → clear the key field → Save |
| Disconnect GitHub | Options → GitHub → Disconnect / sign-out — Connect GitHub |
| Drop the active plan / drafts | Close the browser session (session storage clears), or start a fresh review after the session ends |
| Uninstall | Remove the extension in chrome://extensions. That deletes extension storage for this profile |
Revoking the OAuth grant on GitHub’s side (Settings → Applications) also invalidates submit until you connect again.
CLI
| Goal | How |
|---|---|
| Clear a saved API key | Settings → clear the key and save, or delete apiKey from the config file |
| Stop using a coding agent | Turn off Use My Subscription in Settings, or remove codingAgent from the config file |
| End the session / notes | Ctrl+C the CLI process — in-memory session and notes are gone |
| Wipe saved prefs | Delete ~/.config/guided-review/config.json (or the path under $XDG_CONFIG_HOME / GUIDED_REVIEW_CONFIG_DIR) |
Guided Review never held a cloud copy of these secrets to delete on a server — clearing local storage / the config file is the full wipe for product data.
Website analytics
The marketing site uses an analytics service for page views and a few CTA clicks (install / star). That data is handled by our analytics provider, PostHog. Analytics runs on the website only — not through the extension or CLI. Neither product embeds analytics or tracks review activity. Detail: Cookies · Privacy Policy.
Full policy
Legal detail lives in the Privacy Policy, Terms, and Cookies pages. If something here conflicts with those documents, the legal pages win.
Questions? Email [email protected]. Product questions: FAQ. Setup problems: Troubleshooting.
Next. FAQ · Configure AI provider · Connect GitHub · CLI → Config file