The End of the Second Number

The moment you install a calling app, it has to decide who you are. Most decide for you. They mint a fresh number, or a username, or an internal ID, and now you carry two identities: the number people already know, and the one the app insists on. Every new contact becomes a small act of translation.

MPower makes a different choice. Your existing, verified mobile number is the account. There is no second number to hand out, no handle to explain, no card to reprint. The number you have given people for years is the number that reaches you here.

Identity you already own

Verification is a one-time step. You confirm the number is yours, and from then on it is your identity across the service. It is what other users see when you message or call them. It is how they find you: a contact whose phone you already hold appears as themselves, under the number stored in your address book. Nothing to reconcile, nothing to look up.

This has a quiet consequence. On MPower, discovery is not a directory you opt into or a username you hope is still free. It is the contact graph you already maintain. If someone has your number, they can reach you; if they do not, they cannot. Identity and reachability become the same fact.

Your number on the open network

App-to-app calls, messages, video, files, voice notes and location travel between MPower users at no cost, anywhere in the world. The one paid path is calling an ordinary landline or mobile that is not on MPower, billed per started minute at the destination's rate, drawn from a prepaid balance held in US dollars. The app shows, before you dial, whether a number is free or charged, and what your balance is.

When that outbound call lands on the public network, the receiving handset asks a blunt question: who is calling? By default the call presents a shared MPower number. That works, but it is not you. Once you verify ownership of your number with the carrier, under Settings, Caller ID, your own number is presented instead. The call you place from the app then arrives looking exactly like a call from your phone, because as far as caller ID is concerned, it is. Returned calls come back to you. Saved contacts recognise you. The number stays consistent whether you are reached inside the app or from the outside.

That last part matters more than it sounds. A caller ID that shifts depending on how you happen to be dialling erodes trust on the receiving end. One stable number, verified across app and carrier alike, does not.

What verification is, and is not

Precision is worth more than reassurance here, so two limits stated plainly. Carrier verification establishes that the number is yours and clears it for presentation as caller ID. It is an authorisation step, not a promise about the routing of any single call, and it depends on the destination network honouring the presented number, as most but not all do.

Second, on security. Calls and messages on MPower are encrypted in transit, and messages and stories are also encrypted at rest on our own infrastructure, which runs on servers in Germany. That is meaningful protection against interception on the wire. It is not end-to-end encryption, and we do not claim it to be. Your identity being your real number is a convenience and a trust signal; it is not, on its own, a privacy guarantee, which is why block lists, two-step verification and chat lock sit alongside it.

The principle underneath all of this is restraint. A communication tool should add reach without adding overhead. Keeping your number — one identity, verified once, presented consistently — is the smallest version of that idea, and the one people notice least, because it simply behaves the way they expected in the first place. As the open network moves towards stronger, signed caller identity, a service already anchored to your real, verified number is standing where the rest of the industry is heading.