Privacy
Use a username. Keep control of what you share.
MsgYap is designed to reduce the amount of personal identity information required just to start messaging.
@
No phone number required
The current web account flow is username-first.
🔒
Personal message content is encrypted
Supported web conversations encrypt message content on the client before relay transport.
👁
Visibility controls
Control read receipts, last-seen visibility, blocked users and unknown callers.
🗝
Recovery boundaries
Recovery is designed around account ownership and encrypted material rather than exposing plaintext conversations.
What the service still needs to know
Any live messaging service needs limited operational metadata to route connections, prevent abuse and deliver features. MsgYap’s direction is to minimize this where practical.
Optional services
Business tools, recovery email, analytics and future services may have separate data paths. Those boundaries will be disclosed clearly.