bmuxPrivacy
Updated 24 October 2026.
Account and sign-in
Google sign-in supplies your account identifier, verified email and name. bmux stores those details, hashed login tokens, service-key hashes, public device keys and access grants to authenticate you and connect authorized viewers. Login tokens expire after 30 days.
Remote access
The connection service handles host identifiers, runtime generations, session names, pane identifiers and titles, presence, permissions and live-view permits. Video, page URLs, full session state and input travel through the WebRTC connection. TURN may carry encrypted WebRTC traffic when a direct connection is unavailable. The web viewer and relay identify authorized participants.
Rented machines
Your chosen Hetzner region hosts the box, its browser profiles, cookies, files and credentials you add. They persist on that machine until deletion. bmux stores the rental name, SSH public keys, provider resource identifiers, price quote, billing status and traffic status to operate it. Deleting a box removes its provider machine and files; billing records remain available for accounting. Managed backups are not included.
Billing
Stripe processes payments and stores card details. bmux stores Stripe customer, checkout, subscription and invoice identifiers, payment status and accepted prices. Card numbers are entered in Stripe checkout and are not stored by the bmux commerce service. Transactional billing and setup emails are delivered through Resend.
Help notifications
A help request stores its host, runtime generation, session, pane, episode identifier, reason and resolution status. Notification delivery uses your registered Expo push token. The push payload contains an opaque attention ID, with no page URL, title, screenshot, cookie or task text. The signed-in app retrieves the target afterward. Remove a registered device to stop its notifications.
Access, retention and deletion
Operational records are used to provide access, reconcile billing and resources, deliver requested notifications and investigate failures. Usage counters are retained for 30 days. Billing records are retained for accounting and dispute handling. Contact Tõnis through tonis.dev to request access, correction or account deletion. Do not put passwords, card details or browser cookies in a public issue.