Data Protection Monitor
Global Privacy & Data Protection Intelligence

Greece Data Protection & Privacy Regulation

GR schema gdpri-v2 trajectory: not yet assessed regulated (omnibus) overlaps: Sentinel (AML/CFT), World Payments, artificial-intelligence

Last updated · 10 categories · 87 claims · 46 sources in the cumulative register

The Hellenic Data Protection Authority's enforcement record this cycle centres on a cluster of controller/processor-duty and sectoral findings rather than a single dominant event.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Cross-Border & Adequacy, Sectoral Watch, Children & Vulnerable Groups (3 open gaps).

Evidence re-verified: ·Position last changed: ·
Record history & provenance ▾

Methodology & record provenance: Module confidence is derived from the underlying claims (source tier and primary excerpt retention), while statutory legal force is tracked independently.

Review status: AI-synthesised · Tier-1/2 verified · As-of date: 2026-10-26

Framework postureRegulated (omnibus)10 of 10 modules populated · AI-synthesised · Tier-1/2 verified
Lead supervisory authorityHellenic Data Protection Authority (HDPA)Primary statutory & supervisory perimeter
Next milestone (> 2026-10-26)None scheduledNo dated future statutory milestone on record
Module coverage & confidence10 / 10 modules assessed0 Confirmed · 10 Probable · 0 Uncertain

Law made at European Economic Area (Bloc) level that applies in Greece is covered once, on the European Economic Area (Bloc) page. This page covers Greece’s own layer: implementation, national authorities, national options and local enforcement.

Jurisdiction brief

Latest update · 25 October 2026

Lead Signal

Greece's Hellenic Data Protection Authority published Decision No. 15, dated 28 July 2026 and surfaced via the European Data Protection Board's national-news channel on 8 October 2026, fining the Ministry of Social Cohesion and Family Affairs two hundred thousand euro and its processor, E.E.T.A.A. S.A., one hundred fifty thousand euro. The decision followed violations of Articles 25, 28 and 32 to 34 of the GDPR, arising from outdated IT systems and an inadequate Article 28 processing agreement between the ministry and its processor.

Key regulatory facts for Greece
Regulatory DimensionGreece Standing Position
JurisdictionGreece (GR)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 87 sourced findings)
Regulator & FrameworkFull GDPR direct effect plus a comprehensive, in-force national implementing statute and an active, well-resourced-relative-to-peers regulator.
Lawful Processing & Special DataComprehensive statutory lawful-basis and special-category framework, though the HDPA itself has flagged one internal inconsistency (Article 5 vs GDPR Article 6) and no distinct national pseudonymisation safe-harbour...
Data Subject RightsCore rights actively enforced (access); ancillary rights (restriction, portability) rely on direct GDPR application without located national supplements.
Controller/Processor DutiesStrong, evidenced enforcement across accountability, security and breach sub-modules; retention/disposal relies solely on GDPR Article 5(1)(e).
Primary Instruments CitedGovernment Gazette of the Hellenic Republic / HDPA, IAPP, OneTrust DataGuidance, European Data Protection Board, IAPP
Last Confirmed / Updated2026-11-03 (46 sources in cumulative register)

#

Full GDPR direct effect plus a comprehensive, in-force national implementing statute and an active, well-resourced-relative-to-peers regulator.

Primary frameworkGDPR (Regulation (EU) 2016/679) as implemented and supplemented by Law 4624/2019
Traffic-light rationale — GreenFull GDPR direct effect plus a comprehensive, in-force national implementing statute and an active, well-resourced-relative-to-peers regulator.

Sub-modules (5)

Regulator And AuthorityGreen

HDPA is the constitutionally and statutorily established supervisory authority.

Claims (3):

  • The Hellenic Data Protection Authority (HDPA) is the supervisory authority responsible for enforcing the GDPR and Law 4624/2019 in Greece.
  • Hellenic Data Protection Authority — A constitutionally established independent public authority supervising the application of the GDPR, Law 4624/2019 and Law 3471/2006.
  • Hellenic Data Protection Authority (HDPA) — The HDPA is a constitutionally-established independent authority (Art 9A of the Greek Constitution), currently operating under Law 4624/2019, implementing GDPR and transposing Directive 2016/680; first established under Law 2472/1997

