Join a community without publishing your telecom identity.
Apartment groups, parent networks, clubs, alumni groups and local associations should not require every member’s personal number to be visible to everyone.
MsgYap is a username-first communication platform developed by NAPPILOS LLP. Communities are built around a shared identity and purpose, not around a public phone-number directory.
Where this matters
Apartment communities
Notices, maintenance and resident coordination without a printed number list.
Parent networks
Class and activity coordination without exposing every parent’s SIM.
Local associations
Neighbourhood and civic groups with a shared identity.
Clubs
Sports, hobby and activity groups that need coordination, not a phone directory.
Alumni groups
Reconnect around a shared institution without making personal numbers public.
Events
Temporary coordination around an event, with a clearer boundary than a permanent contact list.
The principle
Joining a community should not automatically mean publishing your telecom identity to every member. A username or community identity can carry the conversation while the personal number stays private.
Current status
- Built: username-first accounts, groups, communities and channels in the current product.
- Partial: community administration and moderation tools continue to improve.
- Roadmap: temporary community identities, stronger membership controls, institutional integrations and broader admin tooling.
See privacy, safety, or open MsgYap.
Community questions
Do I have to share my phone number to join a community?
MsgYap accounts are username-first. A community should not require publishing a personal phone number.
Are communities anonymous?
No. Usernames and membership may be visible depending on settings. MsgYap reduces unnecessary number exposure; it does not promise anonymity.
Can I leave a community?
Yes. Leaving removes your membership from the community, subject to the retention described in the privacy policy.
Are community messages encrypted?
Community messages and attachments are encrypted on the client before relay transport. Membership and routing metadata are still visible to the service, so do not assume a community post is anonymous.
