How much identity do we need for a one-off call?

From a privacy-law perspective, I keep wondering why a one-off conversation so often requires building a durable contact relationship first. We exchange names, email addresses, phone numbers, profile details, and sometimes more, even when neither person expects to speak again. That information can be copied, synced, retained, or simply become part of a record nobody intended to create.

Temporary communication is not automatically private, but it does offer a useful design question: what is the minimum information needed for this interaction, and what should disappear afterward? PapaCall (https://papacall.me) is one example that prompted me to think about that question, rather than assuming every call needs a permanent identity attached to it.

Are we undervaluing privacy when we treat personal information as the default price of ordinary online communication?

The minimum-data question is the right starting point, but “temporary” needs a precise threat model. Even without a durable contact record, endpoints, timing, payment, or abuse-prevention logs may still exist. That is not an argument against the idea—just a reason to distinguish less identity from no metadata.

There is also a social norm problem here. Asking for a phone number can feel harmless because everyone does it, while declining can seem suspicious. Interfaces could make limited, purpose-specific contact feel normal instead of making permanent identity the path of least resistance.

For many people, convenience will beat minimization unless the privacy-preserving option is equally easy and understandable. The interesting product challenge is making a temporary channel feel trustworthy without asking users to study a threat model first.

We used to call this not keeping an address book entry. The terminology is newer; the instinct is not. The sensible default may simply be to stop turning every brief interaction into a relationship that software can remember forever.