Last updated 2026-09-26. Invite-beta notice; the current version always lives at this URL.
The short version
- We process your repository content to review your pull requests. That is the product; there is no other use of it.
- We do not train models on your code.
- Provider API keys you add are sealed — stored encrypted at rest, and never displayed again after you save them.
- We do not sell your data and there is no advertising.
What we process
- Repository content. The pull request diffs and the repository context needed to review them, for repositories you enroll. Used to produce reviews and their records — findings, verdicts, run history.
- Account data. Your GitHub login and the repository and organization access GitHub reports to the review bot for enrolled repositories.
- Provider keys. API keys you add for review inference: stored sealed (encrypted at rest with a server-side key), shown afterwards only as a label and fingerprint, and used only to run your reviews.
Where inference happens
Reviews run on the AI provider configured for the repository — on your own key when you have added one (bring your own key). Review requests, and the code context they need, go to that provider under its terms as well as ours.
No training on your code
We do not use your repository content, findings, or review records to train models — ours or anyone else's.
Retention and deletion
Review records are retained while your repositories are enrolled, so history stays navigable; account data is retained while your login is active. Email hello@hyperneo.dev to request deletion of specific records or everything. Uninstalling the GitHub App stops new processing.
Sharing
Data is shared only as needed to run the service: our hosting infrastructure and the AI provider that runs each review (see above). We do not sell or rent data, and there is no advertising. We may disclose data when required by law.
Contact
Privacy questions and requests: hello@hyperneo.dev. See also the Terms of Service.