The short version
- There is no RepoBeam account.
- Anonymous usage analytics are on by default on a fresh installation and explained in a first-run notice.
- RepoBeam doesn’t upload your repositories, source code, files or Git history.
- You can change the analytics choice at any time under Settings → Privacy.
Anonymous analytics
Anonymous analytics are enabled by default on a fresh installation. RepoBeam shows a first-run notice and provides a permanent control under Settings → Privacy. While enabled, RepoBeam creates a random installation ID and sends cumulative daily counters to https://repobeam-telemetry.repobeam.workers.dev/api/v1/events. The ID is not attached to your name, email address, GitHub account or a RepoBeam account. It lets RepoBeam count launches, active days and returning installations without trying to identify you.
Each daily snapshot can contain only:
- The random installation ID and the date it was created.
- RepoBeam’s version, Windows or Linux, and the install source: Windows installer, Microsoft Store, .deb, AppImage or Snap.
- The UTC day and cumulative counts for app starts, repository opens, commits, pushes, pulls, conflict resolver opens, history previews, Coding Sessions and stash actions.
- The cumulative count of focused-use periods and their total duration in seconds.
RepoBeam never includes repository names or paths, source code, file names or contents, diffs, commit messages, branch or tag names, remote URLs, GitHub usernames, Git names or email addresses, SSH data, credentials or tokens. There is no crash reporting.
The telemetry service is hosted on Cloudflare Workers and stores only the hashed installation ID and aggregated daily counters in Cloudflare D1. Like any web host, Cloudflare necessarily processes the IP address and basic request details to deliver the request, under its own privacy terms. RepoBeam does not store the IP address, location or user agent. There is no raw event-history table. Daily aggregates are removed after 400 days.
Turning analytics off stops future uploads immediately and removes the random ID and local counters from your computer. Aggregates already received remain anonymous and follow the retention period above. Turning analytics on again creates a new ID.
Git and your remotes
When you clone, fetch, pull or push, RepoBeam runs Git: the copy installed on your computer, or the copy included in the snap. Git connects to the remotes configured in your repository — such as GitHub, GitLab or your own server — using your SSH keys and credentials. RepoBeam doesn’t store your passwords or keys. The services behind your remotes handle that data under their own privacy policies.
Update checks
RepoBeam looks for new versions by reading the public release list at github.com/ferchichibaha7/repobeam-releases, and downloads an update from there only when you choose to install it. As with any web request, GitHub receives your IP address and basic request details. Nothing about your repositories is sent.
What stays on your computer
- Your recently opened repositories and app preferences, such as the theme and analytics choice.
- Your optional profile photo.
- Your Git name and email, saved in your Git configuration for all repositories or just one, depending on the scope you choose.
- Coding Session restore points and records, and recovery points, stored inside each repository’s
.gitfolder. Normal Git operations don’t push them.
Links you open
Links such as release notes open in your default browser.
This website
Pages on repobeam.com use no cookies. The site uses Cloudflare Web Analytics, which counts page views and basic visit information — the page, the referring site, country, browser and device type — without cookies and without following you across other sites. Its script is loaded from static.cloudflareinsights.com and the measurements go to Cloudflare. The site is hosted on Netlify, which processes standard request data, such as IP addresses, to deliver it. To show the newest version and download links, the page asks the GitHub API for the latest RepoBeam release and keeps the answer in your browser’s local storage for six hours. The separate Cloudflare telemetry endpoint described above receives daily snapshots only while an app installation has anonymous analytics enabled.
Questions
If anything here is unclear, or you have a privacy request, email bahaferchichi@repobeam.com.
Last updated 20 September 2026.