Privacy Policy

• Account & team: name, email, a securely hashed password, preferred language, team name and membership.
• Integration data: GitHub App installation IDs and selected repositories; for each error tracker you connect, its account identifiers, access credentials and selected projects — for Sentry, your organization and OAuth tokens; for PostHog, a personal API key (encrypted at rest); and, for each custom webhook endpoint you create, its name, repository and settings, the time of its last event and the environments it has received, and its secret token (stored hashed and encrypted).
• Run data: error details from your error tracker or that you send to a custom webhook (titles, types, stack traces, links and any context you include), repository names, branches, the agent's summary or failure reason, generated pull-request links, links to the GitHub Actions run, and token usage / cost estimates.
• Agent configuration: the model and effort you choose, your daily safety cap, and the instructions you write for the agent — including their version history, change notes and authors.
• Billing: plan, subscription status and billing identifiers via Stripe. We do not store full card details.
• Technical: logs and limited usage data needed to operate and secure the Service.

• To provide the Service and your account — performance of a contract (Art. 6(1)(b)).
• To process payments and meet accounting obligations — contract and legal obligation (Art. 6(1)(b), (c)).
• To enforce usage limits, prevent abuse and keep the Service secure — our legitimate interests (Art. 6(1)(f)).
• To send service-related emails such as team invitations and billing notices — contract / legitimate interests.

The agent that generates a fix runs inside your own GitHub Actions runner, using an AI key you provide as a GitHub Actions secret. Your source code and that key never leave your infrastructure and are never sent to bugzero or, by us, to any AI provider. bugzero receives only run metadata — the run status, the agent's summary, the pull-request link, and token-usage and cost estimates. The bugzero GitHub App has no access to repository contents — on the repositories you select, it can only see their names and start the bugzero workflow.

We share data with the following processors strictly to operate the Service:

• GitHub — hosting your repositories, running the fix in GitHub Actions, and opening pull requests.
• Sentry and PostHog — whichever you connect: receiving error events and reading issue details.
• Stripe — payments and subscription management.
• MongoDB Atlas — database hosting.
• Resend — transactional email.
• Vercel — application hosting.

Your AI provider (for example Anthropic or OpenAI) is not a bugzero sub-processor: the agent runs in your own GitHub Actions runner under your own account and key, so that relationship is directly between you and the provider.

Some processors (for example Stripe and GitHub) are located outside the European Economic Area. Such transfers are protected by appropriate safeguards, such as the EU Standard Contractual Clauses or an adequacy decision.

We keep personal data for as long as your account is active and as needed to provide the Service, then delete or anonymize it — except where longer retention is required by law (e.g. accounting records). Deleting your team removes its members, integrations and run history.

Under the GDPR you have the right to access, rectify, erase, restrict or object to processing, to data portability, and to withdraw consent. To exercise these rights, contact contact@bugzero.dev. You also have the right to lodge a complaint with the Polish supervisory authority — Prezes Urzędu Ochrony Danych Osobowych (UODO), ul. Stawki 2, 00-193 Warszawa.

We use industry-standard measures including encryption in transit (TLS), encryption at rest for sensitive secrets (such as your integration tokens and keys), and access controls. No system is perfectly secure, but we work to protect your data.

We use a strictly necessary session cookie to keep you signed in. We also use a language cookie, NEXT_LOCALE, which remembers your chosen language: it is set when you pick or visit a language version, is kept for 1 year and is not used for tracking. We do not use advertising or third-party tracking cookies.

The Service is not intended for anyone under 16, and we do not knowingly collect their data.

We may update this policy; material changes will be notified by email or in-app, with the “last updated” date revised above. This policy may be provided in other languages; if versions differ, the English version prevails.