Last updated: June 22, 2026
Gitling is a Git client for Android. This policy explains what data Gitling handles and how.
Gitling contains no analytics, advertising, or tracking SDKs of any kind. It does not collect usage statistics, does not sell or share any data with third parties, and does not require an account to use its core features.
When you clone, pull, or push a repository, Gitling connects directly from your device to the Git host you specify (e.g. GitHub, GitLab, Bitbucket, or a self-hosted server) using the standard Git protocol over HTTPS or SSH. Gitling has no server of its own and never sees or stores this traffic anywhere except on your device.
If you save a username/password, personal access token, GitHub OAuth token, or an SSH private key passphrase in Gitling, it is encrypted using the Android Keystore and stored only on your device. It is never transmitted to Gitling's developer or any third party, except to the Git host itself when authenticating a Git operation you initiate.
Gitling's optional "Connect with GitHub" feature uses GitHub's OAuth Device Flow. Your GitHub credentials are entered directly on github.com, never inside Gitling. The resulting access token is stored encrypted on your device as described above.
If Gitling crashes, it may ask whether you'd like to send a crash report. If you agree, Gitling opens your device's email app with a pre-filled report (device model, Android version, and the crash details) addressed to the developer -- you must explicitly review and send it yourself. No crash data is collected or transmitted unless you choose to send that email.
Gitling requests INTERNET and ACCESS_NETWORK_STATE only, used solely to perform the Git operations you initiate. Gitling does not request storage, contacts, location, or any other device permission.
Questions about this policy can be sent to bmaneeshacooray@gmail.com, or filed as an issue on GitHub.