Privacy policy

The relay is an optional tunnel service that lets your phone reach your own server from outside your network. It requires an email sign-in — a free account is created on first sign-in — and devices are connected through explicit pairing.

Traffic between the app and your machine is encrypted in transit with TLS. The relay does not store prompts, code, diffs or terminal output; content is processed in memory only while a request is in flight. Your opencode password is injected locally by the relay client and never reaches the relay.

We process the metadata required to run the tunnel and the account safely: your email address, device pairing records, connection timestamps, byte counts and subscription status. The free tier includes one connection slot and 512 MB of traffic per month; paid plans add more traffic and concurrent connections.

Pairing credentials are issued per device and can be revoked at any time in the app. Revoking a credential closes that device's tunnel immediately. You can request deletion of your relay account and its data by emailing our support address.

Connection profiles: the server address, username, target directory and a label you choose. Passwords and pairing credentials are stored separately from the profile data, using the platform secure storage (iOS Keychain, Android Keystore).

Local cache: sessions and chat messages are persisted on your device so the timeline survives restarts and flaky networks. You can clear this at any time from the app or by removing the app.

Settings: theme, language and notification preferences are stored locally on your device.

Relay account: email address, subscription status, device pairing records and monthly traffic counters. Payment transactions are handled by the app stores or the payment channel; we receive subscription status and a channel reference, never your card details.

Relay client on your computer: your opencode address, username and password are stored in a local config file readable only by your user account. They are never uploaded.

When an analytics key is present in the build, the app sends anonymous product events (for example: app opened, connection created, session started) to PostHog. These events never include prompts, code, file contents, credentials or server addresses.

If no analytics key is compiled in, no analytics requests are made at all. Development and self-built binaries default to no analytics.

Your configured opencode server: receives your prompts and returns sessions, events and file contents. It is operated by you or your organization, not by us.

opencode relay (optional): carries TLS-encrypted traffic between your devices as described above and stores account and traffic metadata. It is operated by us and never stores your content.

App stores and payment channels (optional): process relay subscriptions and report the subscription status back to us.

Email delivery (optional): sends relay sign-in codes to the address you provide.

Analytics provider (optional, build-time): receives anonymous event names and platform metadata as described above.

No advertising SDKs, no tracking pixels, no data brokers.

Authentication to your server uses HTTP Basic auth over the transport you configure. We strongly recommend exposing the server over HTTPS through a reverse proxy, VPN or the relay rather than plain HTTP on the public internet.

Relay tunnels are carried over TLS with per-device pairing credentials that can be revoked. Credentials are isolated in platform secure storage and are deliberately excluded from logs and crash reports.

Relay account data is kept while your account is active. Traffic counters are retained for billing and abuse prevention. Sign-in codes and pairing records are deleted after they expire, within 24 hours. Prompts, code, diffs and terminal output are never stored, so there is no content to retain.

Depending on where you live, you may have rights to access, correct or delete personal data we hold about your relay account. Email our support address to make a request. Direct connections involve no account, so there is nothing server-side to delete there; deleting the app removes the data stored on your device.

opencode mobile is a developer tool and is not directed at children under 13. We do not knowingly collect personal information from children.

If this policy changes, the updated version will be published on this page with a new revision date. Material changes will also be noted in the changelog.