The GitHub permissions we ask for, and why

We would rather you see this before you install. The GitHub App is installed only on the repos you choose, and you can remove it from GitHub at any time.

MetadataReadRepo name, branches and collaborators. Required by GitHub.
ContentsRead and writeRead the specs/ folder and propose new specs through a branch and a PR. With this permission the app can read the repo's code.
Pull requestsRead and writeTrack PR status, open spec PRs and comment gate results.
Checks and Commit statusesRead and writePublish the ZPX Forge / gates check, which blocks merging until a person approves.
DeploymentsWrite · ProRespond to the production environment protection rule using the audit decision for the exact commit.
ActionsReadSee whether CI passed or failed for each task.
IssuesRead and write · optionalLink tasks with issues.
AdministrationRead and write · optionalCreate the rules that protect main and develop. Without it, you set them up by hand.
Members (organization)ReadMatch your GitHub team with your company members.
Email addresses (account)ReadYour email when you sign in with GitHub.

What we do and what we don't

  • We don't store your code. From the repo we use specs/, metadata, PRs and CI results.
  • We don't run your code or your tests: that happens on each person's machine.
  • We don't send your code to any AI model: ZPX Forge has no AI of its own.
  • The app only sees the repos you choose, and you remove it from GitHub in one click.