When the law requires one
Under Article 37 of the UK GDPR, controllers and processors must appoint a DPO if any of these apply:
- You are a public authority or body, other than a court or tribunal acting in its judicial capacity.
- Your core activities need regular and systematic monitoring of people on a large scale, such as tracking online behaviour.
- Your core activities involve large-scale processing of special category data, or of personal data about criminal convictions and offences.
"Core activities" are the operations central to what you do, not support functions such as payroll or IT. The UK GDPR doesn't define "large scale" or "regular and systematic monitoring"; the ICO points to the Article 29 Working Party's guidelines on DPOs for how to judge them. If you decide you don't need a DPO, record your reasons.
You also need to publish your DPO's contact details and give them to the ICO.
If you don't have to
You can still appoint a DPO voluntarily. If you do, the same rules apply as for a required one, including independence. If you want a data protection lead without those duties, give the role a different title so no one mistakes it for a DPO.
Either way, you remain responsible for complying with data protection law. A DPO advises and monitors; they don't take on your accountability.
What a DPO does
Article 39 sets out the minimum tasks:
- Inform and advise you and your staff about your data protection obligations
- Monitor compliance, including policies, awareness, training and audits
- Advise on data protection impact assessments and monitor how they are done
- Co-operate with the ICO and act as its contact point
The DPO should take a risk-based approach, giving most attention to the processing that carries the highest risk. People can also contact your DPO about how you use their data and their rights (Article 38).
Independence and conflicts
Article 38 protects the DPO's position. You must:
- Involve the DPO properly and in good time in data protection matters
- Give them the resources they need, and access to personal data and processing
- Don't instruct them on how to carry out their tasks
- Don't dismiss or penalise them for performing their tasks
- Let them report directly to your highest level of management
A DPO can have other tasks, but not ones that lead them to decide the purposes and means of processing personal data. The ICO's example: a head of marketing who plans campaigns, including who to target and which personal data to use, can't also be the DPO. Roles that check compliance, rather than decide what processing happens, are less likely to conflict.
In-house, external or shared
The ICO confirms that you can contract the DPO role out, and that a group of organisations can share one DPO.
| Option | How it works | What to watch |
|---|---|---|
| In-house | An employee appointed as DPO, often alongside other duties | Their other duties must not involve deciding why and how personal data is used |
| External | An individual or firm appointed under a service contract | Same position, tasks and duties as an in-house DPO; check their capacity and experience |
| Shared | One DPO for a group of companies or public authorities | Must still be able to do the job for each organisation, and easy to contact |
Our DPO as a service starts at half a day a month. If you also need help with ISO/IEC 27001, ISO/IEC 27701 or AI governance, the fractional compliance retainer includes DPO appointment.
The Data (Use and Access) Act
The Data (Use and Access) Act 2025 kept the DPO requirement. Its change to Article 37 adds tribunals to the courts excluded from the public body test when acting in their judicial capacity. The ICO says its DPO guidance is under review because of the Act, so check it for updates.
Sources
- UK GDPR Article 37
- Designation of the data protection officer
- UK GDPR Article 38
- Position of the data protection officer
- UK GDPR Article 39
- Tasks of the data protection officer
- ICO: data protection officers
- The ICO's guidance, under review after the Data (Use and Access) Act