Privacy Policy

OpenCode Mobile ("the app") · Effective October 3, 2026

The app connects your phone to an OpenCode server that you run yourself. This policy explains what information the app handles and where it goes.

1. Information kept only on your device

Your servers' URLs, user names and passwords
Settings such as language and theme, today's free message count, and whether you bought "Remove ads"
Notification pairing keys

These are kept in the device's secure storage (the iOS Keychain, encrypted storage on Android) and are never sent to the developer.

2. Talking to your OpenCode server

Chats, attached images, files and terminal input and output go directly between the app and the server you chose. They never pass through the developer's servers, and the developer cannot see them.

To find servers on the same network, the app may browse the local network (mDNS). What it finds stays on your device.

3. Push notifications

When you turn notifications on, the app registers the following with a notification relay run by the developer on Cloudflare Workers:

Your device's notification token (issued by Firebase Cloud Messaging)
The platform (iOS or Android) and when it was registered
An authentication value derived from the pairing key (stored hashed)

What a notification says (project and session names) is encrypted so that only your device can read it; neither the relay nor the developer can. The relay only knows the kind of event (finished, failed, waiting for you, and so on).

The registration is deleted when you turn notifications off or remove the pairing in the app, or when the token stops being valid, for example after the app is uninstalled.

Notifications are delivered through Google's Firebase Cloud Messaging and, on iOS, Apple Push Notification service.

4. Ads

The app shows ads from Google AdMob. To show and measure ads, AdMob may collect your advertising ID (IDFA on iOS, the advertising ID on Android), IP address, device and app information, and how you view and tap ads.

In the European Economic Area, the UK and similar regions, the app asks for consent at launch with Google's tools. You can change your choice in Settings → Ad privacy choices.
On iOS, the IDFA is used only if you allow tracking.
After you buy "Remove ads", no ads are shown, and from the next launch the ad SDK is not started.

See How Google uses information from sites or apps that use our services for details.

5. In-app purchase

"Remove ads" is bought through the App Store or Google Play. Apple or Google handles payment details; the developer never receives them.

6. Crash reports

When the app crashes, it sends the following to Google's Firebase Crashlytics so the cause can be found:

The error and its stack trace
Device model, OS version, app version and device state such as free memory
An identifier Crashlytics creates for each installation of the app

Chats and server connection details are not included. Turn off Settings → Send crash reports to stop sending them.

7. Update check

At launch, the app asks the notification relay for the oldest version still supported. This request carries only what any internet request does (such as your IP address) and nothing that identifies you.

8. Sharing with others

Apart from processing by the service providers above (Google, Apple and Cloudflare), the developer does not share collected information with anyone, unless required by law.

9. Children

The app is a developer tool and is not directed at children under 13.

10. Changes to this policy

Changes will be announced on this page.

11. Contact

Send questions about this policy to support@opencodemobile.app.