Murmur
Privacy

Privacy policy

Effective November 18, 2026 · Peter NDENGO

Murmur is a messenger that works with and without the internet. This page says what the app and our server keep about you, why, for how long, and who we entrust it to. It describes what the software does today.

The short version

Contents
  1. Who is responsible
  2. What stays on your phone
  3. Your account
  4. Your public profile
  5. Your messages and calls
  6. Notifications
  7. Your location
  8. Échos, lives and the directory
  9. Contacts and phone number
  10. Iris and artificial intelligence
  11. Sensitive pictures
  12. Age
  13. Reports and moderation
  14. Payments
  15. Certification
  16. Communities
  17. National dialogue
  18. Linked devices
  19. Logs and security
  20. The companies that help us
  21. What Murmur does not do
  22. How long
  23. Your rights and choices
  24. Changes
  25. Write to us

Who is responsible

Murmur is published by Peter NDENGO, who is responsible for the data described here. For any question about your data: frdrcpeter@gmail.com.

Murmur is made of the app, on your phone, and of a server, the “gateway”, that carries messages over the internet. The ondemurmur.com website is served by that same server.

The rules for using Murmur are in the terms of use.

What stays on your phone

Most of Murmur lives on your phone: your conversations, your contacts, your photos, your drafts and your encryption keys. Murmur keeps them out of Apple’s and Google’s backups: they go neither to iCloud nor to Google Drive. Your keys stay in the phone’s keychain.

Several things are worked out on the phone, without sending anything: the “For you” feed, the transcription of voice messages, translation (Apple or Google only provide the language models to download) and the detection of sensitive pictures.

Without the internet, Murmur goes over Bluetooth and Wi-Fi, from phone to phone. The phones that carry a message cannot read it, but they add their name to it: you and your contact see the route. A phone nearby can see that a Murmur phone is there; with “Visible nearby” (on at first), it also sees your name.

Your account

To create an account, you choose a @username, a name and a password, and you confirm that you are 16 or over and accept the terms of use. Murmur asks for no phone number and no email address for it.

Your password never leaves your phone. The phone turns it into two keys. The first encrypts the backup of your account: your keys, your contacts, your groups and, if you gave it, your date of birth. It never leaves the phone. The second is used to sign in, and our server only keeps a fingerprint of it: it can recognise your password without being able to open your backup.

As long as the account exists, the server keeps: your username, the name given at sign-up, your public keys (your Murmur address), this encrypted backup, a trace of each phone signed in to the account (10 at most), and the number of wrong passwords tried; after several, the account is held back for a while.

Conversation backup. Every day, Murmur backs up the text of your conversations on our server, encrypted with a key kept inside your account’s backup. We cannot read it. It is kept 400 days after the last backup, and erased with your account.

Your public profile

Your @username, your name and your bio are visible to anyone on Murmur; your name and your username also on your username’s web page (ondemurmur.com/u/your-username). The links, city and job you add to your profile are visible too.

Your profile photo goes encrypted, to your mutual contacts only: our server does not see it.

Who you follow, and who follows you, is public, unless your account is private.

Profile views. When this option is on on both sides (it is at first), the person whose profile you open sees that you looked at it. The server keeps these views 31 days.

Your messages and calls

Messages. A message is encrypted on your phone for its recipient only, or for each member of a group. If your contact is not connected, the encrypted message waits on our server for 14 days at most; it is erased as soon as it is delivered.

Photos, voice notes and files. They are encrypted like messages. The larger ones (50 MB at most) go through our server, encrypted with a key of their own that only the recipient receives. The server keeps the encrypted file 14 days.

Scheduled messages. A scheduled message waits on the server until its time, encrypted, with the name to show in the notification.

What the server still sees. When a message goes over the internet: who sends it, to whom, when, and its size. Never its content.

One-to-one calls. Voice and video calls are end-to-end encrypted. If your phones cannot reach each other directly, the call goes through a relay (Cloudflare’s, or ours), which cannot listen to it.

