No account.
No email.
No password. Just call.

There is no sign-up flow because there is nothing to sign up to. No email address, no password, no phone number verification, no social login and no profile. You install the app, it opens on the dial pad, and you dial.

That is unusual enough in this category to be worth stating precisely. Every major competitor requires at least a verified phone number, and most require an email and a password on top. The requirement exists for their reasons — fraud control, cross-device sync, marketing — and each of those reasons costs you something.

What it costs, concretely: an identifier that ties your calling to everything else that identifier touches, a credential that can be leaked, and a marketing list you did not ask to be on.

A service that holds no account credentials cannot lose them. That is not a privacy feature bolted on afterwards; it is a consequence of the architecture, and it is the strongest form of the claim because it does not depend on anybody's good behaviour or on a policy that could change next year.

What that does not mean is that nothing is processed. Placing a call requires knowing the destination number and the duration, because otherwise it cannot be routed or billed. Those are set out in the privacy policy, which is worth reading rather than taking on trust — the useful test of any privacy claim is whether the detailed document agrees with the marketing sentence.

Calls are not recorded. There is no audio held anywhere, which means there is none to retrieve, hand over or leak.

Payment goes through the App Store, so card details never reach us at all. Apple holds them; we receive a purchase confirmation and a credit balance.

Because optional registration is registration for most people, and it changes what the product has to hold. The moment an account exists, the service must store credentials, run recovery flows, handle deletion requests and defend a login endpoint — and it holds an identifier that ties calls to a person whether or not any individual user created one.

The version that is genuinely different is the one where the account does not exist. That is a smaller product with a real limitation, and it is the trade we chose deliberately rather than a feature we have not got round to.

If the limitation is a problem for you — if you need a balance that follows you across devices — a service with accounts is the right answer, and there are several good ones. Saying so is more useful than pretending the trade-off does not exist.