GUIDE · GDPR

DPO: when to appoint one, what they do and their responsibilities

After this guide you will be able to tell whether your company must appoint a data protection officer, what tasks they must perform, how to choose between an internal figure and an external consultant, and why not everyone can take on the role. A key point: responsibility for processing always remains with the company.

Updated october 2026
8 min read
Altovar Technical Editorial Team

1. What a DPO is, and what it is not

DPO stands for Data Protection Officer. This role informs and advises the controller and its staff on privacy obligations, monitors that the regulation is applied and acts as a point of contact for the Garante and for data subjects. It is not the head of information security, nor a name to insert on an organisation chart for formality's sake. It can work alongside the IT department, but it is not part of it in an operational role.

A common mistake is to think the DPO is responsible for everything privacy-related. In reality the controller remains responsible for decisions on processing. The DPO advises, verifies and reports, but cannot take the company's decisions in its place. For this reason the role should be placed clearly within the organisation, with written duties and communication channels. Whoever appoints the DPO needs to understand this.

2. When appointment is mandatory

Appointment is mandatory in certain precise cases, which the regulation sets out. The first concerns public authorities and bodies. The second concerns controllers and processors whose core activities consist of processing that requires regular and systematic monitoring of individuals on a large scale. The third concerns large-scale processing of special category data, such as health data.

The concepts of core activities and large scale have no fixed numerical threshold and must be interpreted case by case. A small company may fall within scope if its core business is profiling or processing health data on a significant scale; a larger one may not if it handles data only marginally. Resolve the doubt with a written opinion, not an estimate based on instinct.

3. The minimum tasks of the DPO

The regulation lists the minimum tasks of the data protection officer. In practice these come down to four things: informing and advising the controller and staff on their obligations, monitoring compliance with the regulation and internal policies, providing opinions when requested, for example on data protection impact assessments, and cooperating with the supervisory authority by acting as its point of contact. These are advisory and oversight tasks, not operational management.

The DPO must carry out these tasks taking into account the risks associated with the processing, with priority given to the most sensitive activities. They must not be limited to a formal check once a year: they must be able to intervene when a new project touches personal data, before the decision is taken. In practice the typical activities are these. Each intervention should be recorded in a DPO activity log.

  • Keep the managers of functions that handle data informed and trained.
  • Check that the record, privacy notices and supplier contracts are up to date.
  • Give opinions on data protection impact assessments and processing choices.
  • Follow up requests from individuals and breach reports.
  • Serve as the point of reference for the supervisory authority and for anyone seeking clarification.

4. Independence and conflicts of interest

The DPO must be able to work independently and must not receive instructions on how to carry out their tasks. They cannot be someone who decides the purposes and means of processing, because they would end up checking themselves. In practice, the head of IT, the head of human resources or the marketing head, who decide on processing, are generally not suitable candidates for this role.

The conflict assessment must be made case by case and documented. If the company chooses an internal DPO, it must give them time, resources and a direct channel to senior management. If it chooses an external consultant, it must verify that they have no other engagements that create a conflict with their role towards the same company. The time dedicated must be proportionate to the complexity of the processing.

5. Internal or external: how to choose

There is no single answer. An internal person knows the company and its processes, but needs adequate skills, available time and genuine autonomy. An external consultant brings experience across several organisations and an independent perspective, but needs time to understand the organisation and must be involved on an ongoing basis, not only when a problem arises. An occasional consultancy rarely covers all processing activities.

Whatever the choice, the appointment must be formalised in writing and the DPO's contact details must be stated in the privacy notice. The modalities for communication to the authority and the minimum content of the appointment document should be verified with your consultant, because they change over time and depend on the case. Ask in writing which procedure will apply in your case and within what timescales.

OptionAdvantagesLimitationsWhat to check
Internal DPOKnows processes and people, quick responseRisk of conflict of interest and often limited timeIndependence, training and resources assigned
External DPOExpertise across several organisations and independenceOperational knowledge is slower to build, variable availabilityOther engagements, response times, confidentiality
Privacy consultant without appointmentFlexible and proportionateDoes not replace an appointment when one is mandatoryWho holds responsibility and whether an appointment is due

6. Responsibility: what stays with the company

Appointing a DPO does not transfer responsibility. The controller remains responsible for ensuring and demonstrating compliance, deciding on measures, keeping records and answering to the authorities. If the company decides differently from the DPO's opinion, it must document the reason for its choice. The DPO, as a rule, is not personally liable for the company's compliance; any individual liability should be clarified with a legal adviser. This distinction should be explained to whoever appoints them.

For this reason the relationship must be formalised in a written appointment, with duties, resources and communication channels. A DPO who discovers problems and is not listened to, or who does not receive the information they need, cannot fulfil their role. The appointment document is also the first thing an inspection will ask for. Keep it together with the record of processing activities.

7. How to start

This week, answer two questions in writing: does your business process special category data on a large scale or systematically monitor individuals? And does whoever currently handles privacy have enough time and autonomy to do it? The answers tell you whether appointment is probably mandatory and whether the current person is suited to the role. Write down the reasons for your answers too.

Then bring the answers to a consultant for a written assessment. If a DPO is needed, define the type of engagement, the expected time and to whom they will report. A clear role, even a modest one, is far more useful than a generic appointment letter signed and forgotten in a drawer. The role should be reviewed each time the organisation, processing activities or main suppliers change.

Frequently Asked Questions

Must a small company always appoint a DPO?

No. Appointment is mandatory only in the cases the regulation specifies, such as public authorities, large-scale systematic monitoring or large-scale processing of special category data. A small company can fall within these if its main processing is of that kind. If you do not fall within them, you can still have a privacy point of contact, which is good practice.

Can the head of IT also act as DPO?

As a rule, no. The head of IT often decides how data is processed and which systems are used, so they would end up checking themselves. The DPO must be independent of decisions on processing. It can be another employee with adequate skills, or an external consultant, always verifying that there are no conflicts of interest.

Is the DPO liable if the company breaches the regulation?

As a rule, compliance remains the controller's responsibility. The DPO advises and verifies, but does not decide for the company. Any personal liability depends on role, contract and actual conduct, and should be clarified with a legal adviser. For this reason the engagement must be in writing, with clear duties and limits.

Do I need to tell the Garante the DPO's name?

Where appointment is mandatory, the regulation requires the DPO's contact details to be communicated to the supervisory authority. The practical procedure should be verified with your consultant, because it may change over time. Once a DPO is appointed, their contact details must also be included in the privacy notice given to individuals.

Does an external DPO cost more than an internal one?

It depends on the scope, the time required and the complexity of the processing. There is no standard figure. Compare offers based on the same activities, specifying timescales, availability in case of an incident and what is included in the fee. A low price with no availability in an emergency can end up costing far more at the moment it is needed.

Can I appoint a DPO shared by several companies?

The regulation allows, in certain cases, a single DPO for several entities, provided they are easily reachable and able to carry out the tasks for each of them. The choice should be assessed with a consultant, because it implies obligations of availability, competence and separation between the organisations involved.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →