The Spanish Data Protection Agency (AEPD) today published a 59-page guide on the legal position of data protection officers, setting out how organisations should appoint them, how far they must be shielded from pressure, and which other jobs they should not hold. The head of the marketing department is among the senior posts the agency considers, as a rule, incompatible with the role.

The reasoning is structural rather than personal. A data protection officer, or DPO, advises and supervises; a marketing director decides. According to the guide, the head of marketing's functions "involve taking decisions relating to the determination of the purposes and means of the processing of personal data for, for example, campaigns, product development, customer management, market research, profiling of individuals, etc." Someone in that seat would end up supervising their own choices.

The document is titled "El estatuto del delegado de protección de datos. Orientaciones sobre el marco de actuación, independencia, garantías organizativas y conflictos de intereses" - in English, "The Statute of the Data Protection Officer. Guidance on the framework for action, independence, organisational safeguards and conflicts of interest". The AEPD published it in Spanish. Quotations in this article come from an English translation of that text.

In Short

Spain's data protection authority today published guidance on how organisations should appoint and protect their data protection officers, and which jobs clash with the role, naming the head of marketing among them. It matters to the advertising business because Spanish law already obliges firms that profile people for advertising, commercial prospecting or market research to have a DPO, and the guide now spells out who cannot fill that seat and what counts as pressure on whoever does. The text creates no new obligations, but it shows how the AEPD reads the existing ones, including when a lost budget, a broken reporting line or a profit-linked bonus can compromise a DPO's independence.

Interpretation, not new law

The guide is careful about its own status. Its stated purpose is "to offer interpretive criteria that facilitate the application of the safeguards provided for in Articles 37 to 39" of the General Data Protection Regulation and Articles 34 to 37 of Organic Law 3/2018 of 5 December, Spain's data protection act, known as the LOPDGDD. "Consequently, it neither introduces new obligations nor imposes a single organisational model," the foreword states.

That foreword is signed by Lorenzo Cotino Hueso, President of the AEPD, and Francisco Pérez Bes, the agency's Deputy. It addresses two audiences at once: DPOs themselves, and the controllers, processors and governing bodies that appoint them. "Independence in the performance of this function is an institutional guarantee whose effectiveness it is for each organisation to ensure," the text reads.

The legal footing is drawn widely. The guide relies on three judgments of the Court of Justice of the European Union - Leistritz (C-534/20, 22 June 2022), X-FAB Dresden (C-453/21, 9 February 2023) and KISA (C-560/21, 9 February 2023) - and on a Spanish Audiencia Nacional judgment of 18 March 2026. It also examines material from the European Data Protection Board, the European Data Protection Supervisor and supervisory authorities in France, Belgium, Italy, the Netherlands, Ireland, Finland, Denmark and Sweden, as well as ISO 37009:2025, the International Organization for Standardization's September 2025 standard on conflicts of interest in organisations.

The trigger for much of this work sits in Brussels. The EDPB's coordinated enforcement action on the designation and position of DPOs, whose report was adopted on 16 January 2024, stressed "conflicts of interest and the lack of independence of the DPO", according to the guide. In its press release, the AEPD said it took part in that action and that the report also identified budgetary dependence and difficult access to senior management.

Who must appoint a DPO in Spain

Article 37 of the GDPR makes a DPO compulsory for public bodies (courts acting in their judicial capacity excepted), for organisations whose core activities involve large-scale processing of sensitive data or criminal records, and for those that carry out "regular and systematic monitoring of individuals on a large scale". The guide gives two examples of the latter: video surveillance and "user profiling on social networks".

Spain goes further. Article 34(1) of the LOPDGDD, reproduced in full in the guide, names 16 categories of entity that must designate a DPO in any event. Two of them sit squarely inside the advertising business. Point (d) covers "information society service providers when they build profiles of service users on a large scale". Point (k) covers "entities carrying out advertising and commercial prospecting activities, including commercial and market research, when they carry out processing based on the preferences of data subjects or engage in activities involving the profiling of data subjects."

