CodeRight does not run a hosted code-review cloud that receives your repository. The desktop app and Rust daemon run on your machine. The control plane, sessions, logs, and orchestration state are local.
| Data | Where it lives | Notes |
|---|---|---|
| Repository files | Your machine | CodeRight reads local files to perform the work you ask it to do. |
| Sessions and run evidence | Local CodeRight storage | Used for replay, review, and verification history. |
| API keys | Local credential storage / local configuration | You bring provider keys. CodeRight does not sell a hosted model relay. |
| Prompts and code context | Your chosen provider or local endpoint | Only when you configure and run that provider. Provider terms apply. |
| CodeRight servers | No repo upload | License/update/waitlist services do not need your repository. |
Local-first does not mean every model is local
CodeRight can call remote model providers because BYOK is part of the design. The important boundary is explicit routing: your code is not uploaded to CodeRight servers, and model requests go only to the provider or local endpoint you configure.
No telemetry by default
The public product story is intentionally narrow: no hosted code ingestion, no account requirement for local runtime use, and no product telemetry stream for your sessions.
Permission gates
CodeRight is built around supervised execution. Tool use, shell commands, file writes, and risky operations are governed by the runtime's permission model rather than hidden inside a hosted agent.
Security contact
For security reports or privacy questions, email hello@coderight.cc. See the full privacy policy for website, waitlist, license, and support data handling.