Act And InstrumentsGreen

Law 4624/2019 (GDPR implementation + LED transposition) and Law 3471/2006 (electronic communications privacy) form the core instruments.

Claims (3):

  • Greece implemented the GDPR through Law 4624/2019, which supplements the GDPR on matters left to Member State discretion, transposes the Law Enforcement Directive (EU) 2016/680, and re-establishes the HDPA.
  • Law 3471/2006 (the Electronic Communications Privacy Law) supplements the GDPR/Law 4624/2019 framework and governs cookies, trackers and electronic communications privacy in Greece.
  • Regulation (EU) 2016/679 (GDPR) — 2018-05-25

Material ScopeGreen

HDPA competence extends to essentially all national and transnational processing, with a national-security carve-out.

Claims (1):

  • The HDPA is competent to supervise every national and transnational personal data processing operation within its jurisdiction, with limited exceptions for national security matters.

Territorial ScopeGreen

HDPA has applied the GDPR Article 3 targeting criterion to assert jurisdiction over non-established controllers.

Claims (1):

  • The HDPA applies the GDPR Article 3 targeting criterion to assert territorial competence over non-established controllers, such as Clearview AI, that process the personal data of individuals in Greece.

Regulator Registration And FilingAmber

No general controller registration/notification regime survives under the GDPR-era framework; accountability/ROPA obligations replace the old Law 2472/1997 notification system.

Claims (1):

  • Greece's GDPR-era regime does not impose a general notification/registration requirement on controllers; the prior registration system under Law 2472/1997 was replaced by the GDPR's accountability and records-of-processing obligations.
Category narrative 56 words

Greece operates a mature, GDPR-aligned omnibus regime. The Hellenic Data Protection Authority (HDPA) is the primary supervisory authority, re-established and empowered by Law 4624/2019, which implements the GDPR domestically, transposes the Law Enforcement Directive (EU) 2016/680, and supplements the Regulation on matters left to Member State discretion. Law 3471/2006 supplements the framework for electronic communications privacy.

No periodic updates recorded in this cycle

Sources and claims (9)
  1. Confirmed Government Gazette of the Hellenic Republic / HDPA — The Hellenic Data Protection Authority (HDPA) is the supervisory authority responsible for enforcing the GDPR and Law 4624/2019 in Greece. observed
  2. Confirmed IAPP — Greece implemented the GDPR through Law 4624/2019, which supplements the GDPR on matters left to Member State discretion, transposes the Law Enforcement Directive (EU) 2016/680, and re-establishes the HDPA. observed
  3. Confirmed OneTrust DataGuidance — Law 3471/2006 (the Electronic Communications Privacy Law) supplements the GDPR/Law 4624/2019 framework and governs cookies, trackers and electronic communications privacy in Greece. observed
  4. Confirmed European Data Protection Board — The HDPA is competent to supervise every national and transnational personal data processing operation within its jurisdiction, with limited exceptions for national security matters. observed
  5. Confirmed IAPP — The HDPA applies the GDPR Article 3 targeting criterion to assert territorial competence over non-established controllers, such as Clearview AI, that process the personal data of individuals in Greece. observed
  6. Probable IAPP — Greece's GDPR-era regime does not impose a general notification/registration requirement on controllers; the prior registration system under Law 2472/1997 was replaced by the GDPR's accountability and records-of-processing obligations. observed
  7. Confirmed Publications Office of the EU — Hellenic Data Protection Authority — A constitutionally established independent public authority supervising the application of the GDPR, Law 4624/2019 and Law 3471/2006. observed
  8. Confirmed DataGuidance — Hellenic Data Protection Authority (HDPA) — The HDPA is a constitutionally-established independent authority (Art 9A of the Greek Constitution), currently operating under Law 4624/2019, implementing GDPR and transposing Directive 2016/680; first established under Law 2472/1997 observed
  9. Confirmed Hellenic Data Protection Authority — Regulation (EU) 2016/679 (GDPR) — 2018-05-25

#

Comprehensive statutory lawful-basis and special-category framework, though the HDPA itself has flagged one internal inconsistency (Article 5 vs GDPR Article 6) and no distinct national pseudonymisation safe-harbour was found.

