Skip to content
← Home

Privacy

Last updated: July 5, 2026.

The waitlist stores your email address so we can tell you when runtime monitoring opens. If you choose to answer the two optional questions on the form — what you build with, and what you would pay per month — we store those answers too; they are optional and the form works with an email alone. Your IP address is not stored: it is hashed to rate-limit signups. We do not sell any of this.

When you install the GitHub App, Bishop reads your code and git history to find and prove issues. Tokens are least-privilege, scoped to one repository for one hour, and encrypted at rest. Logs are redacted at ingestion; a real secret is never placed in a pull request, comment, or a log we store.

If you connect your Sentry, Bishop reads your error data read-only — through an OAuth token stored encrypted — to detect and prove vulnerabilities from real errors. It never writes to your Sentry.

Untrusted test code runs in an isolated sandbox only, never on the host that holds your data.

To access or delete your data, email [email protected].

Information we collect

Waitlist: your email address, and, only if you choose to answer, what you build with and what you would pay per month. Your IP address is not stored; it is hashed to rate-limit signups. Account: when you log in with GitHub, we receive your GitHub profile basics and the repository access you approve. Repositories: when you install the GitHub App, Bishop reads your code and git history to find and prove issues. Sentry: if you connect Sentry, Bishop reads your error data read-only.

How we use it

We use this information to run the service: to find and prove issues, open fix pull requests, tell you when features open, prevent abuse, and answer your messages. We do not sell any of it, and we do not use your code to build products for other customers.

How we protect it

Tokens are least-privilege, scoped to one repository for one hour, and encrypted at rest. Logs are redacted at ingestion; a real secret is never placed in a pull request, comment, or a log we store. Sentry access uses an OAuth token stored encrypted, and Bishop never writes to your Sentry. Untrusted test code runs in an isolated sandbox only, never on the host that holds your data.

Subprocessors

We use third parties that process data on our behalf: our database host, GitHub, Sentry (if you connect it), Slack (if you connect it), and the large-language-model provider that powers analysis. They may process only what is needed to provide their part of the service.

Data retention

We keep waitlist entries until you ask us to remove them or the waitlist is closed. Access tokens are short-lived and expire automatically. Logs are kept only as long as needed to operate and secure the service. Findings and related data are kept while your account is active and deleted or de-identified within a reasonable period after you close it, unless we must keep them by law.

Your rights

You can ask to access, correct, delete, or export your data, and you can withdraw your consent where we rely on it. To exercise any of these rights, email [email protected] and we will respond within a reasonable time. You can also revoke Bishop's access at any time from your GitHub and Sentry settings.

Data location and transfers

Data is stored and processed with our providers, which may be located outside your country. Where required, we rely on appropriate safeguards for international transfers.

Legal basis and regional rights

Where the GDPR or UK GDPR applies, we process data to perform our contract with you, for our legitimate interests in running and securing the service, and on your consent where you give it, such as when joining the waitlist. Where the CCPA or similar laws apply, we do not sell or share personal information, and you may exercise the access and deletion rights above. You may also complain to your local data protection authority.

Cookies and analytics

The site does not use advertising or analytics cookies or trackers. Any cookie set is strictly necessary, for example to keep you logged in.

Changes and contact

We may update this policy and will note the date above, giving notice of material changes. Questions: email [email protected].