Safety & privacy

Understand Pushand's defaults, optional Git actions, production confirmations and network connections.

Your Git and access

push& (Pushand) uses Git already installed on your Mac, with your existing configuration and keys. Watching repositories reads their local state. Counts describe work against the last fetched state; they are not a live promise about the server.

Before a push or update, the app fetches the selected branch’s current server state and checks again. A normal push refuses a behind or diverged branch. A fast-forward update refuses divergence, uncommitted changes and ignored files that it would overwrite.

Defaults and optional actions

Pushing to an existing destination and fast-forward updates start on. Publishing a new branch asks first. Tags, rebase, remote branch deletion and history rewrite start off. Choose defaults and repository-specific exceptions only for actions you understand.

History rewrite checks for intervening server changes and requires the repository name. This check reduces the risk of overwriting someone else’s newer work; it does not make rewriting shared history consequence-free.

Pause before production

Mark a repository as production to require its name before every action. Its linked worktrees share that protection. Automatic cleanup skips production repositories.

The confirmation gives you a moment to check the repository and action. It cannot decide whether the change itself is right for production.

Review before discarding

Cleanup suggestions cover merged and pushed worktrees and branches. Review what will be removed. Automatic cleanup is opt-in and does not discard uncommitted or ignored files.

Discarding uncommitted work requires enabling the option, reviewing the listed files and typing the repository name. Confirmed deletion or discard cannot be undone by turning the setting off afterward.

App connections and website privacy

Git connects to your Git servers using your existing access. The app also makes update and licence checks. There is no in-app analytics or crash reporting. Website visit counting is separate from the app.

Read the approved privacy note for the details of these requests, website analytics and licence data. The licence agreement sets out the terms of use.

For practical help, open the Guide. You can also read how it works, compare plans or check the FAQ.