ePrivacy vs UK GDPR
Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.
At a Glance
They differ on 17 of 18 topics. Each verdict names what it rests on; read the wording before relying on it.
- ePrivacy Asks more on 0 topics Alone on 10 topics More detailed on 2 topics
- UK GDPR Asks more on 0 topics Alone on 5 topics More detailed on 0 topics
| Topic | ePrivacy | UK GDPR | Verdict |
|---|---|---|---|
| Governance | |||
| Security policy | ePrivacy: 1 | UK GDPR: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Protection | |||
| Access control | ePrivacy: 1 | UK GDPR: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Data security | ePrivacy: 1 | UK GDPR: 1 | Both cover itread the wording below |
| Network security | ePrivacy: 1 | UK GDPR: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Secure communications | ePrivacy: 1 | UK GDPR: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Detection and response | |||
| Incident handling | ePrivacy: 1 | UK GDPR: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Reporting to authorities | ePrivacy: 4 | UK GDPR: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Informing customers and the public | ePrivacy: 2 | UK GDPR: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Third parties and supply chain | |||
| Supplier and third-party risk | ePrivacy: 1 | UK GDPR: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Contract requirements | ePrivacy: – | UK GDPR: 1 | Only UK GDPRno specific requirement on the other side in the acts covered |
| Privacy and data protection | |||
| Lawful processing | ePrivacy: 4 | UK GDPR: 2 | ePrivacy more detailedmore requirements on this, not necessarily stricter |
| Transparency | ePrivacy: 3 | UK GDPR: 1 | ePrivacy more detailedmore requirements on this, not necessarily stricter |
| Rights of individuals | ePrivacy: – | UK GDPR: 1 | Only UK GDPRno specific requirement on the other side in the acts covered |
| Impact assessment | ePrivacy: – | UK GDPR: 1 | Only UK GDPRno specific requirement on the other side in the acts covered |
| Records of processing | ePrivacy: – | UK GDPR: 1 | Only UK GDPRno specific requirement on the other side in the acts covered |
| International transfers | ePrivacy: – | UK GDPR: 1 | Only UK GDPRno specific requirement on the other side in the acts covered |
| Supervision and enforcement | |||
| Cooperation with supervisors | ePrivacy: 1 | UK GDPR: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Penalties and liability | ePrivacy: 1 | UK GDPR: – | Only ePrivacyno 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
- ePrivacy 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
Status
Reviewed against the official texts.
Included
- UK GDPR Regulation (EU) 2016/679 as it forms part of UK law; Data Protection Act 2018 (c. 12); Data (Use and Access) Act 2025 (c. 18)
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)
UK GDPR: Not in the acts covered
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)
UK GDPR: Not in the acts covered
Evidence to keep
ePrivacy: Inventory of personal data breachesPersonal Data Breach Under the ePrivacy Directive (Providers of publicly available electronic communications services)
UK GDPR: Not in the acts covered
Incident reports go to
ePrivacy: Competent national authority (Providers of publicly available electronic communications services)
UK GDPR: Not in the acts covered
First notice of an incident
ePrivacy: Within 24 hours of detection, where feasible (Providers of publicly available electronic communications services)
UK GDPR: Not in the acts covered
Incident notification
ePrivacy: Within three days of the initial notification (Providers of publicly available electronic communications services)
UK GDPR: Not in the acts covered
Maximum fines
ePrivacy: Set by each Member State; no EU maximum (Member States and competent national authorities)
UK GDPR: Not in the acts covered
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
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 dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. 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.
Nothing in the acts covered.
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 dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. 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.
Nothing in the acts covered.
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 dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. 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.
Security
Appropriate technical and organisational security, tested regularly.
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 dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. 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.
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 dataAny data processed to convey a communication over an electronic communications network or to bill for it. Providers must erase or anonymise traffic data when it is no longer needed for transmission, subject to permitted further processing and lawful statutory derogations under Article 15 of the ePrivacy Directive. without the users' consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard., 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.
Nothing in the acts covered.
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
Keep a breach inventory
Applies to: Providers of publicly available electronic communications services
Keep an inventory of personal data breachesPersonal Data Breach Under the ePrivacy Directive 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.
Nothing in the acts covered.
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
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 breachA breach of security leading to accidental or unlawful destruction, loss, alteration or unauthorised disclosure of or access to personal data. A controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of the breach, unless it is unlikely to result in a risk to people's rights and freedoms. 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)
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.
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
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 breachA breach of security leading to accidental or unlawful destruction, loss, alteration or unauthorised disclosure of or access to personal data. A controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of the breach, unless it is unlikely to result in a risk to people's rights and freedoms..
Nothing in the acts covered.
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
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.
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
Nothing in the acts covered.
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
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 breachA breach of security leading to accidental or unlawful destruction, loss, alteration or unauthorised disclosure of or access to personal data. A controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of the breach, unless it is unlikely to result in a risk to people's rights and freedoms..
Nothing in the acts covered.
Contract requirements
Only UK 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.
Processors
Contracts with processors setting out their duties.
Privacy and data protection
Lawful processing
ePrivacy more detailed more requirements on this, not necessarily stricter
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 consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. This does not apply to storage or access solely to carry a communication, or strictly necessary for a service the user explicitly asked for.
Traffic data
Applies to: Providers of public communications networks and publicly available electronic communications services
Erase or anonymise traffic dataAny data processed to convey a communication over an electronic communications network or to bill for it. Providers must erase or anonymise traffic data when it is no longer needed for transmission, subject to permitted further processing and lawful statutory derogations under Article 15 of the ePrivacy Directive. 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 consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. Tell subscribers what is processed and for how long, and limit handling to authorised staff.
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 consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. 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 consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. at any time and refuse temporarily, simply and free of charge.
Unsolicited direct marketing
Applies to: Any organisation sending electronic direct marketing
Use automated calling, fax or email for direct marketing only with prior consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. 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 consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. and opt-outAn opt-out is a way for a person to refuse an activity or stop further participation. In direct marketing, it means taking a step such as unsubscribing from messages. In a default-on arrangement, the activity proceeds unless the person refuses. Having an opt-out does not establish valid consent where the applicable law requires a positive agreement beforehand. requirements protect subscribers who are natural persons; Member States protect the interests of other subscribers.
Principles and accountability
Process personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. lawfully, fairly and transparently, for specified purposes, minimised, accurate, kept no longer than needed and secure, and be able to show it.
Lawful bases
Each processing has a lawful basis, including the recognised legitimate interestsA UK GDPR lawful basis for using personal information when this is necessary for a specified public-interest purpose listed in Annex 1. The purposes include safeguarding, emergencies, crime prevention, national security and certain disclosures supporting public tasks. Organisations must meet the relevant conditions and show that the use is necessary. Under ordinary legitimate interests, they must also check whether the affected person's interests, rights or freedoms outweigh their own interests. That additional check is not required for recognised legitimate interests. Other data protection duties still apply. added in 2025.
Transparency
ePrivacy more detailed more requirements on this, not necessarily stricter
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 consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. This does not apply to storage or access solely to carry a communication, or strictly necessary for a service the user explicitly asked for.
Traffic data
Applies to: Providers of public communications networks and publicly available electronic communications services
Erase or anonymise traffic dataAny data processed to convey a communication over an electronic communications network or to bill for it. Providers must erase or anonymise traffic data when it is no longer needed for transmission, subject to permitted further processing and lawful statutory derogations under Article 15 of the ePrivacy Directive. 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 consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. Tell subscribers what is processed and for how long, and limit handling to authorised staff.
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 consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. 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 consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. at any time and refuse temporarily, simply and free of charge.
Transparency
Tell people what you do with their data, when you collect it.
Rights of individuals
Only UK GDPR no specific requirement on the other side in the acts covered
NIST Privacy Framework CT.DM-P
Nothing in the acts covered.
Individuals' rights
Access, rectification, erasure, restriction, portability, objection and rights on automated decisions, answered within a month.
Impact assessment
Only UK GDPR no specific requirement on the other side in the acts covered
NIST Privacy Framework ID.RA-P
Nothing in the acts covered.
Impact assessments
A data protection impact assessmentAn assessment of the impact of planned processing on the protection of personal data, carried out before processing that is likely to result in a high risk to people's rights and freedoms. Article 35 of the GDPR makes it mandatory in those cases. before high-risk processing.
Records of processing
Only UK GDPR no specific requirement on the other side in the acts covered
NIST Privacy Framework ID.IM-P
Nothing in the acts covered.
Records of processing
A record of processing activitiesA written inventory of an organisation's activities involving personal data, used to understand and demonstrate how that information is handled. Under Article 30 of the EU GDPR and UK GDPR, controllers and processors have different record requirements. A controller's record covers matters such as purposes, data and recipient categories, retention and security; a processor's record focuses on processing performed for its clients., with limited exemptions for small organisations.
International transfers
Only UK GDPR no specific requirement on the other side in the acts covered
Nothing in the acts covered.
International transfers
Transfers outside the UK under adequacy regulationsUK Adequacy Regulations, appropriate safeguards such as the International Data Transfer Agreement, or exceptions.
Supervision and enforcement
Cooperation with supervisors
Only ePrivacy no specific requirement on the other side 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 dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. 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.
Nothing in the acts covered.
Penalties and liability
Only ePrivacy no specific requirement on the other side 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.
Nothing in the acts covered.
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
Subject to more than one?
We run one control set for both, without doing the work twice. Ask what that saves you.