Muun

• Name: Muun
• URL: https://muun.com/
• Category: bitcoin wallet operator / recovery-ceremony company / self-custody app-distribution boundary
• Tags: bitcoin-ecosystem
• Summary: Muun clears the bar for an entity note because the useful question is not only what does the wallet do? but which named operator ships the official binaries, defines the recovery ceremony, publishes the legal and privacy shell, and decides what counts as the canonical self-custody path around the wallet? That practical authority sits with Muun Wallet Inc. more cleanly than with a neutral wallet label alone.
• What it does:
  • Distributes the official Muun wallet through the iOS and Android app stores and publishes the legal statement that only those binaries count as the official wallet
  • Maintains the company website, blog, GitHub organization, support channel, and security-disclosure path for the broader Muun stack
  • Packages Muun’s 2-of-2 multisig recovery model, including the Emergency Kit PDF, Recovery Code flow, and the public recovery tool used to exit without Muun’s cooperation
  • Publishes the operator-authored explanation for why Muun rejects a mnemonic-only backup model and instead leans on output descriptors plus a two-part recovery ceremony
  • Defines the app’s privacy and telemetry perimeter, including the first-party statement that the app uses third-party services such as Google Play Services and Firebase Analytics
• Key claims:
  • Muun’s Terms of Use say Muun Wallet Inc. is a Cayman Islands company that provides the self-custodial wallet software and website, which is the clearest first-party statement that the wallet sits inside a named operator boundary
  • The same terms say The only official Muun wallet is the one distributed by us through the official app stores, which makes app-store publication and binary provenance part of the real trust model rather than background admin detail
  • The Privacy Policy says Muun Wallet Inc. built the Muun app as a Free app and documents collection of personal information, error log data, and use of third-party services such as Google Play Services and Firebase Analytics, which is useful because the company boundary still matters even when spend authority stays with the user
  • Muun’s recovery-design post says self-custody is at the core of everything the company does and explains why Muun built the Emergency Kit plus Recovery Code model instead of relying on a mnemonic alone, which makes the company note useful for recovery-ceremony analysis rather than only for app distribution
  • The recovery-tool README says users can transfer all funds out of a Muun account with no collaboration from Muun, reinforcing that this is not a custody monopoly even though the normal operating path still runs through company-shipped binaries, docs, and recovery packaging
  • The same recovery repo also exposes the security-contact and reproducible-binary posture, which matters because Muun’s trust boundary includes not just wallet UX but release and incident workflow around the recovery lane
• Whitepaper: No classic standalone Muun company whitepaper is the point here. The strongest current primary materials are the Terms of Use, Privacy Policy, recovery-design writeup, recovery-tool README, and the existing project-layer source set; see ../whitepapers/muun-company-primary-sources-2026-08-11.md.
• Sources:
  • https://muun.com/
  • https://muun.com/en/terms_and_conditions.html/
  • https://muun.com/privacy_policy.html/
  • https://blog.muun.com/why-not-just-a-mnemonic/
  • https://raw.githubusercontent.com/muun/recovery/master/README.md
  • https://github.com/muun

Internal linkages

• Project-layer note: muun.
• Useful adjacent company reads where self-custody still rides on a named recovery, release, or continuity shell: casa, nunchuk, and foundation-devices.
• Reusable lens: a wallet can justify an entity note even when it is genuinely self-custodial if one company still defines the official binary, the recovery ceremony, the telemetry perimeter, and the support path users will actually trust when things go wrong.

Protocol / company boundary

• muun should stay focused on the product surface: one-balance Bitcoin and Lightning abstraction, 2-of-2 multisig design, fee-estimation posture, and the practical recovery properties of the wallet itself.
• This entity note is for the named operator above that product surface: official app-store distribution, recovery-ceremony packaging, legal and privacy policy, telemetry disclosures, support workflow, and the public release-and-recovery shell around the wallet.
• That split matters because how does Muun work? and which company defines the official wallet, the normal recovery lane, and the software trust perimeter around it? are related but not identical questions.

Control surface

• Practical leverage sits in official binary publication, app-store distribution, recovery-document and recovery-tool stewardship, privacy and telemetry policy, support routing, and the company-authored explanation of what safe self-custody should look like for Muun users.

• Muun cannot normally move funds by itself, but that is not the whole test. The company still shapes which binary most users run, which recovery ceremony they trust, how much diagnostic data the app emits, and what the default emergency path looks like when something breaks.

• Read Muun as a self-custodial wallet company whose software-distribution and recovery-design choices are part of the live security model, not as a neutral wallet label floating free of an operator boundary.

• Last reviewed: 2026-08-11 UTC