Version: 2026-10-15.1
Effective date: 2026-10-15
Who maintains PocketWork
Salty Panda LLC maintains PocketWork, an independent iPhone and iPad companion for OpenCode v2. Contact support@saltypanda.com. This policy covers the OpenCode client.
Your connection and its scope
PocketWork sends requests directly to the OpenCode HTTPS address you review when pairing. Built-in pairing exchanges a short-lived, single-use code for a saved server credential. The tested OpenCode version uses a server-wide credential: pairing can access that server's projects, chats, configured model information and supported file operations. Hiding projects in PocketWork changes only this device's lists; it does not restrict the credential. Tool approvals and chat rules are separate server controls. Only pair a server you are authorized to access.
Network routing
OpenCode's built-in remote access can route the connection through OpenTunnel to your computer. PocketWork validates HTTPS using the system trust store and does not add a developer-operated relay. The reviewed OpenTunnel client terminates the public TLS connection on the computer before forwarding to its local OpenCode service. This does not establish the tunnel operator's metadata logging or retention. The operator can handle connection metadata, such as addresses, hostnames, timing and traffic volume. OpenCode, OpenTunnel and any other hosting or network services you choose have their own practices. PocketWork does not require a separate Tailscale app.
Chats, files and AI services
Messages, question answers, selected skills, photos and documents go to the paired OpenCode server. OpenCode can send them, relevant conversation history, project context and tool results to configured AI providers and other services used by its tools or plugins. Reading chats, model configuration, skills, files and changes also brings that data to this device for display. Provider configuration returned by the server may include sensitive settings. PocketWork does not intentionally log or persist raw provider headers or settings in its sharing-permission records.
Before a new send or attachment preparation, PocketWork checks the server-reported provider configuration and asks you to review the data types being shared. New reported configuration or data types require review again. PocketWork cannot verify the final provider destination: server credentials, environment settings, plugins or a later configuration change may affect routing. The review explains this and requires your deliberate permission to proceed with that uncertainty. Giving permission does not send or upload automatically; you retry the action. This control does not stop work already running on the computer or replace OpenCode's tool permissions. Providers and configured services apply their own retention and use terms.
Photos, documents and results
System Photos and Files pickers share only the items you select with this app. Selected photos are converted to PNG, resized and saved without the original camera or location metadata; your original is unchanged. Other documents retain their contents and may contain metadata. Filenames and transfer details travel with files. Some supported documents are staged on the computer during attachment preparation, before you send the message. Removing the selection or resetting PocketWork does not remove those host copies. Manage them in OpenCode or on the computer. Downloading a result creates a protected local copy. Sharing or copying content sends it to the app or clipboard you choose, outside PocketWork's local reset controls.
What stays on this device
The server credential is stored in this device's Keychain, available while unlocked and not migrated to another device. Protected app storage, excluded from backups, keeps drafts, selected attachment copies, question answers, selected skills, unfinished-action records, local groups, project visibility, new-chat defaults, the last selection and sharing-permission records. An unfinished record may contain submitted text, filenames and delivery details needed to avoid repeating an uncertain action. Earlier OpenWork credentials and recoverable drafts remain in their separate namespace until removed. Appearance and compact Activity preferences use system preferences. PocketWork does not save chat history as a separate transcript database. Displayed history, file lists, searches and diffs are held in memory; selected or downloaded content has the local copies described here. Protection depends on the device and its lock state; it is not a promise against every form of device compromise.
Retention and removal
Drafts, selected files, local preferences and unfinished records can remain until resolved or explicitly removed. Download and preview cleanup removes expired copies when it runs; it is not an immediate secure-erasure guarantee. Data Controls offers text-only draft clearing, downloaded-copy removal, sharing-permission clearing and full local reset. Text-only clearing keeps selected files and uncertain action records. Clearing sharing permission requires review again and stops local work, but cannot undo a request already dispatched. Full reset removes both saved credential namespaces, recognized local drafts, selected files, downloads, consent, groups, defaults and appearance/Activity preferences. Partial Keychain or file failures are reported for retry; unknown files are preserved and reported.
Forget this computer removes the saved connection on this device and keeps drafts. Local Forget or reset does not revoke the credential on the server, stop a remote task, or delete server chats, original files or staged uploads. The tested OpenCode version has no individual-device revocation endpoint. Use its server password controls to invalidate existing credentials for all paired devices. Provider-held data, support requests, shared copies and clipboard contents must be managed with their respective services or apps.
Permissions, diagnostics and other services
Camera access is requested only for scanning a pairing code; pasting a link needs no camera permission. PocketWork does not request broad photo-library access. No advertising, analytics or third-party crash-reporting SDK is bundled. Opt-in development timing diagnostics use static labels and do not intentionally record chat text, tokens or private paths. Apple may handle App Store or TestFlight diagnostics under its own settings and terms. GitHub Pages hosts the public information site. Opening it, GitHub Issues, Apple's EULA or another external destination contacts that service under its own policies.
Support, changes and contact
Email support@saltypanda.com or use https://github.com/BitL8-ByteShort/openwork-remote-ios/issues. GitHub Issues are public: leave out pairing links, credentials, private chats and personal files. Use the repository's private vulnerability-reporting option for a security concern. Information you choose to send for support is handled through the email or GitHub service and may be retained to address the request. Contact us about that information; deleting local app data does not delete a support conversation. The app includes this policy offline. The current public policy is at https://bitl8-byteshort.github.io/openwork-remote-ios/privacy/. We update its version and date when practices change.
Salty Panda LLC. support@saltypanda.com. Support on GitHub. Issues are public; leave out private information.