Privacy policy
Last updated: 2026-10-19.
Summary
ForgeGo is a client for Forgejo, a Git forge that you or someone else hosts. It has no account system. It connects to the Forgejo, SSH and agent servers that you choose. Saved settings and credentials stay on your device; terminal commands run on your chosen SSH server. The one exception is instant notifications, an optional feature you turn on per server, which uses a push service run by devXY; it is described under Notifications.
Who is responsible
devXY, contactable at support@devXY.io, publishes ForgeGo.
What ForgeGo stores on your device
- The address of every Forgejo server you add, together with the personal access token for it, whether signing in created that token on the server or you pasted one yourself. Tokens are stored in the iOS keychain or the Android keystore, not in ordinary app storage.
- SSH profiles, including remote addresses, usernames, repository paths, passwords or private keys, and trusted host fingerprints, stored in platform secure storage.
- Agent server addresses and the access token for each, stored in the iOS keychain or the Android keystore.
- A local cache of the data fetched from those servers, such as repositories, issues, pull requests, notifications, and user profiles.
- Your app preferences, such as theme, accent colour, syntax highlighting theme, favourites, recent searches, and notification settings.
You can delete all of this at any time. Removing a server in the app deletes its token, its cached data, and its favourites from the device. Deleting an SSH profile removes its saved credentials. Trusted SSH host keys can be forgotten from the profile editor.
Signing in
Signing in opens the server’s own login page in a browser view embedded in the app, so the methods that server supports, including an external identity provider, work as they do in a browser. While that view is open it holds the cookies and local storage those pages set, exactly as a browser would. ForgeGo clears both when the view opens and again when it closes, and reads nothing out of the page except the access token the server displays, or the error message the server shows in its place. Your password, and anything else you type on those pages, goes to the server or the identity provider that asked for it; ForgeGo does not read it and does not store it.
What ForgeGo sends where
- Requests to the Forgejo servers you added, authenticated with the token you provided for that server. What those servers log is governed by their own operators and their own privacy policies.
- Terminal commands and input to the SSH server you select, over an encrypted SSH connection. Cloning a repository sends its clone URL to that server, where Git uses the server’s own credentials. Commands may contact other services according to what you run, and shell history and server logs are controlled by that server.
- When you send an issue or pull request to an agent, its content, the comments or checks the chosen action needs, and your prompt, directly to the agent server you connected. Nothing goes to devXY, and ForgeGo does not send your Forgejo token. The scanner that reads the pairing code runs on the device, and the camera is used for nothing else.
- Purchase and subscription requests, handled by the App Store or the Play Store and by RevenueCat, our subscription infrastructure provider.
ForgeGo does not send your repository content, issues, credentials, or server addresses to devXY, except what instant notifications need for the servers you turn them on for, as described under Notifications. SSH workspace access is sent only to the server you choose; Forgejo access tokens are not forwarded to it automatically.
Analytics and tracking
ForgeGo contains no analytics SDK, no advertising SDK, and no cross-app or cross-site tracking. It does not use the Advertising Identifier and does not ask for App Tracking Transparency permission. Nothing you do in the app is reported anywhere, with the single exception described under Subscriptions: which screen sent you to the subscription screen.
Notifications
By default, notifications are produced on your device. When you enable them, the app periodically asks your Forgejo servers for new notifications in the background and raises a local notification if there are any. No push service is involved, so notification content never leaves your device. Because the app has to poll rather than receive a push, your device decides when those checks run in the background, and notifications can be delayed or skipped.
Instant notifications
You can turn on instant notifications for each server separately, on iPhone and on Android. They are off until you turn them on, and turning them on asks you to confirm. For each server you turn them on for:
- The app asks that server for a new access token that can only read your notifications. It cannot read repositories, issues or comments, and cannot change anything. The token appears in your server’s token list, where you can revoke it at any time.
- The app sends that token, the server’s address, your device’s push token (from Apple on iPhone, from Google’s Firebase Cloud Messaging on Android), a random identifier for the server entry in the app, and your anonymous subscription identifier to ForgeGo’s push service, run by devXY. The token is stored encrypted.
- The push service asks that server for new notifications about once a minute. For each new one it sends the notification’s title, its repository name and its type to your device through Apple Push Notification service on iPhone, or Firebase Cloud Messaging on Android. It keeps the identifier and timestamp of each notification it has announced, so it does not announce one twice, but not its title or any other content.
- The subscription identifier is checked with RevenueCat, because instant notifications are part of ForgeGo Pro.
On Android the app contains Google’s Firebase Cloud Messaging library for this alone, with Firebase Analytics switched off; it contacts Google only once you turn instant notifications on for a server. Turning instant notifications off for a server, revoking its token on the server, or the subscription ending deletes everything the push service holds for that server. Uninstalling the app stops delivery, and the push service deletes the registration the next time Apple or Google reports that the device no longer accepts its pushes.
Subscriptions
ForgeGo Pro is an auto-renewing subscription sold through the App Store and the Play Store. Payment is processed by Apple or Google, who do not share your payment details with us. RevenueCat processes the purchase receipt and an anonymous subscriber identifier on our behalf so the app can tell whether your subscription is active. No name, email address, or Forgejo identity is attached to that identifier.
Opening the subscription screen also records which screen you opened it from, such as the unified mode toggle or the favourites limit, against that same anonymous identifier. That tells us which features people actually subscribe for. It is the name of a place in the app and nothing else: no Forgejo server, repository, or account of yours is part of it, and it is recorded only when you open the subscription screen yourself.
See the RevenueCat privacy policy at https://www.revenuecat.com/privacy for their handling of this data.
Children
ForgeGo is a developer tool and is not directed at children.
Your rights
Unless you turn on instant notifications, devXY holds no personal data about you, and there is nothing for us to export or erase on request. If you do, the push service holds what is listed under Instant notifications, and you can erase it yourself by turning them off, or ask us to at support@devXY.io. The rest of the data ForgeGo holds is on your device and under your control, and the data on a Forgejo server is under the control of that server’s operator. For questions about this policy, write to support@devXY.io.
Changes
Material changes to this policy will be published on this page with an updated date and, where they affect what ForgeGo stores or sends, noted in the release notes.