Group calls and lives. Sound and video go through Cloudflare’s servers, which pass them on. They are encrypted in transit, but not end to end. Murmur does not record them.

Murmur’s encryption has not yet been checked by an independent audit.

Notifications

To tell you about something while the app is closed, Murmur goes through Apple (iPhone) or Google (Android). For each of your phones, the server keeps: its notification token, its language, its time zone, the app version, your country, your preview choice, and the list of muted conversations and blocked people, so as not to notify you about them.

With “Message preview” (on at first), the sender gives the server their name, and the group’s when there is one, to write the notification. The text of the message is never in it in clear. On iPhone, the notification also holds an encrypted preview (the first 160 characters) that only your phone can open. Apple and Google always see an identifier of the conversation, even without a preview.

This is erased when you turn notifications off in Settings, when Apple or Google report that the token is no longer valid, when you unlink a device, or with your account.

While Murmur moves from its test version to the official app, the server also notes that your account uses the official app (your key and the date), so as to stop handing your messages to the old version. This note is erased 400 days after your last connection with the official app, or with your account.

Your location

Murmur only reads your location if you allowed it in the phone’s settings.

The map of everyone. A new account is “Visible” at first. While the app is open, your phone then sends the server, at most once a minute, a position rounded to about 250 m. The server keeps only the last one. It shows it on other people’s maps for 24 hours at most, with your username, your name and your bio, and draws from it a distance to the nearest kilometre, which a search for your username shows for 7 days. You need a @username to be on the map.

While you are “Visible”, your phone also adds its position to some requests: to sort échos and lives by distance, and to choose the ads of your region (your country and an area of about 150 km). The part of the map you are looking at is sent, to know whom to show there. The server uses it to answer, without writing it to its database.

Your mutual contacts see your position to about 50 m while you are “Visible”. It goes end-to-end encrypted: our server cannot read it.

“Ghost”, on the map or in Settings › Privacy › Share my location, erases your position from the server. From then on, your phone sends nothing of your position, not even an approximate one: nothing for the map, nor with échos, lives, salons, the pro directory or search. Only an SOS you accept still sends it. Ads are then chosen by the country of the phone’s language alone. The map only asks the server about areas where you are not. “Nearby” lives are not offered to you, and you cannot host one.

Map tiles. Your phone gets them from OpenFreeMap, which sees your IP address and the area shown.

Live location. It shares your position for 15 minutes, 1 hour or 8 hours, end-to-end encrypted for the chosen conversation only.

SOS. If you agree at the time of the call, your exact position goes with the call for help, to every Murmur phone nearby and through our server. Each signal lasts 30 minutes, the alert 2 hours at most.

The place of an écho. You can name a place, your town for instance. To suggest some, while you are “Visible”, your phone sends a position rounded to about 1 km; the names come from OpenStreetMap, which our server asks. The place you choose is public with the écho.

Échos, lives and the directory

Everything you post in Échos is public: text, photos, videos, sounds, place, and also comments, likes and shares. Any Murmur phone can read it, and our server keeps it to pass it on.

An écho lasts what you choose when you post it: 24 hours, 48 hours, 7 days, or “Never” (10 years at most). Its comments and likes last as long as it does.

Before sending, Murmur removes the GPS position, the date and the device model from photos and videos. The high-definition photos and long videos of an écho are kept unencrypted on our server; anyone who has their link can see them.

Taking an écho back removes it from the feed, the search and the trends, and erases its comments, its likes and its high-definition version from the server. Its original version stays stored, marked as taken back, until the end of its lifetime; phones no longer show it.

An écho posted “without your name” is signed by a throwaway key: it is not tied to your account.

Statistics. To show you how your échos do and to reward creators, the server counts, per écho and per day, views, watch time, likes, comments and shares, without keeping who watched (400 days). The detail of who saw or liked which écho is kept 3 days, and the karats each écho earned, per month, 775 days.

