Who this covers

Munk AI is a local-first developer workbench. Most coding and verification work runs on your own computer. Cloud features on munk.sh exist to support account sign-in, device pairing, remote access tickets, membership, and related product operations.

The iPhone app is a pairing client only: it pairs with your desktop instance and opens your workbench UI in the system Safari View Controller. It does not install or run dynamic app bundles.

Information we collect

Account and identity (website / desktop Cloud sign-in): email address and authentication identifiers provided by our auth provider when you create or sign in to a Munk AI Cloud account.

Device pairing (mobile host apps): when you scan a pairing QR or redeem a pairing link, we process a device identifier generated on the phone, an optional device display name (for example “Tao’s iPhone”), cryptographic public-key material used for device authentication, and association with the Cloud account / desktop instance that issued the pair challenge. Pairing private keys stay on the device (Secure Enclave on iPhone; Android Keystore where available).

Product interaction for pairing and remote access: pair, open-workbench ticket, and revoke/unbind events needed to operate the pairing and Remote UI flows on munk.sh.

Operational logs: standard server logs (such as timestamps, request paths, and IP addresses) for security, reliability, and abuse prevention.

Camera: the mobile apps may use the camera only to scan pairing QR codes on device. Camera frames are not uploaded to our servers.

We do not sell personal information. We do not use App Tracking Transparency tracking, advertising identifiers for cross-app advertising, or third-party ad networks in the iPhone app.

How we use information

Provide and secure Cloud accounts, desktop Cloud binding, and membership features.

Complete device pairing, issue short-lived Remote UI tickets, list and revoke paired devices, and show device labels in the product UI.

Operate, monitor, and improve reliability and security of munk.sh services.

Communicate about account, security, or product-critical notices when needed.

Where information is processed

Website and API services run on our cloud infrastructure (including Cloudflare and related providers used to host munk.sh).

Desktop and local workspaces remain on your machine unless you explicitly use Cloud or remote features that send data to our servers.

Remote UI content opened after pairing is loaded over HTTPS from hosts under munk.sh and displayed in the system browser view on the phone.

Retention and deletion

Account information is retained while your account remains active.

Paired-device records are retained until you unbind on the phone, revoke the device on the website, or otherwise remove the association. You can revoke devices at https://www.munk.sh/remote/instances after signing in.

Operational logs are retained for a limited period needed for security and operations, then deleted or aggregated.

Sharing

We share information with service providers that help us run authentication, hosting, email, and infrastructure, only as needed to provide the product.

We may disclose information if required by law or to protect the security of users and the service.

We do not sell personal information.

Children

Munk AI is intended for developers and professional users. It is not directed to children under 13, and we do not knowingly collect personal information from children under 13.

Your choices

Unbind a phone from Workbench in the mobile app, or revoke it from the website device list.

Sign out of Cloud on the desktop / website and request account deletion by contacting us.

Deny camera permission; you can still paste a pairing link instead of scanning.

Contact

Questions about this policy: support@munk.sh

Website: https://www.munk.sh

Changes

We may update this Privacy Policy as the product evolves. The “Last updated” date at the top will change when we do. Continued use of the services after an update means you acknowledge the revised policy.