All news
Tech & AI August 18, 2026 4 min

The Dutch authority publishes a self-assessment for generative AI

A tool that walks the controller from choosing a system to governing its everyday use. It is not binding outside the Netherlands, but the questions travel

The Dutch data protection authority has released a self-assessment tool on generative AI systems: a path that takes an organisation through whether it has appropriate governance measures in place, how it picks a GDPR-compliant system, how it puts that system into service and how it supervises its use.

Why such a tool is needed now

The practical problem of these months is not prohibition: it is that generative AI enters organisations through the back door. Not with a project, but with a checkbox inside a business application the supplier has updated, or a subscription taken out by one department without passing by anyone. By the time the data protection officer notices, the processing has been running for months.

A self-assessment does not solve that, but it makes it discussable: it gives the DPO a document to put on the table that does not look like a personal objection, and gives the controller a sequence of questions to answer in writing.

The four decisions that have to be written down

The questions concentrate on four moments: whether there is any governance of the phenomenon before adopting a tool at all; on what criteria the supplier is chosen; on what conditions the system goes live; and who supervises its use over time. They are the same four points an inspection asks about — and the same four for which, usually, not a line has been written.

To be clear: the tool belongs to the Dutch authority and does not bind the others. It creates no presumption of compliance and does not replace the Article 35 impact assessment where one is due. But the questions are not Dutch: they are the ones a DPO would ask in Italy, in Portugal or in Norway.

What to actually do with it

The useful move is to treat it as an inventory, not an exam. A round of emails to clients with three questions — which generative AI tools are live, who authorised them, what data goes into them — almost always produces a surprise, and that surprise is the real starting point.

And keep the order right: first establish whether the processing is lawful and whether it needs an impact assessment, then choose the supplier. The reverse — system chosen, then an assessment written to justify it — is the fastest way to turn a legal duty into a fiction.

Looking for a workspace for your DPO work?

DPO Workspace is built by a certified DPO. 30-day free trial.

Start free

Related articles

Tech & AI
art. 9a face that pays is biometric data, not a password

Paying with your face: what changes when the key is you

From 24 to 26 September 2026 Revolut trialled a payment system in three London coffee shops that recognises a customer's face at the till and matches it against the selfie uploaded when the account was opened. Enrolment is opt-in, payments above £200 need a second check, and the company states it complies with UK GDPR. For a DPO the interesting part lies elsewhere: a face used to identify someone is biometric data under Article 9, and the privacy notice holds two distinct data — the biometric template and the photo taken at the till — with different deletion rules.

Sep 24, 2026New 7 min
Tech & AI
180AI products supervised over five years

180 AI products in five years: what the regulator asked

On 25 September 2026 the Irish Data Protection Commission published its report on the supervision of artificial intelligence products and services between 2021 and 2025. Around 180 products engaged on, thousands of pages of assessments read, and two points recurring in almost every file: legitimate interest as the basis for training, and the transparency of processing nobody manages to explain simply.

Sep 25, 2026 6 min
Tech & AI
680customers contacted, and no intrusion into the systems

The request came from a real government domain

On 12 September 2026 Revolut confirmed it had disclosed customer data in response to fraudulent requests sent from a legitimate government agency email domain. The data included dates of birth, addresses, phone numbers, copies of passports and driving licences, verification selfies, account statements and transaction histories. Around 680 customers were contacted. This is not an intrusion into the systems: it is a personal data breach by unauthorised disclosure, and it turns on a procedure almost nobody has written down.

Sep 23, 2026 6 min