runhmd is the phone companion for hmd (Heimdall), a coding-session tool that runs on your own computer. The app has no backend of its own. We do not run any server that receives your data, so we do not collect, store, sell or share your personal data. One optional feature uses third-party delivery services: notifications, if you turn them on (see “Notifications”).
Effective date: 2026-10-05 · Last updated: 2026-10-05
runhmd (iOS and Android, app id dev.runheimdall.hmd)
Mewt Account Private Limited
There is no sign-up or sign-in. The app has no user identity of any kind.
Pairing. You scan or paste a QR code or pairing text from your own hmd session. It is read on your phone and used only to connect to the address it names (your own computer, directly or through a relay). The session credentials the app keeps are stored in the iOS Keychain or Android Keystore-backed secure storage, never in plain app storage, and are deleted when you forget the session or uninstall the app.
Session data and chat. Session status, gates, panels and the messages you send travel only between your phone and your own computer. When you use the relay, this content is end-to-end encrypted on your devices. The relay is a message-forwarding service deployed by the operator of your hmd, not by us, and sees only encrypted data.
Camera and photos. The camera is used only when you open the Pair screen to scan a QR code, or when you tap “attach” and choose “Take photo”. QR scanning happens on your phone; no frame is saved or sent. If you attach a photo (from the camera or by choosing one in the system picker), the app re-encodes it on your phone and strips its EXIF/GPS and other metadata before anything leaves the phone. It is sent only when you tap send, end-to-end encrypted to your own computer. The app never asks for access to your whole photo library, and never asks for the microphone.
Face ID, Touch ID and passcode. The app asks your operating system to check you before consequential actions. The operating system does the check; the app learns only whether it passed, and never receives biometric data.
Receipt share card. The Share action draws a card on your phone from a short list of counts (verdict, gates passed, agents, files changed, test time) and hands it to the system share sheet. The app uploads nothing.
Notifications are off by default and the system permission prompt appears only after you tap “Turn on” for a session. When on:
The app asks Expo's push service for a push token. That request carries your phone's platform push token, the app id, the app's project id and an installation id generated for this app. The token is kept in memory only.
The app sends the token to your own hmd, inside the end-to-end encrypted channel. Your hmd, not the app and not us, writes and sends each notification.
A notification passes through Expo's push service to Apple (APNs) or Google (Firebase Cloud Messaging) for delivery. These services can see its title and body, which are short summaries built by your hmd from a fixed list (session label, event type, counts, a scrubbed question summary). They never contain code, file paths, URLs, command text, chat text or tokens. Expo, Apple and Google handle push tokens and delivery records under their own privacy policies.
Use the session's switch in Profile, the system notification settings, or forget the session. Uninstalling the app invalidates the token.
On Android, the notification library includes Google's Firebase Cloud Messaging client for delivery only. The app includes no Firebase Analytics, Crashlytics or other Firebase product.
The app keeps the latest error as one redacted record (error name, a short message, a few code locations; URLs, tokens, keys and codes removed) in secure storage on your phone. It leaves the phone only if you tap “Copy diagnostics” in Profile and paste it somewhere yourself. Note that the system clipboard is shared by the operating system: other apps, clipboard managers and clipboard sync between your devices may be able to read it.
We hold nothing about you on any server, so there is nothing for us to delete. On your phone, forgetting a session deletes its credentials immediately; uninstalling the app removes everything it stored. Turning off notifications for a session, or forgetting it while connected, asks your hmd to delete its record of your push token; your hmd also deletes it after 7 days without contact. Expo, Apple and Google keep push data under their own policies.
The app is a developer tool, is not directed at children, and collects no personal data from anyone of any age.
If what the app does with data changes, this page will be updated before the change ships.