Skip to main content

Privacy and Data Handling

Buzzbin needs access to part of your repository and review output so it can review merge requests. At the same time, the product is designed so repository source code is not kept as permanent application data.

What Buzzbin processes during a review​

In a typical run, the system processes:

  • GitLab events such as opened MRs, new pushes, or MR notes
  • repository connection data such as the project URL and related identifiers
  • the diff and the relevant files needed for that MR review
  • organization-level or repository-level review configuration

What is stored​

Buzzbin keeps these kinds of data so the product can work and bill correctly:

  • organization and repository records
  • the Project Access Token and webhook secret in encrypted form
  • organization and repository review settings
  • run metadata such as status, timestamps, selected model, token usage, and cost
  • findings, merge-risk output, answers, and other review artifacts
  • wallet and transaction history
  • 👍/👎 feedback on finding threads

What is not kept as permanent application data​

By design, these are not meant to be stored permanently as application data:

  • a permanent clone of your repository source code
  • the full plaintext Project Access Token
  • a permanent snapshot of full project history just for review purposes

Put differently, zero-retention applies to cloned code used during a run, not to the repository record, run history, or review output.

What remains in GitLab​

Comments, replies, and MR changes that Buzzbin posts into GitLab become part of your GitLab data and remain there according to GitLab's normal behavior. Buzzbin is the producer or synchronizer of that output, not the long-term owner of your GitLab records.

About the access token​

The repository token is sensitive. For that reason:

  • it is stored encrypted at rest
  • the full value is not shown in normal UI or API responses
  • if it is rotated or revoked, you must replace it with a new value

Scope of this page​

This page explains the operational behavior of the product so you know what data Buzzbin needs for execution and billing. For legal or contractual commitments, your formal company policies remain the final source of truth.