Privacy Policy
How OpenCode Mobile — Unofficial handles data. Last updated: 23 August 2026.
This is an unofficial third-party client for opencode. It is not published by the opencode project. This page covers the iOS and Android apps only — not your opencode server, and not the opencode project.
Snapshot
| Kind | Where it lives | When |
|---|---|---|
| Connection password | Device only (iOS Keychain / Android Keystore-backed storage) | Always |
| Host, username, profile names | Device only (ordinary local storage) | Always |
| Session cache, drafts, themes, diagnostic log buffer | Device only | Always |
| Prompts, messages, files | The opencode server you configured, plus on-device cache copies | Always |
| Crash reports and automatic diagnostics | Google Firebase, release builds | Always on release builds. No in-app switch. |
| Product usage events | Google Firebase, release builds | On by default. Turn off in Settings → Privacy. Clear All Data turns it back on. |
| Advertising ID / ads | Not used | — |
Who we are
Ivan Fenenko publishes OpenCode Mobile — Unofficial as an independent client. The apps have no account system and do not relay traffic to your opencode server.
On this device
Connection passwords stay in iOS Keychain or Android Keystore-backed storage. Host, username, display name, and related profile fields stay in ordinary on-device storage.
The apps also keep session and message cache, unsent composer drafts, theme and display preferences, and a rolling diagnostic log buffer on the device. Diagnostic Logs in Settings are a share-sheet export. They are not uploaded automatically. Redaction is heuristic, not a guarantee.
Settings → Clear All Data removes this local data and resets the product-usage switch to on.
Your server
Prompts, messages, attachments, and project content you send through the app go to the opencode server you configured. That traffic and any server-side logging are outside this policy. Delete that content on the server.
Sent to us
Release builds include Firebase Crashlytics and Firebase Analytics. Debug builds do not include this Firebase runtime and send nothing to us.
Crash reports and automatic diagnostics have no extra switch. They can include device and OS information, app version, crash stack traces, Firebase installation / app-instance identifiers, and automatic lifecycle events such as first open and session start. Automatic screen / page-view reporting is disabled. Advertising ID is not collected for ads or ad personalization. That is not the same as “no device identifiers.”
Product usage events are optional and on by
default. When the Settings → Privacy switch is on, release builds
may send product_screen_view and
product_user_action. Parameters are short enum IDs
(screen, action, presentation, trigger, outcome, and similar
flags). Connection-edit events are IDs such as “edited password,”
not the URL or password itself. These events do not include
prompts, file contents, or credential values. Turn the switch off
and those events do not fire. Crash reporting stays on.
Why
To keep the apps working, find crashes, and see which screens or actions fail. Not for advertising. Data is not sold.
Who processes it
Crash and product-usage data is sent to Google Firebase (Crashlytics and Analytics) so those services can run. Google may process that data on servers outside your country. There is no other recipient and no sale of data.
How long
Developer-held diagnostics follow the Firebase project defaults. There is no separate user database.
Your choices
- Settings → Privacy → Product Analytics turns optional usage events off or on. The switch starts on. Crash reporting does not change.
- Settings → Clear All Data removes local app data and turns Product Analytics back on.
- Settings → Diagnostic Logs lets you share a local log window. Nothing is sent until you share it.
Deletion
The apps have no accounts. There is no user ID to look up. Email digitalpotatoapps@gmail.com with the subject “OpenCode Mobile data deletion” and whatever you can share: app version, OS, approximate crash time, and a Firebase installation ID if you have one. Identifiable diagnostics we control will be deleted. A complete wipe is not guaranteed.
Content on your opencode server is outside this process. Delete it there.
Children
The apps are for people 18 and over and are not directed at children.
Changes
The date at the top moves when these practices change.
Contact
Questions about this policy: digitalpotatoapps@gmail.com