Account-scoped
Git server records and the API operations that use them are scoped to the currently authenticated Branch Manager user.
Security practices
Connections are private by design, not by accident.
Branch Manager treats a Git provider credential as a sensitive connection. It is scoped to your account, encrypted before persistence, and used only to make the provider request you initiated.
Connection safeguards
Four controls that keep the boundary clear.
These are implemented product behaviors, not a claim of certification or a substitute for your own Git-provider access controls.
Encrypted before storage
Personal access tokens are encrypted with authenticated AES-256-GCM before they are persisted in the application database.
Not returned to clients
The public application API does not return stored personal access tokens after a connection has been saved.
Safer host validation
Production connections require HTTPS, and private or reserved network targets are rejected by default.
Credential lifecycle
Use the smallest provider permission that does the job.
Branch Manager relies on the personal access token or credential you choose for each server. Your provider controls which repositories and organization actions that credential can access.
- Create a token with only the scopes necessary for the repositories and actions you intend to use.
- Keep the token private and revoke or rotate it with your Git provider if you believe it has been exposed.
- Remove a server connection from Branch Manager when you no longer want its encrypted credential record stored here.
- Delete your Branch Manager account to remove all saved server connections and their encrypted credential records from the application database.
Your provider stays in control.
Branch Manager sends requested repository actions to the Git provider you selected. Repository permissions, provider-side audit records, and provider retention remain under that provider’s controls.
Know what this does not promise.
No service or transmission method can be guaranteed completely secure. Branch Manager does not claim a security certification, and its controls complement rather than replace the security choices in your Git provider account.
Your data choices
Account deletion Need to remove a connection or your account?
You can remove individual server connections in the product. A signed-in user can also delete the Branch Manager account and saved connections from the public account-deletion flow.