Git Brain Privacy | Data and Telemetry Summary

Repository data stays scoped to the product workflow

Git Brain operates inside the editor against repositories the user opens. Its visual Git features read local repository state to show history, branches, stashes, diffs, worktrees, synchronization status, and merge conflicts.

The local MCP server is bundled with the extension. Tool results exclude credentials and absolute repository paths, and mutating operations remain subject to the extension's review and confirmation safeguards. Git Brain does not expose repository data through a hosted public MCP endpoint.

Showcase analytics are limited

The showcase uses pseudonymous product analytics and privacy-masked session replay to understand page visits, navigation, section reach, scroll depth, clicks, and usability. It does not identify visitors or use automatic interaction capture.

Session replay masks every input and blocks complete forms and marked private regions. It excludes console logs, network request headers and bodies, cross-origin frames, and fonts. Showcase telemetry also excludes form values, email addresses, filenames, external URL query strings, and raw error messages.

Support data is submitted deliberately

Bug and suggestion forms send only the information a visitor chooses to provide. Users should remove secrets, tokens, private source code, and confidential repository details before submitting text or screenshots.

Privacy questions and data requests can be sent to support@git-brain-api.com. The full Privacy Policy describes the applicable data categories, purposes, retention terms, rights, and contact process and takes precedence over this summary.

• No showcase visitor identification; session replays are privacy-masked and retained for 30 days.
• No code, file content, diffs, or credentials in anonymous showcase telemetry.
• A direct support channel for privacy questions and requests.