Memory That Doesn’t Ask
OpenAI’s Dreaming update is a real convenience. For anyone running a business on these tools, it’s also a confidentiality question.
OpenAI began rolling out a new memory system on June 4. They call it Dreaming, and the pitch is continuity: ChatGPT now learns your preferences and projects in the background, so you stop reintroducing yourself at the top of every conversation. For most people that’s a real improvement. Starting from a blank page every time was the most tedious thing about the tool.
I’ve been running AI through my photography business since June of last year, which is long enough to have formed opinions about where the convenience stories hold up and where they leave something out. This is one that leaves something out.
The old memory was passive. It wrote down what you explicitly told it to remember, and not much else. The new system is active. In OpenAI’s own description, it synthesizes context from your chat history on its own, including information that comes up naturally in conversation rather than through a “remember this” instruction. It also acts on what they call implicit preferences, the things you never stated but that it inferred from how you work.
Read the announcement and the example they lead with is a vacation. You plan a trip, ChatGPT remembers your travel style, future trips get easier. That’s the version of the worry most people land on, too: is my vacation going to end up somewhere it shouldn’t.
It’s the wrong example. Not wrong exactly, just not the business example.
Here is the one that should concern anyone with clients. You write a proposal for Client X in ChatGPT. Next week you write one for Client Y, in the same account, because that’s simply how a person uses one login. The system isn’t storing a note that says “this pricing is confidential to X.” It’s building a working model of your projects and surfacing what’s relevant. And the moment relevance peaks, the moment the model is most ready to volunteer what it knows about your proposal work, is the moment you sit down to write the next proposal.
What crosses over necessarily isn’t a name you’d catch on a read. It’s a number. A scope assumption. A piece of positioning you developed for X, arriving fluent and on-topic in the draft for Y.
This is a different failure than the one I usually write about. Fabrication gets caught eventually, because some part of you stays alert to the invented detail that was never real. I’ve called that plausible fiction. This isn’t that. The detail here is real. It’s just real about the wrong client. Your accuracy radar never fires, because nothing is inaccurate. The content is correct. The context is the breach.
That’s what makes it slip. Bleed that reads as competent is the kind that clears review.
And the stakes clear a real bar. If X and Y compete, and in a narrow market they often do, two firms in the same city, two organizations chasing the same grant, this stops being a privacy curiosity and becomes a confidentiality exposure with NDA-shaped edges. The embarrassing version is your dinner preferences showing up in a work email. The serious version is one client’s terms shaping another client’s deal.
I’ve mentioned this before but it bears repeating. If your business works with confidential information, or even information that you’d rather not share, be certain you are using a subscription that respects your privacy. Check that they are not training future models on your quotes, communications, etc. If you are using a personal subscription rather than a business tier one, you are probably making a mistake.
The defense isn’t clever, and that’s the point. Keep client work in separate, governed spaces. Use Temporary Chat, which doesn’t read or write memory, for anything you don’t want synthesized into the general model of you. Read the memory summary page now and then, so you actually know what the tool thinks it knows. None of that is hard. It’s just deliberate, and deliberate is exactly what the convenience pitch invites you to stop being.
That’s the whole tension in a line. The casual user hears Dreaming and thinks, good, now I don’t have to bother. Run a business on these tools and the conclusion runs the other way. The bother was never overhead you could finally shed. The bother is the discipline that keeps one client’s work out of another client’s draft. It’s the moat.
The setting worth reviewing isn’t in the menu. It’s the assumption that convenience comes free.