When AI Chat History Bites
What do your AI chats say about you? Would you want someone else reading them and drawing their own conclusions? Maybe take a look at how long you keep them.
-
-
Worth Reading – The Hidden Dangers of AI Chat History
There’s the obvious privacy issue with public AI tools, but people often overlook another reality: at work, someone likely has the same access to your AI interactions as they do to your email and Teams messages. As a company using AI, you’re also responsible for all that data. You must protect it, keep it private, and, if required, collect it in response to a lawsuit or investigation.
Are you prepared to do that?
-
Shared Links (bi-weekly) Oct. 4, 2026
??? For more like this, subscribe to the newsletter and get these links and more in your email. Last year on the blog:
-
Worth Reading – AI is Forcing Organisations to ask Data Governance questions they have avoided for years
That’s exactly why IG professionals have been telling us to clean up our data. Too many people didn’t, and as mentioned in the link above, every AI meeting ends up being about governance.
We did our future selves a disservice by ignoring these questions for years, and now we have to either pay the piper or increase the risk exponentially by letting AI loose on this data.
What governance conversations are you having now thanks to AI?
-
Shared Links (bi-weekly) July 12, 2026
For more like this, subscribe to the newsletter and get these links and more in your email.
-
Worth Reading – EDRM Invites Global Community to Shape EDRM 2.0 via Public Comment
Those of you in the eDiscovery arena might already be aware of this new public comment period for the EDRM version 2.0. I took a quick look at it, and the one thing I will say is that I agree that eDiscovery is part of the Information Governance strategy for every firm, so I was glad to see that model as the underlying thread.
It also helps, when thinking about AI, to bring it into the full IG scope rather than considering it only as an eDiscovery problem. Because it’s likely not that big of an eDiscovery problem, yet, but it’s absolutely an IG problem.
