Security and data handling.

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. This page summarizes the live app configuration, the Privacy Policy, and the published docs. The Privacy Policy and Terms of Service 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 .

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.

See the app on GitHub
PermissionScopeAccessWhy
MetadataRepositoryRead-onlyIdentify the installation, repositories, and pull requests in scope.
Pull requestsRepositoryRead and writeRead the pull request and its exact base and head, then publish review comments and the review summary.
ChecksRepositoryRead and writeFind and publish the review's neutral check run on the exact head commit.
IssuesRepositoryRead-onlyReceive maintainer commands written as pull-request comments.
ContentsRepositoryRead and writeRead: 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.
MembersOrganizationRead-onlyCheck, 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 addressesAccountRead-onlyRead 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 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. Read the data-handling docs.

Who processes it.

The providers named in the Privacy Policy; sub-processors for business customers' data are listed in the Data Processing Addendum. 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.

Google Cloud Platform
Hosted application, regional database, object storage, queues, logs, key management, and isolated review infrastructure.
Google Cloud Vertex AI
Model processing for reviews: Anthropic's Claude models as Google provides them, through the Vertex AI global endpoint. Request-response logging is not enabled. Google may keep parts of a request in a prompt cache that only our Google Cloud project can use, for up to one hour after their last use.
Azure OpenAI
Model processing for repository scans, fixes, and reviews that do not run on Vertex AI.
GitHub
Sign-in, and repository, pull-request, and delivery data for the repositories you connect.
WorkOS
Our previous sign-in provider. It signs in nobody new, and keeps the account records of people who signed in before sign-in moved to GitHub until we close our account there.
Stripe
Checkout, subscriptions, and payments for paid plans. Card details go to Stripe directly.
Resend
Transactional email for account, service, and inquiry messages.
Google Analytics 4, Microsoft Clarity, PostHog
Optional measurement, loaded only after you consent. PostHog event properties exclude code, finding text, email addresses, and authentication tokens.

Retention.

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

Review records and source-derived artifacts
Kept under the workspace retention policy, subject to legal hold, security investigation, backup, and billing-integrity exceptions.
Server and request logs
Up to 90 days, then deleted or aggregated.
Email correspondence
Up to 24 months, then deleted when no longer needed.
Billing and tax records
For the period accounting, tax, fraud-prevention, and legal obligations require.
Account and membership mappings
While the workspace is active, and for the limited period needed for security, disputes, and legal obligations after closure.

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.

Personal account
Settings → Applications → Installed GitHub Apps → Configure next to Veridical.dev → Uninstall.
Organization
Your organizations → Settings → GitHub Apps (under Third-party Access) → Configure next to Veridical.dev → Uninstall.

The same Configure page lets you narrow repository access instead of uninstalling. If you also authorized the app on your personal account, you can revoke that under Authorized GitHub Apps. To delete account or review data, email contact@veridical.dev with the installation and repository identifiers needed to find the records.

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.