Primary frameworkGDPR Articles 6, 7, 9 as supplemented by Law 4624/2019 Articles 5, 21-23
Traffic-light rationale — GreenComprehensive statutory lawful-basis and special-category framework, though the HDPA itself has flagged one internal inconsistency (Article 5 vs GDPR Article 6) and no distinct national pseudonymisation safe-harbour was found.
D2 · Lawful Processing — Full Module Record4 sub-modules · 37 words · 5 traced claims · Re-verified 2026-11-03

The decision headline, regulatory posture (Green), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Core rights actively enforced (access); ancillary rights (restriction, portability) rely on direct GDPR application without located national supplements.

Primary frameworkGDPR Articles 12-22 (direct effect), no material national derogation identified
Traffic-light rationale — GreenCore rights actively enforced (access); ancillary rights (restriction, portability) rely on direct GDPR application without located national supplements.

Sub-modules (5)

Access RightGreen

Actively enforced; multiple fines for DSAR non-compliance.

Claims (3):

  • The HDPA has enforced the GDPR Article 15 right of access, including fining UGHL €7,000 for unlawful data processing and failure to fulfill a data access request.
  • The HDPA fined an association for people with Autism Spectrum Disorder for failing to satisfy a parental right-of-access request for CCTV footage and for unlawfully transmitting a minor's sensitive data to a third party.
  • HDPA — Administrative fine of EUR 30,000 on a telecommunications company for violating GDPR Articles 12(1),(2),(3),(4), 15 and 18 concerning right of access and restriction of processing.

Rectification And ErasureAmber

Greece participated in the EDPB's 2025 CEF right-to-erasure action.

Claims (2):

  • Greece participated as one of 32 DPAs in the EDPB's 2025 Coordinated Enforcement Framework (CEF) action examining implementation of the GDPR right to erasure.
  • Hellenic Data Protection Authority (HDPA) — HDPA participated in the EDPB's 2025 Coordinated Enforcement Framework (CEF) action concerning controllers' handling of erasure requests, presented at HDPA's Data Protection Day 2026 event

Restriction And ObjectionRed

No Greece-specific derogation identified.

Claims (1):

  • No Greece-specific derogation from the GDPR Articles 18 and 21 restriction/objection rights was identified beyond direct application of the Regulation.

Data PortabilityRed

No Greece-specific derogation identified.

Claims (1):

  • No Greece-specific derogation from the GDPR Article 20 data portability right was identified; the right applies as set out directly in the Regulation.

Deadlines And Response WindowsAmber

GDPR Article 12(3) one-month (extendable) window applies directly.

Claims (1):

  • The GDPR Article 12(3) one-month response deadline (extendable by two further months for complex requests) applies directly to Greek controllers without a shorter or longer national derogation identified.
Category narrative 43 words

GDPR Articles 12-22 apply directly. HDPA enforcement activity demonstrates active protection of the access right in particular; erasure was the subject of a 2025 EDPB Coordinated Enforcement Framework action involving Greece. No distinct Greek derogations were identified for restriction, objection or portability rights.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (8)
  1. Confirmed OneTrust DataGuidance — The HDPA has enforced the GDPR Article 15 right of access, including fining UGHL €7,000 for unlawful data processing and failure to fulfill a data access request. observed
  2. Confirmed European Data Protection Board — The HDPA fined an association for people with Autism Spectrum Disorder for failing to satisfy a parental right-of-access request for CCTV footage and for unlawfully transmitting a minor's sensitive data to a third party. observed
  3. Probable OneTrust DataGuidance — Greece participated as one of 32 DPAs in the EDPB's 2025 Coordinated Enforcement Framework (CEF) action examining implementation of the GDPR right to erasure. observed
  4. Uncertain Government Gazette of the Hellenic Republic / HDPA — No Greece-specific derogation from the GDPR Articles 18 and 21 restriction/objection rights was identified beyond direct application of the Regulation. observed
  5. Uncertain Government Gazette of the Hellenic Republic / HDPA — No Greece-specific derogation from the GDPR Article 20 data portability right was identified; the right applies as set out directly in the Regulation. observed
  6. Probable Government Gazette of the Hellenic Republic / HDPA — The GDPR Article 12(3) one-month response deadline (extendable by two further months for complex requests) applies directly to Greek controllers without a shorter or longer national derogation identified. observed
  7. Confirmed European Data Protection Board — HDPA — Administrative fine of EUR 30,000 on a telecommunications company for violating GDPR Articles 12(1),(2),(3),(4), 15 and 18 concerning right of access and restriction of processing. observed
  8. Probable Hellenic Data Protection Authority — Hellenic Data Protection Authority (HDPA) — HDPA participated in the EDPB's 2025 Coordinated Enforcement Framework (CEF) action concerning controllers' handling of erasure requests, presented at HDPA's Data Protection Day 2026 event observed

