More people use ChatGPT, Copilot, or Gemini for work every month. And more employers are asking: who uses what, and with which data? That is a fair question, because the organisation stays liable for what happens to personal data. But workplace monitoring is bound by rules. The GDPR does not decide whether you can monitor AI use. It decides how.
The short answer: yes, within limits
An employer can monitor whether staff use AI tools. The GDPR does not forbid it. What the GDPR does is set three conditions on any form of monitoring:
- A legitimate purpose. Monitoring "just in case" is not a purpose. Preventing customer or patient data from ending up in an unsecured tool is.
- Proportionality and necessity. The monitoring may go no further than needed for that purpose. If a less intrusive option exists, it takes priority.
- Transparency in advance. Staff must know that monitoring happens, what it covers, and why. That belongs in an AI policy or staff handbook, not in the fine print after the fact.
Quietly reading chats, recording screens, or logging keystrokes without anyone knowing is almost always unlawful. Only with a concrete suspicion of serious wrongdoing, and where no lighter alternative exists, can covert monitoring be defensible as a rare exception.
Why an employer wants to monitor at all
The trigger is usually not distrust, but liability. The Dutch data protection authority warns that a growing number of data breaches start when staff paste personal data into AI chatbots. When that happens, responsibility sits with the organisation, not the individual employee. As an employer, you cannot simply say afterwards that someone acted on their own.
This connects to GDPR for employee AI tools: an organisation needs to know which tools are in use, whether the vendor has a data processing agreement, and whether staff know what they can and cannot share. Some visibility into usage is sometimes necessary for that. But visibility is not the same as reading along.
What is allowed, and what is not
Usually allowed:
- Tracking which AI tools are approved for work and who holds a licence.
- Seeing, at an aggregate level, how often approved tools are used.
- Flagging when sensitive data is about to enter a prompt, without storing the full chat.
- Blocking or warning on unapproved tools, if that was communicated in advance.
Usually not allowed:
- Reading the content of personal chats by default.
- Continuously recording keystrokes or screens "to see what people do".
- Using monitoring as a disguised assessment of someone's performance.
- Keeping data longer than needed for the monitoring purpose.
The line sits at the volume and traceability of the data you collect. The more you record about an individual, the stronger your justification has to be.
The first two "usually allowed" points, tracking which tools are approved and seeing aggregate usage, are what BeeSensible's Shadow AI catalog is built for: every tool scored for risk, usage counted per tool rather than per person, and nothing pre-approved or pre-blocked until someone decides.