Privacy

Installing the Bishop GitHub App on its own does not make Bishop read your code. Bishop scans a repository only after a signed-in user who accepted the current Terms of Service picks that repository in Bishop. Once it is picked, Bishop copies the repository — including its full git history — to a temporary folder on its worker, scans it, and deletes the folder when the scan ends. It reads the history to look for keys that were committed in the past. The access token for each scan covers that one repository only, can read its contents and comment on pull requests, and is not stored.

On a pull request, Bishop posts what it found as a comment on that pull request. Short excerpts of code can appear in the comment; keys that Bishop's key scanner detects are masked first.

To decide some candidate findings — possible SQL injection and possible unescaped HTML — Bishop may send a short excerpt of the code around the candidate to a large language model run by DeepSeek. A scan sends at most 40 such requests, and none when it finds no such candidate. Keys that Bishop's key scanner detects are masked before sending, and a request that still contains one is refused. A copy of each request and reply is kept as an audit record on the worker's temporary disk. The worker has no persistent volume, so these copies are lost when the worker is redeployed or restarted; until then they are kept, and only the operator can remove them.

DeepSeek's privacy policy names its data controller as Hangzhou DeepSeek Artificial Intelligence Co., Ltd., with a registered address in China. The code excerpts sent during a scan therefore go to a provider based in China. For what DeepSeek keeps, and for how long, see DeepSeek's privacy policy and its developer terms; we have not confirmed which document governs data sent through its API.

Bishop does not open fix pull requests during this beta. While they are off, no code is sent to the sandbox provider. Log drains are not offered in this beta.

The database holds findings and records, not a copy of your repository: for each finding the repository name, rule, file and line, a title and a plain-language reason, and the commit it was found on; which repositories you picked; a log of events such as an install or a posted finding; and short records used to avoid scanning the same webhook twice.

Signing in with GitHub sets one cookie, bishop_session. It holds your GitHub login and a GitHub token used only to list your installations and repositories. It is encrypted, cannot be read by scripts on the page, and expires after 7 days; logging out clears it. A second, short-lived cookie protects the sign-in step. When you tick "I accept the Terms of Service", a third cookie, signed and short-lived (15 minutes), carries that acceptance through the GitHub sign-in. The site may use Vercel Web Analytics to count page views, only if it is enabled for the project.

When you accept the Terms of Service, Bishop keeps a record of it: your GitHub user id and login, the version of the terms you accepted, and when. It keeps this to show which terms you agreed to before Bishop read your code. It stores nothing else with it — no IP address and no browser details.

If you connect your Sentry, Bishop reads your error data read-only — through an OAuth token stored encrypted — to find issues in real errors. It never writes to your Sentry.

The temporary copy of your repository is deleted at the end of each scan. GitHub webhook data waiting in Bishop's job queue is deleted 7 days after its job finishes. Records used to avoid duplicate scans are deleted after 30 days. Findings, events, and the list of repositories you picked are kept until you ask for them to be deleted — Bishop does not delete them automatically today, and uninstalling the App stops new scans but does not delete what is already stored.

You can uninstall the GitHub App at any time from your GitHub settings. To see or delete your data, email bishop.startup@gmail.com. During the beta, deletion is done by hand by the operator.