§ DMA · ePrivacy Directive COMPARISON

DMA vs ePrivacy Directive: Where They Overlap and Conflict

3 overlaps, 1 conflicts and 2 gaps mapped between DMA and ePrivacy Directive in the Fontvera regulatory corpus.

Summary

DMA and ePrivacy Directive both apply across European business activity, but they were drafted at different times with different policy goals. This page summarises every article-level crossref between the two in the Fontvera corpus.

3 overlaps mean the same conduct triggers obligations in both regimes — design controls once, document twice. 1 conflicts mean the two regulations push in opposite directions on a specific question. 2 gaps mean one regulation leaves something on a topic the other addresses.

Who this applies to
Compliance teams who need to map a single control framework onto both DMA and ePrivacy Directive.
Compliance deadline
§ Detail

In depth

Summary statistics

Overlaps: 3 · Conflicts: 1 · Gaps: 2

6 article-level crossrefs catalogued between DMA and ePrivacy Directive from the Fontvera EU regulatory corpus. Article numbers are verbatim from the underlying obligation_crossrefs table; descriptions are extracted, not paraphrased.

All crossrefs between these regulations

Article (A)Article (B)TypeSeverityDescription
DMA Art 13ePrivacy Directive Art 5overlaphigh[entity affected: gatekeeper / provider of publicly available electronic communications service] Both regulations require entities to obtain valid consent from users before processing personal data or
DMA Art 15ePrivacy Directive Art 5overlapmedium[entity affected: gatekeeper / provider of publicly available electronic communications service] Both regulations mandate transparency regarding data processing activities, requiring gatekeepers to pu
DMA Art 1ePrivacy Directive Art 15conflicthigh[entity affected: Member States] DMA prohibits Member States from imposing further obligations on gatekeepers to ensure contestable markets, while ePrivacy allows Member States to restrict rights for
DMA Art ?ePrivacy Directive Art 4gapmedium[entity affected: provider of publicly available electronic communications service] ePrivacy requires specific technical and organizational security measures for electronic communications services, bu
DMA Art ?ePrivacy Directive Art 13gapmedium[entity affected: sender of electronic mail / gatekeeper] ePrivacy strictly regulates direct marketing via email requiring prior consent or opt-out, while DMA focuses on platform contestability and do
DMA Art 11ePrivacy Directive Art 18overlaplow[entity affected: gatekeeper / Commission] Both regulations require the submission of reports to the Commission regarding compliance and application of the rules, ensuring regulatory oversight and tra

Conflicts explained

The 1 article-level conflicts between DMA and ePrivacy Directive mean a control that satisfies one can pull the wrong way on the other:

Which regulation takes precedence

EU law does not lay down a universal precedence rule between DMA and ePrivacy Directive. In practice three resolution approaches apply: lex specialis (the more specific provision wins when both purport to govern the same conduct); regulator guidance (EDPB, EBA, ESMA and the AI Office have all issued joint readings on overlapping articles — check the most recent applicable opinion); and document the choice (when the regulations leave the call to the controller, the audit defence is your written reasoning, not the regulator's silence). Where the corpus surfaces a conflict rather than an overlap, treat that as an escalation path to legal — not a control-design question.

What this means for your compliance team

Treat the 3 overlaps as design opportunities — one control, two regulatory anchors. Treat the 1 conflicts as escalation paths to legal: the regulations themselves don't resolve them, you do, and you document the reasoning. The 2 gaps point at scenarios where one regulation is silent while the other speaks — assume the regulator who has the explicit rule will win.

Related Fontvera pages

Check your full compliance exposure with the 5-minute Fontvera diagnostic →

§ What Fontvera found

Documents in our corpus

Enforcement data is expanding. AI Act enforcement begins 2 August 2026 — this section will populate automatically as authorities and courts publish decisions citing the regulations covered on this page.
§ Cross-references

Related Fontvera intelligence

Need a cross-border briefing on this?
Search Fontvera ↵ Run the AI Act diagnostic
AI Act enforcement
63 days
until 2026-08-02, when most AI Act provisions begin to apply.