What a review uses
- 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 reads. For private repositories, web access is limited by
default to an allowlist of documentation sites.
- On Pro and Team Pro, the wiki pages of the modules the pull request touches,
from the repository’s latest completed
codebase scan, used
only for reviews of that repository in your workspace.
- The review’s own output: findings, evidence, coverage, and publication state.
- Account identity from your GitHub sign-in (numeric ID, username, name,
avatar, and primary verified email), workspace membership, plan and usage
records, and capacity, abuse-prevention, and operational records.
Access and minimization
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.
Customer views omit provider credentials, model routing, raw internal votes, and
internal cost figures. Secrets and secret-bearing environment variables are
redacted from receipts.
Retention and deletion
These terms follow section 11 of the
Data Processing Addendum, which governs.
- Stopping processing. Uninstalling the Veridical GitHub App, or removing a
repository from it, stops new processing for that scope. Comments and checks
already published to a repository stay there, under that repository’s own
controls.
- Deletion. When you stop using the service, or earlier on a written request
to contact@veridical.dev, Veridical deletes
customer personal data within 30 days, unless EU or member-state law requires
keeping it. Before deletion you can ask for a copy of the review findings held
for your workspace.
- Copies that expire on their own. Review artifacts in object storage are
deleted automatically 30 days after they are created, and deleted objects stay
recoverable for a further 7 days. Database backups and recovery logs are kept
for 7 days. Operational logs expire under the periods in the
Privacy Policy.
Security, fraud, billing, and audit records may have a separate legal retention
basis.
For a data request, include only the installation and repository identifiers
needed to locate the record, and see Support. Never
email tokens, private keys, raw private source, or unredacted evidence.Last modified on November 19, 2026