#

Strong, evidenced enforcement across accountability, security and breach sub-modules; retention/disposal relies solely on GDPR Article 5(1)(e).

Primary frameworkGDPR Articles 5, 24-32, 33-35, 37-39 as supplemented by Law 4624/2019
Traffic-light rationale — GreenStrong, evidenced enforcement across accountability, security and breach sub-modules; retention/disposal relies solely on GDPR Article 5(1)(e).
Periodic update · new data 2026-10-25

Controller/Processor Duties

The Hellenic Data Protection Authority's Decision No. 15, dated 28 July 2026 and published via the European Data Protection Board's national-news channel on 8 October 2026, fined the Ministry of Social Cohesion and Family Affairs two hundred thousand euro and its processor, E.E.T.A.A. S.A., one hundred fifty thousand euro. The decision arose from a data breach and was grounded in violations of Articles 25, 28 and 32 to 34 of the GDPR. The Authority's reasoning centred on outdated IT systems maintained by the processor and an inadequate Article 28 processing agreement between the ministry as controller and E.E.T.A.A. as processor, meaning the deficiency was found at both the technical-measures level and the contractual-governance level of the controller-processor relationship.

The decision is notable for addressing both parties to a processing relationship in a single action, with separate and substantial fines attaching to the controller and the processor respectively, rather than concentrating liability on the public-sector controller alone. This distributes accountability for security and contractual adequacy across both sides of a processing arrangement involving a public ministry and a public-sector-adjacent processing entity.

Outlook

Further detail on the specific IT system deficiencies and the precise terms found wanting in the Article 28 agreement would sharpen understanding of what the Authority now expects from public-sector processing arrangements of this kind.

Periodic update · new data 2026-10-18

Controller/Processor Duties

The Hellenic Data Protection Authority fined the Ministry of Social Cohesion and Family Affairs EUR200,000 and its processor E.E.T.A.A. S.A. EUR150,000, a combined total of EUR350,000, in a decision dated 28 July 2026 and published by the European Data Protection Board on 8 October 2026. The decision followed a data breach and found violations of Articles 25, 28 and 32 GDPR. The breach was linked to outdated IT systems operated by the processor and the absence, at the time of the breach, of a processing agreement between the Ministry as controller and E.E.T.A.A. as processor that met Article 28's requirements. The HDPA's findings identified the processor's security failures as the primary driver of the violation, while the controller's own breach-notification obligations were found to have been met.

This decision establishes a clear enforcement marker on the consequences of operating a controller-processor relationship without a compliant Article 28 agreement in place at the time a breach occurs, and on the security-by-design and security-by-default duties under Article 25 and the processing-security duties under Article 32 that attach to the processor directly.

Outlook

Whether the HDPA issues further decisions citing this precedent, particularly in other public-sector controller-processor relationships, is the item to watch. Confirmation of any appeal against the 28 July 2026 decision has not been located.

Periodic update · new data 2026-10-11

Controller/Processor Duties

The HDPA's Decision No. 15, issued 28 July 2026, found the Ministry of Social Cohesion and Family and its processor EETAA in violation of two distinct duties. The first, under GDPR Article 28(3), was a failure to establish a formal data-processing agreement between the controller and processor. The second, under Article 32(1), was insufficient security measures, found following a data breach affecting approximately 2.5 million data subjects. The HDPA imposed a combined fine of EUR350,000, comprising EUR200,000 against the Ministry and EUR150,000 against EETAA. This decision stands as a clear instance of the HDPA applying both the formal-agreement requirement and the security-measures requirement together against a public-sector controller and its processor in the same action.

