Privacy

Use a username. Keep control of what you share.

MsgYap is designed to reduce the personal identity information required just to start messaging. This page is a summary; the canonical policy is served inside the app.

@

No phone number required

The account flow is username-first. There is no SMS step, no phone-number field and no contact upload.

🔒

Content is encrypted

Chats, groups, calls, statuses, communities and attachments are encrypted on the client before relay transport.

👁

Visibility controls

Control read receipts, last-seen visibility, blocked users and unknown senders.

🗑

Erasure in the app

Settings → Delete account removes the directory entry, queued messages, push tokens, email and encrypted backups.

What the service holds

A messaging service needs a small amount of data to route connections and keep accounts recoverable. The server-side list is short:

  • Your handle and public keys — so people can find you by username and check that a message came from you.
  • Sealed envelopes — ciphertext waiting for an offline device, dropped after delivery.
  • A push token — only if you enable notifications; notifications carry no message text.
  • An optional email address — only if you add one for recovery.
  • Organisation records — name, domain, verification status, members, roles, catalogue and plan for a workspace you belong to.

What we do not collect

Message content, your contacts, your location, your phone number and any third-party analytics profile. There is no ad SDK and no tracking pixel on this site.

Reports and organisations

Abuse reports contain the reporter, the reported username, a reason and the time. Organisation records are processed on the organisation’s instructions. Retention, sub-processors and the delete-account path are set out in the full policy.

Read the Privacy Policy

The canonical policy is served inside the app at msgyap.app/privacy, and /privacy-policy on this site redirects there. The Terms of Use are served the same way at msgyap.app/terms.