Ask an organisation for its AI policy and you will usually get one within a day. Ask which data goes into one automated decision, on what legal basis, who receives it and what comes back out, and the answer takes three departments and a week. The policy exists. The trace does not.
AI governance is the ability to trace one automated decision from data input to outcome. Most organisations can produce a policy and a steering committee but not that trace, because the gap sits in the tag and container configuration. The EU AI Act high-risk obligations moved to 2 December 2027 and 2 August 2028, while the transparency rules have applied since 2 August 2026.
AI governance is the ability to trace an automated decision from its data input to its outcome, and to say whether that use is defensible.
It rarely starts with a governance question. It starts with something concrete from a marketing, IT or legal team. Can we use first-party customer data to improve conversion modelling? Does our consent cover this personalisation model? Can the chatbot access order history? What happens when an agent can call a tool or an API?
Those look like four questions for four departments. They are four versions of the same question: what data goes into an automated decision, for what purpose, who gets access, and what happens as a result.
The calendar changed. The work did not.
The Digital Omnibus on AI entered into force in July 2026 and moved the high-risk obligations to 2 December 2027 for Annex III systems and 2 August 2028 for high-risk AI embedded in regulated products. Four things did not move.
| What | Status |
|---|---|
| Transparency obligations for chatbots and AI generated content | Applied since 2 August 2026, with a short grace period until 2 December 2026 for marking content from systems already on the market |
| AI literacy obligation | Applied since February 2025 for providers and deployers |
| GDPR and ePrivacy on the data feeding these systems | Unchanged and in full force |
| Supervision | The Autoriteit Persoonsgegevens has named AI one of three strategic priorities for 2026 to 2028, with a shift towards early intervention during model development |
The deferral buys time on one set of obligations. It buys none at all on the data layer, which is where almost every organisation actually has a problem.
Because AI is no longer a project with an owner. It is a property of systems other people already bought.
For most companies AI now sits inside ad platforms and conversion models, personalisation engines, customer data platforms, customer service chatbots, office assistants, and increasingly agents that can call tools, read data through connectors and take actions. Nobody approved an AI project. A vendor shipped a feature.
That changes the nature of the risk. A model that generates the wrong sentence is a content problem. A system that reads customer data, triggers a workflow and decides something is a data protection problem, a contract problem and a measurement problem at the same time.
Ownership is fragmented by design. IT owns the tooling, legal owns parts of the rules, procurement owns the contract, and marketing or operations configure the platform. The data moves across all of them, which means nobody sees the whole flow.
At the gap between what the consent banner promises and what the tags actually do.
An organisation writes a privacy notice, configures a consent management platform, which is the software that shows the banner and records the visitor's choice, and considers the purpose question answered. Then a tag manager fires vendor scripts before consent, a server-side container forwards identifiers the notice never mentioned, and a conversion model is trained on data collected under a purpose that does not cover modelling.
Every model, recommendation engine and agent downstream inherits that gap. You cannot fix it at the model. It was created three steps earlier, in a container configuration no policy document has ever looked at.
Which is why the humble data map has quietly become an AI governance document. Not the version in a compliance folder, but the version that reflects the actual technical flow: which tag fires, on which signal, to which recipient, carrying which identifier.
Cloud Nine Digital measured exactly that distance on 5 October 2026 across 2,450 Dutch domains, of which 1,925 fall in six commercial sectors. On 596 of those 1,925, which is 31.0 percent, marketing tracking loaded before the visitor made any choice. The pattern is not malice. It is that nobody owns the distance between what the interface claims and what the flow does.
Because the unit of governance is the data flow, not the tool.
A list of AI tools tells you what your organisation has bought. It does not tell you which decisions those tools influence, or which data reaches them. Two companies can use the identical personalisation engine, one defensibly and one not, purely because of what is connected to it upstream.
Vendor language does not close that gap either. Claims such as privacy preserving, on-device, hashed, or not used for training are commercially useful and frequently true, but they are assertions until someone verifies them against the actual technical flow and the actual contract. Treating a vendor's marketing page as evidence is the single most common failure Cloud Nine Digital encounters in audits, which is an observation from implementation work and not a measured finding.
The person configuring the platform, not the committee approving the policy.
Most AI training is aimed at leadership. Meanwhile the daily governance decisions are made by the people setting up the ad platform, the chatbot, the customer data platform or the agent. Whether a conversion event carries a user identifier, whether a chatbot can reach the order database, whether an agent gets a write scope or a read scope: these are governance decisions, and they are made in a configuration screen on a Tuesday afternoon.
Train the operators. They make more governance decisions in a week than a steering committee makes in a year.
Five moves, and the last one is the test.
Brent Stevens is Commercial Director at Cloud Nine Digital, a data and analytics consultancy in Amsterdam and part of LevelUp Group that builds, validates and monitors data collection layers. Cloud Nine Digital measured what happens before the visitor's choice on 2,450 Dutch domains on 5 October 2026.
Cloud Nine Digital ranked first in the Data Science and Analytics Agencies category of the Emerce 100 in 2026, with 6 out of 7 stars, based on an image study by Motivaction among decision-makers in the Dutch market.
This article is not legal advice.
What makes the layer underneath this reliable is set out on the Cloud Nine Digital reference page What makes a data layer reliable at scale.
If you want to know whether one AI enabled decision in your organisation can be traced from data input to outcome, Cloud Nine Digital runs that trace as a fixed-scope assessment.