Lives. A live is public. Our server records neither the picture nor the sound, and keeps the chat in memory while the live lasts. It keeps a trace of each live (who hosts it, its title, its times, the number of viewers) for 400 days, and who watched which host for 90 days, to tell you about that host’s next lives. A replay stays on the host’s phone.

The directory of pros. A card is public: name, trade, area (to within a few kilometres), hours, prices, photos, and a phone number if you give one. It lasts 90 days at most, unless you renew it.

If you delete your account, all your échos and everything under them are erased at once, as are your comments, likes and shares under other people’s échos, and your other public posts (SOS, salons). Our server refuses them if a phone hands them in again later.

Contacts and phone number

Your address book is only read if you tap “Find my contacts”, then every 3 days at most, once access was given. Neither numbers nor names leave in clear: the phone only sends the very beginning of a fingerprint of each (the first 20 bits for a number, the first 12 for each word of a name), shared by thousands of numbers or names, and does the comparison itself. The server keeps nothing of what is asked.

Verified number (optional, when the service is offered). A code is sent to you by text message, through Africa’s Talking. The server does not keep your number in clear, only fingerprints: one so that a number belongs to one account only and, while “Find me by my number” is on, another so that people who know you can find you. These fingerprints are erased with your account.

“Show my contacts” (on at first). Your mutual contacts can see the list of your mutual contacts, with their name and username. It goes encrypted from one phone to the other.

“Online status” (on at first). So that your mutual contacts see when you are connected, your phone gives the server the list of their Murmur addresses. It stays in memory, never in the database.

Inviting someone from your address book opens WhatsApp or your text messages with their number: nothing goes through our server.

Iris and artificial intelligence

Iris, Murmur’s assistant, summarises conversations, suggests replies and reads aloud. On an iPhone with Apple Intelligence, summaries and suggested replies are made on the phone first: nothing leaves it.

Otherwise, nothing leaves without your agreement, and every request for it names OpenAI, our provider, before anything is sent.

Summaries. The chosen messages go to our server, then to OpenAI. People in them are replaced by “P1”, “P2”…; a voice message is transcribed on your phone, and the sound does not leave. Never sent: photos, positions, disappearing messages, view-once media, deleted messages. What your contact wrote goes too, when you choose it.

Suggested replies. The last messages of the conversation go to OpenAI, 10 at most, without any name, with a few traits of the way you write.

Reading aloud. When Iris reads a summary, the text read, names included, goes to OpenAI.

Iris live, the spoken conversation, sends your voice from your phone to OpenAI, with the messages of the chosen conversation, names included.

The call interpreter. When the person speaking agrees (“Allow”), their voice goes to OpenAI to be translated, with a fingerprint of the Murmur address of the phone that translates, which OpenAI asks for to fight abuse.

“Suggest a caption” for an écho sends OpenAI up to 3 pictures, the words spoken in the video and your text.

What OpenAI keeps. For texts and pictures (summaries, suggested replies, captions), we ask OpenAI not to keep them. For the voice (reading aloud, Iris live, the interpreter), we cannot ask it: OpenAI’s voice services have no such option. In every case, OpenAI applies its own rules, notably against abuse.

Our server keeps none of these texts, pictures or voices: only daily counters (35 days) and the date you first used Iris (180 days after the last use).

To withdraw your agreement: Settings › Privacy › Sending to Iris.

Sensitive pictures

Murmur blurs pictures that could shock. Detection happens on your phone (Apple’s analysis on iPhone, and a model built into Murmur): the picture does not leave.

The phone only sends the server a note: for an écho, which one and its author; for a conversation, the day and the kind (one-to-one or group), without saying which. The note carries your phone’s Murmur address and is kept 180 days, to follow moderation.

If the option is on on our server, the photos of new échos, and the cover picture of their videos, are also sent to Google Cloud Vision, which says whether they are shocking. Google receives neither your name nor your text; we only keep its answer when it flags the picture.

Age

Murmur is for people aged 16 or over. You confirm it when you create your account, as you accept the terms of use. An account created before confirms it the same way at its first public post: an écho, a comment or a live. Murmur does not ask your date of birth for this.