For a business in advertising, commercial prospecting or market research, preference-based processing or profiling is therefore enough on its own to make a DPO mandatory under Spanish law. Unlike points (c) and (d), point (k) carries no large-scale qualifier, and it applies independently of the GDPR's large-scale monitoring test.

Point Entities that must designate a DPO under Article 34(1) LOPDGDD
a Professional associations and their general councils
b Educational establishments at any level, and public and private universities
c Electronic communications network operators and service providers, when they process personal data regularly, systematically and on a large scale
d Information society service providers that build profiles of service users on a large scale
e Entities covered by Article 1 of Law 10/2014 on credit institutions
f Financial credit establishments
g Insurance and reinsurance entities
h Investment services firms
i Distributors and suppliers of electricity and natural gas
j Entities responsible for common files on financial solvency and credit, or on fraud prevention, including anti-money laundering files
k Advertising and commercial prospecting entities, including commercial and market research, when processing is based on data subjects' preferences or involves profiling
l Healthcare centres legally obliged to keep patients' medical records (individual practitioners excluded)
m Entities that issue commercial reports that may refer to natural persons
n Online gambling operators
ñ Private security companies
o Sports federations when they process data of minors

Source: Article 34(1) LOPDGDD, as reproduced in the AEPD guide. Organisations outside the list may appoint a DPO voluntarily under Article 34(2), and are then subject to the same regime.

Article 34(3) sets a short clock. Controllers and processors must notify the AEPD, or the relevant regional authority, "within ten days, of the designations, appointments and dismissals of data protection officers, both where designation is mandatory and where it is voluntary." The guide reads that obligation as covering terminations too, warning that a failure to update the register leaves "the former DPO as the visible interlocutor with the supervisory authority, data subjects or third parties despite their relationship with the organisation having effectively ended."

How designation works, according to the guide

