Bug✳Hunter Connect a repo Star on GitHub
Policy · privacy and data

Privacy, plainly.

Bug Hunter is open source. This page describes what the hosted instance and a self-hosted copy store, what leaves your server, and how to turn features off. Last updated 2026-11-08.

What is processed

To review a pull request, Bug Hunter sends the pull-request diff, title, description, linked issue text and selected repository files to the model provider you configure (Google, Anthropic, OpenAI, DeepSeek, OpenRouter, an OpenAI-compatible endpoint, or a local Ollama server). Those requests are subject to that provider's terms. Your API key stays in the server environment.

Repository rule files (.bughunter.md, AGENTS.md, CLAUDE.md, .cursorrules) are read from the base branch and sent with the review. API keys and secrets are scrubbed from logs and outgoing payloads.

What is stored

When DATABASE_URL is set, the server keeps:

  • Hunt history — repository, pull-request number/title/URL, finding counts, token usage and estimated cost.
  • Repo authorisation mapping — the GitHub login and that user's token, encrypted with AES-256-GCM using SESSION_SECRET. Tokens are never stored in plaintext.
  • Reviewer learnings — the correction text and a link to the comment it came from.
  • Installed repositories — the list GitHub reports for the App installation.
  • Page views — the path and a timestamp, with no IP address, user agent or cookie identifier.

Without DATABASE_URL the same records live in process memory and disappear on restart. There are no third-party analytics scripts, ad trackers or tracking cookies.

Cookies and analytics

If GitHub login is enabled, one signed session cookie keeps you signed in. It is HTTP-only and encrypted. The site counts page views with a first-party beacon to this server; it stores only the path and time, and it is skipped when your browser sends Do Not Track or Global Privacy Control. Nothing is sent to a third party.

Third parties

GitHub (webhooks and API), the model provider you choose, and — only if you configure it — your own n8n webhook. There are no other outbound integrations.

Retention and deletion

Records are kept until the operator deletes them. Delete hunts or learnings through the dashboard/API, clear the database tables, or remove the deployment. For the hosted demo, open a GitHub issue in the repository to request deletion.

Self-hosting

If you run Bug Hunter yourself, you are the data controller. You decide which model provider receives diffs, whether Postgres is used, and whether n8n is configured. Nothing is sent anywhere else.

Questions or removal requests: open an issue at github.com/dk3yyyy/bug-hunter/issues. Security reports: see SECURITY.md.