Phone numbers, eSIMs and email aliases.
JMP.chat
Canadian and US phone numbers for SMS, MMS and calls over XMPP, operating under Canadian and BC jurisdiction.
jmp.chat
- No routine KYC
- CA
- Evidence and facts →
Canadian and US phone numbers for SMS, MMS and calls over XMPP, operating under Canadian and BC jurisdiction.
Evidence and facts
Evidence and facts
Specs
Review analysis, source material, related services, and history
Analysis
JMP.chat offers US or Canadian phone numbers for SMS, MMS and calls over XMPP. Its reviewed FAQ/privacy materials state no routine identity-document check; signup still uses a Jabber ID and paid service account.
The service operates under Canadian and British Columbia jurisdiction, and the record flags telephone metadata, carrier and XMPP routing, and lawful requests as ongoing threat-model risks despite the minimal-data design.
North American number/XMPP comparison for users who distinguish the stated normal signup flow from activation, payment, porting and telecom identity exposure.
Ownership and funding
Corporate identity
Other cited research. Not audited. Each claim links its own source.
- LEGAL ENTITY
- MBOA TECHNOLOGY CO-OPERATIVE INCother research ↗
- ULTIMATE OWNER
- Employee-governed co-operative (provider-reported)other research ↗
Frequently Asked Questions
Is identity verification required?
No identity verification is recorded for typical use. No routine identity-document check is stated in the reviewed FAQ/privacy pages. Signup uses a Jabber ID and paid service account. New accounts must receive a human text before outbound use unless referred or ported; payment methods, number porting and XMPP hosting can add identity exposure.
Where is it available?
Recorded availability: US, CA.
Is the operator based in a Five Eyes country?
Yes. The recorded jurisdiction is CA, a Five Eyes country (US, UK, CA, AU, NZ). This is jurisdiction context and does not by itself establish that a service is safer or less safe.
How are identity, operator, and evidence fields reported?
Identity exposure is level 0 of 4. Hosted operator data has not been established. Jurisdiction is shown as context, not a safety verdict. Source coverage is verified evidence, last reviewed 2026-11-08, and recorded risk is caution.
Sources and history
Terms and privacy policy
No changes to the document we watch since we started checking on 9 Aug 2026. Last checked 9 Aug 2026.
Evidence basis: Claims on this page are linked to published sources for comparison, not certification, audit, endorsement, or recommendation; read the methodology and coverage map before relying on an entry.