<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress.com" -->
<urlset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd"
	xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
	xmlns:news="http://www.google.com/schemas/sitemap-news/0.9"
	xmlns:image="http://www.google.com/schemas/sitemap-image/1.1"
	>
<url><loc>https://onlinejournalismblog.com/2026/08/18/how-to-judge-and-minimise-the-risk-of-using-sensitive-information-with-an-ai-chatbot/</loc><news:news><news:publication><news:name>Online Journalism Blog</news:name><news:language>en</news:language></news:publication><news:publication_date>2026-08-18T15:05:04+00:00</news:publication_date><news:title>How to judge (and minimise) the risk of using sensitive information with an AI chatbot</news:title><news:keywords>privacy, security, data retention, threat modelling, threat models, AI, artificial intelligence, reinforcement learning, ChatGPT, gemini, Henk Van Ess, Claude, tokens, knowledge cutoff, pretraining, RLHF, Copilot, extraction attacks, legal orders, reverse search warrants, anonymisation</news:keywords></news:news></url></urlset>