Your code is the most sensitive thing you own. We treat it that way.
CodeReviewer reads your code to review it, fix it and test it. Here is how we keep access narrow, secrets sealed and security testing safe.
Access only where you grant it
CodeReviewer connects through a GitHub App you install. It only sees the repositories you choose, and you can remove repositories or uninstall the app from GitHub at any time.
Secrets stay secret
Test logins, database credentials and other secrets are encrypted at rest. Recorded tests reference credentials by name, never by value, and replays run without AI. Your passwords are never shown to the AI when tests replay.
Your workspace is yours
Each organisation’s projects, repositories, findings and test results are isolated from every other organisation. Within a workspace, access is scoped per project.
Least privilege for your team
Admins and members have different roles. Admins decide exactly what members can do: merge pull requests, apply fixes, trigger AI runs, manage test suites, connect databases and more.
Passive by default
Security scans are passive unless you opt in. Active scanning, which sends attack-style traffic, only runs against domains you have proven you own. Ownership is re-checked automatically, and a domain that fails the check drops out.
Databases are optional
Connecting a database is opt-in and set per project. It helps confirm bugs against real data. Credentials are encrypted, members need explicit permission to manage them, and you can remove a connection at any time.
Used for your work. Nothing else.
CodeReviewer accesses your code only to do what you ask: review a pull request, write a fix, validate an issue, or author and repair tests.
To export or delete data, or to close your workspace, email support@codereviewer.cloud. Our Privacy Policy and Data Processing Addendum explain the details.
- Repositories you install it onyes
- Pull-request branches (fixes)yes
- Mergingonly if you enable it
- Databasesonly if you connect one
- Active scansverified domains only
- Repositories you didn’t selectno
Found something? Tell us.
Email security@codereviewer.cloud with a description and steps to reproduce. We’ll confirm we’ve received it, work on a fix, and keep you updated. Please give us reasonable time to fix the issue before disclosing it. Don’t access other customers’ data or degrade the service.
Security questions.
What access does the GitHub App request?
Enough to do the job on the repositories you install it on: read code, comment on and update pull requests, commit fixes to PR branches, merge when you enable auto-merge, and work with issues. It has no access to repositories you do not select.
Will CodeReviewer push to my main branch?
Fixes are committed to the pull request’s own branch. Merging only happens if you turn on auto-merge for a repository, and then only for pull requests that meet the rules you set.
How do active security scans stay safe?
Active scans only run against domains you have verified, using a DNS record or a file on the site. Verification is re-checked automatically. If the proof disappears, active scans stop for that domain.
How are test credentials protected?
Credentials are encrypted at rest and only decrypted when a test runs. Recorded tests refer to credentials by name, never by value. Replays run without AI, so passwords are never shown to the AI during a replay.
Can we delete our data?
Yes. Contact support@codereviewer.cloud to request that data be exported or deleted, or that your workspace be closed. You can remove database connections, test credentials and repositories yourself at any time.
How do I report a vulnerability?
Email security@codereviewer.cloud with the details and steps to reproduce. We’ll confirm we’ve received it, keep you updated, and credit you if you’d like. Please don’t test against other customers’ data or disrupt the service.
Give every PR the review it deserves.
Start your 15-day free trial. We onboard a few teams every week.