← Back to MsgYap MsgYap

Privacy Policy

MsgYap is a username-first messenger. This page sets out exactly what the server holds, what it can never read, and how to make it forget you.

Effective 16 November 2026 Last updated 16 November 2026 India · DPDP Act 2023 · IT Rules 2021

The short version. Your messages are encrypted on your device before they are sent, so the server holds sealed envelopes it cannot open. It keeps your handle, your public keys, anything waiting to be delivered, and a notification token. It never asks for your phone number, does not upload your address book, and does not track your location, and it runs no third-party analytics. Deleting your account removes what the server holds; it cannot remove what other people already received.

Who we are

MsgYap is operated by Nappilos LLP, a company based in India. For the personal data described here, MsgYap is the Data Fiduciary under India’s Digital Personal Data Protection Act, 2023 (the DPDP Act). Where the GDPR or UK GDPR applies — for example because you are in the EU or UK — MsgYap is the controller of the same limited data.

This policy covers msgyap.app, the MsgYap web app, and the MsgYap apps for iOS and Android. It does not cover what another person does with a message after it reaches their phone, and it does not cover a school’s or clinic’s own records, which that organisation controls.

What MsgYap is

MsgYap is a messenger built around a username. You choose a handle such as @asha_k, and that handle is your address. There is no phone number, no SIM check and no SMS code, so there is no number to leak, recycle, or quietly link to your other accounts.

Your identity is a key pair generated on your device. The private half stays there; only the public half is registered with the relay. To reach someone you need their handle or their card — you open a link or scan a QR code. We do not publish a searchable directory of personal handles. Verified business profiles can opt in to a listing, and that is their choice, not a default.

What the server stores

The relay is deliberately boring. It keeps the minimum needed to route messages and keep accounts working:

  • Your handle and public keys. The handle, the public half of your identity key, and the record that ties the two together.
  • Sealed envelopes. When someone messages you while you are offline, the encrypted message waits in a queue under your handle. Each queue holds at most 200 envelopes; when it is full, the oldest are dropped first. The server cannot open any of them.
  • A push subscription or device token. If you enable notifications, we keep the endpoint your browser or phone gave us so we can wake the app. It points at your device; it does not contain the message.
  • Device sessions. A label, a platform and a last-seen time for each device signed in to your account, so Settings → Devices can show you something real and you can spot a device you do not recognise.
  • An email address, only if you add one. It is optional. When you add it we verify it with a one-time code, and it is used for exactly two things: proving the account is yours on a new device, and holding an encrypted backup that we cannot decrypt. Remove the email and both go with it.
  • Encrypted media. Photos, files and voice notes are encrypted on your device before upload and stored as ciphertext in object storage. The keys travel inside the message, not alongside the file.
  • Organisation records. If you create or join an organisation: its name, verified domain, plan, member list with roles, and an audit log of actions taken in the workspace.
  • Abuse reports. The reporter’s handle, the reported handle, the category and any note written. Reports contain no message content, because there is none for us to attach.
  • Security events. IP address, timestamps, failed or rate-limited requests and error output, kept for 30 days as described in section 8.

What the server can and cannot read

  • It cannot read message text, photos, files, voice notes or call media. These are encrypted on the sender’s device and decrypted only on the recipient’s. There is no server-side key, no escrow copy, and no switch we could flip to read them.
  • It cannot read your recovery phrase. Those 16 words exist on paper or in your head, never on our servers. If you lose them, we cannot reconstruct them.
  • It can see who messages whom, when, and roughly how much. An envelope has a sender, a recipient, a size and a timestamp, and routing needs all four. That routing data is kept only as long as delivery needs it, plus the 30-day security log.
  • It can see what you publish. A handle, profile name and avatar are visible to anyone you share your card or link with. That is the point of a card.

We would rather say this plainly than claim the server sees nothing. A messenger that sees no metadata is either not a messenger or not telling you the truth.

What we do not collect

  • Message content. Not on the server, not readable in backups, not available to staff or to anyone who buys the company.
  • Your address book or contacts. The app never asks for that permission. You can send one contact card yourself and it travels as an encrypted message, but nothing is uploaded from your phone.
  • Your location. We do not track it and never ask for it in the background. If you tap “share location” in a chat, your device reads GPS at that moment and sends the coordinates as an ordinary encrypted message to that one person — we are not part of the exchange and do not store the result.
  • Your phone number. Never requested, never verified, never stored.
  • Advertising identifiers. No IDFA, no GAID, no advertising SDK, no attribution partner.
  • Third-party analytics or crash reporting. Google Analytics, Firebase Analytics, Meta Pixel, Mixpanel, Sentry and their equivalents are deliberately absent. There is no tracking cookie and no cross-site profile of you.

What stays on your device — your keys, your message history, your settings — is not uploaded. Clearing site data or uninstalling the app removes it.

Children and child safety

MsgYap is built with families, schools and clinics in mind, so this section is not boilerplate.

  • Minimum age: 13. You may not create an account below that age. Where a school or clinic workspace is used by younger children, that organisation is responsible for obtaining parent or guardian consent and for supervising use.
  • No advertising, no profiling, no behavioural tracking and no sale of data — for anyone, and especially not for children. There is no public directory of personal handles; a handle is shared deliberately, by link or QR.
  • We do not knowingly keep an account held by a child below the minimum age. If we learn of one, we suspend it and delete the data, and we tell the parent or guardian who raised it what we did.
  • If you believe a child is at risk on MsgYap, write to support@msgyap.com with “child safety” in the subject, or to the grievance officer in section 13. These reports are treated as urgent and acknowledged within 24 hours.