Outlook

Whether further HDPA decisions follow against other public-sector controller-processor arrangements, particularly where formal data-processing agreements may be similarly absent, is the clearest signal to watch for in this module going forward.

Periodic update · new data 2026-09-22

Controller/Processor Duties

HDPA's largest fines to date in Greece target failures in security-of-processing and transparency obligations under the GDPR: a EUR 6 million fine against COSMOTE and a EUR 3.25 million fine against OTE, addressing unclear subscriber information and inadequate security measures, including infrastructure security failures. These are the most significant financial penalties in HDPA's enforcement history and demonstrate that the authority is prepared to impose substantial fines where controller obligations around security of processing and transparent subscriber communication are found deficient, particularly in the telecommunications sector, which handles large volumes of subscriber personal data.

These fines should be read cautiously on sourcing grounds: the underlying claim is drawn from a single lower-tier aggregator source rather than a direct HDPA decision publication, so while the figures are treated as confirmed for the purposes of this brief, a Tier-1 confirmation from HDPA's own decision register would strengthen the evidentiary basis. Even with that caveat, the scale of the fines is consistent with HDPA's demonstrated willingness to escalate enforcement against controller-side security and transparency failures at large telecom operators, a pattern that sits alongside the authority's separate access-rights enforcement action this cycle.

Outlook

Confirmation of the COSMOTE and OTE fine figures via a primary HDPA decision publication remains the key outstanding verification step. Should these figures be confirmed at a Tier-1 source, they would stand as the clearest evidence yet of HDPA's capacity and willingness to impose GDPR's higher-end penalty tiers against large controllers.

D4 · Controller & Processor — Full Module Record7 sub-modules · 55 words · 14 traced claims · Re-verified 2026-11-03

The decision headline, regulatory posture (Green), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Chapter V applies with full direct effect; no Greek derogation or gap identified beyond the EU-wide framework.

Primary frameworkGDPR Chapter V (Articles 44-49), direct effect in Greece
Traffic-light rationale — GreenChapter V applies with full direct effect; no Greek derogation or gap identified beyond the EU-wide framework.
D5 · Cross-Border & Adequacy — Full Module Record6 sub-modules · 57 words · 7 traced claims · Re-verified 2026-11-03

The decision headline, regulatory posture (Green), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Strong telecoms/employment/health coverage; credit-scoring sub-module has no located sectoral statute beyond GDPR Article 22.

Primary frameworkGDPR + Law 4624/2019 sectoral provisions + Law 3471/2006 (telecoms)
Traffic-light rationale — AmberStrong telecoms/employment/health coverage; credit-scoring sub-module has no located sectoral statute beyond GDPR Article 22.
D6 · Sectoral Watch — Full Module Record7 sub-modules · 40 words · 8 traced claims · Re-verified 2026-11-03

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Core cookie/marketing regime is solid; newer adtech-specific concepts (dark patterns, GPC-style signals, clean rooms) are not distinctly regulated nationally.

Primary frameworkLaw 3471/2006 (ePrivacy transposition) + GDPR consent/legitimate-interest framework
Traffic-light rationale — AmberCore cookie/marketing regime is solid; newer adtech-specific concepts (dark patterns, GPC-style signals, clean rooms) are not distinctly regulated nationally.
D7 · AdTech & Marketing — Full Module Record6 sub-modules · 34 words · 7 traced claims · Re-verified 2026-11-03

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Strong, landmark biometric enforcement; AI-risk-assessment and ADM-transparency sub-modules remain reliant on general GDPR application pending fuller national AI-Act interface, and state-surveillance oversight faces documented independence concerns.

Primary frameworkGDPR Articles 9, 22 as supplemented by Law 4624/2019 Article 23; EU AI Act interface emerging
Traffic-light rationale — AmberStrong, landmark biometric enforcement; AI-risk-assessment and ADM-transparency sub-modules remain reliant on general GDPR application pending fuller national AI-Act interface, and state-surveillance oversight faces documented independence concerns.
D8 · AI, Biometrics & Automated — Full Module Record6 sub-modules · 62 words · 8 traced claims · Re-verified 2026-11-03

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Parental-consent threshold is clearly defined and enforced; age-verification, minor-profiling and dependent-adults sub-modules rely solely on general GDPR provisions.

