I have spent more than a decade building products whose entire premise is that people want a boundary around their communication. Hushed exists because giving a stranger your real phone number is a decision you cannot take back.
That work has made me pay attention to a particular pattern, and I see it clearly right now with AI: the convenience arrives immediately and the exposure arrives later, usually to someone who had no say in the original decision.
A prompt is an upload
It does not feel like one. It feels like typing into a box. But pasting a contract, a customer list, a support transcript or a medical letter into a hosted model is a transfer of that data to infrastructure you do not control, under terms you probably did not read, retained for a period you cannot verify.
That is not an argument against using these tools. I use them. It is an argument for being clear-eyed that the question "is this useful?" and the question "who now has this?" are separate, and only one of them gets asked in the moment.
The delay is the whole problem
Privacy failures are rarely dramatic on the day they happen. Data gets collected because collecting it was easy and someone might want it later. Nothing goes wrong for a long time. Then there is a breach, an acquisition, a policy change, or a subpoena, and the data turns out to have been sitting there the whole time.
By then the person who pasted it has moved on, and the person affected is a customer who never knew the exchange took place.
This is exactly the shape of the problem I have watched play out with phone numbers for years. Nobody regrets giving out their number at the moment they give it out. They regret it eighteen months later.
What actually helps
The practical answers are unglamorous, and they are the same ones that have always worked.
Decide what categories of information never go into a hosted tool, and make that a short, memorable list rather than a policy document nobody opens. Prefer tools that will tell you plainly whether your inputs train their models, and treat vagueness on that point as an answer. Give people an approved option that is genuinely good, because if the sanctioned tool is painful they will quietly use their own. And check what your vendors retain, not what their marketing implies.
None of that slows a team down much. It mostly requires deciding once, in advance, rather than a thousand times in the moment by whoever happens to be typing.
The tools are extraordinary and I am not arguing anyone should avoid them. I am arguing that the bill for this arrives on a delay, and the organisations that come through it well will be the ones that were deliberate early — while being deliberate was still cheap.
