The Risk You Approved Is Not the Risk You Run
Most boards still picture AI risk as a decision they make: which model to license, which vendor to trust, which contract to sign. That picture is now wrong. The exposure that matters most is the one no one approved. Verizon's 2026 Data Breach Investigations Report found that regular AI use on corporate devices tripled in twelve months, from 15 to 45 percent of employees, and that two thirds of those people reach the tools through personal accounts that sit entirely outside enterprise control.
This is Shadow AI: capable software adopted faster than any policy can keep up. It is now the third most common non-malicious insider action that data loss prevention systems flag, a fourfold jump in a single year. The people doing it are not careless. They are productive employees solving real problems with the best tool in front of them. That is exactly why a memo will not stop it.
Your Source Code Is the First Thing to Leave
When the same report ranked what employees actually paste into public AI tools, source code led every other category by a wide margin, ahead of images and structured data. The blunt way to read that finding is this: source code in a public model is intellectual property in someone else's training pipeline. For a company whose advantage lives in its code, its pricing logic, or its client records, that is not a hypothetical. It is a daily, invisible transfer of the assets you are paid to protect.
The damage does not announce itself. There is no breach notification, no ransom note, no dramatic outage. A model simply gets a little better at reproducing the thing you thought was yours, and one day a competitor's prompt returns something that feels familiar. By then the question is not how to recover the data. It is whether you can even prove it left.
The Regulator Already Told You What to Do
On 15 June 2026 the European Data Protection Supervisor reframed Shadow AI as a compliance problem, not a help-desk one. Data entered into unapproved tools falls into a regulatory blind spot: no agreement on the legal basis for processing, no clarity on retention, no safeguard for international transfer, no transparency about whether it trains a model. Under the GDPR, a blind spot is not a defense. It is an open finding waiting for an auditor.
What the EDPS did not recommend is a ban. It said the answer is active management: define what AI use is authorized, classify the data that may never leave, enforce technical controls, and give people an approved tool good enough that they stop reaching for the unapproved one. Prohibition fails because it does not change the incentive. It only moves the same behavior somewhere you can no longer see it.
Read next: The Works Council Can Veto Your AI · Your AI Agent Can Now Spend Your Money. The Hard Part Is Everything That Happens After.