To see a blurred picture, Murmur asks your date of birth once: you must be 18. It stays on your phone and in your account’s encrypted backup. If you share your birthday (off at first), the day and month go encrypted to your mutual contacts.

Hosting a live is for people aged 18 or over.

Reports and moderation

Reporting an écho, a live or a pro’s card sends the server what you report, why, your Murmur address and a copy of what is reported; for a live, also the last 20 chat messages and a picture. This is kept 30 days. The person reported does not see who reported them.

Reporting a group sends the server the group’s id, its name, its number of members, the reason you chose, your Murmur address and the time. Never a message, nor anything said in it: the group stays end-to-end encrypted. This report is kept 90 days, read only by Murmur’s team, and erased with your account. Nobody in the group is told.

Reporting someone by email opens your mail app, addressed to frdrcpeter@gmail.com, with their name, their Murmur address and the quoted message.

An écho taken down by moderation is erased; we keep an 80-character excerpt, the name shown and the reason, until 30 days after the écho’s planned end. A username blocked by moderation stays blocked for as long as it is: we keep the username, the name shown, the reason and, when the phone is blocked too, its key.

If you delete your account, the reports you made and those about your échos or lives are erased, as are the sensitive picture notes made by you or about you.

Payments

In the version of Murmur from Google Play, karats and the examination of a certification request are bought through Google Play. You pay at Google: Murmur sees neither your card nor your means of payment. With the purchase, Google receives a code drawn from your Murmur address (never the address itself), so that the purchase counts for the right account. Our server then asks Google whether the purchase was paid, and keeps: the product, the quantity, the karats given, Google’s order number and purchase token, the date, the buyer’s country according to Google, the state of the purchase and, where it applies, its refund. In this version, interpreter minutes, ads and a front place in the directory are paid in karats; an ad on an écho is paid in karats or bought through Google Play.

In the version of Murmur from the App Store, karats and the examination of a certification request are bought through Apple’s in-app purchase. Apple takes the payment: you pay at Apple, and Murmur sees neither your card nor your means of payment. With the purchase, Apple receives a code drawn from your Murmur address (never the address itself), so that the purchase counts for the right account. Your phone then hands our server the purchase as Apple signed it; the server checks Apple’s signature and keeps: Apple’s transaction identifier, the product, the quantity, the karats given, the date, the country of your App Store account (the storefront), whether it was a test purchase, the state of the purchase and, where it applies, its refund, which Apple tells us about. In this version too, interpreter minutes, ads and a front place in the directory are paid in karats; an ad on an écho is paid in karats or bought through Apple’s in-app purchase.

In the other versions, purchases (karats, certification, ads, interpreter minutes) go through Paystack or, in the DR Congo, through Mobile Money, with WonyaPay and your operator (Orange, Airtel, M-Pesa or Afrimoney).

With Paystack, you type your email in Murmur, and your card or M-Pesa details on Paystack’s page: Murmur never sees them. Paystack receives your email, the amount, the currency and a reference, without your username.

With WonyaPay, your Mobile Money number, the amount and a short description (for instance “Murmur : 100 karats”) go to WonyaPay and to your operator, which asks you to confirm on your phone.

For a purchase through Paystack or WonyaPay, we keep: the amount, the currency, the reference, the status, the receipt email, and the number for a certification paid by Mobile Money.

All these purchase records serve accounting and disputes. The record of an ad on an écho also says which écho it paid for. They are kept 5 years after each payment, even if you delete your account; an ad on an écho given for free, where it costs nothing, is no payment and goes with the account. The statement of your karats and interpreter minutes (what is bought, earned, spent) is kept as long as your account exists, then 5 years after each operation.

A payment request sent in a conversation is only an encrypted card: no money goes through Murmur.

Certification

A request for the “Certified account” badge holds what you give: name, contact (email or number), role, legal name, registration number, country, phone, and up to two documents (a registration, a letter, an identity document). A badge granted is visible to everyone.

