No. GitPassword is a Windows desktop GUI app. Vault content is encrypted locally and stored in the Git repository you choose.
The vault workflow is based on your local app password and your Git repository credentials. A GitBraints website account is not required for storing readable vault content.
A Git provider can see encrypted vault objects and normal Git metadata such as commit times, branch names, object sizes, and repository access logs. It should not receive readable passwords, notes, or file contents from GitPassword.
Passwords, secure notes, and file contents are encrypted before they are written to the Git-backed vault. Some operational metadata remains visible through Git, including commit history and object sizes.
GitPassword does not keep a server-side plaintext copy of your vault. If the password and local recovery material are lost, the encrypted vault cannot be recovered by GitBraints.
GitPassword writes encrypted vault data into a local Git repository, then syncs with GitHub, GitLab, Bitbucket, self-hosted Git, or a local repository path you configure.
When multiple devices change the vault, GitPassword uses Git history and sync state to help you resolve conflicts and return to earlier encrypted vault versions when needed.
Windows is available on the Microsoft Store. The GitPassword download menu opens the Store listing.
Desktop downloads are available for Windows, macOS on Apple Silicon, and Linux. An Android APK is also available from the Download menu. iOS is still planned.
There is no GitBraints SaaS subscription for the vault—you use your own Git hosting. The Windows build is distributed through the Microsoft Store, which may be a paid purchase with a free trial. Check the Store listing for current pricing.