Most people think about privacy in terms of what they reveal, but in practice, the more interesting question is who can connect what they reveal.
A phone number used for a restaurant reservation may also be attached to a delivery account, a loyalty program, an old event registration and a professional profile, turning several ordinary pieces of information into a reliable identifier. None of those organizations needs to have done anything particularly intrusive, and no single record is especially revealing, but once the records can be connected, they begin to describe a person rather well.
This is where security professionals often think in terms of compartmentalization. The objective is not to make information disappear, which is usually impossible, but to prevent every interaction from automatically pointing back to the same identity.
If a high-profile person is traveling for a few days, the hotel may need to know who the guest is, but it does not necessarily need to know where they are having dinner tomorrow. The restaurant needs to know how many people are coming and when, but it may have no reason to know which hotel they are staying in. The driver needs a pickup location and a time, but there is little operational value in handing over the person's complete itinerary.
The person coordinating the trip, however, may legitimately need to know all of it.
This is the familiar security principle of need-to-know, but it is surprisingly easy to abandon in ordinary life because convenience rewards the opposite behavior. People sometimes forward the entire itinerary rather than extracting the one detail someone needs, give a restaurant a personal phone number because the booking agent asks for it, and use the same email address everywhere because, frankly, remembering seventeen identities sounds like a punishment invented by an unusually vindictive system administrator.
There is another reason this matters: information rarely stays where it was first given. An itinerary copied into an assistant's calendar may become part of a shared schedule, a pickup detail may be passed to a driver, a booking may be entered into another system, and a phone number supplied for convenience may become another identifier attached to the same person. None of these transfers necessarily involves negligence or bad intentions; information simply acquires a life beyond the purpose for which it was originally disclosed.
Good operational security therefore asks not only who can access information, but how far that information needs to travel.
For most people, this is primarily a privacy issue. For people who are highly visible, politically prominent, or responsible for someone who is, it can become a security issue.
This is also why something as simple as a booking alias can have value when used appropriately. An alias does not necessarily mean inventing a fictional identity, and it certainly does not mean using a false name where a legal identity is required.
In security terms, the more useful idea is pseudonymization: using a secondary identifier that allows a service to recognize and deal with you without automatically connecting that interaction to the identity you use everywhere else. That might be as simple as a separate email address or phone number for reservations, or a consistent booking name where a service permits one.
A hotel may still require your legal name and identification, an airline certainly will in most circumstances, and a payment provider may still know exactly who you are. The value of the alias appears elsewhere, in a guest list, a reservation made on someone’s behalf, or any other interaction where your full public identity is simply not necessary. Used properly, an alias is not a disguise; it is a boundary.
There is a subtle shift in perspective here: instead of asking “Who knows where I am?”, ask “Who knows enough to work out where I am?”
Modern privacy is increasingly less about keeping every individual fact secret and more about controlling the relationships between facts. You may not be able to stop a service from knowing what it legitimately needs to know, but you can be deliberate about whether those pieces of information are allowed to form a single, easily searchable picture of your life.
The objective is not to become invisible. It is to make unnecessary connections harder to establish.
