Privacy Policy
Pocket Agent ("the app") · Effective October 3, 2026 · Updated October 8, 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.
1Information 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.
2Talking 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.
Conversation mode and read-aloud use the speech recognition and text-to-speech built into your device's operating system. Depending on the system, your speech may be processed by the OS provider's service (such as Apple or Google). The app does not keep recordings and never sends audio to the developer. The recognized text goes only to your server, like any chat message.
3Push 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.
4Ads
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 (used to estimate your approximate region), 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.
5In-app purchase
"Remove ads" is bought through the App Store or Google Play. Apple or Google handles payment details; the developer never receives them.
6Crash 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.
7Usage statistics
To improve the app, it collects usage statistics with Google's Firebase Analytics. It sends:
- When the app was installed and opened, and for how long it was used
- Which kinds of screens were opened (such as Settings or Chat; never project or session names or IDs)
- Device model, OS version, app version, language, and an approximate region estimated from the IP address
- An identifier Firebase Analytics creates for each installation of the app
The advertising ID (IDFA on iOS, the advertising ID on Android) and the IDFV are not used, and the statistics are not used for ads or tracking. Chats and server connection details are not included. The developer sees only aggregated numbers that do not identify you.
The app also records how its screens are used with Microsoft Clarity, to find screens that are hard to use. It sends:
- The layout of each screen and taps, scrolls and other gestures
- Which kinds of screens were opened (as above, never project or session names or IDs)
- Device model, OS version, app version, and an approximate region estimated from the IP address
- An identifier Clarity creates for each installation of the app
All text and images are hidden in these recordings on every screen except the app's settings. Chats, code, terminal output, server URLs and passwords, and anything you type are never recorded. The advertising ID is not used, and the recordings are not used for ads or tracking.
Turn off Settings → Send usage statistics to stop sending to both Firebase Analytics and Microsoft Clarity.
8Update 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.
9Sharing with others
Apart from processing by the service providers above (Google, Apple, Cloudflare and Microsoft), the developer does not share collected information with anyone, unless required by law.
- Google Privacy Policy (AdMob, Firebase)
- Apple Privacy Policy
- Cloudflare Privacy Policy
- Microsoft Privacy Statement (Clarity)
10Children
The app is a developer tool and is not directed at children under 13.
11Changes to this policy
Changes will be announced on this page.
12Website analytics
This website (opencodemobile.app) uses Cloudflare Web Analytics to learn which pages are read. It sets no cookies, stores nothing on your device and does not create any identifier for visitors. It collects the page URL, the page you came from, your browser and OS type, your country estimated from your IP address, and how fast the page loaded; the developer sees only totals. Cloudflare does not use this information for ads (Cloudflare Privacy Policy).
The website also uses Microsoft Clarity to learn which parts of a page are read and where visitors leave. Clarity uses cookies and sends Microsoft:
- The pages you open, and your clicks, scrolling and mouse movement (used to replay how a page was used and to count where people click)
- Your browser, OS, screen size and an approximate region estimated from your IP address
- An identifier Clarity creates for each browser
The website has no input fields, so Clarity never receives anything you type. The developer does not use this for ads or tracking. You can delete or block Clarity's cookies in your browser settings (Microsoft Privacy Statement).
13Contact
Send questions about this policy to [email protected].