legal
Privacy Policy
How Jargons accesses, uses, and stores your data when it reviews your code. Last updated July 2026.
What we access
When you install the Jargons GitHub App, we access only the repositories you select. Through GitHub we read repository metadata, file contents, and pull request diffs, and we write review comments and fix pull requests. We never access repositories you have not connected.
When you sign in, we receive your public GitHub profile (username, name, avatar, and email) via GitHub OAuth to create your account and workspace.
How we use it
To review a pull request or scan a codebase, Jargons sends the relevant diffs and file contents to our large language model provider (currently Google Gemini) to generate the findings and suggested fixes. Jargons itself does not retain your source code beyond producing the review, and does not use it to train any model.
Your content is processed by Google under the Gemini API terms, which govern how that content is handled. We do not send your code to any other third party.
What we store
We store your workspace and profile, the list of connected repositories, pull request metadata, review findings, and codebase scan results. We do not store full copies of your source code; files are fetched on demand at review time and not retained beyond what is needed to generate a review.
Third parties
Jargons relies on GitHub (source hosting and identity) and Google Gemini (to generate reviews and fixes). Each processes data only to provide its part of the service. We do not sell your data or share it with any other third party.
Retention and deletion
You can revoke access at any time by uninstalling the Jargons GitHub App from your GitHub settings, which immediately stops all repository access. To delete the data associated with your workspace, contact us and we will remove it.
Contact
Questions about privacy? Reach out through the Jargons GitHub App page.