# Security and data handling.

Source: https://veridical.dev/security (this is a plain-text copy of that page)

What the Veridical GitHub App can access, what a review processes and who processes it, how to remove access, and how to report a problem. The [Privacy Policy](https://veridical.dev/privacy) and [Terms of Service](https://veridical.dev/terms) remain the governing documents.

## GitHub App permissions.

The Veridical.dev GitHub App requests five repository permissions, one organization permission, and one account permission. This is the set GitHub reports for the live app, checked on November 19, 2026. It does not request administration, Actions, secrets, workflows, deployments, or environments. It reads organization members only to check the membership of people who sign in to Veridical.

| Permission | Scope | Access | Why |
| --- | --- | --- | --- |
| Metadata | Repository | Read-only | Identify the installation, repositories, and pull requests in scope. |
| Pull requests | Repository | Read and write | Read the pull request and its exact base and head, then publish review comments and the review summary. |
| Checks | Repository | Read and write | Find and publish the review's neutral check run on the exact head commit. |
| Issues | Repository | Read-only | Receive maintainer commands written as pull-request comments. |
| Contents | Repository | Read and write | Read: fetch the exact base and head revisions under review. Write: publish a verified fix on its own branch and open a pull request for it, on plans that include repair. |
| Members | Organization | Read-only | Check, with the installation's own token, whether a person signing in is an active member of the organization, so they can join the Team workspace that connected it. If an organization owner has not approved it, the installation keeps working, and people join by invitation or wait until an admin adds them. |
| Email addresses | Account | Read-only | Read the verified email addresses on your GitHub account when you sign in. A new account uses your primary one, and the others help find an existing Veridical account that is yours. GitHub asks you to approve this when you authorize Veridical. |

### Why contents write exists

Write access to contents is used for one operation: publishing a verified fix as a separate branch and pull request, on plans that include repair. The Free plan is review-only, so Free reviews never push code. Fix pull requests are never merged automatically, and Veridical does not merge pull requests.

### Where to install it

To start reviews, [create a workspace](https://veridical.dev/signup?redirect_to=%2Fapp%2Frepositories%3Fnew%3Drepository) and install the app from there. An installation started on GitHub alone is not connected to a review allowance until a workspace claims it.

## Webhook events.

The app subscribes to 6 events. GitHub also sends installation and repository-selection events to every app installation, and tells the app when someone revokes its authorization, which ends their Veridical sign-in sessions.

- `pull_request`: Start, update, supersede, or close review work.
- `issue_comment`: Accept commands, such as an additional review, from repository insiders only.
- `pull_request_review_comment`: Receive review-comment events. Only changes to Veridical's own comments are recorded; replies are ignored, and nothing uses the records yet.
- `pull_request_review_thread`: Track resolved and unresolved review threads.
- `repository`: Keep a repository's stored visibility current when it is made private or public, or archived or unarchived.
- `organization`: End a Team workspace membership that came from the organization when the person leaves it or is removed. Invited members are not affected.

## What a review processes.

Only what is needed to review the exact pull-request revision and run the service. The marketing website never receives repository credentials, code, or card data.

- GitHub installation, repository, pull-request, base, and head identifiers.
- Pull-request metadata, commits, and the source files and diffs needed to review the exact base and head revisions.
- The output of the commands the review agent runs in the isolated sandbox, and public web pages it fetches (for private repositories, by default only an allowlist of documentation sites).
- The review's own output: findings, evidence receipts, coverage, and publication state.
- Account identity from your GitHub sign-in (numeric ID, username, name, avatar, and primary verified email), and plan and usage records.
- Capacity, abuse-prevention, and operational records.

### Safeguards in the hosted design

- Webhook signatures are verified before any work is accepted.
- GitHub installation tokens are short-lived and scoped to the repository being reviewed.
- Review workers do not receive the GitHub App private key or standing cloud credentials.
- Secrets and secret-bearing environment variables are redacted from receipts.
- Customer views omit provider credentials, model routing, and internal cost telemetry.

These are design controls, not a certification or a guarantee.

## Who processes it.

The providers named in the [Privacy Policy](https://veridical.dev/privacy); sub-processors for business customers' data are listed in the [Data Processing Addendum](https://veridical.dev/dpa). The hosted control plane is designed for Google Cloud's Warsaw region. Some providers, including Azure and Vertex AI model processing, may process data outside Poland or the EEA under Standard Contractual Clauses or the EU-US Data Privacy Framework.

Providers: Google Cloud Platform, Google Cloud Vertex AI, Azure OpenAI, GitHub, WorkOS, Stripe, Resend; and, only after you consent to measurement, Google Analytics 4, Microsoft Clarity, PostHog.

## Retention.

As set out in the Privacy Policy. Security, fraud, billing, and audit records may have a separate legal retention basis.

## Remove access.

Uninstalling the app, or removing a repository from it, stops new review work for that scope. Comments and checks already posted stay on GitHub, under your repository's controls.

## Report a security issue.

Email contact@veridical.dev with a description of the issue, the steps to reproduce it, and only the identifiers needed to locate it. Never send tokens, private keys, private source code, or unredacted evidence by email. The same contact is published in [/.well-known/security.txt](https://veridical.dev/.well-known/security.txt).
