Privacy & security

Your token stays local#

Sign-in uses GitHub's OAuth Device Flow. The resulting token is held in the OS keychain — Keychain on macOS, Credential Manager on Windows, Secret Service on Linux — not in a plaintext config file. The OAuth client ID is public, as GitHub intends for this flow, and there is no client secret to leak.

Your code stays yours#

Reviewly has no backend. The only outbound calls the app makes are to GitHub (to do your review) and to the AI backend you explicitly configure — and that call receives only the PR diff and conversation, never your whole repository. If you use a local CLI or a local model, nothing leaves your machine at all.

AI runs where you choose#

AI review is optional, and when you turn it on, you choose exactly what runs it:

• A local CLI already on your machine — Claude, Codex, or Gemini — detected automatically when it's on your PATH and signed in.
• Your own OpenAI-compatible endpoint — OpenAI, a local Ollama or LM Studio server, OpenRouter, or anything else that speaks the same API.

Either way, only the PR diff (and, for chat, your conversation) is sent to that backend — never a copy of the whole repository, and never to Reviewly itself.

No telemetry#

Reviewly doesn't phone home, track usage, or collect analytics. What you review, how you review it, and which AI provider you use stays on your machine.