weaver Download
  1. Weaver
  2. Privacy

Privacy policy

Weaver does not collect your data. It has no telemetry, analytics, advertising or crash reporting, and nothing you do in it is sent to its developer. Last updated 12 October 2026.

Who this covers

This policy covers the Weaver desktop app, including the version distributed through the Microsoft Store as "Weaver - Git Desktop Client", and this website. Weaver is developed by Keone Somers as an independent open-source project.

What stays on your computer

  • Your repositories. Weaver reads and changes the Git repositories you open in it. Their contents are never uploaded anywhere except to the Git remotes you push to.
  • Settings. Your repository list, theme and preferences are saved in a settings file on your computer.
  • Your GitHub token. If you sign in to GitHub, the access token is kept in your operating system's credential store (Windows Credential Manager, the macOS keychain or the Linux Secret Service). It is sent only to GitHub.

What Weaver sends, and to whom

Weaver only contacts other services to do what you ask of it.

  • Your Git remotes. Fetching, pulling, pushing and cloning exchange repository data with the servers you have configured, such as GitHub, GitLab or a server of your own. Git commits include the name and email address from your Git configuration.
  • GitHub, if you sign in. Signing in is optional. When you do, Weaver asks GitHub for your username and the list of repositories you can access, so it can show them to you. GitHub handles that information under its own privacy statement.
  • Version checks. About once a day Weaver asks a public GitHub address whether a newer version of Git is available, and builds with their own updater ask the same about Weaver. These requests carry no account or repository information, and can be turned off in Settings.

Like any internet request, these reveal your IP address to the service being contacted. Weaver's developer does not operate any of these services and receives none of this data.

Git, extensions and the Microsoft Store

Weaver runs the Git installed on your computer, along with any hooks, credential helpers and LFS filters you have set up. Extensions you choose to install run their own code. What those programs do is governed by their own authors, not by this policy. If you install Weaver from the Microsoft Store, Microsoft handles the download, updates and any Store statistics under the Microsoft Privacy Statement.

This website

This site uses no advertising or tracking cookies. If you pick a theme or accent colour, that choice is remembered in your browser's local storage and never leaves your device. The company hosting the site may keep standard server logs, such as IP addresses and requested pages.

To count visits, the site uses a self-hosted copy of Umami, an open-source analytics tool. It sets no cookies and builds no profile of you. It records the page viewed, the referring site, and your browser, operating system, device type and approximate country, in a form that cannot be tied back to you or followed across other websites. This applies to the website only: the Weaver app itself still sends no analytics.

Removing your data

Because nothing is collected, there is nothing held about you to request or delete. To remove what Weaver stored locally, sign out of GitHub in Weaver's settings, which deletes the token, and delete the settings folder (%APPDATA%\Weaver on Windows, ~/.config/Weaver on macOS and Linux). You can also revoke Weaver's access from your GitHub account settings at any time.

Changes and contact

If this policy changes, the new version will be published on this page with a new date. Questions are welcome on the project's issue tracker. Weaver's source code is public, so everything described here can be checked in the repository.