The documents are erased when the request is approved, refused or withdrawn, at the latest 30 days after the decision. The decided request (without its documents), the record of the decision and a revoked badge are kept 2 years after the decision.

If you delete your account, a request in progress is deleted with its documents, the documents of decided requests are deleted too, and your badge is revoked.

Communities

A request to be recognized as a member of a community holds the name to show, a phone number or an email address, and a document if you attach one. Murmur checks it. If the community has an owner (an account Murmur chose), the owner then sees your name, your username and what Murmur checked, and approves or declines; the owner sees neither your contact nor your document. Your membership of a community is visible to everyone, like a badge.

A community’s feed of announcements is not end-to-end encrypted, unlike groups. Our server keeps the owner’s announcements, the members’ reactions (who reacted, and how), and, for each group of the community, its name, the owner’s invitation (or that of the member who proposed it) and its number of members. Only the members and the owner can read the feed, except the announcements the owner makes public: anyone reads those on the community’s page, and they go out in Échos as an écho of the owner. That page, open to everyone, also shows the community’s name, logo, country, number of members and description. Announcements and their reactions are kept 365 days.

An announcement may carry photos, a video, a voice message or a file. Each one is encrypted on the owner’s phone, with a key that is only in the announcement: our server keeps only the encrypted version, and only those who can read the announcement can open them. They are kept as long as the announcement, and deleted with it.

A community’s groups are groups like any other: their messages stay end-to-end encrypted.

To show the logos of your two most active communities after your name, your phone counts your activity itself and sends only the order of your communities, signed by it. Our server keeps the latest one and passes it on, with the badges, to every Murmur phone.

A community’s description is written by its owner, shown on its page and kept on our server; a report of a community (who made it, why and when) is kept 90 days, read only by Murmur’s team, and erased with your account.

A member can propose one of their groups to the community. The proposal (the group’s name, its photo if it has one, its number of members and the member’s invitation) is kept on our server and shown to the owner only, until the owner answers, 30 days at most. Once accepted, declined or withdrawn, only the group’s name and the answer stay 7 days, so that the member learns it. Accepted, the group is shown to the members like the community’s other groups.

If you delete your account, your announcements, your reactions, the order of your communities, your group proposals and a pending request are deleted, and your community badges are revoked. A community you owned no longer has an owner, and the description you wrote for it is erased.

National dialogue

If you answer a question of the National Dialogue, we keep your answer (text or voice), the province if you give it, and your username only if you choose to answer with it. The answer is tied to a fingerprint of your Murmur address, not to your name. The Dialogue team reads and listens to it as it is. It is kept 365 days; you can replace or withdraw it for 30 days. It is erased with your account.

Linked devices

You can link up to 4 devices to your phone. The server keeps the signed list of your devices (name, kind, date linked) and hands a new device your recent history, encrypted for it alone and erased 48 hours later at most.

If you delete your account, this list and the history in transit are erased. Your linked devices are cut off and erase themselves when they next connect: for that, the server keeps their keys 30 days.

Logs and security

What the app and our server exchange is encrypted (HTTPS).

The server does not log requests. Your IP address is used, in memory only, to limit abuse (too many tries, too many sends): it is not written to the database. The server’s error messages may hold a username, the beginning of a Murmur address or a payment reference. Our host and Cloudflare may keep their own connection logs.

To count active phones, the server notes the first and the last day each phone connects, erased 90 days after its last visit. For calls, it notes when it gave your phone access to a relay (30 days).

The companies that help us

These services receive what their task needs. They may be located outside your country.

