A company must appoint a data protection officer (DPO) in three cases set by the GDPR, and in a few cases specific to Belgium that are often overlooked: a contract with a federal administration, and use of the National Register number. Here is how to tell whether yours is covered, and what to do on the day someone asks for it.
In short
- The GDPR requires a DPO for public bodies. It also requires one for companies whose core activity is to monitor people or to process sensitive data, on a large scale.
- In Belgium, a private company that processes data for a federal public authority must also appoint one, if the processing may present a high risk.
- Using the National Register number under an authorisation requires a DPO.
- The DPO may be external. Their contact details are published and communicated to the Belgian Data Protection Authority (APD).
- The fine can reach €10 million or 2% of worldwide turnover.
When does the GDPR require a DPO?
In three cases, for the controller and for the processor alike (Article 37(1)).
| Case | Examples | Article |
|---|---|---|
| Public authority or body | Municipality, public social welfare centre, intermunicipal company, body mainly financed or controlled by public authorities | Article 37(1)(a) |
| Regular and systematic monitoring of people, on a large scale | Telecom operator, behavioural advertising, app that tracks location, loyalty programme, connected devices | Article 37(1)(b) |
| Sensitive or criminal data, on a large scale | Hospital, insurer, platform for exchanging medical data | Article 37(1)(c) |
Two notions decide everything. The core activity is what your business is about: paying your staff or providing IT support is not part of it. Large scale is assessed by the number of people, the volume of data, the duration and the geographical extent. A doctor or a lawyer practising alone does not process on a large scale. Neither does a small business filming its till.
Headcount does not matter. A company of ten people whose app monitors its users on a large scale is covered. A company of three hundred people that only processes the data of its staff and customers is not necessarily covered.
Which cases does Belgian law add?
Three cases, which also reach private companies.
A contract or assignment for a federal public authority. Two kinds of private body are covered: one that processes data on behalf of a federal public authority, and one to which that authority transfers data. It appoints a DPO where the processing may result in a high risk (Act of 30 July 2018, Article 21). High risk is the risk that triggers a data protection impact assessment (GDPR, Article 35). This covers, for example, a software publisher, a hosting provider, a call centre or a consultancy performing a federal contract with citizens' data.
The National Register number. Anyone authorised or empowered to use the National Register number must appoint a DPO. The DPO's identity is communicated to the Minister of the Interior. Their contact details are published and sent to the APD (Act of 8 August 1983, Article 10; GDPR, Article 37(7)).
Research. Some processing for scientific, historical or statistical research relies on the derogations in the Act. Its controller appoints a DPO where the processing may result in a high risk (Act of 30 July 2018, Articles 186 and 190).
When does the question come up?
Rarely when reading the GDPR. Almost always on the day someone asks you.
| The moment | What you are asked for |
|---|---|
| You bid for a public contract in which you will process data | Sufficient guarantees (GDPR, Article 28(1)), and a DPO if the authority is federal and the risk is high |
| A large customer sends you a data processing agreement | Your security measures, and the right to audit you (GDPR, Article 28(3)) |
| You apply to use the National Register number | The identity of your DPO |
| The APD writes to you, or you suffer a data breach | A contact: the DPO cooperates with the authority and acts as its contact point (GDPR, Article 39(1)) |
| Your DPO is away, or also holds a management role | A DPO who is available and free of conflicts of interest (GDPR, Article 38(6)) |
What does a company without a DPO risk?
Breaching the rules on the DPO is punishable by a fine. It can reach €10 million or 2% of total worldwide annual turnover, whichever is higher (GDPR, Article 83(4)).
The APD also looks at how the role is held. In 2020, it imposed a fine of €50,000 on a company whose DPO was at the same time head of compliance, risk and audit (decision 18/2020). In 2025, it found that a municipality had no DPO (decision 163/2025).
The most frequent risk lies elsewhere: the bid that is rejected, the contract that is not signed, the authorisation that is refused.
Internal or external DPO?
Both are allowed. The DPO may be a staff member or act under a service contract (GDPR, Article 37(6)). A group may appoint a single DPO, provided they are easily reachable from each establishment (Article 37(2)).
Three rules apply in both cases. The DPO receives no instructions about their tasks. They report to the highest management level (Article 38(3)). Their other tasks must not create a conflict of interests (Article 38(6)): the director or the IT manager who decides on the processing cannot be the one who checks it.
A company that is not required to appoint a DPO may do so. It then takes on all the rules of the role. If it prefers not to, it can name a contact person, without giving them that title.
What I do in practice
I am a certified data protection officer (ECPC-B, Maastricht University) and I act as an external DPO.
The online test tells you in six to nine questions whether your company must appoint a DPO. Nothing is sent to the firm.
The external DPO mandate starts at €390 a month excl. VAT for a small organisation, and at €2,200 for a complex entity. It can cover the absence of your own DPO, for an agreed period.
If you are not required to appoint a DPO, an advisory retainer is enough. For one and the same company, I am not both the DPO and the lawyer who advises.
Frequently asked questions
Does a company of ten people have to appoint a DPO?
That depends on its activity, not on its size. Article 37 of the GDPR sets no staff threshold.
Is an IT service provider covered?
Yes, if its core activity falls within one of the cases: the rules apply to the processor as they do to the controller (GDPR, Article 37(1)). And if it works for a federal public authority, Article 21 of the Act of 30 July 2018 applies as well.
Can the director be appointed?
No, if the director decides on the purposes and means of the processing: they would be checking themselves (GDPR, Article 38(6)).
Does the DPO have to be declared?
Yes. Their contact details are published and communicated to the APD (GDPR, Article 37(7)).
A tender, a customer or the APD is asking for your DPO? Write to me about your situation in three lines.
Sources
- Regulation (EU) 2016/679 (GDPR), Articles 28, 35, 37, 38, 39 and 83 (CELEX 32016R0679, EUR-Lex)
- Belgian Act of 30 July 2018 on the protection of natural persons with regard to the processing of personal data, Articles 5, 21, 186 and 190 (numac 2018040581, Justel)
- Belgian Act of 8 August 1983 organising a National Register of natural persons, Article 10, replaced by the Act of 25 November 2018 (Belgian Official Gazette of 13 December 2018, numac 2018032324)
- Belgian Data Protection Authority, "Lecture de l'eID"; GDPR guide for SMEs, January 2018; decisions 18/2020 of 28 April 2020 and 163/2025 of 10 October 2025
- Article 29 Working Party, Guidelines on Data Protection Officers (WP 243), annex
This article is general information, current as of 16 November 2026. It is not an opinion on your situation.
On this subject, see also the page GDPR and outsourced DPO: services, timing and fees.
Translated from the French original published on 16 November 2026. The analysis concerns Belgian and European Union law. Read the French original.
