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

The question that exposes an analytics estate is simple: who could see this dataset last quarter? In most organisations the honest answer takes a week of investigation.

This page covers data governance and compliance for analytics estates in Antwerp: 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 ports, terminals and maritime, chemicals and process industry, and logistics and freight, 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 obligations that touch analytics most directly are data minimisation, storage limitation, access control, and the ability to answer access and erasure requests. 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 Antwerp

Antwerp's economy means the governance conversation here is not generic. With one of Europe's largest ports and the largest integrated petrochemical cluster in Europe after Houston shaping the local client base, these are the obligations that come up in practice.

Chemicals and process industry

REACH, CLP and environmental permit reporting all require auditable activity data with a documented calculation method. Continuous process data at high frequency, batch genealogy, yield and energy intensity, with safety and environmental reporting drawing on the same sources.

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.

Textiles, fashion and luxury goods

Supply-chain due diligence and product traceability obligations are expanding, and the underlying supplier data is rarely reportable today. Typical systems in scope: PLM, ERP, wholesale order management, retail EPOS and ecommerce platform.

Ports, terminals and maritime

Customs and security data is tightly controlled, and NIS2 applies to many port operators as critical infrastructure.

Who can see what, and how you prove it

This is the question that exposes an estate, and the fix is unglamorous. The difference is between an afternoon of investigation and a parameterised report. Individual grants accumulated over years require the first; groups that mirror your control model allow the second.

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 chemicals and process industry, the groups normally need granularity by function and by entity or site.

Classification, labels and the export problem

Most estates lose control of data at the export button. The intent is almost always benign, which is precisely why policy alone does not stop it. 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: defineOperating model with named owners and stewards, classification scheme, retention rules and access standards, agreed with legal and the business, not drafted in isolation.
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 Antwerp organisation.

We work across Belgium and deliver into neighbouring markets regularly. Nearby pages worth reading if your group has sites elsewhere: Sint-Niklaas, Bruges, Mechelen, Aalst, Kortrijk and Roeselare.

Frequently asked questions