Cosmote
bd_1f46abd7a50c676c · schema v1 · pii pii-v1
Full breach record for Cosmote →Regulator's decision — not a breach notification
This record is a regulator's decision, not the organisation's own breach notice. Breach-notification fields (discovery date, notification clock) are structurally absent — what this source establishes is the outcome and the provisions the decision cites.
The HDPA (Greece) issued a other regarding Cosmote. A fine of EUR 9,100,000 was imposed. GDPR articles: Article 5(1)(a) GDPR, Article 5(1)(f) GDPR, Article 5(2) GDPR, Article 13 GDPR, Article 14 GDPR, Article 25(1) GDPR, Article 26 GDPR, Article 28 GDPR, Article 32 GDPR, Article 35(7) GDPR, Article 83 GDPR.
P pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Nov 30, 2021
Filed
—
No linked breach filing · watching
Compliance clocks stay unassessable until a breach filing is linked. This record is the regulator's action, not a breach notice. Dashed segments fill in automatically when corroboration arrives.
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
If an SEC 8-K, state-AG notice or victim statement lands, DisclosureLens merges it into an incident and links it here.
Source ceiling
- data categories
- cross-border scope
- outcome + articles (decisions)
- discovery date
- affected count
- notification clock
See the underlying breach notice, if filed.