Our guiding principles
- Short-lived processing – We never permanently store your repository’s source code. Your code is fetched into an isolated, short-lived sandbox only while an AI review is running and is irreversibly deleted as soon as the job completes.
- Encryption everywhere – All data is encrypted in transit (TLS 1.2+) and at rest (AES-256), including database records and object storage.
- Least-privilege access – The cubic GitHub App requests the minimum scope required to perform reviews. No additional write-or-admin permissions are granted unless they are strictly necessary (see below).
- Transparent operations – We publish this page so that every customer—current or prospective—can understand exactly how we treat their data. If you have questions, email us any time at contact@cubic.dev. Our data handling practices are further detailed in our Privacy Policy and use of the service is governed by our Terms of Service.
- No AI model training on customer data – Our AI model providers (e.g., OpenAI, Anthropic) contractually commit that code snippets and metadata passed through their APIs are not used to train or improve their underlying models.
SOC 2 compliant
cubic is SOC 2 Type 1 compliant, demonstrating our commitment to security and trust for our customers. We maintain comprehensive controls for change management, access management, and vulnerability management.Permissions requested by the cubic GitHub App
Granting the following scopes allows cubic to read pull-requests, leave review comments, and update PR status checks.| Scope | Access | Why we need it |
|---|---|---|
| Administration | Read-only | Access repository settings and organization information |
| Actions | Read & write | Manage GitHub Actions workflows when Background Agents create fix PRs (read-only for basic reviews) |
| Checks | Read & write | Surface pass/fail status checks for AI review completion |
| Code | Read & write | Read: Fetch PR diffs and context for reviews. Write: Enable Background Agents to create fix PRs targeting your feature branch (never pushes directly to main or protected branches—all fixes go through PR review) |
| Commit statuses | Read-only | Monitor and display commit status in the cubic UI |
| Deployments | Read-only | Access deployment information for integration purposes |
| Issues | Read & write | Create issues for tracking review findings when configured (optional feature) |
| Metadata | Read-only | Display repository information inside the cubic UI |
| Pull requests | Read & write | Post AI-generated review comments, resolve threads when feedback is addressed, and create fix PRs via Background Agents |
| Workflows | Read & write | Run CI/CD checks on fix PRs created by Background Agents (read-only for basic reviews) |
Note: You can install the cubic App on a single repository or an entire organization. Access is scoped to the repositories you select during installation, and can be modified at any time from GitHub’s “Installed Apps” settings page. Write permissions are primarily needed for the Background Agents feature, which creates separate PRs with proposed fixes—never direct commits to your main branch. The Background Agents feature uses Claude Code in an ephemeral sandbox to generate fixes, ensuring all changes go through your standard PR review process.
For extra peace of mind: While cubic never pushes directly to your main branch, you can
enhance security by enabling branch protection rules. Configure branch protection
rules
on your main/default branch to prevent direct commits and require pull request reviews before
merging. This ensures all changes—including those from cubic’s Background Agents—must go through
your standard review process.
How AI code review works
- Event trigger – Whenever a pull request is opened or updated, GitHub sends cubic a webhook describing the event.
- Ephemeral sandbox – A new isolated container is launched. The sandbox has no network egress.
- Analysis – The pull-request diff and only the necessary context needed for reviewing the PR are processed by AI models.
- Comment publication – The generated review comments are posted back to the PR via the GitHub API.
- Secure teardown – The sandbox (filesystem, memory, logs) is destroyed immediately after the review finishes.