What should we ask a vendor about this?

What is kept, for how long, who inside the organisation can see it, and whether the answer differs on our plan. The last question is the one that changes answers most often, and asking it about the plan rather than the product avoids reassurance that turns out not to apply.

Is turning it off the responsible choice?

Only if you have somewhere sensible for the work to go instead. Removing continuity makes the tool markedly less useful, and the common result is people using personal accounts where it still works, which relocates the material rather than protecting it.

Does deleting undo what it learnt about me?

Not necessarily, because facts extracted and carried forward are frequently stored separately from the exchanges they came from. Products that do this generally offer a way to see and clear that store, and it is a separate control from deleting conversations, which is the part people miss.

Glossary

Conversation history

Conversation history is what a product keeps from earlier sessions, and the awkward part is that one setting governs two unrelated things: how useful it is and how much of your work it holds.

In plain terms

What the product keeps from the times you used it before. Keeping more makes it more useful, because you can return to something and it knows where you were. Keeping more also means a growing store of your work sits on somebody else's system, and the same switch usually controls both.

Why it matters

Because two genuinely different concerns are bundled into one choice, and people answer the convenience question without noticing they answered the other one. A year of work conversations is an unusually revealing record of what an organisation is doing, and it accumulates by default rather than by decision.

How it works

What is retained varies more than the interface suggests, and the categories matter. Some products keep the exchanges themselves, some keep separately extracted facts about you, some keep both under one label, and the second kind persists even where the underlying conversation was deleted.

Deleting from the interface and deleting from the systems behind it are not the same act. Removal from your view is immediate, and backups, logs and safety records frequently keep their own copies for their own periods, which is standard practice across software and is worth knowing rather than being alarmed by.

Continuity is the genuine benefit and it is substantial. Returning to a piece of work without re-establishing what it was is most of what makes a tool feel like a colleague rather than a service, and teams that switch it off usually discover that the friction they removed was doing real work.

The business and consumer versions of one product frequently answer this differently. Whether material may be used to improve the service, how long anything is held and who can see it across an organisation are plan-level questions, so a policy written about a product name rather than a plan is describing something nobody is actually using.

One switch, two questions

What makes this worth pausing on is the sheer difference in how the two questions feel. One is a preference about convenience, decided instantly and revisited whenever it becomes annoying. The other is a decision about where a detailed record of the organisation's thinking accumulates, which in any other setting would involve at least two departments. Bundling them is not a trick; it is a reasonable interface simplification that happens to hide the heavier of the two behind the lighter one. The practical response is not to agonise over the switch but to answer the second question once, deliberately, at the level of the organisation rather than the individual, and to say plainly what may be discussed in which account. That converts a thousand unconsidered choices into one considered one, and the switch afterwards can be set on convenience alone, which is what people were doing anyway.

Seen in the wild

A general assistant keeping related conversations, files and instructions together in projects, so returning to a piece of work does not start it again.
ChatGPT
An assistant with dedicated workspaces per workstream, where what was established in one place stays established.
Claude
A subscription reaching many systems at once, where each has its own arrangement for what it keeps and the account sits above them.
Poe

Common misconceptions

People assume

Deleting a conversation removes it.

In fact

It removes it from your view, and backups, logs and safety records commonly hold their own copies on their own schedules. This is ordinary practice rather than anything sinister, and it does mean deletion is not the eraser people picture when they rely on it.

People assume

Switching it off is the safe default.

In fact

It is the cautious default and it has a real cost. Continuity is most of what makes these tools feel worth using, and teams that turn it off frequently find their people quietly moving to personal accounts where it works, which is a worse outcome than the one being avoided.

Telling them apart

Conversation history vs Memory

Conversation history

The exchanges themselves, kept as a record.

Memory

Facts extracted from them and carried forward deliberately.

The second can outlive the first, which is why deleting a conversation does not always undo what it taught the product about you.

Questions

What should we ask a vendor about this?: What is kept, for how long, who inside the organisation can see it, and whether the answer differs on our plan. The last question is the one that changes answers most often, and asking it about the plan rather than the product avoids reassurance that turns out not to apply.
Is turning it off the responsible choice?: Only if you have somewhere sensible for the work to go instead. Removing continuity makes the tool markedly less useful, and the common result is people using personal accounts where it still works, which relocates the material rather than protecting it.
Does deleting undo what it learnt about me?: Not necessarily, because facts extracted and carried forward are frequently stored separately from the exchanges they came from. Products that do this generally offer a way to see and clear that store, and it is a separate control from deleting conversations, which is the part people miss.

Key takeaways

One setting governs convenience and exposure, which are unrelated concerns.
Extracted facts can outlive the conversations they came from.
Deleting from view is not deleting from every system behind it.
Continuity is doing real work; removing it has a cost.
The answers are plan-level, so a policy naming only a product describes nothing.