DMA & GDPR: First Thoughts on the Joint Guidelines

← All articles
Data protection · EN

DMA & GDPR: First Thoughts on the Joint Guidelines

The new joint guidelines by the EDPB and European Commission are a step toward coherence, but they lean heavily on restating existing principles rather than providing operational clarity. For gatekeepers and business users, this may translate into interpretation risk and compliance friction, unless supplemented by detailed technical standards and enforcement coordination frameworks. Examples:

1) Consent Requirements Under Article 5(2) DMA

The text reiterates GDPR standards—consent must be “freely given, specific, informed and unambiguous” (Articles 4(11) and 7 GDPR), but offers little practical guidance for implementing scalable consent flows. It warns against pre-ticked boxes and nudging (paras. 29–33, 43–45) without providing design templates or UX best practices.

2) Data Portability and Real-Time Access

Article 6(9) DMA introduces continuous and real-time portability, far beyond GDPR’s Article 20. Yet, the guidelines only state that gatekeepers should use “appropriate technical measures, such as APIs” without specifying security standards or interoperability benchmarks (paras. 120–124).

3) Anonymisation for Search Data Sharing

For Article 6(11) DMA, the guidance repeats GDPR recital 26 and CJEU case law but does not define concrete anonymisation techniques or thresholds for “insignificant likelihood of identification” (paras. 177–181).

Bottom line:

Without actionable detail (such as technical standards, UX patterns, or enforcement protocols) these guidelines risk becoming a compliance checklist rather than a practical roadmap. However, this is still a draft. The public consultation is open until 4 December 2025.

This post has a document attached on LinkedIn. View on LinkedIn →

Discuss on LinkedIn