Why MsgYap

Why should a conversation require your permanent mobile number?

A conversation needs an identity. It does not always need the number attached to your SIM, your bank, your recovery codes and your family.

MsgYap is a username-first communication platform developed by NAPPILOS LLP. It lets people and organisations communicate through a username instead of making a mobile number their public messaging identity.

One number, many digital identities

In practice, a single mobile number often carries all of these roles at once:

  • telecom identity and SIM registration;
  • messaging identity in consumer apps;
  • OTP and account-recovery channel;
  • banking and UPI-linked contact;
  • business and customer contact;
  • school–parent contact;
  • healthcare and appointment contact;
  • public or community contact.

Those roles are not the same permission. Permission to message someone should not automatically become permission to retain the telecom identifier behind their banking, work and family life.

Numbers have a lifecycle

A communication identity tied to a telecom number inherits the lifecycle and dependency of that number: SIM management, connectivity, number retention and eventual reassignment. Numbers can be lost, replaced, become inactive, or be reassigned to someone else. People sometimes buy a second SIM just to separate personal and business identities.

Short-term communication can create long-term exposure. A delivery, booking or marketplace enquiry may be over in minutes while the number remains known indefinitely.

Phone-number-first and username-first are different architectures

AreaPhone-number-first modelUsername-first MsgYap direction
Identity sharedOften the mobile numberUsername
Temporary interactionThe number may remain knownAlias/contact token (roadmap)
Business separationOften a second number or SIMRole/business identity direction
School communicationPersonal numbers may be involvedRole-based institutional identity (pilot)
Community joiningPhone identity may be exposedUsername/community identity direction
RecoveryTelecom-dependent in many servicesRecovery phrase + optional verified email
Child modelGeneric consumer identityParent/organisation-controlled (roadmap)

This is an architectural comparison, not a claim that another product is unsafe or that MsgYap is complete.

Who benefits

Individuals & families

Keep the number used for OTPs and bank calls out of everyday chats.

Children & students

A school or activity identity should not require a child’s permanent number to be published. Stronger safeguards and parental controls are required.

Women & personal safety

Hotels, deliveries, marketplace sellers and service providers may need a channel without permanent access to a private number.

Elderly parents & NRI families

Reduce unnecessary number exposure while keeping family communication simple. Fraud prevention remains a separate, shared responsibility.

Public-facing professionals

Doctors, lawyers, founders, journalists and officials can separate a public contact identity from a private number.

Businesses

Give customers a role or organisation identity instead of an employee’s personal SIM. Business →

A ten-minute conversation should not require ten years of number exposure

Many relationships are temporary: delivery, repair, travel, property enquiry, marketplace transaction, hotel or restaurant interaction. A future direction is a temporary username, alias or contact token that expires with the relationship. This is roadmap, not a shipped feature today.

What exists today

Built: username-first accounts without a phone number, end-to-end encrypted chats, groups, calls, statuses, communities and attachments, optional email recovery, organisation workspaces, organisation management, account deletion and abuse reporting.
Partial/pilot: school and clinic workflows, the staff portal (a preview on sample data), native parity.
Roadmap: independent audit completion, production multi-device, group-call infrastructure, temporary identity tokens, institutional integrations.
Price today: every organisation workspace is free right now — nothing is charged.

Read the security overview, the phone-number privacy page, or open the app.

Questions people ask

What is MsgYap?

MsgYap is a username-first messaging platform for private chats, calls, groups and organisation communication, developed by NAPPILOS LLP.

Why use a username instead of a phone number?

A username allows communication without unnecessarily exposing the telecom number that may also be linked to banking, OTP, work and family services.

Does MsgYap require a phone number?

No. Current account creation is username-first and does not require a phone number.

Can MsgYap replace WhatsApp?

MsgYap is not marketed as a replacement. It takes a different username-first identity approach. Choose the tool that fits your needs.

Who owns MsgYap?

MsgYap is developed by NAPPILOS LLP.

Is MsgYap available in India?

MsgYap Web is available at msgyap.app. A native Android build is available on request, and the iPhone app is in testing.

Is MsgYap end-to-end encrypted?

Chats, groups, calls, statuses, communities and attachments are encrypted on the client before relay transport. The system has not yet completed an independent security audit; see the security page for current limits.