How long we keep data

Sealed envelopes
Deleted as soon as the recipient’s device confirms delivery. If they are never delivered, they are dropped when the queue passes its cap of 200, oldest first. We do not archive them.
Handle and public keys
Until you delete your account.
Push subscriptions and device tokens
Until you turn notifications off, sign that device out, or delete the account.
Recovery email and encrypted backup
Until you remove the email or delete the account. The backup is ciphertext; we cannot read it or restore it for you.
Security events and server logs
30 days, then deleted. This is the only place an IP address is kept.
Organisation records and audit log
While the organisation exists. Your membership ends when you leave it or delete your account.
Abuse reports
Until the report is closed and any appeal period has passed, so a repeat offender cannot re-register into a clean slate.
Deleted accounts
Removed from the live service immediately. Encrypted backups that contain the account are deleted at the same time.

Your rights

As a Data Principal under the DPDP Act you can:

  • Access a summary of the personal data we hold about you, and the identity of anyone we shared it with (our sub-processors, section 11).
  • Correct or complete what is wrong — your optional email, your profile details, the devices listed on your account.
  • Erase your data by deleting your account (section 10), or by asking us to erase a specific item.
  • Nominate someone to exercise these rights on your behalf if you die or become incapacitated. Write to us with their name and contact and we will record it.
  • Complain to us first, and then to the Data Protection Board of India if we do not resolve it.

If you are in the EU or UK you also have the right to restrict or object to processing, to receive your data in a portable format, and to complain to your local supervisory authority.

Write to privacy@msgyap.com from the email on the account, or use Settings → Your data in the app. There is no charge. We may ask you to prove the account is yours with a one-time code or an account token — we cannot verify you by reading your messages, because we cannot read them. We aim to respond within 30 days; grievances follow section 13.

Erasure has one honest limit: what you already sent lives on other people’s phones. We can delete what we hold. We cannot reach into someone else’s device.

Deleting your account

In the app: Settings → Your data → Delete my account, then type your handle to confirm. It takes effect immediately and cannot be undone.

Deletion removes your handle and public key; every sealed envelope waiting for you; your push subscriptions and device tokens; your optional email and encrypted backup; your organisation membership (an organisation you solely own is transferred to another admin or closed); your entry on any business listing; and every retained encrypted backup of the account. Account tokens issued before deletion stop working, so a copied token cannot bring the account back.

Deletion cannot remove messages already delivered to other people’s phones, media they saved, screenshots, or anything they choose to repeat. Those copies are outside our control. Abuse reports you or others filed are kept without message content.

On your device the app clears its local store, caches and identity record. If you delete through the app, do it before uninstalling; otherwise clear the site data or uninstall the app yourself.

Who we share data with

We do not sell personal data and we do not share it for advertising. We use three sub-processors and no others:

Hostinger
Hosting for the relay and the website, and outgoing email (SMTP) that delivers recovery codes. It holds the data we store and sees the address a code is sent to.
Cloudflare
DNS and the CDN in front of the site; R2 object storage for encrypted media; TURN relays that carry call traffic when a direct connection fails; and Turnstile, the human check at signup. Cloudflare sees connection metadata and ciphertext, not message content.
Razorpay
Payment processing for organisation plans only. Card and UPI details go to Razorpay; we never receive them.

We may also disclose data where a law, court order or lawful request requires it, and we will tell you unless we are barred from doing so. If MsgYap is merged or sold, account data may transfer to the successor under these same terms, and we will say so on this page.

Security

  • Traffic to and from the app uses TLS. Envelopes are sealed with the recipient’s keys before they leave the sender’s device.
  • Media is encrypted before upload. Private keys and recovery phrases never leave your device.
  • Production access is limited, secrets live in server environment variables rather than in the app, and signup is rate-limited and gated by Turnstile.
  • Security events are logged for 30 days so that an incident can be reconstructed afterwards.

No system is perfect, and a policy that claims otherwise is not being honest with you. If you find a flaw, write to security@msgyap.com with the steps to reproduce it; we will not pursue good-faith research, and we will tell you when it is fixed. If a breach affects your data, we will notify you and the Data Protection Board of India as the DPDP Act requires.

Your part: guard the 16-word recovery phrase, keep a screen lock on your device, and check Settings → Devices for anything you do not recognise.

Grievance officer

Under the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 and the DPDP Act:

Grievance officer: Grievance Officer, Nappilos LLP
Email: grievance@msgyap.com

We acknowledge every complaint within 24 hours. Urgent complaints — child safety, threats of violence, impersonation, account takeover — are actioned within 24 hours. Everything else is resolved within 15 days of receipt, as the IT Rules require. If you are not satisfied, you may appeal to the Grievance Appellate Committee under the IT Rules, or complain to the Data Protection Board of India on a data-protection matter.

Changes to this policy

When this policy changes we update the date at the top. Material changes — a new sub-processor, a new category of data, a change in retention — are announced in the app before they take effect. If you disagree with a change, delete your account before it applies; continuing to use MsgYap after that date means you accept the updated policy.

Questions about this page: privacy@msgyap.com. General help: support@msgyap.com. Security: security@msgyap.com.