Hostinger
Rents us Murmur’s server: everything the server keeps goes through it.
MongoDB Atlas
Hosts the server’s database.
Cloudflare
Stands in front of our server (network, protection); relays some one-to-one calls, without being able to listen to them; carries the sound and video of group calls and lives; helps two phones find each other for a call.
Apple and Google
Notifications; Google Play to install Murmur, with the invitation link that opens the right person or group after installing, and for purchases in the Google Play version; the App Store for purchases in the App Store version; translation models downloaded to the phone; Google also helps two phones find each other for a call.
OpenAI
Iris (summaries, suggested replies, reading aloud, Iris live), the call interpreter and écho captions (see Iris).
Google Cloud Vision
Checks the photos of public échos, if the option is on.
Paystack
Card and M-Pesa payments, outside the Google Play and App Store versions.
WonyaPay and the operators
Mobile Money in the DR Congo, outside the Google Play and App Store versions.
Africa’s Talking
Text messages that verify a number, when the service is offered.
GIPHY or Klipy
GIF search: only the words searched, through our server.
Deezer
Music search and previews, from your phone.
LRCLIB
Song lyrics (title, artist, length), from your phone.
OpenFreeMap
Map tiles, from your phone: this service sees your IP address and the area shown.
OpenStreetMap (Nominatim)
Place names, through our server, from a position rounded to about 1 km or a name typed.
The websites you send links to
Your phone fetches the page’s preview (“Link previews”, on at first): the site sees your IP address.

The ondemurmur.com website sets no tracking cookie. Its home page loads its fonts from Google Fonts and a 3D library from cdnjs (Cloudflare), which see your IP address.

What Murmur does not do

  • No analytics tool, no crash report sent, no advertising identifier.
  • Murmur’s ads are our own. They are chosen by your country and an area of about 150 km or, as a “Ghost”, by the country of the phone’s language alone; we count them per ad and per hour, without knowing who saw them.
  • We neither sell nor rent any data.

How long

As long as your account exists, each piece of data is kept for the time given here, then erased. If you delete your account, everything is erased at once, except what the Delete an account page lists under “What remains”, each for its own time.

Account and profile
Until the account is deleted.
Messages and files waiting (encrypted)
14 days at most.
Encrypted conversation backup
400 days after the last one.
Échos, comments and likes
The lifetime chosen when posting, 10 years at most.
Position on the map
The last one only, shown for 24 hours; erased as a “Ghost”.
Profile views
31 days.
Écho statistics
400 days; the detail per person, 3 days; the karats earned per écho, 775 days.
Lives
Trace of the live, 400 days; who watched which host, 90 days.
Reports
30 days.
Reports of a group
90 days.
Sensitive picture notes
180 days.
Iris counters
35 days; date of first use, 180 days after the last.
Days the phone connected
90 days after the last visit.
National Dialogue answers
365 days.
Pro directory card
90 days at most.
Payments
5 years after each payment, even after the account is deleted.
Statement of karats and interpreter minutes
As long as the account exists, then 5 years after each operation.
Documents of a certification request
Erased at the decision, 30 days after it at most.
Certification decisions
2 years after the decision, without the documents.
A community’s announcements and reactions
365 days.
A community’s groups (name, invitation)
As long as the owner, or the member who proposed it, keeps them, or until their account is deleted.
Groups proposed to a community
Until the owner answers, 30 days at most; then the name and the answer only, 7 days.
The order of your communities
The latest only, until the account is deleted.
Reports of a community
90 days.
Use of the official app
400 days after the last connection.
Usernames blocked by moderation
As long as they are blocked.
Échos taken down by moderation
An excerpt, 30 days after the écho’s planned end.
Linked devices of a deleted account
Their keys, 30 days, so that they erase themselves.
Deletion requests sent from the web
30 days after they are handled, 90 days at most.

Your rights and choices

At any time, you can:

  • see and correct your profile, in the app;
  • get a copy of what our server keeps about you, or have something corrected, by writing to frdrcpeter@gmail.com;
  • delete your account, in the app or from the Delete an account page; take an écho back; erase your position with “Ghost”; turn off “Find me by my number” in Edit profile;
  • withdraw an agreement in Settings: Sending to Iris, Share my location, Show my contacts, Online status, Link previews, Message preview; and turn off Profile views;
  • object to a use of your data, or ask a question, by writing to us.

You can also contact the data protection authority of your country.

Changes

When this policy changes, the date at the top of the page changes too.

Write to us

Peter NDENGO · frdrcpeter@gmail.com