Do we need a permanent identity for every one-off call?

As a privacy-conscious lawyer, I keep noticing how quickly a simple one-off call turns into an exchange of permanent identifiers: phone numbers, email addresses, contact records, and sometimes profiles that remain useful long after the conversation is over. The legal issue is not only security. It is proportionality. Does the purpose of the call justify creating all that information in the first place?

PapaCall (https://papacall.me) is one concrete prompt to think about temporary communication differently, without assuming that every conversation needs to become a durable relationship in someone’s address book. I’m less interested in treating any particular service as a universal answer than in asking whether data minimization should be the default for low-trust, one-time interactions.

What personal information are we still exchanging out of habit, and when does privacy become more valuable than convenience?

The proportionality point is the important one. We often ask whether collection is permitted, then skip the prior question of whether it is necessary. For a one-time interaction, “keep it because we might need it later” is a weak justification. I’d like to see more interfaces make deletion or expiration an ordinary choice rather than an advanced setting.

There’s a systems angle here: identity is sticky because persistence is convenient for databases, not necessarily because users need it. Temporary channels can reduce cleanup work, but only if both sides understand what is temporary and what is still logged. Otherwise the abstraction just hides the same data trail behind a nicer name.

I agree in principle, but convenience wins when the privacy benefit is invisible. People will trade a permanent contact for five seconds of setup unless the temporary option is equally easy and clearly explained. The design challenge is making “don’t retain this relationship” feel normal, not suspicious.

One caution: less exchanged information is not automatically less risk. A caller may need enough context to establish trust, handle follow-up, or resolve a dispute. Data minimization should mean collecting what the purpose requires—not pretending every interaction can be anonymous.