Trust center ยท reviewed July 10, 2026
Inspect the boundary before you install.
Guard is designed to run its repository analysis in GitHub Actions inside the repository you select. This page explains what it can access, what may leave that boundary, and what it does not claim to prove.
- Runtime
- GitHub Actions in the selected repository
- Repository scope
- Only repositories selected during App installation
- Removal
- Remove the workflow and uninstall the App
Access and execution
What Guard reads
Pull-request metadata, repository contents, changed paths, workflow and scanner outputs, and CODEOWNERS or other owner-routing files when present.
What Guard can write
A reviewable setup pull request, GitHub Check Runs, optional pull-request comments, and workflow artifacts after explicit installation or configuration.
Least privilege
Install the GitHub App only on selected repositories. Review the setup pull request and workflow permissions before merging.
Missing evidence
Disabled or unavailable scanners are reported as explicit unknowns. Guard does not silently treat missing evidence as proof.
Data that may be processed
- Repository and pull-request identifiers, titles, authors, changed paths, and file-level impact summaries.
- Mapped tests, scanner summaries, dependency findings, owner routes, policy status, blockers, and unknowns.
- Business contact and subscription metadata needed for intake, support, checkout, or Guard Pro access verification.
- For the install-free preview, the submitted public pull-request URL and bounded public diff evidence.
Optional external services include Stripe for checkout, private operator ledgers or signed webhooks when configured, and customer-selected scanners such as Semgrep or OSV. See the human-readable data handling summary for retention and deletion details.
Controls available to buyers
- Keep reports as workflow artifacts instead of pull-request comments.
- Disable optional scanner integrations, with missing coverage preserved as unknown.
- Configure or omit optional operator ledgers and webhooks.
- Request deletion or redaction of operator-controlled service metadata, subject to accounting, fraud, dispute, or legal retention needs.
- Cancel the subscription, remove the workflow, and uninstall App access.