Primary frameworkLaw 4624/2019 Article 21 (digital consent age) + GDPR
Traffic-light rationale — AmberParental-consent threshold is clearly defined and enforced; age-verification, minor-profiling and dependent-adults sub-modules rely solely on general GDPR provisions.
D9 · Children's Privacy — Full Module Record5 sub-modules · 44 words · 6 traced claims · Re-verified 2026-11-03

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Powers and historical enforcement activity are robust and well evidenced; the recent_developments_180d sub-module could not be populated with a confirmed decision inside the strict 180-day window, and collective-redress mechanisms remain comparatively underdeveloped.

Primary frameworkGDPR Articles 58, 77-84, 83 as supplemented by Law 4624/2019
Traffic-light rationale — AmberPowers and historical enforcement activity are robust and well evidenced; the recent_developments_180d sub-module could not be populated with a confirmed decision inside the strict 180-day window, and collective-redress mechanisms remain comparatively underdeveloped.
Periodic update · new data 2026-10-25

Enforcement & Redress

The Hellenic Data Protection Authority's enforcement activity has remained elevated over the trailing months, with Decision No. 15, published 8 October 2026, fining the Ministry of Social Cohesion and Family Affairs two hundred thousand euro and its processor E.E.T.A.A. S.A. one hundred fifty thousand euro, the largest of the Authority's recent decisions by combined value. This followed the General Hospital of Thessaloniki fine of twenty-five thousand euro on 7 July 2026, issued after a weekly surgery-patient list was published online in violation of Articles 5(1)(f), 12, 13, 32(1), 33(1), 34(1) and 37 of the GDPR. Together, these decisions, alongside a further action referenced in the Authority's own enforcement pattern, bring the total fined across three decisions in the trailing four months to four hundred seventy-five thousand euro.

The Authority exercises these powers under Article 58 of the GDPR and Article 15 of Law 4624/2019, the national statute implementing the GDPR and transposing Directive 2016/680, which together give it control, corrective, advisory and licensing competence. The pattern across these recent decisions, spanning a public ministry and its processor, and a public hospital, indicates sustained attention to public-sector and public-adjacent data controllers rather than a single-sector enforcement focus.

Outlook

The trajectory of three fines in four months suggests continued active enforcement; what would clarify the picture further is whether a comparable pace continues into the next reporting window and whether any of these decisions are subject to appeal.

Periodic update · new data 2026-10-18

Enforcement & Redress

The most recent public enforcement record from the Hellenic Data Protection Authority is the EUR350,000 combined fine against the Ministry of Social Cohesion and Family Affairs and its processor E.E.T.A.A. S.A., a decision dated 28 July 2026 and published by the European Data Protection Board on 8 October 2026. The fine split EUR200,000 to the Ministry as controller and EUR150,000 to E.E.T.A.A. as processor, reflecting GDPR Articles 25, 28 and 32 violations tied to outdated IT systems and the absence of a compliant Article 28 processing agreement at the time of the breach. No change to Greece's maximum fine tiers under GDPR accompanies this decision; the fine was assessed within the existing statutory maxima.

Whether any newer HDPA enforcement decision falls within a narrower, more recent reporting window has not been resolved; the EETAA/Ministry decision, reported via the European Data Protection Board on 8 October 2026, is the most recent public record located.

Outlook

The item to watch is whether the HDPA publishes further enforcement decisions, and whether the EETAA/Ministry decision is appealed. The precedent set regarding the consequences of an absent Article 28 agreement is likely to inform how the HDPA approaches future public-sector processor-relationship breaches.

Periodic update · new data 2026-10-11

Enforcement & Redress

The HDPA's maximum fine exposure extends to EUR20 million or 4% of global annual turnover for private entities, and up to EUR10 million for public bodies. Against that ceiling, the authority's 2026 enforcement record shows at least three dated decisions: a EUR100,000 fine against the ZeniTh gas company on 5 June 2026, a EUR25,000 fine against the General Hospital of Thessaloniki on 7 July 2026, and the EUR350,000 combined fine against the Ministry of Social Cohesion and Family and EETAA on 28 July 2026. This sequence of three fines within roughly two months indicates a sustained enforcement tempo for the year, rather than a single isolated action, with the Ministry/EETAA decision the largest of the three both in fine amount and in the scale of data subjects affected (approximately 2.5 million).

