Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.neo.projectdiscovery.io/llms.txt

Use this file to discover all available pages before exploring further.

This page is the public trust and support reference for Neo on GitHub.

​
What GitHub Data Neo Uses

Neo uses GitHub data only to support the pull request work you initiate. At a high level, that includes:
  • the pull request diff and the contents of files touched by it (plus a small set of related files when review expansion activates)
  • pull request and commit metadata needed to anchor reviews to the right place
  • the comment that triggered a @pdneo command, along with the surrounding PR context
  • user identity details needed to map the GitHub user to the right Neo team and access context
Neo uses this data to run the requested review or command, post results back on the PR, and keep the task tied to the correct team and user context.

​
What Neo Does Not Read

  • repositories not granted to the install
  • branches outside the PR being reviewed
  • private repos on the org that aren’t in the install’s “selected repositories” scope
  • contents of files outside the diff unless review expansion explicitly pulls them in for security-sensitive PRs

​
Data Handling Principles

Neo follows the same platform-wide privacy and security model on GitHub as it does elsewhere:
  • your code, diffs, and findings are not used to train models
  • repo data stays within Neo’s customer-scoped execution model
  • credentials and sensitive data are handled under Neo’s broader security controls
For the full platform-wide model, see Security & Privacy.
Neo never trains on your code, PR content, review findings, or GitHub task output.

​
Access Controls

Two layers protect what Neo will act on:
  1. GitHub App permissions. Neo only requests the scopes it needs; the install owner approves them on github.com.
  2. Per-repo collaborator check. Even within Neo’s team-trust model, per-repo operations re-verify via GitHub that the calling user has collaborator access on the specific repository. See Admin & Permissions.

​
Support

If you need help with the GitHub integration, use these public support paths: Public legal and trust resources: If your team needs deeper security or compliance details, the broader Neo documentation is here:

​
Security And Compliance Questions

For security and compliance evaluation, the Trust Center is the best starting point. If you need a deeper conversation about how Neo handles data, privacy, or deployment controls, use the support or contact paths above to route the request appropriately.