According to the AEPD, the designation process "must be formal, documented and transparent", whether the DPO is a single person or a collegiate body. The guide sets out seven phases.

  1. Identify the obligation. The organisation assesses whether Article 37 GDPR or Article 34 LOPDGDD applies to it.
  2. Define the profile. The guide links the profile to size (a part-time external DPO "may suffice" in an SME; a large company may need an internal team), complexity of processing, sector and knowledge of the organisation.
  3. Assess suitability. The suggested parameters cover knowledge and experience, independence, availability, resources and certifications. One of the independence questions asks whether any other team or unit handles data protection matters that do not belong to the DPO.
  4. Formalise the designation. The governing body approves the appointment. In the private sector, according to the guide, that means the board of directors, chief executive, general manager or a person empowered by special power of attorney. The written designation records the DPO's name and contact details, functions under Article 39 GDPR, scope, duration if temporary, resources (budget, team, tools) and "guarantees of independence". The organisation then communicates it to the AEPD, to employees and to data subjects, and publishes the contact details as Article 37(7) GDPR requires.
  5. Apply the Article 39 tasks. These are informing and advising, monitoring compliance, advising on and monitoring the data protection impact assessment, cooperating with the AEPD, and acting as contact point for supervisors and data subjects. The guide warns against the reading that designation makes privacy the DPO's exclusive responsibility: "Under no circumstances can the formal designation of a DPO be understood as a transfer of the responsibility for regulatory compliance that the GDPR and the LOPDGDD assign to the controller or processor."
  6. Plan for termination. Notifications cover dismissals as well as appointments, and the guide suggests a collegiate "privacy office" as a way to keep the function running through absences.
  7. Follow good practice. The EDPB and the AEPD list a high administrative level (levels 28 to 30 in Spain's General State Administration), a "Letter of Mission (Carta de Misión)" for internal DPOs or a clear contract for external ones, a place on the organisation chart, a data protection office or committee for continuity, a conflict-of-interest check before appointment, designation by the board or general management, direct reporting to senior management, no operational functions that may create conflicts, and sufficient budget, tools and team.

The guide anchors the last phase in case law. Audiencia Nacional Judgment 139/2026 of 18 March 2026 (ECLI:ES:AN:2026:1355), according to the AEPD, "confirms the need to examine the functions actually assigned to the person designated, especially when they take part in decisions that determine the purposes and means of the processing they must subsequently supervise". The judgment upheld an AEPD sanction of 19 July 2023 over the appointment of the secretary of a professional association as its DPO.

Independence, in five parts

Article 38(3) of the GDPR is the core text. It provides that the controller and processor "shall ensure that the data protection officer does not receive any instructions regarding the exercise of those tasks. He or she shall not be dismissed or penalised by the controller or the processor for performing his tasks." The guide breaks that guarantee into five parts.

Functional independence

A DPO cannot be told what conclusion to reach. "For example, if the DPO identifies and assesses a risk in a data processing operation, they cannot be pressured to minimise it, ignore it, avoid it or reconsider their assessment." Reports, recommendations and alerts must not be "modified or censored by the organisation".

Hierarchical independence

The DPO reports to the highest level - in the private sector, to general management or the board. Where an organisation has separate administrative and management bodies, the guide recommends reporting to both.

Conflicts of interest

The guide cites ISO 37009:2025 and asks controllers to "draw up internal rules that allow possible conflicts of interest to be identified and properly managed", ideally before the DPO is appointed. Its two headline examples are being head of a department that processes personal data, such as marketing, HR or IT, and taking "the final decision on the implementation and configuration of a video surveillance system".

Economic independence

This section matters for anyone who designs pay structures. "The DPO must have adequate remuneration and stability in the post to avoid economic pressure," the guide states. It then adds: "A bonus or variable remuneration linked to financial results or business profit could also affect their independence, as it could influence their objectivity." A DPO who was the majority shareholder of a company supplying data processing services to the organisation would face the same problem, according to the AEPD.

Organisational independence

The DPO needs "material access to all the data, processes and systems necessary", including records of processing, impact assessments and processor contracts, plus staff, tools and a budget for training and outside advice. Early consultation is part of it: the guide's example is that DPOs "must contribute their advice at the design stage of a new AI system that processes personal data." The DPO must also have access to the organisation's whistleblowing channel to report pressure on their own independence.

Where marketing, ad tech and procurement come in

The guide calls it "the main practical rule": "if a role within the organisation, directly or indirectly, defines, participates in or approves the purposes and means of the processing of personal data, that task rules out designation as DPO." Deciding those purposes and means belongs to the data controller - "the exclusive competence of the controller", in the guide's words - which is why the DPO cannot share it.

Following the Article 29 Working Party's WP243 guidelines, later endorsed by the EDPB, the AEPD lists chief executive, chief operating officer, chief financial officer, chief medical officer, head of marketing, head of human resources and head of IT as posts that "are, as a rule, considered incompatible with the DPO function". Seniority is not the test. "Even lower posts in the organisational structure may create a conflict if they involve, directly or indirectly, determining the purposes and means of the processing."

Several passages touch commercial data work even more directly than the marketing-director example:

  • Market research and customer selection. In the section on internal audit and risk, the guide states that "a conflict of interest would arise if the DPO took part in financial risk management and made decisions on data subjects' financial capacity, or if they took part in a market audit or investigation involving analysing and selecting potential customers according to certain consumer profiles, for the purpose of generating those profiles."
  • Vendors that sell DPO services. When a data processor or sub-processor also acts as DPO, it would be advising on its own processing. The guide describes a product or service that bundles DPO functions with the processing itself, and concludes that "its advice and supervision would be worthless, as it could amount to an obvious situation of conflict of interest."
  • Platform configuration. A DPO who works with IT "on the default configuration of platforms and on decisions relating to the information those platforms will collect about natural persons or the retention period of log data" would be configuring systems they later supervise.
  • Procurement. "In no case is it for the DPO to decide on the acquisition of a product or service, take decisions relating to the configuration of that product or service, or act as the controller's representative in procurement processes." The DPO should, however, advise before requirements are drawn up, including on international transfers and Article 28 processor contracts.
  • Cheap, crowded DPO-as-a-service. Where one DPO serves many controllers, the guide says the conflict risk "multiplies when serving multiple controllers and processors is done at abnormally low costs". The conclusion calls such fees "derisory or recklessly insufficient".

Who, then, can hold the post? The guide's answer is roles that "focus on advice, verification or audit, but have no decision-making capacity over the purposes and means of the processing of personal data" - legal advice, compliance, internal audit, risk management, quality and transparency - and even then only after a case-by-case check. It adds that "in practice, it would be advisable to have a full-time DPO and add other functions to it where possible."

The guide also limits its own reach. The positions it examines "are indicative and do not constitute a list of automatic or structural incompatibilities, but situations to be analysed according to the effectiveness of the mitigation measures." Functional segregation, independent validation by a third party and "regulated abstention" are the mitigation tools it names, and both the procedure and the residual risk must be documented.

Post or situation AEPD assessment Condition or mitigation named in the guide
CEO, COO, CFO, chief medical officer, head of marketing, HR or IT As a rule incompatible Lower posts also conflict if they shape purposes and means
Head of ICT Cannot hold the post where they decide on processing or system configuration None stated
Information security officer (CISO/RSI) Conflict where they decide security measures, tools or levels Exceptionally acceptable in small organisations, documented and temporary (Legal report 2018-0170)
Head of the ethics or whistleblowing channel "Obvious position of conflict of interest" Abstention mechanisms if the channel is run by a collegiate body that includes the DPO
Chief data officer, analytics, AI or data science roles DPO cannot decide datasets, AI mechanisms or secondary uses DPO advises on dataset selection, excess and alternatives
Legal advice or regulatory compliance Potentially compatible Conflict if the DPO represents the organisation in court or in infringement proceedings
Internal audit, risk management, quality Potentially compatible Conflict in financial risk decisions or profile-based customer selection
Transparency, archives, data governance Compatible without decision power over archiving or data life cycle None stated
Service inspection Conflict possible Abstention protocols make both compatible
Processor or sub-processor acting as DPO "Obvious conflict of interest" None stated
Part-time or shared DPO, many clients High risk, especially at "abnormally low costs" Viability of the offer must be justified, especially in public procurement

Source: AEPD guide, sections III and VII.

AI roles and the chief data officer

The rapid arrival of AI in organisations is, according to the guide, the main reason the boundary between the DPO and newer data roles needs drawing. "The DPO cannot take the decisions that may be necessary when selecting datasets or using AI mechanisms that may be included in the organisation's processes; nor can they take decisions in relation to any secondary purpose for which data collected for an initially different purpose might be used (machine learning, data analytics, etc.)."

What the DPO can do is advise on "the selection and adequacy of datasets, their possible excess, AI mechanisms, secondary uses and possible alternatives". The guide also sees the record of processing activities as the place where AI use becomes visible: involvement in managing it would allow a DPO "to relate processing operations to the use of AI agents and assistants in the organisation's processes". The foreword lists the relationship between data protection functions and AI responsibilities as one of the AEPD's next lines of work.

That fits a pattern. In February 2026 the AEPD published a 71-page guide on agentic AI, and PPC Land reported at the time that Spain's data watchdog mapped the hidden GDPR risks of agentic AI. On 27 October the agency followed with a consumer-facing 10-point guide for people who let AI agents act for them.

What the DPO advises on but does not own

Section VI of the guide deals with the accountability tools of the GDPR and draws the same line each time.

On data protection policies, the DPO can advise on whether to draft one and on its content, then supervise it. But "a controller who instructed the DPO to draw up, approve or update a data protection policy that the DPO themselves must supervise would be violating the DPO's independence and creating a conflict of interest in the performance of their work."

On records of processing, the controller remains responsible under Article 30 GDPR, though the guide, citing WP243, says management of the record can be delegated to the DPO as part of the supervisory function. The DPO still has "no decision-making power to implement new processing operations or new processing activities."

On the DPIA, the DPO advises on risk, methodology, design and security measures and, where residual risk stays high, can propose prior consultation with the AEPD under Article 36 GDPR. "In no case does the DPO approve or assume the final decision to continue with a processing activity or on the safeguards to be applied." A policy that made the DPO responsible for carrying out or approving the DPIA "could create a conflict of interest".

On breaches, the DPO advises on risk and may be involved in Article 33 notifications and Article 34 communications, but the guide separates that from "operational responsibility for managing the incident, which lies with the technical areas and the competent officers."

Reporting without a mandatory annual report

The guide declines to impose a format. "Although the General Data Protection Regulation neither requires an annual report nor establishes a formal model of periodic report, it does require that the DPO be involved, properly and in a timely manner." Larger organisations may want structured reports; smaller ones can rely on minutes, documented communications and records of recommendations.

The CNIL's DPO activity report template of 27 April 2026 is cited as "an especially valuable reference". The EDPB's 2024 report, in its section 4.6, had identified difficulties of access to senior management. The AEPD's main recommendation in this area is documentary: when an organisation departs from the DPO's view, it should record why. The guide presents that as a way to strengthen traceability "without altering the non-binding nature of the DPO's recommendations." Article 36(4) of the LOPDGDD separately requires a DPO to document and communicate significant breaches to the administrative and management bodies immediately.

Dismissal, retaliation and the question of 'disguised removal'

Spain already gives internal DPOs more protection than the GDPR requires. Under Article 36(2) of the LOPDGDD, a DPO who is a natural person integrated into the organisation "may not be removed or penalised by the controller or processor for performing their functions unless they incur intent or gross negligence in doing so."

The guide explains how far that goes. In Leistritz, the CJEU held that Article 38(3) covers decisions that end the DPO's functions, harm them or act as a penalty, "provided they are linked to the performance of the tasks entrusted to them", without creating absolute irremovability. Leistritz and X-FAB Dresden also confirmed that member states may set higher protection, as Germany does: its BDSG ties revocation to serious cause by reference to Section 626 of the German Civil Code. At the same time, a 2026 judgment of the High Court of Justice of Madrid (STSJ M 7356/2026) is cited for the point that DPO independence does not bring the special dismissal protection that Spanish law grants workers' representatives.

The more practical passage concerns measures short of dismissal. "There is currently no consolidated legal category of 'disguised removal' or 'material dismissal'," the guide acknowledges. It nonetheless lists six types of organisational decision that should be examined against Article 38:

  • the substantial removal of functions proper to the DPO;
  • the loss of direct access to senior management;
  • the significant reduction of resources indispensable for the performance of their functions;
  • the abolition of support structures necessary for the effective exercise of the function;
  • the reassignment of essential competences to other bodies;
  • any other measure that substantially empties of content the functions assigned to the DPO.

In those cases, organisations "should expressly assess the impact of the measure on the independence and capacity to act of the DPO and document the reasons justifying its adoption." Drawing on AEPD Legal Report 0038/2023, the guide also says the DPO's opinion should be sought before a reorganisation that affects their position. The Belgian Data Protection Authority's guidance, updated on 24 January 2024, is cited for a wider view of retaliation that includes "delays in promotion, denial of benefits or threats of adopting unfavourable decisions".

Minimum safeguards, according to the guide, are direct access to the top, sufficient human and material resources, access to information, organisational support, continuing training and a "real capacity to escalate risks, observations and disagreements".

For EU institutions the bar is already higher. PPC Land reported in February that the EDPS now holds a dismissal veto over DPOs at EU institutions under Decision 01/2026 of 16 January 2026, which the AEPD lists among its references.

Where a DPO can turn

The guide closes its legal analysis with three tiers of protection.

  1. Internal routes. Direct access to the highest level of management "without going through intermediaries or filters"; the internal whistleblowing channel under Law 2/2023 of 20 February; and, under Article 36(4) LOPDGDD, formal documentation and immediate communication of significant breaches or a serious lack of resources or safeguards.
  2. The supervisory authority. A DPO may consult the AEPD, protected by the authority's duty of secrecy. "Failure by the controller or processor to comply with the obligations relating to the position, resources and independence of the DPO (Articles 37 to 39 GDPR) constitutes a legal infringement," and the authority may open preliminary investigations or a penalty procedure.
  3. The courts. Labour courts for employees, and administrative or labour courts for public employees, to seek invalidation of dismissal, removal, penalty or a substantial change of conditions adopted as retaliation.

Decisions and judgments the guide relies on

Decision or judgment Date Issue, according to the guide
CJEU, Leistritz, C-534/20 22 June 2022 Scope of protection against dismissal; national law may add safeguards
CJEU, X-FAB Dresden, C-453/21 9 February 2023 Higher national protection compatible with the GDPR
CJEU, KISA, C-560/21 9 February 2023 Reinforced national safeguards against removal
Irish DPC, IN-18-12-01 10 May 2021 DPO advice must be considered; record reasons when not followed
AEPD, PS/00345/2022 19 July 2023 Secretary of a professional association designated as DPO
AEPD, appeal decision in PS/00382/2023 14 June 2024 Conflict of a DPO who submits pleadings on behalf of the controller
AEPD, PS/00548/2024 5 March 2026 DPO and head of the internal information system incompatible
Audiencia Nacional, judgment 139/2026 18 March 2026 Confirms PS/00345/2022; examine functions actually assigned
High Court of Justice of Madrid, STSJ M 7356/2026 2026 DPO not entitled to workers' representatives' dismissal protection
Supreme Court (Social Chamber), appeal 384/2025 22 September 2026 Listed in references, not discussed in the text
EDPS, Decision 01/2026 16 January 2026 Prior EDPS consent for dismissal of DPOs at EU bodies

Source: AEPD guide, sections II, V and X.

A year in the making

According to the foreword, preparation took "nearly a year". The draft went through two rounds of consultation with professional associations and with public-sector DPOs. The Andalusian Transparency and Data Protection Council commented on it, and the text was made available to the Catalan and Basque data protection authorities. The AEPD thanks four associations by name: the Data Protection Officer Club of the Spanish Association for Quality (AEC), the Spanish Professional Association for Privacy and Artificial Intelligence (APEP·IA), the Association of National Experts of ICT Law (ENATIC) and ISMS Forum.

The project belongs to the AEPD's 2025-2030 Strategic Plan, presented on 3 July 2025. That plan, according to the foreword, came out of "some fifty meetings" and a public consultation with "nearly five hundred contributions, more than a fifth of them from privacy professionals". The guide implements measures 4.1, 4.2, 4.3 and 7.3 of the plan. Through 2026 the agency also ran a dialogue with DPOs of the General State Administration, including an event with more than seventy professionals, which produced recommendations dated 14 July 2026.

The text is described as open. The AEPD plans, with some of the participating associations, to develop good practices for preventing and resolving conflicts of interest in specific situations, and says it will keep channels open for comments.

Why this matters for marketing

For most advertisers the DPO is a back-office name in a privacy notice. In Spain, Article 34(1)(k) means that any entity carrying out advertising, prospecting or market research based on preferences or profiling is required to have one, and today's guide sets out how independent that person has to be from the people running campaigns.

Spanish enforcement has been active in the same territory. In May, PPC Land reported that Spain fined Amadeus IT Group €14.4 million for passenger data profiling, after a pilot that matched booking records with hotel-chain customer data. Enforcement across Europe runs at scale too: national authorities issued €1.15 billion in GDPR fines in 2025, according to the EDPB's annual report.

The guide also lands in the middle of a debate about compliance workload. A noyb survey of 510 privacy professionals, covered by PPC Land in March, found that GDPR practitioners want less paperwork rather than fewer rights, with records of processing ranked as the heaviest burden. The AEPD's guide insists repeatedly that its reporting suggestions are not meant "to increase the documentary burden", yet it recommends documenting the DPO's advice, the reasons for overruling it and the effect of reorganisations on the post. Meanwhile the European Commission's November 2025 Digital Omnibus drafts focused on the definition of personal data, AI training and impact assessment lists, and in February the EDPB and EDPS rejected the Commission's plan to narrow GDPR protections.

Other authorities have been working on the same question from different angles. Germany's Thuringia regulator, in an annual report covered by PPC Land in February, said that two data protection officers is one too many for a single area of responsibility. Israel's draft guidance from July 2025 said that a CISO cannot also serve as DPO, a stricter line than the AEPD's small-organisation exception. A CNIL study reported by PPC Land found that 42% of DPOs said the role gave their organisation an advantage in tenders. And in November the EDPB chose AI candidate screening as its 2027 coordinated enforcement target, an area where the guide's passages on HR heads and AI decision-makers serving as DPOs are directly relevant.

For ad tech vendors that sell compliance bundles, the processor passage may be the sharpest. A service provider that also acts as its client's DPO, the guide says, is in an "obvious situation of conflict of interest". Martech contracts that include an outsourced DPO alongside the data processing itself fit that description.

What the guide does not settle

The guide sets no thresholds for DPO resources in the private sector, gives no figure for how many clients one external DPO can reasonably serve, and names no date for its planned work on AI roles or on conflict-of-interest good practices. A Supreme Court judgment of 22 September 2026 appears in the references without discussion in the text, and the guide gives no indication of how often the AEPD has sanctioned breaches of the DPO articles beyond the decisions it cites.

Key facts

  • Document: "El estatuto del delegado de protección de datos. Orientaciones sobre el marco de actuación, independencia, garantías organizativas y conflictos de intereses" (The Statute of the Data Protection Officer. Guidance on the framework for action, independence, organisational safeguards and conflicts of interest)
  • Publisher: Agencia Española de Protección de Datos (AEPD)
  • Publication date: 19 November 2026 (cover: "Guía publicada en noviembre de 2026")
  • Length: 59 pages (Spanish original)
  • Signed by: Lorenzo Cotino Hueso, President; Francisco Pérez Bes, Deputy
  • Legal basis interpreted: GDPR Articles 37 to 39; LOPDGDD (Organic Law 3/2018 of 5 December) Articles 34 to 37
  • Status: Interpretive guidance; "neither introduces new obligations nor imposes a single organisational model"
  • Advertising-specific obligation cited: Article 34(1)(k) LOPDGDD, mandatory DPO for advertising and commercial prospecting entities, including commercial and market research, that process based on preferences or profile data subjects
  • Notification deadline: 10 days for designations, appointments and dismissals (Article 34(3) LOPDGDD)
  • Dismissal protection for internal DPOs: only for intent or gross negligence (Article 36(2) LOPDGDD)
  • Case law: CJEU C-534/20 (Leistritz), C-453/21 (X-FAB Dresden), C-560/21 (KISA); Audiencia Nacional judgment 139/2026, ECLI:ES:AN:2026:1355
  • Strategic Plan measures implemented: 4.1, 4.2, 4.3 and 7.3 of the AEPD 2025-2030 Strategic Plan
  • Guide URL: https://www.aepd.es/guias/estatuto-dpd-orientaciones-actuacion-independencia-garantias-conflictos.pdf
  • Press release URL: https://www.aepd.es/prensa-y-comunicacion/notas-de-prensa/aepd-publica-el-estatuto-del-delegado-proteccion-datos-independencia-garantias

Timeline

Summary

Who: The Spanish Data Protection Agency (AEPD), with a foreword signed by its President, Lorenzo Cotino Hueso, and Deputy, Francisco Pérez Bes. The guidance addresses data protection officers and the companies, public bodies, controllers and processors that appoint them, including advertising, commercial prospecting and market research firms that Spanish law already requires to have a DPO when they profile people.

What: A 59-page interpretive guide, "The Statute of the Data Protection Officer", that sets out how DPOs should be designated, what functional, hierarchical, economic and organisational independence means, how they should report to senior management, how they are protected against dismissal and retaliation, and which posts conflict with the role. The head of marketing is among the senior posts treated as, as a rule, incompatible, and the guide warns that profit-linked bonuses, processor-as-DPO arrangements and unusually cheap multi-client DPO services can compromise independence.

When: Published today, 19 November 2026, after nearly a year of preparation and two rounds of consultation.

Where: Spain, applying the EU GDPR and Spain's Organic Law 3/2018, drawing on CJEU case law and on guidance from the EDPB, the EDPS and eight other European supervisory authorities.

Why: The AEPD's 2025-2030 Strategic Plan committed it to strengthening DPOs' independence and clarifying their legal status, after the EDPB's 2024 coordinated enforcement report found conflicts of interest and a lack of independence among DPOs across Europe. The guide creates no new obligations but sets out how the agency reads the existing ones.