ePrivacy Lithuania vs SecNumCloud
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 0 of 0 topics. Each verdict names what it rests on; read the wording before relying on it.
- ePrivacy Lithuania Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
- SecNumCloud Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
| Topic | ePrivacy Lithuania | SecNumCloud | Verdict |
|---|
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
National requirements
2 national requirements recorded, as departures from the Directive or additions to it. Everything else applies as the Directive has it.
Status
Reviewed against the official texts.
Included
- SecNumCloud SecNumCloud requirements framework v3.2 (8 March 2022), approved by order of 12 August 2026; Law No. 2024-449 of 21 May 2024 (SREN), Article 31; Decree No. 2026-272 of 14 April 2026
Status
Reviewed against the official texts.
Key Numbers
Deadline
ePrivacy Lithuania: Without undue delay after detection (Providers of publicly available electronic communications services); Immediately (Providers contracted by a provider of publicly available electronic communications services)
SecNumCloud: Not in the acts covered
Goes to
ePrivacy Lithuania: 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)
SecNumCloud: Not in the acts covered
Evidence to keep
ePrivacy Lithuania: Inventory of personal data breachesPersonal Data Breach Under the ePrivacy Directive (Providers of publicly available electronic communications services)
SecNumCloud: Not in the acts covered
Incident reports go to
ePrivacy Lithuania: Competent national authority (Providers of publicly available electronic communications services)
SecNumCloud: Not in the acts covered
First notice of an incident
ePrivacy Lithuania: Within 24 hours of detection, where feasible (Providers of publicly available electronic communications services)
SecNumCloud: Not in the acts covered
Incident notification
ePrivacy Lithuania: Within three days of the initial notification (Providers of publicly available electronic communications services)
SecNumCloud: Not in the acts covered
Maximum fines
ePrivacy Lithuania: Set by each Member State; no EU maximum (Member States and competent national authorities)
SecNumCloud: Not 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. 13 topics where all apply the Directive as it is are not shown.
More Comparisons
Subject to more than one?
We run one control set for both, without doing the work twice. Ask what that saves you.