> DSA vs ePrivacy side by side, topic by topic: where they overlap, where they differ and which asks more, with incident deadlines, testing, third parties and fines.

# DSA vs ePrivacy

Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.

[DSA](https://grc.plus/regulation/digital-services-act-dsa/)

[ePrivacy](https://grc.plus/regulation/eprivacy-directive/)Providers of publicly available electronic communications services; Article 5(3) and Article 13 also reach other organisations

## At a Glance

They differ on 13 of 13 topics. Each verdict names what it rests on; read the wording before relying on it.

- **DSA** Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
- **ePrivacy** Asks more on 0 topics Alone on 13 topics More detailed on 0 topics

| Topic | DSA | ePrivacy | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Security policy | DSA: – | ePrivacy: 1 | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Protection |  |  |  |
| Access control | DSA: – | ePrivacy: 1 | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Data security | DSA: – | ePrivacy: 1 | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Network security | DSA: – | ePrivacy: 1 | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Secure communications | DSA: – | ePrivacy: 1 | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Detection and response |  |  |  |
| Incident handling | DSA: – | ePrivacy: 1 | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Reporting to authorities | DSA: – | ePrivacy: 4 | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Informing customers and the public | DSA: – | ePrivacy: 2 | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Third parties and supply chain |  |  |  |
| Supplier and third-party risk | DSA: – | ePrivacy: 1 | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Privacy and data protection |  |  |  |
| Lawful processing | DSA: – | ePrivacy: 4 | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Transparency | DSA: – | ePrivacy: 3 | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Supervision and enforcement |  |  |  |
| Cooperation with supervisors | DSA: – | ePrivacy: 1 | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Penalties and liability | DSA: – | ePrivacy: 1 | **Only ePrivacy**no specific requirement on the other side in the acts covered |

## What This Covers

The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.

Included

- [UŚUDE](https://grc.plus/regulation/poland-electronic-services-act/) Ustawa z dnia 18 lipca 2002 r., Dz.U. 2002 nr 144 poz. 1204; consolidated text Dz.U. 2024 poz. 1513; amended by the Act of 4 September 2026, Dz.U. 2026 poz. 1296 Articles 5, 8, 18, 22 · 4 requirements

Status

Reviewed against the official texts.

Included

- [ePrivacy](https://grc.plus/regulation/eprivacy-directive/) Directive 2002/58/EC of the European Parliament and of the Council of 12 July 2002, as amended by Directive 2009/136/EC; Commission Regulation (EU) No 611/2013 Articles 2, 4 to 6, 9, 13, 15 · 18 requirements

Status

Reviewed against the official texts.

## Key Numbers

### Deadline

DSA: Not in the acts covered

ePrivacy: Without undue delay after detection (Providers of publicly available electronic communications services); Immediately (Providers contracted by a provider of publicly available electronic communications services)

### Goes to

DSA: Not in the acts covered

ePrivacy: Subscribers (Providers of publicly available electronic communications services); Subscribers and individuals affected (Providers of publicly available electronic communications services); Contracting provider (Providers contracted by a provider of publicly available electronic communications services)

### Evidence to keep

DSA: Not in the acts covered

ePrivacy: Inventory of personal data breaches (Providers of publicly available electronic communications services)

### Incident reports go to

DSA: Not in the acts covered

ePrivacy: Competent national authority (Providers of publicly available electronic communications services)

### First notice of an incident

DSA: Not in the acts covered

ePrivacy: Within 24 hours of detection, where feasible (Providers of publicly available electronic communications services)

### Incident notification

DSA: Not in the acts covered

ePrivacy: Within three days of the initial notification (Providers of publicly available electronic communications services)

### Maximum fines

DSA: Not in the acts covered

ePrivacy: Set by each Member State; no EU maximum (Member States and competent national authorities)

## Governance

### Security policy

**Only ePrivacy** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.PO · ISO/IEC 27001:2022 A.5.1

Nothing in the acts covered.

- Secure the service
  Applies to: Providers of publicly available electronic communications services
  Take technical and organisational measures suited to the risk to secure the service, with the network provider where needed. At least limit access to personal data to authorised staff for lawful purposes, protect stored or transmitted data against destruction, loss, alteration and unauthorised processing, and apply a security policy. National authorities may audit the measures.
  [ePrivacy, Article 4(1) and (1a)](https://grc.plus/regulation/eprivacy-directive/#requirements)

## Protection

### Access control

**Only ePrivacy** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.15, A.5.18, A.8.2, A.8.3

Nothing in the acts covered.

- Secure the service
  Applies to: Providers of publicly available electronic communications services
  Take technical and organisational measures suited to the risk to secure the service, with the network provider where needed. At least limit access to personal data to authorised staff for lawful purposes, protect stored or transmitted data against destruction, loss, alteration and unauthorised processing, and apply a security policy. National authorities may audit the measures.
  [ePrivacy, Article 4(1) and (1a)](https://grc.plus/regulation/eprivacy-directive/#requirements)

### Data security

**Only ePrivacy** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12

Nothing in the acts covered.

- Secure the service
  Applies to: Providers of publicly available electronic communications services
  Take technical and organisational measures suited to the risk to secure the service, with the network provider where needed. At least limit access to personal data to authorised staff for lawful purposes, protect stored or transmitted data against destruction, loss, alteration and unauthorised processing, and apply a security policy. National authorities may audit the measures.
  [ePrivacy, Article 4(1) and (1a)](https://grc.plus/regulation/eprivacy-directive/#requirements)

### Network security

**Only ePrivacy** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.8.20 to A.8.22

Nothing in the acts covered.

- Secure the service
  Applies to: Providers of publicly available electronic communications services
  Take technical and organisational measures suited to the risk to secure the service, with the network provider where needed. At least limit access to personal data to authorised staff for lawful purposes, protect stored or transmitted data against destruction, loss, alteration and unauthorised processing, and apply a security policy. National authorities may audit the measures.
  [ePrivacy, Article 4(1) and (1a)](https://grc.plus/regulation/eprivacy-directive/#requirements)

### Secure communications

**Only ePrivacy** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.14

Nothing in the acts covered.

- Confidentiality of communications
  Applies to: Anyone other than the users of the communication
  Do not listen to, tap, store or otherwise intercept communications and related traffic data without the users' consent, unless legally authorised under Article 15(1). Technical storage needed for transmission remains allowed. Regulation (EU) 2026/1881 gives a temporary exception, until 3 April 2028, for number-independent interpersonal communications services detecting online child sexual abuse under its conditions.
  [ePrivacy, Article 5(1)](https://grc.plus/regulation/eprivacy-directive/#requirements)

## Detection and response

### Incident handling

**Only ePrivacy** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.MA, RS.AN, RS.MI · ISO/IEC 27001:2022 A.5.24 to A.5.28

Nothing in the acts covered.

- Keep a breach inventory
  Applies to: Providers of publicly available electronic communications services
  Keep an inventory of personal data breaches recording the facts, effects and remedial action, with only the information authorities need to check compliance. Authorities may issue guidelines and instructions, can audit compliance and must impose appropriate sanctions for failures.
  [ePrivacy, Article 4(4)](https://grc.plus/regulation/eprivacy-directive/#requirements)

### Reporting to authorities

**Only ePrivacy** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5

Nothing in the acts covered.

- Notify the authority of a personal data breach
  Applies to: Providers of publicly available electronic communications services
  For providers of publicly available electronic communications services only: report every personal data breach to the competent national authority without undue delay, within 24 hours of detection where feasible. Detection means enough awareness to make a meaningful notification, not a mere suspicion. Describe the breach, contact points, recommended mitigation, the consequences and the measures taken.
  [ePrivacy, Article 4(3); Regulation (EU) No 611/2013, Article 2(1) and (2)](https://grc.plus/regulation/eprivacy-directive/#requirements)
- Second notification to the authority
  Applies to: Providers of publicly available electronic communications services
  For providers of publicly available electronic communications services only: where full information is not yet available and further investigation is needed, send an initial notification within 24 hours of detection. Send a second notification as soon as possible and at the latest within three days of the initial one. If information is still missing then, send what is held with a reasoned justification for the delay and the rest as soon as possible.
  [ePrivacy, Regulation (EU) No 611/2013, Article 2(3)](https://grc.plus/regulation/eprivacy-directive/#requirements)
- Tell subscribers and individuals
  Applies to: Providers of publicly available electronic communications services
  For providers of publicly available electronic communications services only: where a breach is likely to harm a person's data or privacy, tell them without undue delay after detection, in clear language and without promoting services. This is not needed if the provider satisfies the authority that the data was unintelligible, for example securely encrypted with the key uncompromised. Delay is allowed only in exceptional cases where telling them could put the investigation at risk, and only with the authority's agreement.
  [ePrivacy, Article 4(3); Regulation (EU) No 611/2013, Articles 3 and 4](https://grc.plus/regulation/eprivacy-directive/#requirements)
- Subcontracted provider informs the contracting provider
  Applies to: Providers contracted by a provider of publicly available electronic communications services
  A provider contracted to deliver part of an electronic communications service, with no direct contract with subscribers, immediately tells the contracting provider of a personal data breach.
  [ePrivacy, Regulation (EU) No 611/2013, Article 5](https://grc.plus/regulation/eprivacy-directive/#requirements)

### Informing customers and the public

**Only ePrivacy** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO, RC.CO

Nothing in the acts covered.

- Warn of a network security risk
  Applies to: Providers of publicly available electronic communications services
  Where there is a particular risk of a breach of network security, tell subscribers about the risk. Where the risk lies outside the provider's own measures, also tell them of any possible remedies and their likely cost.
  [ePrivacy, Article 4(2)](https://grc.plus/regulation/eprivacy-directive/#requirements)
- Tell subscribers and individuals
  Applies to: Providers of publicly available electronic communications services
  For providers of publicly available electronic communications services only: where a breach is likely to harm a person's data or privacy, tell them without undue delay after detection, in clear language and without promoting services. This is not needed if the provider satisfies the authority that the data was unintelligible, for example securely encrypted with the key uncompromised. Delay is allowed only in exceptional cases where telling them could put the investigation at risk, and only with the authority's agreement.
  [ePrivacy, Article 4(3); Regulation (EU) No 611/2013, Articles 3 and 4](https://grc.plus/regulation/eprivacy-directive/#requirements)

## Third parties and supply chain

### Supplier and third-party risk

**Only ePrivacy** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.19, A.5.21 to A.5.23

Nothing in the acts covered.

- Subcontracted provider informs the contracting provider
  Applies to: Providers contracted by a provider of publicly available electronic communications services
  A provider contracted to deliver part of an electronic communications service, with no direct contract with subscribers, immediately tells the contracting provider of a personal data breach.
  [ePrivacy, Regulation (EU) No 611/2013, Article 5](https://grc.plus/regulation/eprivacy-directive/#requirements)

## Privacy and data protection

### Lawful processing

**Only ePrivacy** no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.PO-P

Nothing in the acts covered.

- Storing or reading data on a device
  Applies to: Any organisation storing or reading information on a user's device
  Before storing or reading information on a user's device, give clear and comprehensive information and obtain consent. This does not apply to storage or access solely to carry a communication, or strictly necessary for a service the user explicitly asked for.
  [ePrivacy, Article 5(3)](https://grc.plus/regulation/eprivacy-directive/#requirements)
- Traffic data
  Applies to: Providers of public communications networks and publicly available electronic communications services
  Erase or anonymise traffic data once it is no longer needed for transmission, apart from billing until the challenge period ends and marketing or value added services with prior, withdrawable consent. Tell subscribers what is processed and for how long, and limit handling to authorised staff.
  [ePrivacy, Article 6(1) to (5)](https://grc.plus/regulation/eprivacy-directive/#requirements)
- Location data other than traffic data
  Applies to: Providers of public communications networks and publicly available electronic communications services, and third parties providing value added services that process location data
  Process location data only anonymised, or with consent for a value added service for as long as that service needs. Tell users first about the data, purpose, duration and any third-party transfer. Let them withdraw consent at any time and refuse temporarily, simply and free of charge.
  [ePrivacy, Article 9](https://grc.plus/regulation/eprivacy-directive/#requirements)
- Unsolicited direct marketing
  Applies to: Any organisation sending electronic direct marketing
  Use automated calling, fax or email for direct marketing only with prior consent. A customer's email details may be used for the seller's own similar products if the customer can object easily and free of charge at collection and in each message. Other marketing follows the national choice of opt-in or opt-out. Marketing emails must not hide the sender's identity or lack a valid address for opt-out requests. The consent and opt-out requirements protect subscribers who are natural persons; Member States protect the interests of other subscribers.
  [ePrivacy, Article 13(1) to (5)](https://grc.plus/regulation/eprivacy-directive/#requirements)

### Transparency

**Only ePrivacy** no specific requirement on the other side in the acts covered

NIST Privacy Framework CM.AW-P

Nothing in the acts covered.

- Storing or reading data on a device
  Applies to: Any organisation storing or reading information on a user's device
  Before storing or reading information on a user's device, give clear and comprehensive information and obtain consent. This does not apply to storage or access solely to carry a communication, or strictly necessary for a service the user explicitly asked for.
  [ePrivacy, Article 5(3)](https://grc.plus/regulation/eprivacy-directive/#requirements)
- Traffic data
  Applies to: Providers of public communications networks and publicly available electronic communications services
  Erase or anonymise traffic data once it is no longer needed for transmission, apart from billing until the challenge period ends and marketing or value added services with prior, withdrawable consent. Tell subscribers what is processed and for how long, and limit handling to authorised staff.
  [ePrivacy, Article 6(1) to (5)](https://grc.plus/regulation/eprivacy-directive/#requirements)
- Location data other than traffic data
  Applies to: Providers of public communications networks and publicly available electronic communications services, and third parties providing value added services that process location data
  Process location data only anonymised, or with consent for a value added service for as long as that service needs. Tell users first about the data, purpose, duration and any third-party transfer. Let them withdraw consent at any time and refuse temporarily, simply and free of charge.
  [ePrivacy, Article 9](https://grc.plus/regulation/eprivacy-directive/#requirements)

## Supervision and enforcement

### Cooperation with supervisors

**Only ePrivacy** no specific requirement on the other side in the acts covered

Nothing in the acts covered.

- Procedures for access requests
  Applies to: Providers of publicly available electronic communications services
  Set internal procedures for answering requests for access to users' personal data made under national law adopted under Article 15(1). On demand, give the competent national authority information on those procedures, the number of requests received, the legal justification invoked and the response given.
  [ePrivacy, Article 15(1b)](https://grc.plus/regulation/eprivacy-directive/#requirements)

### Penalties and liability

**Only ePrivacy** no specific requirement on the other side in the acts covered

Nothing in the acts covered.

- Penalties set nationally
  Applies to: Member States and competent national authorities
  Member States set penalties for infringements, including criminal sanctions where appropriate, which are effective, proportionate and dissuasive. Competent authorities can order infringements to stop and have investigative powers and resources, including to obtain information.
  [ePrivacy, Article 15a(1) to (3)](https://grc.plus/regulation/eprivacy-directive/#requirements)

Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022.

## More Comparisons

- [Compare DSA](https://grc.plus/compare/dsa/)
- [Compare ePrivacy](https://grc.plus/compare/eprivacy/)

Source: https://grc.plus/compare/dsa-vs-eprivacy/
