Know what’s on your site before a plaintiff’s firm does
A free privacy audit shows which cookies, pixels and trackers are running — and which ones commonly appear in privacy claims.
Spain’s data protection authority has put its thinking on data protection officers into one place. On November 19, 2026, the Agencia Española de Protección de Datos (AEPD) published El estatuto del delegado de protección de datos, a 59-page document with guidance on how DPOs should be appointed, how far their independence reaches, how they report to leadership, what protects them against dismissal and which other jobs can put them in a conflict of interest. The AEPD stresses that the text is not a regulation and creates no new obligations. It is still the clearest signal yet of what Spain’s regulator expects to see when it looks at whether a DPO can actually do the job.
TL;DR
- The AEPD published a non-binding guide on November 19, 2026, interpreting the DPO rules in Articles 37 to 39 of the GDPR and Articles 34 to 37 of Spain’s LOPDGDD.
- It reads those rules in light of three Court of Justice rulings (Leistritz, X-FAB Dresden and KISA) and a March 18, 2026, judgment of Spain’s Audiencia Nacional.
- Independence is split into four dimensions (functional, hierarchical, economic and organizational), and conflicts of interest are assessed case by case rather than through automatic bans.

What the AEPD published, and what it is not
According to the AEPD’s press release, the document pulls together the agency’s existing criteria on the DPO’s position in public and private organizations. Its legal anchors are Articles 37 to 39 of the GDPR, which cover designation, position and tasks, and Articles 34 to 37 of the Ley Orgánica 3/2018 (LOPDGDD), Spain’s data protection act. It reads both through the Court of Justice of the European Union’s judgments in Leistritz (C-534/20, June 22, 2022), X-FAB Dresden (C-453/21, February 9, 2023) and KISA (C-560/21, February 9, 2023), and through Audiencia Nacional judgment 139/2026 of March 18, 2026.
Early summaries described this as guidance on “complying with legal requirements.” That needs a qualifier. The AEPD says plainly that the text has no regulatory force and adds no obligations. What it does is explain how the regulator reads obligations that already exist. That still matters. A Spanish organization whose DPO arrangements depart from this reading should expect to explain why.
The agency says the draft went through two rounds of consultation with privacy professional associations, including the DPO Club of the Asociación Española para la Calidad, APEP·IA, ENATIC and ISMS Forum, as well as with public-sector DPOs. It also presents the guide as a response to the European Data Protection Board’s coordinated enforcement action on DPOs. The EDPB’s report from that action flagged conflicts of interest, weak independence, budget dependence and poor access to senior management.
Four kinds of independence
The guide takes Article 38(3) of the GDPR as its starting point: a DPO must not receive instructions on how to carry out their tasks and cannot be dismissed or penalized for performing them. It then breaks independence into four parts:
- Functional. No one tells the DPO what their advice or supervision should conclude.
- Hierarchical. The DPO reports directly to the highest level of management, such as the board or the chief executive.
- Economic. The role has enough resources, and pay is not structured in a way that could bend judgment. The guide gives the example of a bonus tied to financial results or company profit.
- Organizational. The DPO has real access to data, processes and systems, including the records of processing, impact assessments and processor contracts. They are also consulted early, at the design stage of new projects, including AI systems that process personal data.
The guide also makes a point that boards sometimes miss: appointing a DPO does not move accountability onto that person. Compliance stays with the controller or processor. The DPO advises and supervises, but does not decide on the purposes and means of processing. Our explainer on the difference between a data controller and a DPO covers that division in more detail.
Dismissal protection is strong but not absolute
On removal, the AEPD relies on the Court of Justice. In Leistritz, the Court held that Article 38(3) protects DPOs against decisions that end their role, put them at a disadvantage or amount to a penalty, as long as those decisions are linked to the performance of their tasks. All three judgments confirm that national law may add stronger protection, including a requirement of serious cause for dismissal, provided it does not undermine the GDPR’s aims.
Spain has done that. For a DPO who is part of the organization, the LOPDGDD provides that they cannot be removed or sanctioned for carrying out their functions unless they act with intent or gross negligence. The AEPD’s reading is that decisions affecting a DPO’s tenure, duties, resources or position should be judged by their practical effect, not their label. Before making such a change, the organization should ask for the DPO’s view, assess the impact and record its reasons.
The guide also tells DPOs where to go when pressure builds. They can escalate directly to senior management, use the internal whistleblowing channel, consult the supervisory authority or report the facts to it, and, where appropriate, go to court.
Conflicts of interest, role by role
Article 38(6) of the GDPR allows a DPO to hold other tasks as long as they do not create a conflict of interest. The AEPD does not publish a list of banned job combinations. It looks at what the person actually decides. The Audiencia Nacional judgment it cites points the same way: what counts are the functions actually assigned, especially where the designated person helps decide the purposes and means of processing they later have to supervise.
Roles the guide treats as likely to conflict include senior managers with operational responsibilities, an information security officer who decides on security measures, the person running the ethics and whistleblower channel, and data or AI leads with decision-making power. Roles that may be compatible, provided they involve no decisions on purposes and means, include legal advice, compliance, internal audit and transparency. Even there, the guide adds limits. A DPO who is asked to represent the organization before a court or in a data protection infringement proceeding is in a conflict, because that means defending the organization’s interests. A DPO taking part in financial risk decisions about individuals’ creditworthiness would also cross the line.
The guide also lists situations that need watching: an external DPO who also acts as a processor for the same client, a DPO carrying too many clients or roles, and a function without enough resources. For background on this tension, see our piece on the legal conflict of interest problem for DPOs.
A practical DPO independence checklist
Here is how an organization in Spain, or any EU organization that wants a defensible setup, could turn the AEPD’s guidance into concrete steps:
- Formalize the appointment at the top. Approve it at board or chief executive level, document it, and set out the role in a mission letter for an internal DPO or a contract for an external one. Spanish law also requires controllers and processors to notify the AEPD of the designation within ten days.
- Screen for conflicts before you appoint. Write down in advance which roles in your structure could conflict and how unforeseen conflicts will be handled.
- Fix the reporting line. Give the DPO a direct route to the highest level of management, and be able to prove that the communication happened.
- Check the pay plan. Remove variable pay tied to profit or financial targets that could influence the DPO’s objectivity.
- Fund the role. Provide budget, tools and support staff, plus outside legal or technical help when needed.
- Grant access by default. Give the DPO the processing records, DPIAs, processor contracts and systems they need, without requiring a new request each time.
- Bring the DPO in early. Make consultation a gate at the design stage of new processing, including AI projects.
- Record disagreements. When management rejects the DPO’s advice, document the reasons.
- Protect the channel. Make sure the DPO can use the whistleblowing channel to report pressure on their independence.
- Audit independence itself. Include the DPO’s position in your data protection audits, as the guide recommends.
The guide does not require a fixed reporting format or an annual report. It treats a yearly report to senior management, which cannot be edited or censored, as a good practice. France’s regulator has encouraged something similar, as we covered when the CNIL urged DPOs to produce activity reports.
Internal, external or outsourced
The GDPR allows the DPO to be an employee or a service provider. The AEPD’s guide applies to both, but it highlights two risks for the external model: a provider that also processes data for the client, and a provider spread across too many clients to give each one real attention. If you are weighing the options, our guide on how to outsource DPO work covers the contract terms that keep an external DPO independent. If you are still not sure whether you need one at all, start with whether your business needs a DPO. For groups dealing with non-EU establishments, our Article 27 representative and DPO guide explains why a representative and a DPO are different roles.
What comes next
The AEPD calls the statute an open document. The first planned addition is a set of good practices for resolving conflicts of interest in specific cases, prepared with the professional associations. The agency also plans to examine how DPO duties relate to AI-related responsibilities, so it can draw boundaries between them and protect DPO independence as organizations create AI governance roles. It has invited DPOs, organizations and associations to send feedback on how the document works in practice. The full text is available as a PDF on the AEPD website (in Spanish).
Frequently asked questions
Is the AEPD’s DPO statute legally binding?
No. The AEPD says it has no regulatory force and creates no new obligations. It explains how the agency reads the GDPR and the LOPDGDD, which are binding, so it is a strong indication of what the regulator will look for.
Can our general counsel also be the DPO?
Possibly, but only if the role is limited to advice and supervision with no decisions on purposes and means of processing. If the same person defends the organization in court or in data protection proceedings, the guide treats that as a conflict.
Can a DPO ever be dismissed?
Yes, for reasons unrelated to performing the role. The protection is not a guarantee of a job for life. In Spain, an internal DPO cannot be removed or sanctioned for doing the job unless they act with intent or gross negligence.
Does the guide apply outside Spain?
It is written for organizations under the AEPD’s supervision, but it relies on GDPR articles and Court of Justice case law that apply across the EU. It is a useful benchmark for any EU-based DPO program.
The bottom line
The AEPD’s message is that independence is something an organization must provide, not a personal privilege for the DPO. A DPO with a title but no budget, no direct line to the board and a bonus tied to quarterly results may meet the letter of an appointment while failing its purpose. Spain has now spelled out what the difference looks like.
Put this into practice
Turn privacy guidance into working controls.
Captain Compliance helps teams discover tracking technologies, enforce consent, manage privacy requests and document the evidence behind every decision.