Privacy
Privacy policy
Last updated: 21 August 2026
The short version: your audio never touches our servers, the apps send no telemetry, this website sets no cookies and runs no analytics — and the only personal data we ever hold is the email address and license of people who buy a subscription. Using Muxvox requires no account. The rest of this page spells that out properly.
Who we are
Muxvox is a registered brand of Mountaineers Holding B.V., the data controller for anything described on this page.
Mountaineers Holding B.V.Amstellaan 9
5691 HC Son en Breugel
The Netherlands
hello@muxvox.io
The apps
Muxvox Desktop and Muxvox Remote are built so that your audio never touches us:
- Audio travels directly between the phones and the desktop over your own local network, encrypted with DTLS. There is no Muxvox cloud in the audio path, and we cannot hear, store or access anything.
- There are no user accounts. You never create a login or password, and using the apps — including the free plan, and every phone on any plan — requires giving us nothing at all. A paid desktop holds a license key (see "Subscriptions" below).
- Settings and device approvals are stored locally on your own devices, nowhere else.
- The apps send no telemetry, usage statistics or crash reports to us.
- A desktop with a subscription, trial or early-access grant contacts our licensing service in the background to refresh its entitlement — sending only its license key and a random installation identifier, never audio, meeting contents, device lists or network details. These checks never happen on the audio path, and a week of offline grace means they can never interrupt a meeting.
Microphone access on the phones is used solely to capture audio for the session you started, and only while the app is running. On Android, the foreground-service notification doubles as the microphone indicator.
This website
- The site is static. It sets no cookies and runs no analytics or advertising scripts.
- Our hosting infrastructure keeps standard access logs (IP address, requested page, timestamp, user agent) for security and debugging. These are not used to profile anyone and are rotated routinely.
- The site loads the Rubik typeface from Google Fonts. Your browser requests the font files from Google's servers, which means Google receives your IP address for that request. See Google's privacy policy.
Subscriptions
If you buy a Team subscription, we process what billing requires and nothing more:
- What we store: your email address, your subscription's plan/seat/renewal state, a hashed copy of your license key, and which installations hold seats (a random identifier plus the Mac's name as you set it). We never see or store your card number.
- Payment processing: checkout, cards, invoices and the customer portal are operated by Stripe. Stripe's checkout pages set cookies of their own under Stripe's policy; this site still sets none.
- Email delivery: license keys and portal links are sent through Mailgun (EU region), which processes the recipient address for delivery.
- Retention and deletion: billing records are kept as long as tax law requires; everything else goes when you ask us to delete it at hello@muxvox.io. Phone users have nothing stored about them to delete.
If you email us — for example to be notified about pricing — we keep the correspondence and use your address only to reply and to send the notification you asked for. We do not sell or share mailing lists.
App stores
The iOS app is distributed through the App Store (and TestFlight for beta builds); the Android app through Google Play. Apple and Google process data as part of distribution and install statistics under their own privacy policies — that part is between you and them.
Your rights
Under the GDPR you can ask us for access to, correction of, or deletion of any personal data we hold about you (in practice: little to none beyond email correspondence). Write to hello@muxvox.io. You also have the right to lodge a complaint with the Dutch data protection authority, the Autoriteit Persoonsgegevens.
Changes
If this policy changes, the new version appears on this page with an updated date. We won't quietly weaken it; a material change will be called out on the site.