Outlook

Continuation of this enforcement tempo, and whether further decisions in the second half of 2026 approach or exceed the public-body maximum of EUR10 million, are the clearest signals to watch for in assessing the authority's enforcement trajectory.

Periodic update · new data 2026-09-22

Enforcement & Redress

HDPA has launched the EDPB's 2026 Coordinated Enforcement Framework (CEF) action on Transparency and the Right to Information of Data Subjects, joining other EU data protection authorities in a synchronised enforcement initiative around this theme. This is a confirmed, forward-looking enforcement development: it signals that transparency and the right-to-information obligations will receive coordinated, EU-wide scrutiny in the coming period, with Greece an active participant rather than an observer.

This new coordinated action sits alongside HDPA's already substantial telecom-sector enforcement record this cycle, comprising the EUR 30,000 access-and-restriction-rights fine and the EUR 6 million and EUR 3.25 million security-and-transparency fines against COSMOTE and OTE respectively. Taken together, these three developments indicate a sustained and escalating enforcement posture in Greece: HDPA is both actively sanctioning past violations and positioning itself for forward enforcement activity through EU-coordinated mechanisms. The combination of a well-established individual case record and participation in a new coordinated framework action suggests transparency and information-rights compliance will remain a live enforcement priority for organisations processing personal data in Greece.

Outlook

The EDPB CEF action on transparency is the clearest forward marker this cycle. Its findings, once published, are likely to surface further Greece-specific transparency and information-rights enforcement activity, potentially extending beyond the telecommunications sector that has dominated HDPA's enforcement record to date.

D10 · Enforcement & Redress — Full Module Record6 sub-modules · 106 words · 15 traced claims · Re-verified 2026-11-03

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

No categories match.

Filters combine as OR inside a group and AND across groups.

Provenance and declared absence

Disclosure model: category cards load OPEN; narratives render in full; standing narratives load as a clamped teaser with an explicit “read full” control carrying the true word count. No text is hidden without disclosing how much of it there is.

Sub-modules are DP-specific nested subsections with their own real per-sub-module traffic light, rendered under each category across all regulatory modules.

Traffic-light dots are REAL data (baseline.<category>.traffic_light), not renderer-invented taxonomy, and are never suppressed -- unlike WPM, where a RAG dot would be forbidden as invented severity.

Family/accent taxonomy is renderer-level presentation config, not a JID field; it decorates the RAG dot, it does not replace it. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-04. A year-precision row is never promoted into a tighter band.

Envelope: baseline resolved at jurisdiction_json.baseline; 10 categories, 57 sub-module(s), 87 claim(s) (87 category placement(s)), 46 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 24 Oct 2026: not upheld (5 confirmed against the cited source; 2 contradicted by the cited source; 5 could not be checked). An automated, adversarial test run by a second model; no person has assessed the result.

Think something on this page is wrong? Report an error.

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (14 mapped).

Show article map
GDPR article to category mapping
ArticleCategorySub-module
Art. 5Controller/Processor Dutiesaccountability and dpia
Art. 6Lawful Processing & Special Datalawful bases
Art. 7Lawful Processing & Special Dataconsent thresholds
Art. 9Lawful Processing & Special Dataspecial categories
Art. 22Algorithmic, Biometric & Surveillance Governanceautomated decision making transparency
Art. 25Controller/Processor Dutiesaccountability and dpia
Art. 28Controller/Processor Dutiesjoint controller arrangements
Art. 30Controller/Processor Dutiesropa requirements
Art. 35Controller/Processor Dutiesaccountability and dpia
Art. 13-22Data Subject Rightsaccess right
Art. 32-34Controller/Processor Dutiessecurity measures
Art. 37-39Controller/Processor Dutiesdpo requirements
Art. 44-49Cross-Border & Adequacytransfer mechanisms
Art. 77-84Enforcement & Redressregulator powers and penalties