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

# ePrivacy vs GDPR

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

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

[GDPR](https://grc.plus/regulation/general-data-protection-regulation-gdpr/)Controllers and processors

## At a Glance

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

- **ePrivacy** Asks more on 0 topics Alone on 4 topics More detailed on 0 topics
- **GDPR** Asks more on 0 topics Alone on 14 topics More detailed on 0 topics

| Topic | ePrivacy | GDPR | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Roles and independence | ePrivacy: – | GDPR: 2 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Security policy | ePrivacy: 1 | GDPR: – | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Risk management |  |  |  |
| Risk management framework | ePrivacy: – | GDPR: 1 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Risk assessment | ePrivacy: – | GDPR: 1 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Protection |  |  |  |
| Access control | ePrivacy: 1 | GDPR: – | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Cryptography and encryption | ePrivacy: – | GDPR: 1 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Data security | ePrivacy: 1 | GDPR: 2 | **Both cover it**read the wording below |
| Network security | ePrivacy: 1 | GDPR: – | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Secure communications | ePrivacy: 1 | GDPR: – | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Human resources security | ePrivacy: – | GDPR: 1 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Detection and response |  |  |  |
| Incident handling | ePrivacy: 1 | GDPR: 1 | **Both cover it**read the wording below |
| Reporting to authorities | ePrivacy: 4 | GDPR: 3 | **Both cover it**read the wording below |
| Informing customers and the public | ePrivacy: 2 | GDPR: 1 | **Both cover it**read the wording below |
| Continuity and resilience |  |  |  |
| Backup and recovery | ePrivacy: – | GDPR: 1 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Security testing | ePrivacy: – | GDPR: 1 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Third parties and supply chain |  |  |  |
| Supplier and third-party risk | ePrivacy: 1 | GDPR: 2 | **Both cover it**read the wording below |
| Contract requirements | ePrivacy: – | GDPR: 1 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Privacy and data protection |  |  |  |
| Lawful processing | ePrivacy: 4 | GDPR: 7 | **Both cover it**read the wording below |
| Transparency | ePrivacy: 3 | GDPR: 2 | **Both cover it**read the wording below |
| Rights of individuals | ePrivacy: – | GDPR: 7 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Privacy by design and by default | ePrivacy: – | GDPR: 2 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Impact assessment | ePrivacy: – | GDPR: 3 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Records of processing | ePrivacy: – | GDPR: 2 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Data protection officer | ePrivacy: – | GDPR: 2 | **Only GDPR**no specific requirement on the other side in the acts covered |
| International transfers | ePrivacy: – | GDPR: 4 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Supervision and enforcement |  |  |  |
| Cooperation with supervisors | ePrivacy: 1 | GDPR: 1 | **Both cover it**read the wording below |
| Penalties and liability | ePrivacy: 1 | GDPR: 2 | **Both cover it**read the wording below |

## 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

- [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.

Included

- [GDPR](https://grc.plus/regulation/general-data-protection-regulation-gdpr/) Regulation (EU) 2016/679 Articles 5 to 10, 12 to 22, 24 to 39, 44 to 49, 58, 83 · 50 requirements

Status

Reviewed against the official texts.

## Key Numbers

### Deadline

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)

GDPR: At the time the data are obtained (Controllers); Within a reasonable period and at the latest one month after obtaining the data; if used to contact the person, at the latest at first communication; if disclosure is envisaged, at the latest at first disclosure (Controllers); Without undue delay and in any event within one month of receipt of the request; extendable by two further months where necessary (Controllers); Without undue delay and in any event within one month of receipt of the request (Article 12(3)); extendable by two further months where necessary (Controllers); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (Controllers); Before the processing starts; where the authority considers the processing would infringe, it gives written advice within up to eight weeks of receipt of the request, extendable by six weeks (Controllers)

### Threshold

ePrivacy: Not in the acts covered

GDPR: Under 16; Member States may lower the age, not below 13 (Controllers offering information society services directly to children); Exemption only below 250 persons, and only if none of the listed conditions applies (Controllers)

### Goes to

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)

GDPR: Controller (Processors); Data subjects (Controllers)

### Evidence to keep

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

GDPR: Written record of processing activities (Controllers); Written record of processing activities (Processors); Internal record of each breach: facts, effects and remedial action (Controllers)

### Incident reports go to

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

GDPR: Competent supervisory authority (Controllers)

### First notice of an incident

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

GDPR: Without undue delay and, where feasible, within 72 hours of becoming aware (Controllers)

### Incident notification

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

GDPR: Not in the acts covered

### Intermediate report

ePrivacy: Not in the acts covered

GDPR: In phases, without undue further delay (Controllers)

### External assessment or certification

ePrivacy: Not in the acts covered

GDPR: Approved code of conduct or certification may help show compliance (Controllers)

### Review of the risk framework

ePrivacy: Not in the acts covered

GDPR: Where necessary (Controllers)

### Testing of critical systems

ePrivacy: Not in the acts covered

GDPR: Regularly

### Maximum fines

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

GDPR: Up to EUR 10 million or, for an undertaking, 2% of total worldwide annual turnover of the preceding financial year, whichever is higher; Up to EUR 20 million or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, whichever is higher

## Governance

### Roles and independence

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

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.5.2, A.5.3

Nothing in the acts covered.

- Joint controllers
  Applies to: Joint controllers
  Joint controllers set out their respective responsibilities in an arrangement, unless EU or Member State law determines them, including who handles rights requests and information duties, and make its essence available to people. A person may exercise their rights against any of them regardless of the arrangement.
  [GDPR, Article 26](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- EU representative
  Applies to: Controllers and processors not established in the EU, under Article 3(2)
  A controller or processor outside the EU that falls under Article 3(2) designates a representative in writing, established in a Member State where the affected people are. Occasional low-risk processing without large-scale special category or criminal data, and public bodies, are exempt.
  [GDPR, Article 27](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### 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

- 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)

Nothing in the acts covered.

## Risk management

### Risk management framework

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

NIST CSF 2.0 GV.RM · ISO/IEC 27001:2022 Clause 6.1

Nothing in the acts covered.

- Measures to ensure and show compliance
  Applies to: Controllers
  Put in place technical and organisational measures suited to the risks of the processing, so that it complies and the controller can show it does. Review and update them where needed. Where proportionate, these include data protection policies.
  [GDPR, Article 24](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Risk assessment

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

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2

Nothing in the acts covered.

- Assess security risk
  When judging the right level of security, weigh the risks of processing, in particular accidental or unlawful destruction, loss, alteration, and unauthorised disclosure of or access to personal data.
  [GDPR, Article 32(2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#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

- 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)

Nothing in the acts covered.

### Cryptography and encryption

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

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

Nothing in the acts covered.

- Pseudonymisation and encryption
  Apply pseudonymisation and encryption of personal data, as appropriate to the risk.
  [GDPR, Article 32(1)(a)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Data security

**Both cover it** read the wording below

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

- 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)

- Integrity and confidentiality
  Applies to: Controllers
  Process personal data with appropriate security, using appropriate technical or organisational measures, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage.
  [GDPR, Article 5(1)(f)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Security of systems and services
  Be able to keep processing systems and services confidential, intact, available and resilient on an ongoing basis, as appropriate to the risk.
  [GDPR, Article 32(1)(b)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#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

- 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)

Nothing in the acts covered.

### 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

- 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)

Nothing in the acts covered.

### Human resources security

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

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.6.1 to A.6.6

Nothing in the acts covered.

- Staff act only on instructions
  Processors, and anyone with access to personal data under the authority of a controller or processor, process it only on the controller's instructions unless EU or Member State law requires otherwise. Controllers and processors take steps to ensure this.
  [GDPR, Articles 29 and 32(4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

## Detection and response

### Incident handling

**Both cover it** read the wording below

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

- 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)

- Document every breach
  Applies to: Controllers
  Record each personal data breach, whether notified or not, with its facts, effects and remedial action, so the authority can check compliance.
  [GDPR, Article 33(5)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Reporting to authorities

**Both cover it** read the wording below

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

- 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)

- Notify a personal data breach
  Applies to: Controllers
  Notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to risk people's rights and freedoms. Give reasons if the notice is late.
  [GDPR, Article 33(1)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Processor tells the controller
  Applies to: Processors
  Tell the controller of a personal data breach without undue delay after becoming aware of it.
  [GDPR, Article 33(2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- What the breach notice contains
  Applies to: Controllers
  Describe the breach, including the categories and approximate numbers of people and records where possible, the DPO or other contact point, the likely consequences, and the measures taken or proposed. Information not yet available may follow in phases.
  [GDPR, Article 33(3) and (4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Informing customers and the public

**Both cover it** read the wording below

NIST CSF 2.0 RS.CO, RC.CO

- 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)

- Tell the people affected
  Applies to: Controllers
  Where a breach is likely to cause high risk to people, tell them in plain language without undue delay, with the contact point, likely consequences and measures. This is not needed where the data was unintelligible, for example encrypted, where later measures remove the high risk, or where a public notice replaces disproportionate effort. The authority may require notice.
  [GDPR, Article 34(1) to (4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

## Continuity and resilience

### Backup and recovery

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

NIST CSF 2.0 PR.DS, RC.RP · ISO/IEC 27001:2022 A.8.13, A.8.14

Nothing in the acts covered.

- Restoring access after an incident
  Be able to restore availability of and access to personal data in a timely way after a physical or technical incident, as appropriate to the risk.
  [GDPR, Article 32(1)(c)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Security testing

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

NIST CSF 2.0 ID.IM · ISO/IEC 27001:2022 A.5.35, A.8.29, A.8.34

Nothing in the acts covered.

- Testing the measures
  Have a process to test and evaluate regularly whether the technical and organisational security measures work, as appropriate to the risk.
  [GDPR, Article 32(1)(d)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

## Third parties and supply chain

### Supplier and third-party risk

**Both cover it** read the wording below

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

- 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)

- Use only processors with sufficient guarantees
  Applies to: Controllers
  Use only processors that give adequate assurances of technical and organisational measures that meet the Regulation and protect people's rights.
  [GDPR, Article 28(1)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Sub-processors
  Applies to: Processors
  Do not engage another processor without the controller's prior written authorisation, specific or general, and under general authorisation give notice of changes so the controller can object. Bind the sub-processor by contract to the same data protection obligations. The initial processor stays fully liable for the sub-processor's failures.
  [GDPR, Article 28(2) and (4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Contract requirements

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

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.20

Nothing in the acts covered.

- Processing contract
  Govern processing by a written contract or other legal act covering subject matter, duration, nature and purpose, data types, the people concerned and the controller's obligations and rights. It requires the processor to act on documented instructions, keep staff bound to confidentiality, secure the data, follow the sub-processor requirements, help with rights and Articles 32 to 36, delete or return data at the end at the controller's choice, provide compliance information and allow audits. The processor warns the controller at once if an instruction appears to breach data protection law.
  [GDPR, Article 28(3) and (9)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

## Privacy and data protection

### Lawful processing

**Both cover it** read the wording below

NIST Privacy Framework CT.PO-P

- 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)

- Purpose limitation and data minimisation
  Applies to: Controllers
  Collect personal data for specified, explicit and legitimate purposes and do not use it later in a way that conflicts with them. Keep the data adequate, relevant and limited to what those purposes need.
  [GDPR, Article 5(1)(b) and (c)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Accuracy and storage limitation
  Applies to: Controllers
  Keep personal data accurate and, where needed, up to date, and take every reasonable step to erase or correct inaccurate data without delay. Keep data in a form that identifies people only for as long as the purpose needs, or longer solely for archiving, research or statistics under Article 89(1) with safeguards.
  [GDPR, Article 5(1)(d) and (e)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Accountability
  Applies to: Controllers
  The controller is responsible for meeting the data protection principles and must be able to demonstrate that it does.
  [GDPR, Article 5(2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Lawful basis
  Applies to: Controllers
  Process personal data lawfully, fairly and transparently, and only where at least one basis applies: consent, contract, legal obligation, vital interests, a public-interest task or official authority, or legitimate interests. Legitimate interests do not apply where the person's interests or rights override them, and are not open to public authorities performing their tasks.
  [GDPR, Articles 5(1)(a) and 6(1)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Conditions for consent
  Applies to: Controllers
  Be able to prove consent, and keep a written consent request separate from other matters and in plain language. Let people withdraw at any time, as easily as they gave consent, and tell them so beforehand. Consent tied to a contract for data the contract does not need may not count as freely given.
  [GDPR, Article 7](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Children's consent to online services
  Applies to: Controllers offering information society services directly to children
  Where consent is the basis for processing in relation to offering an information society service directly to a child under the age limit, make sure consent is given or authorised by the holder of parental responsibility. Make reasonable efforts, given the available technology, to verify it.
  [GDPR, Article 8(1) and (2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Special category and criminal offence data
  Applies to: Controllers
  Do not process special category data, such as health, biometric identification or genetic data, unless a condition in Article 9(2) applies. Process criminal conviction and offence data only under official authority or where EU or Member State law authorises it with safeguards.
  [GDPR, Articles 9 and 10](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Transparency

**Both cover it** read the wording below

NIST Privacy Framework CM.AW-P

- 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)

- Information when collecting from the person
  Applies to: Controllers
  Tell people, concisely and in plain language, who the controller and any DPO are, the purposes and legal basis, any legitimate interests relied on, recipients, transfers, retention, their rights, whether they must provide the data, and any automated decision-making. Before using the data for a new purpose, give information on that purpose and any relevant further details. This is not needed where the person already has the information.
  [GDPR, Articles 12(1) and 13](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Information when data comes from elsewhere
  Applies to: Controllers
  Give the same information, plus the categories of data and their source, when the data was not obtained from the person. Exceptions include where the person already has it, where this proves impossible or takes disproportionate effort, in which case take appropriate measures to protect the person, including making the information public, or where law requires the obtaining or disclosure or professional secrecy applies.
  [GDPR, Article 14](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Rights of individuals

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

NIST Privacy Framework CT.DM-P

Nothing in the acts covered.

- Answer rights requests in time
  Applies to: Controllers
  Act on a request under Articles 15 to 22 and tell the person the outcome free of charge. If more time is needed for complex or numerous requests, say so and why within the first month. If no action will be taken, say why without delay and within the first month, and explain the right to complain to an authority and seek a judicial remedy. Manifestly unfounded or excessive requests may be charged for or refused, and the controller must show why.
  [GDPR, Article 12(3) to (5)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Right of access
  Applies to: Controllers
  Confirm whether personal data about the person is processed and give access to it, with a copy and information on purposes, data categories, recipients, retention, rights, source and automated decision-making. A reasonable fee may be charged for further copies. The right to a copy must not adversely affect the rights and freedoms of others.
  [GDPR, Article 15](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Rectification, restriction and telling recipients
  Applies to: Controllers
  Correct inaccurate data without undue delay and, taking account of the purposes, complete incomplete data. On request, restrict processing while accuracy is contested or an Article 21(1) objection is being checked, where processing is unlawful and the person prefers restriction to erasure, or where the controller no longer needs the data but the person needs it for legal claims. Tell each recipient of any rectification, erasure or restriction unless this proves impossible or takes disproportionate effort, and tell the person who the recipients are if asked.
  [GDPR, Articles 16, 18 and 19](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Right to erasure
  Applies to: Controllers
  Erase personal data without undue delay where it is no longer needed, consent is withdrawn with no other basis, the person objects under Article 21(1) without overriding grounds or objects to direct marketing, processing was unlawful, law requires it, or it was collected for an information society service under Article 8(1). If the data was made public, take reasonable steps to tell other controllers of the request. The right does not apply where processing is needed for freedom of expression, a legal obligation or public task, public health, archiving, research or statistics where erasure would seriously impair them, or legal claims.
  [GDPR, Article 17](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Right to data portability
  Applies to: Controllers
  Where processing is automated and rests on consent or contract, give people, on request, the data they provided in a structured, commonly used, machine-readable format. On request, send it directly to another controller where technically feasible. The right does not apply to public-task processing and must not adversely affect the rights of others.
  [GDPR, Article 20](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Right to object
  Applies to: Controllers
  Stop processing based on a public task or legitimate interests when the person objects on grounds of their particular situation, unless the controller demonstrates compelling legitimate grounds that override the person's interests, or legal claims. Stop direct marketing, and related profiling, on objection without exception. Present this right clearly and separately, at the latest at first communication.
  [GDPR, Article 21](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Solely automated decisions
  Applies to: Controllers
  Do not subject people to decisions based solely on automated processing, including profiling, with legal or similarly significant effects, unless a contract need, law or explicit consent allows it. In the contract and consent cases, provide human intervention, a chance to give a view and a way to contest the decision. Special category data needs further conditions and safeguards.
  [GDPR, Article 22](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Privacy by design and by default

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

NIST Privacy Framework CT.DP-P

Nothing in the acts covered.

- Data protection by design
  Applies to: Controllers
  When deciding how to process and during processing, apply measures such as pseudonymisation that put the data protection principles into effect and build safeguards into the processing. Take account of the state of the art, cost and risk.
  [GDPR, Article 25(1)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Data protection by default
  Applies to: Controllers
  By default, process only the data needed for each purpose, in amount, extent, storage period and accessibility. Do not make personal data available to an indefinite number of people without the person's intervention.
  [GDPR, Article 25(2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Impact assessment

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

NIST Privacy Framework ID.RA-P

Nothing in the acts covered.

- When an impact assessment is needed
  Applies to: Controllers
  Assess the impact on personal data before processing that is likely to cause high risk, especially with new technologies. It is required for systematic and extensive automated evaluation with legal or similarly significant effects, large-scale special category or criminal data, and large-scale systematic monitoring of a publicly accessible area.
  [GDPR, Article 35(1) and (3)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- What the assessment contains
  Applies to: Controllers
  Describe the processing and its purposes, assess necessity and proportionality, assess the risks to people, and set out the measures to address them. Seek the advice of the DPO where one is designated, and where appropriate the views of those affected. Where necessary, review whether processing follows the assessment, at least when the risk changes.
  [GDPR, Article 35(2), (7), (9) and (11)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Prior consultation
  Applies to: Controllers
  Consult the supervisory authority before processing if the assessment shows the processing would result in a high risk in the absence of measures taken by the controller to mitigate it. Provide responsibilities, purposes and means, safeguards, DPO contact details, the assessment and anything else the authority asks for.
  [GDPR, Article 36(1) to (3)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Records of processing

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

NIST Privacy Framework ID.IM-P

Nothing in the acts covered.

- Controller's record of processing
  Applies to: Controllers
  Keep a written or electronic record of the name and contact details of the controller and any joint controller, representative and DPO, purposes, categories of people, data and recipients, transfers, erasure time limits and security measures where possible, and show it to the authority on request. The duty does not apply to organisations under 250 persons, unless the processing is likely to risk people's rights, is not occasional, or includes special category or criminal data.
  [GDPR, Article 30(1), (3), (4) and (5)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Processor's record of processing
  Applies to: Processors
  Keep a written or electronic record of the name and contact details of the processor, each controller served and any representative and DPO, the categories of processing for each controller, transfers and, where possible, security measures. Show it to the authority on request. The same 250-person exemption applies.
  [GDPR, Article 30(2) to (5)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Data protection officer

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

NIST Privacy Framework GV.PO-P

Nothing in the acts covered.

- Designate a data protection officer
  Designate a DPO if the organisation is a public body, except courts acting in their judicial capacity, if its core activities need regular and systematic large-scale monitoring of people, or if they involve large-scale special category or criminal data. Choose the DPO for expertise in data protection law and practice. Publish the DPO's contact details and give them to the authority.
  [GDPR, Article 37(1), (5) and (7)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Position and tasks of the DPO
  Involve the DPO promptly in all data protection issues and give the resources and access needed. The DPO takes no instructions on these tasks, cannot be dismissed or penalised for doing them, and reports to the highest management level, and other duties must not create a conflict of interests. The DPO advises, monitors compliance including staff training and audits, advises on impact assessments and acts as contact point for the authority.
  [GDPR, Articles 38 and 39](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### International transfers

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

Nothing in the acts covered.

- Transfers need a Chapter V ground
  Transfer personal data to a third country or international organisation, including onward transfers, only under the conditions of Chapter V. A Commission adequacy decision allows a transfer without specific authorisation.
  [GDPR, Articles 44 and 45](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Appropriate safeguards
  Without an adequacy decision, transfer only with appropriate safeguards and enforceable rights and remedies for people. Options without specific authority approval include binding corporate rules approved under Article 47, standard data protection clauses, and approved codes or certification with binding commitments. Bespoke contractual clauses need the authority's authorisation.
  [GDPR, Articles 46 and 47](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Third-country orders
  Treat a third-country court or authority order to transfer or disclose personal data as recognised or enforceable only where it rests on an international agreement, such as a mutual legal assistance treaty, without prejudice to other Chapter V grounds.
  [GDPR, Article 48](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Derogations for specific situations
  Without adequacy or safeguards, transfer only on a listed ground such as explicit informed consent, contract need, important public interest, legal claims or vital interests. As a last resort, a non-repetitive transfer about few people may rest on compelling legitimate interests not overridden by the person's interests or rights, if the controller assesses it, applies safeguards, informs the authority and the people concerned, and records it. Public authorities exercising public powers cannot use the consent, contract or last-resort grounds.
  [GDPR, Article 49](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

## Supervision and enforcement

### Cooperation with supervisors

**Both cover it** read the wording below

- 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)

- Cooperate with supervisory authority powers
  Cooperate with the supervisory authority on request. The authority can order information, audit, access data and premises, and issue warnings, reprimands and orders, including a processing ban, suspension of data flows or a fine.
  [GDPR, Articles 31 and 58](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Penalties and liability

**Both cover it** read the wording below

- 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)

- Fines for operational obligations
  Infringing the duties of controllers and processors in Articles 8, 11, 25 to 39, 42 and 43, or of certification and monitoring bodies, can be fined, and fines are set case by case to be effective, proportionate and dissuasive. Several infringements in the same or linked processing operations are capped at the amount for the gravest one.
  [GDPR, Article 83(1) to (4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Fines for principles, rights and transfers
  Infringing the principles and consent requirements in Articles 5, 6, 7 and 9, rights in Articles 12 to 22, transfer requirements in Articles 44 to 49, Member State law adopted under Chapter IX, or ignoring an authority's order or denying it access can be fined at the higher level.
  [GDPR, Article 83(5) and (6)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#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 ePrivacy](https://grc.plus/compare/eprivacy/)
- [Compare GDPR](https://grc.plus/compare/gdpr/)

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