By · Last updated 2026-05-29

Back to BlogGDPR & Compliance

APD Belgium: IAB, Finance & NIS2

Belgium's APD issued the landmark IAB Europe consent ruling affecting the €220B digital ad industry. 82 enforcement decisions in 2024.

May 29, 20268 minute read
Belgium APDIAB EuropeGDPR financial sectorNIS2 complianceEU data protection

APD Belgium: IAB, Finance & NIS2

Belgium's data watchdog holds a unique spot in the EU. The country hosts EU and NATO head offices. It has more global banks and financial bodies than any EU state except Luxembourg. That gives the Autorité de protection des données/Gegevensbeschermingsautoriteit (APD/GBA) wide reach and clout.

The IAB Europe Ruling

In February 2022, Belgium's regulator ruled against IAB Europe. The case was about the Transparency and Consent Framework (TCF). The TCF drives about €220 billion in EU digital ads each year.

What the watchdog found: The TCF consent string is personal data. It ties to a user's pseudonymous ID. IAB Europe was named a joint controller. This made it liable for how publishers and ad firms use that data.

The €250,000 fine was small. The real impact was far bigger. The authority required a full TCF redesign. Every EU publisher using a consent tool felt this. So did every ad buyer.

The lesson: whole-sector tech can breach GDPR. It is not just lone firms at risk. The whole chain can be held to account. No link in that chain is safe from scrutiny.

Financial Sector: NIS2 and GDPR Together

Belgium is home to the EU Banking Authority, EIOPA, and the SWIFT global hub. Banks and insurers there must meet both GDPR Article 32 and NIS2 Article 21. These two laws share much ground.

NIS2 Article 21 sets out these rules:

  • Risk checks in human, physical, and digital areas
  • Incident reports filed within 24 hours
  • Business recovery plans
  • Supply chain security checks
  • Encryption for data in motion and at rest
  • Multi-factor access controls

GDPR Article 32 sets out these rules:

  • Data masking and encryption of personal records
  • Ability to restore access after an incident
  • Regular testing of security controls
  • Risk-based technical safeguards

These controls appear in both laws: encryption, access control, incident response, and supply chain checks. Strong GDPR Article 32 programs meet most NIS2 Article 21 needs too. One set of joined-up controls is the most efficient path. See our GDPR compliance guide for a full review of both laws.

Enforcement in 2024: Key Themes

Belgium's regulator issued 82 decisions in 2024. Financial sector cases rose 56% from 2023. Four themes stand out.

Profiling without consent: Banks using transaction data for spending analysis or product offers must meet GDPR rules. The watchdog rejected "service improvement" as a valid reason when profiling relies on such data.

AI credit scoring: GDPR Article 22 governs automated credit decisions. It demands human review and clear reasons. Several fintech firms lacked these safeguards. This was a key focus.

Post-merger data merges: Banks that merged records after buyouts often broke purpose rules. The original consent did not cover the new combined use.

Outsourcing without transfer tools: Firms that sent IT work to third countries without proper legal tools faced action. Cases covered India, Morocco, and the Philippines.

For firms with Belgian banking ops: joined-up GDPR and NIS2 controls are the best defense before an audit. Our security and compliance overview covers how zero-knowledge design cuts exposure at the source.

Sources

Ready to protect your data?

Start anonymizing PII with 285+ entity types across 48 languages.

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

Related reading

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our servers live in Falkenstein, Germany.

We use Hetzner. They hold ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

We run a full check suite on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We track recall and precision on a labelled set.

Bad runs block the deploy.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

You can top up at any time.

Unused credits roll over each month.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.