Your cookie preferences

EDPB guidance · Art. 7 GDPR

We use technical cookies essential for the platform to work (login, security, sessions). We would also like to use analytics cookies to understand how to improve it.

You can accept all, reject all, or choose which categories to switch on.Your consent is valid for 6 months and you can withdraw it at any time from the footer.

You will find everything in our privacy notice.

All news
Regulation August 10, 2026 5 min

A DPO who decides cannot supervise themselves

The French DPA publishes guidance on conflicts of interest: which combined roles are incompatible, how to document a recusal, and why a deputy DPO cannot be a subordinate

On 10 August 2026 the CNIL published practical guidance on a problem nearly every organisation has and almost none has written down: the conflict of interest of the data protection officer.

The starting point is Art. 38(6) GDPR. The DPO may perform tasks beyond those in Art. 39, subject to two cumulative conditions: those tasks must not deprive them of the time needed to act as DPO, and must not place them in a conflict of interest.

The questions that reveal it

The CNIL recommends carrying out the analysis before designating a DPO, or before assigning new duties to a serving one. These are the questions it proposes:

  • Which other roles are combined with that of DPO?
  • Does the DPO hold management duties? Chief executive and head of HR are generally incompatible, but so may be lower-ranking roles if they lead the DPO to determine the purposes and means of processing
  • Do the DPO or their team hold decision-making power over purposes or means? If the DPO is also head of information security: do they set log retention periods, propose security measures, decide on access requests to staff data?
  • In their other duties, does the DPO take positions on projects involving personal data, for example as a member of an ethics committee?
  • Is the DPO a staff representative or trade union officer? A vote may require them to take a position on employee monitoring measures
  • If the DPO is external: have they already represented the organisation in data protection litigation? Do they belong to a body with opposing interests, such as a processor or a joint controller?

If there is a conflict, it must be removed

The designating organisation is under an obligation to end the conflict. There are three routes: replace the DPO, withdraw the third-party duties that generate the conflict, or adopt other remedial measures.

Recusal and the deputy DPO

The most common measure is recusal: the DPO steps back from the affected scope and a deputy DPO acts there instead. The CNIL is firm that this cannot be a formality. A mere countersignature, without genuine decision-making power for the deputy, is not enough.

The deputy must enjoy the same guarantees as Arts. 37 and 39: resources, training, involvement in matters within their scope. And they must have no relationship of subordination to the designated DPO. The CNIL's example is plain: if an insurer's DPO is also head of anti-fraud and must recuse themselves there, an anti-fraud analyst cannot serve as deputy, because they cannot independently supervise processing decided by their own line manager.

Both the risk justifying the recusal and the division of responsibilities between DPO and deputy must be documented, so that no processing is left uncovered. The deputy is not notified to the authority: the point of contact remains the designated DPO, who must however be able to inform the deputy when the authority writes about processing within the recused scope.

Looking for a workspace for your DPO work?

DPO Workspace is built by a certified DPO. 30-day free trial.

Start free

Related articles

Regulation
nullathe decision on a worker taken by the algorithm alone, from 23 October

A dismissal decided by the algorithm is void: from 23 October in Italy

Published in Official Gazette no. 234 of 8 October 2026 and in force since 23 October, decree no. 179/2026 provides that final decisions on the employment relationship cannot be based solely on automated processing, that the worker may request an understandable explanation, and that decisions taken in breach are void. In parallel, AI systems affecting work organisation enter the risk assessment under Article 28 of decree 81/2008. For a DPO this is the rare case where the consequence is not economic but civil, and it changes how the check is framed.

Oct 08, 2026New 8 min
Regulation
3signals that make notification due

Poland's UODO: not every breach must be notified. Public-register data on one side, PESEL, health and financial data on the other

If an invoicing system leaks only a sole trader's name, business name, tax number and registered address, already public in the business register, risk is normally unlikely. If it also leaks the national ID number, purchase details revealing health, or financial data, notification is due. Either way, the decision goes into the internal register.

Oct 05, 2026New 5 min
Regulation
120days to charge you, not to fine you

The 120 days are not the deadline to fine you: they are the deadline to charge you

Anyone who built an appeal on the authority's delay should re-read the calendar. The Court clarifies three things: the complaint procedure and the sanctioning procedure are autonomous, so overrunning the nine-to-twelve months on the complaint does not extinguish the power to fine; the 120 days are for notifying the charge, not for imposing the fine; and they run from the «definitive finding», which is not the first notice but the moment the authority can assess every element — including the hearing of your side. After the charge, only the five-year limitation period remains.

Sep 20, 2026 7 min