Gantry / Legal
Gantry
Privacy Policy
Last updated:
This policy explains how Gantry for Android (“Gantry”, “the app”) handles information. Gantry is developed by Sam Russell and published by Creative Spark Pty Ltd under the Sam Russell Tech name in Australia (“I”, “me”, “my”). It applies to the app and these Gantry web pages, not to GitHub or the Gitea or Forgejo instance you sign in to, or other services you choose to open.
1. Scope and website
This policy covers Gantry’s sign-in, repositories, files, issues, pull requests, wiki, Actions, notifications, notes, bookmarks and settings. It does not replace the privacy policy of the Gitea or Forgejo instance you sign in to, your email provider, Google Play, or any other service you choose to open. Your instance operator controls the server-side copy of your repositories and its own retention rules.
This website uses no advertising, analytics or tracking cookies. If you switch between light and dark mode, your browser saves only that site-theme preference locally on your device. As with most websites, hosting and network providers process standard connection details such as IP address, request time and requested URL to deliver the page.
2. Information Gantry processes on your phone
Gantry keeps its working data in the Android app sandbox. “On-device” below describes what the Gantry code does; it does not override your instance’s own copy of your repositories.
| Information | Why Gantry uses it | How Gantry stores it |
|---|---|---|
| Account tokens and Cloudflare Access service tokens | Authenticate to each GitHub, Gitea or Forgejo account you add, including instances behind a Cloudflare Access gateway. | EncryptedSharedPreferences backed by the Android Keystore (AES-256). The master key is device-bound and non-exportable, so this store is excluded from Android backup and device transfer. Tokens are never written in plain text. |
| Instance URLs and account labels | Remember which instances you have added and how to reach them. | Stored alongside the encrypted account record. |
| Appearance and behaviour preferences | Theme, accent colour, biometric lock, notification and landing preferences. | Local preferences on your device. |
| Bookmarks and personal notes | Keep shortcuts and notes alongside your work. | Local app storage on your device. They are not uploaded to your instance or to any Gantry server. |
| Image cache | Display avatars, repository images and file previews. | The app’s private cache folder. You can clear it, and it is removed when you uninstall the app. |
| Downloaded files | Save files you choose to download, such as release assets. | Written to the location you choose (see Permissions). Gantry does not upload them anywhere. |
| App lock | Gate the app with your fingerprint or face. | The lock preference is stored locally. Biometric matching is performed by Android; Gantry does not receive your biometric data. |
3. When Gantry connects to external services
3.1 GitHub and your Gitea or Forgejo instance
Gantry is a client for GitHub, Gitea and Forgejo. Repository, issue, pull request, wiki and Actions requests go to GitHub or the instance you sign in to, whether that is a server you run yourself, one your organisation runs, or a hosted provider. GitHub’s own privacy policy governs data you access on github.com; for a self-hosted instance, that operator’s privacy policy and terms govern the server-side copy, and its location and retention rules are its own.
All instance traffic uses HTTPS. Gantry sends your token (and, when configured, your Cloudflare Access service token) only to the instance you added. There is no Gantry server in the middle, and no analytics or crash reporting is sent to me.
3.2 Cloudflare Access
If your instance sits behind a Cloudflare Zero Trust gateway, you can add a Cloudflare Access service token. Gantry sends the service-token headers to your instance’s gateway so the request can pass. The token is stored encrypted like your account tokens. Cloudflare’s own privacy policy governs the gateway.
3.3 Notifications
Gantry can show local notifications for activity you care about. Notification content is fetched from your instance; it is not routed through a developer-operated push server. On Android 13 and later, showing notifications is a runtime permission you grant.
3.4 Support email
Suggestions and requests opens your chosen email app with a draft to samrusselltech.dev@gmail.com. The draft includes the app version, Android version and device model to make bug reports easier to understand. You can edit or remove those details before sending. Gantry does not transmit the message itself; your email provider sends it only when you choose to send it.
4. Permissions and special access
Android’s permission labels can be broad. Here is how Gantry uses each one:
| Permission or access | Purpose and boundary |
|---|---|
Internet (INTERNET) | Reach GitHub or your Gitea or Forgejo instance. All traffic uses HTTPS. |
Network state (ACCESS_NETWORK_STATE) | Check whether a connection is available before making requests. |
Biometrics (USE_BIOMETRIC) | Optional app lock. Android performs biometric matching; Gantry stores only the lock preference. |
Notifications (POST_NOTIFICATIONS) | Show local notifications for activity you care about. On Android 13 and later this is a runtime permission you grant. |
Storage (WRITE_EXTERNAL_STORAGE, older Android only) | Save files you choose to download, such as release assets, on Android versions that require it. Newer Android versions use the system file picker instead. |
Gantry does not request the camera, microphone, location or contacts.
5. Backups and exports
The encrypted credential store is device-bound: its Android Keystore master key cannot be exported, so tokens are excluded from Android backup and device transfer. If you move to a new phone, you sign in again. Non-encrypted preferences may be included in Android’s standard app backup depending on your device settings; they contain no tokens.
Files you download are saved to the location you choose and are outside Gantry’s storage afterwards. Treat any exported file according to its sensitivity.
6. Retention and deletion
On-device data stays until you remove it. Removing an account deletes its tokens and cached data. Uninstalling Gantry removes the app sandbox, including the credential store, preferences, bookmarks, notes and cache. Your instance keeps its own copy of your repositories under its operator’s retention rules; deleting the app does not delete anything on your instance.
7. Other services
Gantry itself integrates no advertising, analytics or crash-reporting SDKs. When you open a repository web link, a file, or the Google Play listing, the destination’s own privacy policy applies. Google Play processes your purchase under Google’s terms; I receive only the aggregate sales information Google provides and never your payment details.
8. Security
Tokens are encrypted at rest with the Android Keystore and sent only over HTTPS to the instance you added. No security measure is perfect: keep your device locked, use a token with the smallest scope you need, and revoke tokens you no longer use from your instance’s settings. If you believe you have found a security issue, please contact me below.
9. Children
Gantry is a developer tool and is not directed at children. It does not knowingly collect personal information from children.
10. Your choices and rights
You can remove any account, clear the image cache, turn off the biometric lock and notifications, and uninstall the app at any time. Because Gantry has no developer-operated server and no analytics, there is no account profile held by me to access or delete. Depending on where you live, you may have rights over personal information; the only personal information Gantry processes is on your device and on the instance you choose, so those rights are exercised there.
11. International processing
Your data goes to the instance you choose, wherever that instance is hosted. I am based in Australia. The instance operator’s location and laws govern the server-side copy.
12. Changes to this policy
If this policy changes, the “Last updated” date above will change and the new version will be posted here. Material changes will also be noted in the app’s release notes.
13. Contact
Questions or requests: samrusselltech.dev@gmail.com. Post: Creative Spark Pty Ltd, Randwick NSW, Australia.