Privacy policy
Last updated: 25 July 2026
The short version: Git on the Go runs on your device. There is no server on our side, no account with us, and nothing for us to collect — we could not see your work if we wanted to. The app talks to GitHub, and to whichever host your repositories live on, because that is where you put them.
What the app stores, and where
- Your repositories are cloned to your device. Working files live in the app's Documents folder, visible in the Files app; Git's own database lives in the app's private Application Support area. Deleting a repository in the app, or deleting the app, removes both.
- Your GitHub access token is stored in the iCloud Keychain. It never appears in files, logs, or a network request to anyone but the host it authenticates you to.
- That token syncs between your own devices. The Keychain item is marked synchronizable, so iCloud Keychain carries it to your other Apple devices — end-to-end encrypted against your device passcodes, which means Apple cannot read it and neither can we. Sign in on the iPad and the iPhone is signed in too. Nothing else about the app syncs: you clone repositories when you're ready.
- Settings — appearance, the app-lock preference, how often it checks for changes, your default branch name, and whether diffs highlight changed words — are stored on that device only.
Where the app connects
Three kinds of request leave the app, and nothing else does.
- Signing in and browsing repositories go to github.com and api.github.com. When you search for a repository, your search text is sent to GitHub — the same as typing it into their website.
- Git operations — clone, fetch, pull, push — go straight to the host that repository's remote points at. For a GitHub repository that is GitHub. If you clone from, or add a remote for, GitLab, Bitbucket or a server of your own, the app talks to that host instead. Either way it is a direct connection: nothing is proxied, mirrored or copied through anywhere on the way.
- Nothing else. No telemetry hosts, no analytics endpoints, no content delivery network, no update checks.
Sign-in
“Continue with GitHub” opens GitHub's own login page in a system authentication session. Your password or passkey is entered by you on GitHub, never in the app, and the app never sees it. What comes back is an OAuth access token.
That token carries GitHub's repo scope. It is a broad one — it covers reading and writing your private repositories — because GitHub does not offer a narrower scope that still allows pushing. We would use a smaller one if it existed. You can see exactly what the app is asking for on GitHub's authorisation screen before you approve it, and you can withdraw it at any time.
What is not collected
- No analytics, telemetry, or usage tracking of any kind.
- No crash-reporting SDKs or third-party frameworks that phone home.
- No advertising identifiers, no fingerprinting.
- No account with the developer — the app has no server side at all.
Revoking access
Sign out in the app at any time and the token is deleted from the Keychain. Because it syncs, deleting it removes it from your other devices too. Your repositories stay where they are — signing out is not a wipe.
You can also revoke the app's authorisation from your GitHub account settings (Settings → Applications), which invalidates the token immediately, everywhere, whether or not the app is running.
Changes to this policy
If a future version of the app changes any of the above — an opt-in crash reporter, say, or support for signing in to another host — this page will say so plainly before that version ships.
Contact
Questions about this policy can be raised with the developer through the support link on the app's App Store page.