Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A data protection officer advises on data protection law, monitors compliance, and acts as the contact point for the ICO and for individuals, with statutory independence from the business.

What Does a Data Protection Officer Do?
A data protection officer is a statutory role created by Article 37 of the UK GDPR. The holder advises the organisation on data protection obligations, monitors whether it is actually meeting them, and serves as the point of contact for the Information Commissioner’s Office and for the people whose data is being processed.
The defining feature is independence. A DPO reports to the highest management level, cannot be dismissed or penalised for performing the role, and must not receive instructions on how to carry out their tasks. That protection exists because the job involves telling the organisation things it would prefer not to hear.
Under Article 37, a DPO is mandatory in three cases:
“Core activities” means processing that is inseparable from what the organisation does, not administrative processing such as payroll. A hospital’s patient records are a core activity; a manufacturer’s HR files are not. Many organisations appoint voluntarily, and the ICO’s position is that a voluntary appointment attracts the same statutory requirements, so the decision should be deliberate rather than casual.
Article 39 lists them. In practice the work divides as follows.
Day to day this looks like reviewing new processing proposals, maintaining the Article 30 record of processing activities, advising on international transfers and the lawful basis for new products, handling subject access requests, and taking a central part when a personal data breach occurs and the 72-hour notification clock starts.
Article 38(6) allows a DPO to hold other duties provided they do not create a conflict of interest. European and UK guidance has consistently held that anyone who determines the purposes and means of processing cannot be the DPO. That rules out the head of IT, the head of HR, the head of marketing, and in most cases the chief operating officer or chief executive.
The CISO position is more nuanced. A CISO who owns security systems and decides how personal data is protected is making processing decisions, so combining the roles is usually a conflict. The two roles overlap in breach response and in risk assessment, but they are not interchangeable: the DPO protects the interests of data subjects, while the CISO protects the organisation’s information assets. Those interests usually align and occasionally do not.
Article 37(6) permits a DPO to be an external contractor, which suits organisations that need the expertise but not a full post. The arrangement works when the contract gives genuine access to management, sufficient time, and a direct line into the governance structure. It fails when the external DPO sees processing proposals only after launch, which leaves them accountable for compliance they could not influence.
Whether internal or external, the appointment must be published and the contact details given to the ICO.
The Data (Use and Access) Act 2025 reforms parts of UK data protection law. Earlier reform proposals would have replaced the mandatory DPO with a less prescriptive senior responsible individual, and organisations should track how the final provisions and ICO guidance settle. In the meantime the Article 37 obligations stand, and organisations processing EU personal data will keep a DPO regardless of UK changes, because EU GDPR continues to apply to that processing.
One practical point is worth stating plainly: the DPO is not personally liable for the organisation’s compliance failures. Accountability under Article 5(2) sits with the controller. The DPO’s exposure is professional rather than legal, and an organisation that treats the role as a liability shield has misunderstood it.
Data protection advice needs technical evidence underneath it, particularly for DPIAs and breach assessments. Our regulation and compliance services help DPOs show that the measures described on paper exist in the systems.
No. UK GDPR requires one only for public authorities, for organisations whose core activities involve regular and systematic monitoring of individuals on a large scale, and for those whose core activities involve large-scale processing of special category or criminal offence data. Others may appoint voluntarily, but the ICO treats a voluntary appointment as attracting the same statutory requirements.
Usually not. A CISO who decides how personal data is protected is determining the means of processing, which creates the conflict of interest Article 38(6) prohibits. The same reasoning excludes heads of IT, HR, and marketing. Organisations that cannot find a conflict-free internal candidate commonly appoint an external DPO instead.
Yes. Article 37(6) allows the role to be fulfilled under a service contract, and this is common among small and medium organisations. The arrangement needs genuine access to senior management, enough contracted time to monitor compliance rather than just answer questions, and early involvement in new processing proposals rather than review after launch.
No. Accountability for compliance rests with the controller under Article 5(2), and enforcement action is taken against the organisation. The DPO advises and monitors; they do not decide. Their exposure is professional rather than legal. An organisation appointing a DPO to shift blame has misunderstood both the role and the protections attached to it.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.