This policy covers the Muqun mobile app and website. Muqun connects to a Gateway you control. There is no Muqun account, advertising, or advertising tracking. Optional AI and voice services process data as described below.
Data on your device
Muqun stores Gateway names, addresses, pairing details and credentials; SSH connection details and credentials if configured; preferences and quick commands; agent and project information, session lists and task records; themes, fonts and downloaded assets. Conversation and terminal content is also held in memory while you use it. Selected files, images and recordings can create temporary local copies.
Gateway and SSH credentials are encrypted in the operating system’s secure credential storage. Voice settings, including the API key, also use secure credential storage. These entries use device-only accessibility on iOS. Other preferences, records and files use ordinary app storage; their backup behavior depends on the operating system. They are not all protected or deleted in the same way as credentials.
Your Gateway, agents and AI providers
Terminal and agent connections go to the Gateway you pair, without an Osuki relay. The Gateway receives the credentials, workspace and session identifiers, commands, prompts, attachments and other content needed for your actions, and returns terminal output, conversations and tool results. If you use SSH, the configured SSH host also handles that connection.
An agent running on your computer may send your prompts, files, code, conversation context and tool results to its configured AI model provider or other connected services. The recipients depend on your Gateway and agent configuration; the agent software is not necessarily the final provider. Review those services’ privacy and retention terms before sharing personal or confidential information. Use HTTPS or a trusted encrypted private network such as Tailscale; HTTP alone does not encrypt traffic.
Pairing sends your device name and a locally generated installation identifier to the Gateway. When Gateway transport encryption is enabled, pairing establishes device-specific keys that protect supported app-to-Gateway requests and responses; the Gateway can still read the content. Gateway owners can disable this encryption, and older pairings may lack it. It does not protect onward connections to AI or voice services. In manual address pairing, the submitted pairing code itself is not protected by that code-based encryption, so use HTTPS or a trusted encrypted connection such as SSH or Tailscale.
Where supported, opening agent account details or refreshing account limits asks the Gateway for a usage snapshot from the agent account configured on your computer. The app displays reported usage, limits, reset times, plan or credit information; it does not request the provider’s login credentials for this feature. These are account-wide snapshots, which may be temporarily cached by the Gateway, rather than a complete billing record.
Camera, photos and files
When you scan a pairing QR code, camera frames are processed on your device and are not saved or uploaded. You can enter a Gateway address manually instead.
Taking an attachment photo or choosing photos or files is different: Muqun starts uploading the selected items to the chosen Gateway after selection, before you send the message. File contents and details such as names and types are included. Removing an attachment from the draft does not recall an upload that has already reached the Gateway. Sending the message makes the attachment available to the agent, which may pass it to its configured providers.
Viewing conversation images can fetch thumbnails, previews or originals from your Gateway. Opening an image or saving it may download the original, depending on Gateway support; selected upload images may also be resized before upload. Displayed or decrypted images can be kept in memory, image caches or temporary local files, so transport encryption does not mean there is no local image copy. Saving to Photos, Files or a sharing destination creates a separate copy outside the app’s cache, which you must manage there.
Optional voice transcription
Audio is sent only when you configure a transcription service in Settings and actively use voice input with microphone permission. The built-in presets point to OpenAI; you can choose a compatible custom service. In file mode, a temporary recording is sent directly to that service when you finish recording. In realtime mode, audio is streamed directly to the service while recording. The request also includes the configured model, language and API key where applicable. This connection does not pass through your Gateway or an Osuki relay.
The returned transcript goes into your draft for editing before you send it. Audio has already been shared with the transcription service at that point. Cancelling stops further recording and requests but cannot recall audio already transmitted. Muqun attempts to delete the temporary recording when the session finishes or is cancelled; interrupted cleanup can leave a local copy. You can stop using voice input, remove its configuration in Settings, or revoke microphone permission in system settings. Provider retention and deletion follow the service’s terms.
App Lock
With App Lock enabled, your operating system performs biometric or passcode authentication. Muqun receives the result, not your biometric data or passcode.
Optional notifications
When notifications are enabled, Muqun registers an Expo push token and sends it, your device name, platform and language to your Gateway. Delivery uses Expo and Apple or Google push services, which process the token, notification content and delivery metadata. Content depends on notifications generated by the Gateway and may include workspace or task information. Turning notifications off attempts to unregister the token from the Gateway and disables the app’s push registration; an unreachable Gateway may retain its record. You can also disable notifications in system settings.
Updates, themes and website requests
App builds with online updates enabled contact updates.muqun.dev to check for and download updates and release notes. Requests include technical information such as platform, update channel, build compatibility and release identifiers; release-note requests include your selected language. The compatibility identifier describes the app build, not a biometric fingerprint. Cloudflare hosts this infrastructure and the website and can process IP addresses and request metadata needed to serve them.
Browsing or importing online themes and other remote assets contacts muqun.dev, GitHub or the source you choose. Those hosts receive the requested address and ordinary connection metadata. Downloaded themes and assets are stored locally. The website stores your appearance preference in your browser’s local storage; you can clear it with browser site data. These service requests are separate from your terminal and agent connections.
Retention, deletion and your choices
Remove saved Gateways and SSH hosts in the app and clear voice configuration to remove their saved connection records. Settings → Storage can clear supported image caches and temporary copies; it does not erase all app data, agent records, credentials or installed themes. Themes can be managed in the theme library. Local preferences and records remain until changed or removed through the relevant feature or app-data controls. Do not rely on uninstalling alone to remove iOS secure credential entries.
Removing a local record, clearing a cache or uninstalling Muqun does not delete data from your Gateway, agent, AI provider, transcription service or notification provider. Supported session deletion requests are sent to the Gateway; this is not a guarantee that providers or backups are erased. Manage remote files, histories and device access with the Gateway operator and request provider deletion under their policies. Revoke Gateway access tokens or third-party API keys at their source to invalidate them. Muqun does not set or guarantee those services’ retention periods.
Support, changes and contact
If you contact Osuki for support, we use the information you provide to respond. Avoid sending access tokens, private code or unredacted logs. We may revise this policy when features or services change; the revision date appears above. For privacy questions, contact us at: hello@muqun.dev