security & privacy

Trust is the product.

You’re granting an outside service access to private source code. That’s a big deal, so we hold ourselves to least-privilege access, strict data handling, and isolation you can verify, in plain English.

[ 01 · our promises ]

Four promises we hold ourselves to.

Read-only by default

Out of the box Crit only reads to learn your Standard and only writes review comments. Writing fixes as commits is a separate mode you turn on per repo, every other repo stays read-only.

One company can never see another's data

Every standard, review, screenshot and log is scoped to your organisation and isolated at the database level. A stranger connecting a private repo is fully walled off from everyone else.

We never train on your code or designs

Your code and screenshots are used only to produce your review. They never train any model, ours or anyone else's.

You can disconnect and delete, anytime

Remove a repo or delete all of your data from Settings whenever you like. Screenshots are auto-deleted on a retention schedule you control (30 days by default).

[ 02 · what Crit accesses ]

The smallest set of permissions that does the job, and why.

You choose exactly which repositories Crit can see at install, never “all repositories.” We never request admin, secrets, or actions.

ScopeAccessWhy
metadataReadThe baseline GitHub requires to see a repository exists.
contentsReadTo read your Tailwind config, CSS variables and components so Crit can learn your Standard. Write access is only ever used on a repo you explicitly switch into autofix mode.
pull_requestsRead · WriteTo read the PR and its changed files, and to post the review comment and inline fix suggestions.
checksRead · WriteTo post the status check that can block a merge until serious issues are resolved.
deploymentsReadTo find the preview deployment your CI already builds, so Crit can render the real screen.
  • No admin access
  • No secrets access
  • No Actions access
  • Per-repo selection
  • Encrypted tokens at rest
[ 03 · data lifecycle ]

What happens to your data, start to finish.

01 · captured

Captured

Crit renders your existing preview deploy and stores screenshots in a private, tenant-scoped bucket. Tokens are short-lived and encrypted.

02 · used once

Used once

Screenshots + computed styles produce your review. They are never used to train any model, ours or anyone else's.

03 · deleted

Deleted

Screenshots auto-delete on your retention schedule (30 days by default). Disconnect a repo or delete everything from Settings, anytime.

Ready when you are.

Connect one repo, read-only, and see your first review.