The short version
- There is no RepoBeam account.
- RepoBeam contains no telemetry, analytics or crash reporting.
- RepoBeam doesn’t upload your repositories, code or history. There are no RepoBeam servers that receive them.
- Apart from Git talking to your remotes, the only requests the app makes on its own are update checks with GitHub.
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.
- 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 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
repobeam.com uses no cookies and no analytics or tracking scripts. It is hosted on Netlify, which processes standard request data, such as IP addresses, to deliver the site. 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.
Questions
If anything here is unclear, open an issue on GitHub.
Last updated 13 September 2026.