comparison · Anonymous SIM / eSIM

JMP.chat vs MySudo

Both are listed in Anonymous SIM / eSIM. The table below pulls directly from each service’s data sheet; see each entry for sourcing.

JMP.chat — summary

JMP.

• + Receives voice and SMS to a real phone number, delivered to your XMPP account.
• + Crypto and Lightning payment accepted.
• + Operator is open-source and runs a parallel XMPP server (Snikket Hosting).
• − Canada/U.S. number pool — number geography matters for some uses (banks, OTPs).
• − Voice quality depends on XMPP-Jingle codecs.
• − Facts need re-verification by operator (last seeded 2026-01).

Full entry → JMP.chat

MySudo — summary

MySudo is a useful compartmentalization product (one app, many disposable numbers and emails) but it is not no-KYC — Apple/Google billing binds the user.

• + Polished UX for managing multiple identities (numbers, emails, payment cards) from one app.
• − Operator binds payment via Apple/Google billing; you are very much identified.
• − The "Sudo" identity model is about compartmentalization within services *to other parties*, not anonymity from MySudo itself.
• − Not appropriate when the threat model includes a U.S. operator with subpoena reachability.

Full entry → MySudo

When to choose which

Treat this section as heuristic. Privacy properties depend on how you use the service, not just which one you pick.

• Choose JMP.chat if receives voice and sms to a real phone number, delivered to your xmpp account..
• Choose MySudo if polished ux for managing multiple identities (numbers, emails, payment cards) from one app..
• Either way, re-check the entry’s last verified date — the Anonymous SIM / eSIM category churns.

Mentioned in (combined)

Pages on the site that reference JMP.chat, MySudo, or both.

Compared as of Jan 1, 2026.