Diff Brokerβ Back to Diff Broker

Privacy Policy

Last updated October 05, 2026

Diff Broker is in beta. Features may change, break or be removed, data may be lost, and this document may change as the product develops. Please keep that in mind when you rely on it.

Diff Broker (diff.broker, "Diff Broker", "we") shows the pull requests that involve you on one screen. This policy explains what we collect, why, and what you can do about it. We keep it short because we collect little.

Who is responsible

Diff Broker is operated by Iurii Sidorov (Autónomo), Girona, Spain, who is the data controller for the personal data described here. Contact: gitbroker@yurisidorov.com.

What we collect

  • Account data from GitHub. When you sign in with GitHub we receive your GitHub id, login, name, avatar, email address, and the organizations and teams you belong to.
  • Your GitHub access token. We ask GitHub for the repo, read:org, user:email and read:project scopes. The token is stored encrypted and used only to read your pull requests and, when you click a button, to act on them as you (approve, comment, merge, re-run checks and similar). If you add a personal access token, it is stored encrypted the same way.
  • Pull request data. For every pull request that involves you (and any you pin) we sync titles, descriptions, branches, labels, check results, reviews, comments, review threads and the metadata around them, and fetch diffs from GitHub when you open them. This includes data from private repositories you can access.
  • Your activity in Diff Broker. Read state, pins, snoozes, mutes, quiz answers, settings, a log of the GitHub actions you took through Diff Broker, and when you were last active.
  • Companion and token data. If you pair the optional companion (the diffbroker gem) we store the device name, version, platform and the logs your own agent relays for runs you start. If you create MCP tokens we store a hash of each token and its scopes.
  • Technical data. Standard server logs (IP address, user agent, requested URL, time) and error reports.
  • Anonymous visit statistics. A privacy-friendly analytics pixel (Nullitics) receives the page URL, referrer, screen width and the country derived from your IP address. It sets no cookies and does not build a profile of you.

What we do not do

  • We do not sell your data and we do not show advertising.
  • The Diff Broker server does not send your code or pull requests to an AI service. AI features run on your own Claude Code or Codex through the companion, under your own account and terms with that provider. (Optional AI pull request summaries exist but are off unless the operator turns them on; if that ever changes, this policy will say so first.)
  • We do not read your private code for any purpose other than showing it to you.

Why we use it, and the legal basis

We use the data to sign you in, sync and display your pull requests, track what you have read, carry out the actions you ask for, keep the service secure and fix errors. Where the GDPR and Spain's data protection law apply, the basis is performing our agreement with you (providing the service) and our legitimate interest in running a secure, reliable service. Where we ask for it, consent is the basis, and you can withdraw it at any time.

Who else receives data

  • GitHub, because that is where the data comes from and where your actions are sent.
  • Hosting and infrastructure providers that run our servers and encrypted backups.
  • An email provider that delivers sign-in and notification emails you have not turned off.
  • Nullitics for the anonymous statistics above.
  • Authorities, when the law requires it.

Your pull request data is not visible to other Diff Broker users, except what GitHub itself already shows them (for example, the people on the same team who can see the same repository).

Retention

We keep your data while your account exists. Pull request data is refreshed as GitHub changes it and removed when you lose access to the repository or delete your account. Server logs are kept for a limited time for security and debugging. Encrypted backups roll off on a schedule.

Your rights

Depending on where you live, you can ask to access, correct, export or delete your data, object to or restrict some processing, and complain to your data protection authority (in Spain, the Agencia Española de Protección de Datos, aepd.es). You can disconnect GitHub, revoke tokens and delete your account in Diff Broker's settings, and you can revoke Diff Broker's access at any time in your GitHub settings under Applications. For anything else, write to gitbroker@yurisidorov.com.

International transfers

Our servers and providers may be outside your country. Where required, we rely on appropriate safeguards for transfers, such as standard contractual clauses.

Security

Access tokens are encrypted at rest, connections use HTTPS, write actions are checked against the current head of the pull request and logged, and agent tasks get narrowly scoped, short-lived tokens. No system is perfectly secure; tell us if you find a problem.

Children

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

Changes

If we change this policy in a meaningful way we will update the date above and, for significant changes, tell you in the product or by email. See also our Legal Notice, Cookie Policy and Terms of Use.