Data governance and GDPR for Leuven organisations: controls that produce evidence

Most governance programmes we are asked to rescue failed for the same reason: they were designed to be complied with rather than to be useful.

This page covers data governance and compliance for analytics estates in Leuven: what the Data Protection Authority (APD / GBA) expects under the EU GDPR and the Belgian Data Protection Act of 2018, which sector rules bite hardest given the local economy of electronics and semiconductors, pharmaceuticals and biotech, and higher education and research, and how to implement controls in Microsoft Purview and Power BI that produce evidence rather than paperwork.

What the Data Protection Authority (APD / GBA) expects of an analytics estate

Under the EU GDPR and the Belgian Data Protection Act of 2018, the duties that bite hardest in analytics are minimisation, retention limits, access control, and being able to respond when someone asks what you hold or asks you to delete it. Analytics estates fail these quietly: a warehouse accumulates every column from every source because it was easier than deciding, retention defaults to forever, and permissions are granted to individuals who then change role.

• Belgium's federal structure means some reporting obligations sit with the regions (Flanders, Wallonia and Brussels) rather than nationally, which multiplies the datasets a single organisation must produce.
• Language legislation affects employee-facing systems: reporting used in employment contexts may need to be available in the language of the region where staff are employed.
• As the host of the EU institutions, Brussels has an unusual concentration of organisations working to EU-level reporting rules ahead of national implementation.
• NIS2 and DORA apply in full, and the Belgian transposition brings supervisory reporting duties for in-scope operators.

None of this requires a governance department. The working parts are a catalogue people search, classification that changes what happens to the data, access delegated through groups, and evidence on demand. None of that requires a governance function.

Sector rules that bite in Leuven

Leuven's economy means the governance conversation here is not generic. With one of the world's leading nanoelectronics research institutes and pharmaceutical research and manufacturing shaping the local client base, these are the obligations that come up in practice.

Electronics and semiconductors

Export control classification applies to many components and to the associated technical data. Very high volume test and yield data per die or unit, complex multi-stage processes, and component supply with long and volatile lead times.

The practical consequence for an analytics estate is that access design cannot be retrofitted. Row-level and object-level security have to reflect how authority is actually delegated in the organisation, and the design needs testing from a non-privileged account rather than assumed from documentation.

Higher education and research

Student data is personal data with additional duties around special-category attributes, and research data may carry funder-specific restrictions. Typical systems in scope: student records system, research grant management, finance system, virtual learning environment and HR.

Pharmaceuticals and biotech

GxP data integrity expectations (attributable, legible, contemporaneous, original, accurate) apply to analytics pipelines handling regulated data.

Who can see what, and how you prove it

This is the question that exposes an estate, and the fix is unglamorous. Permissions granted to individuals over several years cannot be evidenced without manual investigation. Permissions granted to directory groups that mirror your control model can be reported on in minutes.

The sequence is always the same: extract the permissions that actually exist, design groups around how the organisation really delegates authority, migrate and remove the individual grants, then make the evidence self-service so your second line runs the report instead of raising a request. For a business in electronics and semiconductors, the groups normally need granularity by function and by entity or site.

Classification, labels and the export problem

The leak is usually an export, not an attack. Someone needed the figures in a spreadsheet to do their job, and the spreadsheet then went somewhere nobody tracked. Sensitivity labels applied in Power BI travel with the exported file, so encryption and access restrictions persist outside the platform, and export can be blocked entirely for specific labels or audiences.

The classification scheme has to align to the information security policy you already have rather than introduce a competing taxonomy, and retention has to be enforced against your actual obligation under the EU GDPR and the Belgian Data Protection Act of 2018 instead of kept forever by default. Every control is then verified from a non-privileged account, because the most common finding in a governance review is a restriction that was configured correctly and never actually tried.

Working with Belgian organisations: the practical constraints

• Bilingual or trilingual stakeholder groups are the norm: plan for Dutch, French and English in the same programme.
• Works council and trade union consultation applies to systems that can monitor individual performance, similar to Germany.
• Many Belgian organisations operate as the European hub of a larger group, so local analytics has to reconcile with group reporting standards.

Belgium's federal structure means some obligations sit with the regions rather than nationally, which multiplies the datasets a single organisation must produce. Language legislation also affects employee-facing reporting, so the same report may need to exist in Dutch and French.

A 90-day plan that produces evidence

1. Days 1 to 15: assessAccess extract versus policy, data map, classification gaps, retention reality. Output is a risk-ranked remediation plan, ordered by exposure rather than by ease.
2. Days 15 to 35: defineNamed owners and stewards, a classification scheme, retention rules and access standards, all signed off by legal and by the business rather than written by the data team alone.
3. Days 35 to 70: implementPurview scanning and catalogue populated, labels published and applied, access rebuilt onto groups, lineage switched on, suppression implemented in measures.
4. Days 70 to 90: evidenceAccess evidence reporting, audit pack generation, steward training, and the first governance review run with your team rather than for them.

That sequence works because each stage produces something usable on its own. If the programme stops after the assessment, you still hold a risk-ranked plan an auditor would accept. Book a technical review if you want that assessment for a Leuven organisation.

We work across Belgium and deliver into neighbouring markets regularly. Nearby pages worth reading if your group has sites elsewhere: Louvain-la-Neuve, Ghent, Namur, Mons, Wavre and Brussels.

Frequently asked questions