Daily PII Exposure Math
Cyberhaven research found that enterprise employees make an average of 3.8 sensitive data pastes into ChatGPT per user per day. For a 100-person support team, that is 380 instances of customer records entering ChatGPT every day.
Each instance can be a GDPR data minimisation breach under Article 5(1)(c). That article requires personal information to be "adequate, relevant and limited to what is necessary."
These are not rogue employees ignoring policy. The 3.8 figure reflects normal work. Agents copy customer emails to draft replies. They paste complaint text to get empathetic suggestions. They include account details to get context-aware answers. Each paste is a valid productivity step that happens to carry PII along.
Behavior Training Does Not Fix This
A 2024 EU audit found that 63% of ChatGPT user data contained personal identifiable information. Only 22% of users knew they could opt out via the tool's settings. Most content pasted into an AI assistant contains PII. Most users are unaware of the controls. The result is daily exposure at scale.
Policy training runs into a basic problem. The copy-paste habit is decades old. Users have been copying and pasting text since their first day at a computer. Plugging an AI chat tool in as a paste target adds a new destination. It does not change the habit.
A "do not paste customer PII into the AI assistant" policy asks agents to insert a classification step — "does this text contain PII?" — into a habitual action that has no natural pause. Training effects wear off. The cumulative result of 380 daily paste decisions is a compliance risk that policy alone cannot hold.
Where Technical Controls Work
The fix operates at the paste action itself. A browser extension intercepts clipboard content the moment the agent presses paste, before the text reaches the input field. The agent sees a preview modal. It shows what was detected and what will be anonymised before the text is sent.
This is not a blocking control. Agents can proceed, override, or stop. It is a transparency step. It adds one moment of visibility to an otherwise automatic action.
Consider a German e-commerce support team lead drafting replies to customer complaints. The workflow stays the same: copy the complaint, paste into ChatGPT, generate a reply. The extension adds a two-second check. The agent sees that names, addresses, and order numbers were detected. The agent clicks proceed. The tool receives the anonymised version. The compliance breach does not occur.
Our GDPR compliance guide covers the legal basis for these controls. See also our AI policy vs. technical controls comparison and the browser DLP for ChatGPT guide for implementation detail.