Data Protection Monitor
Global Privacy & Data Protection Intelligence

Romania Data Protection & Privacy Regulation

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

Last updated · 10 categories · 44 claims · 37 sources in the cumulative register

Continental Automotive Products SRL was fined RON 76,336, approximately EUR 15,000, by ANSPDCP for violations of GDPR Articles 32(1)(b) and 32(2), following a data breach involving employees' medical data.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Regulator & Framework, Enforcement & Redress (2 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 authorityAutoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal (ANSPrimary 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 Romania is covered once, on the European Economic Area (Bloc) page. This page covers Romania’s own layer: implementation, national authorities, national options and local enforcement.

Jurisdiction brief

Latest update · 25 October 2026

Lead Signal

Romania's data protection enforcement posture continued to intensify across this reporting window, with the Autoritatea Nationala de Supraveghere a Prelucrarii Datelor cu Caracter Personal issuing a sustained sequence of sanctions concentrated on security-of-processing failures under Article 32 of the GDPR. A fine announced on 25 September 2026 referenced the sensitivity of biometric data, though the fined entity and exact amount were not established within the retrieved material; this was followed by a EUR 5,000 fine on 2 October 2026 against an operator following a self-notified cyber-attack, for breaches of Article 32(1)(b), 32(1)(d) and 32(2), and a further fine of approximately EUR 1,000 on 7 October 2026 against a veterinary-hospital operator for failing to properly resolve a data subject access request. The largest sanction within the broader 2026 pattern, EUR 125,000 against Renault Commercial Roumanie S.R.L. in March 2026, also centred on Article 32 security failures compounded by an Article 28(1) processor-oversight breach after a cyberattack on a processor-administered application led to unauthorised publication of personal data.

Key regulatory facts for Romania
Regulatory DimensionRomania Standing Position
JurisdictionRomania (RO)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 44 sourced findings)
Regulator & FrameworkFully operational GDPR-aligned regime with an active, resourced DPA and a national implementing statute in force since 2018.
Lawful Processing & Special DataDirect GDPR application with CJEU-clarified consent standard originating from a Romanian reference.
Data Subject RightsRights framework mirrors GDPR baseline; enforcement record shows the regulator actively polices non-compliance with erasure and access obligations.
Controller/Processor DutiesFramework is GDPR-aligned (green in principle) but repeated enforcement findings of Article 32/33 non-compliance among controllers warrant an amber operational rating.
Primary Instruments CitedDataGuidance, DataGuidance, EUR-Lex, DataGuidance, ANSPDCP
Last Confirmed / Updated2026-11-04 (37 sources in cumulative register)

#

Fully operational GDPR-aligned regime with an active, resourced DPA and a national implementing statute in force since 2018.

Primary frameworkRegulation (EU) 2016/679 (GDPR) as implemented by Law No. 190/2018
Traffic-light rationale — GreenFully operational GDPR-aligned regime with an active, resourced DPA and a national implementing statute in force since 2018.

Sub-modules (5)

Regulator And AuthorityGreen

ANSPDCP is the single national competent authority for GDPR matters in Romania, operating under Law No. 102/2005 (organisational statute) and Law No. 190/2018 (GDPR implementation).

Claims (2):

  • The National Supervisory Authority for Personal Data Processing (ANSPDCP) is the competent supervisory authority for data protection matters in Romania under Law No. 190/2018.
  • ANSPDCP published an update on 19 October 2026 reporting on the EDPB's 13-14 October 2026 plenary session, within this recency window.

Act And InstrumentsGreen

The operative instruments are the GDPR itself and the national implementing Law No. 190/2018.

Claims (1):

  • Romania implemented the GDPR through Law No. 190/2018 Implementing the General Data Protection Regulation (Regulation (EU) 2016/679).

Material ScopeGreen

Material scope follows GDPR Art 2/4 directly; Law 190/2018 adds detailed rules for journalistic, academic, artistic and literary expression processing.

Claims (1):

  • Law No. 190/2018 is relatively comprehensive and includes detailed provisions on the processing of data for journalistic purposes or academic or artistic expression, on certification bodies, and on corrective measures and sanctions for both private and public bodies.

Territorial ScopeGreen

Territorial scope follows GDPR Art 3 directly (establishment + targeting tests); no Romania-specific narrowing or broadening identified.

Claims (1):

  • Territorial scope of the Romanian regime tracks GDPR Article 3 directly, applying to controllers/processors established in Romania and, via the targeting test, to non-established controllers processing data of subjects in Romania.

Registration And FilingGreen

Romania abolished the pre-GDPR general notification/registration obligation; ANSPDCP issued a public statement confirming elimination of the notification duty, consistent with GDPR's accountability-based model (Recital 89).

Claims (1):

  • ANSPDCP issued a statement on the elimination of the obligation to notify data processing operations, consistent with the GDPR's shift away from ex-ante registration toward accountability-based compliance (Recital 89, Articles 36-37 GDPR).
Category narrative 60 words

Romania implements the GDPR through Law No. 190/2018 Implementing the General Data Protection Regulation, with the National Supervisory Authority for Personal Data Processing (ANSPDCP) as the competent supervisory authority. The regime is a fully-operational EU Member State omnibus regime; Romania did not enact a broad derogation architecture beyond the sector-specific carve-outs (journalism/academic/artistic expression, certification bodies) permitted by GDPR opening clauses.

No periodic updates recorded in this cycle

Sources and claims (6)
  1. Confirmed DataGuidance — The National Supervisory Authority for Personal Data Processing (ANSPDCP) is the competent supervisory authority for data protection matters in Romania under Law No. 190/2018. observed
  2. Confirmed DataGuidance — Romania implemented the GDPR through Law No. 190/2018 Implementing the General Data Protection Regulation (Regulation (EU) 2016/679). observed
  3. Confirmed DataGuidance — Law No. 190/2018 is relatively comprehensive and includes detailed provisions on the processing of data for journalistic purposes or academic or artistic expression, on certification bodies, and on corrective measures and sanctions for both private and public bodies. observed
  4. Probable EUR-Lex — Territorial scope of the Romanian regime tracks GDPR Article 3 directly, applying to controllers/processors established in Romania and, via the targeting test, to non-established controllers processing data of subjects in Romania. observed
  5. Confirmed DataGuidance — ANSPDCP issued a statement on the elimination of the obligation to notify data processing operations, consistent with the GDPR's shift away from ex-ante registration toward accountability-based compliance (Recital 89, Articles 36-37 GDPR). observed
  6. Uncertain ANSPDCP — ANSPDCP published an update on 19 October 2026 reporting on the EDPB's 13-14 October 2026 plenary session, within this recency window. observed

#

Direct GDPR application with CJEU-clarified consent standard originating from a Romanian reference.

Primary frameworkGDPR Articles 6, 7, 9; Law No. 190/2018
Supervisory authorityANSPDCP
Traffic-light rationale — GreenDirect GDPR application with CJEU-clarified consent standard originating from a Romanian reference.
D2 · Lawful Processing — Full Module Record4 sub-modules · 51 words · 4 traced claims · Re-verified 2026-11-04

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

#

Rights framework mirrors GDPR baseline; enforcement record shows the regulator actively polices non-compliance with erasure and access obligations.

Primary frameworkGDPR Articles 12-22; Law No. 190/2018
Supervisory authorityANSPDCP
Traffic-light rationale — GreenRights framework mirrors GDPR baseline; enforcement record shows the regulator actively polices non-compliance with erasure and access obligations.

Sub-modules (5)

Access RightGreen

Access right follows GDPR Article 15 directly; no national supplementary access regime identified.

Claims (1):

  • Spitalul Veterinar Tineretului SRL — ANSPDCP fined the operator 5,242 RON (approx. EUR 1,000) on 7 October 2026 for failing to properly resolve a data subject's access request for call-recording and CCTV data.

Rectification And ErasureAmber

ANSPDCP sanctioned an individual for, among other violations, failing to respond to a data-subject erasure request under GDPR Article 17(1) after identity cards were published online.

Claims (1):

  • ANSPDCP fined an individual RON 50,890 for, inter alia, violating GDPR Article 17(1) by failing to respond to a request to delete personal data, in addition to publishing identity cards online without a legal basis.

Restriction And ObjectionAmber

Restriction/objection rights follow GDPR Articles 18/21 directly; no Romania-specific case identified in this research pass.

Data PortabilityAmber

Portability follows GDPR Article 20 directly; no Romania-specific derogation or guidance identified in this research pass.

Deadlines And Response WindowsGreen

Response deadlines follow the GDPR Article 12(3) one-month default (extendable by two further months for complex requests); no Romania-specific shortening/lengthening identified.

Claims (1):

  • The individual sanctioned by ANSPDCP was found to have breached GDPR Article 12(3)-12(4) transparency and response-timeliness obligations toward data subjects.
Category narrative 47 words

Data subject rights (access, rectification, erasure, restriction, objection, portability) apply per GDPR Articles 15-22 with no Romania-specific derogations identified in Law 190/2018 beyond the general journalistic/academic/artistic exemptions. ANSPDCP enforcement actions confirm active supervision of erasure-request compliance (e.g., the evita-teparii.ro case for failure to honour a deletion request).

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

Sources and claims (3)
  1. Confirmed DataGuidance — ANSPDCP fined an individual RON 50,890 for, inter alia, violating GDPR Article 17(1) by failing to respond to a request to delete personal data, in addition to publishing identity cards online without a legal basis. observed
  2. Confirmed DataGuidance — The individual sanctioned by ANSPDCP was found to have breached GDPR Article 12(3)-12(4) transparency and response-timeliness obligations toward data subjects. observed
  3. Probable LegalUp — Spitalul Veterinar Tineretului SRL — ANSPDCP fined the operator 5,242 RON (approx. EUR 1,000) on 7 October 2026 for failing to properly resolve a data subject's access request for call-recording and CCTV data. observed

#

Framework is GDPR-aligned (green in principle) but repeated enforcement findings of Article 32/33 non-compliance among controllers warrant an amber operational rating.

Primary frameworkGDPR Articles 5, 24-25, 28, 30, 32-35, 37-39; Law No. 190/2018
Supervisory authorityANSPDCP
Traffic-light rationale — AmberFramework is GDPR-aligned (green in principle) but repeated enforcement findings of Article 32/33 non-compliance among controllers warrant an amber operational rating.
Periodic update · new data 2026-10-18

Controller/Processor Duties

Article 32 security-of-processing obligations dominate ANSPDCP's controller and processor enforcement activity within this recency window. On 2 October 2026, the authority fined GLOBAL CUSTOMER CARE SERVICES S.R.L. EUR 5,000 for breaches of Article 32(1)(b) and 32(1)(d), together with Article 32(2), following a self-notified cyber-attack. The self-notification detail is significant: the operator appears to have reported the incident to ANSPDCP rather than the breach surfacing through complaint or external discovery, yet the authority nonetheless proceeded to sanction, indicating that voluntary notification does not by itself forestall enforcement where the underlying technical and organisational measures are found deficient.

This fine sits within a broader pattern anchored by ANSPDCP's largest sanction of 2026, a EUR 125,000 fine against Renault Commercial Roumanie S.R.L., decided in March 2026. That decision similarly rested on breaches of Article 32(1)(b), 32(1)(d) and 32(2), but combined these security findings with an Article 28(1) processor-oversight breach, after a cyberattack on an application administered by a processor on the controller's behalf led to unauthorised publication of personal data. The Renault decision is directly sourced from ANSPDCP's own press release, giving it a higher evidentiary standing than the press-reported October decisions, and its combination of a security failure with a processor-supervision failure under Article 28 illustrates how ANSPDCP treats inadequate oversight of a processor as compounding, rather than separate from, the underlying security deficiency.

The consistency of the legal bases cited across these two decisions, Article 32(1)(b), 32(1)(d) and 32(2) in both cases, suggests ANSPDCP has settled on a recurring analytical framework for assessing security-of-processing failures following a cyberattack: inadequate measures to ensure ongoing confidentiality and resilience of processing systems, and inadequate processes for regularly testing and evaluating the effectiveness of technical and organisational measures. Controllers and processors operating in Romania should note that the amounts involved vary substantially, from EUR 5,000 to EUR 125,000, suggesting that the scale of the breach, the sensitivity of the data involved, and the presence or absence of compounding factors such as inadequate processor oversight materially affect the sanction ultimately imposed, even where the underlying legal bases cited are similar.

Outlook

Given the cadence of Article 32-based enforcement observed across this window, including the 2 October 2026 decision and the earlier Renault decision, continued ANSPDCP attention to security-of-processing compliance, particularly following cyberattacks and data breaches, should be expected to persist. Controllers relying on processors for application administration or data handling should take note of the Renault precedent's combination of Article 32 and Article 28(1) findings, which indicates that inadequate processor oversight is being treated as an aggravating rather than separate factor in ANSPDCP's assessment of such incidents.

D4 · Controller & Processor — Full Module Record7 sub-modules · 56 words · 7 traced claims · Re-verified 2026-11-04

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

#

Transfer mechanisms are the harmonised EU-wide GDPR Chapter V toolkit; no Romania-specific localisation mandate identified.

Primary frameworkGDPR Articles 44-50 (Chapter V); EU adequacy decisions
Supervisory authorityANSPDCP
Traffic-light rationale — GreenTransfer mechanisms are the harmonised EU-wide GDPR Chapter V toolkit; no Romania-specific localisation mandate identified.
D5 · Cross-Border & Adequacy — Full Module Record6 sub-modules · 72 words · 2 traced claims · Re-verified 2026-11-04

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

#

Financial and employment overlays are evidenced by case law/enforcement; health, education, telecoms-specific and insurance overlays were not separately confirmed in this pass and are marked absent.

Primary frameworkGDPR (general); ECHR Article 8 (employment monitoring, via Bărbulescu); Law No. 190/2018
Supervisory authorityANSPDCP
Traffic-light rationale — AmberFinancial and employment overlays are evidenced by case law/enforcement; health, education, telecoms-specific and insurance overlays were not separately confirmed in this pass and are marked absent.
Periodic update · new data 2026-10-25

Sectoral Watch

Romania's domestic implementation framework for the EU Data Act, Regulation (EU) 2023/2854, progressed through a public consultation stage without reaching adoption. The Autoritatea Nationala pentru Administrare si Reglementare in Comunicatii launched the consultation on 2 July 2026, and it closed on 3 August 2026. The draft law under consultation addresses the designation of competent national authorities for Data Act purposes and establishes an enforcement and sanctions framework for the directly-applicable EU regulation. As a directly applicable EU Regulation, the Data Act's substantive provisions already bind relevant parties in Romania regardless of domestic implementing legislation; what the draft law under consultation would add is the domestic institutional machinery, designated authorities, enforcement powers and sanctions, needed to operationalise compliance and enforcement at the national level.

This consultation-stage development should be read alongside Romania's broader pattern, visible elsewhere in the coverage, of EU-level direct obligations outpacing the domestic institutional infrastructure needed to give them full practical effect. The Data Act consultation closing without adoption as of the material reaching leaves open the question of which specific body or bodies will ultimately hold enforcement authority, and what sanctions regime will apply to Data Act breaches in Romania, pending finalisation of the implementing law.

Outlook

The regulatory horizon identifies the fourth quarter of 2026 as a tentative estimate for adoption of ANCOM's Data Act implementing law, carrying a half-year uncertainty band that should be read as scheduled rather than assured given the consultation closed in early August 2026 without a stated adoption date. Whether the draft law has advanced toward adoption since the 3 August 2026 consultation close was not established within the sourcing and remains an open item. Once adopted, the law would designate the competent authorities responsible for Data Act enforcement in Romania and establish the sanctions regime applicable to breaches of the directly-applicable EU Regulation.

Periodic update · new data 2026-10-18

Sectoral Watch

Romania's domestic implementation framework for the EU Data Act, Regulation (EU) 2023/2854, progressed through a public consultation stage this cycle without reaching adoption. The Autoritatea Nationala pentru Administrare si Reglementare in Comunicatii launched the consultation on 2 July 2026, and it closed on 3 August 2026. The draft law under consultation addresses the designation of competent national authorities for Data Act purposes and establishes an enforcement and sanctions framework for the directly-applicable EU regulation. As a directly applicable EU Regulation, the Data Act's substantive provisions already bind relevant parties in Romania regardless of domestic implementing legislation; what the draft law under consultation would add is the domestic institutional machinery, designated authorities, enforcement powers and sanctions, needed to operationalise compliance and enforcement at the national level.

This consultation-stage development should be read alongside Romania's broader pattern, visible elsewhere in this cycle's coverage, of EU-level direct obligations outpacing the domestic institutional infrastructure needed to give them full practical effect. The Data Act consultation closing without adoption as of the material reaching this cycle leaves open the question of which specific body or bodies will ultimately hold enforcement authority, and what sanctions regime will apply to Data Act breaches in Romania, pending finalisation of the implementing law.

Outlook

The regulatory horizon identifies the fourth quarter of 2026 as a tentative estimate for adoption of ANCOM's Data Act implementing law, carrying a half-year uncertainty band that should be read as scheduled rather than assured given the consultation closed in early August 2026 without a stated adoption date. Whether the draft law has advanced toward adoption since the 3 August 2026 consultation close was not established within this cycle's sourcing and remains an open item. Once adopted, the law would designate the competent authorities responsible for Data Act enforcement in Romania and establish the sanctions regime applicable to breaches of the directly-applicable EU Regulation.

D6 · Sectoral Watch — Full Module Record7 sub-modules · 63 words · 4 traced claims · Re-verified 2026-11-04

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

#

Cookie-consent enforcement is confirmed and active; dark patterns, opt-out signal recognition, clean-room rules and cross-context advertising lack confirmed Romania-specific findings in this pass.

Primary frameworkDirective 2002/58/EC as transposed by Law No. 506/2004; GDPR
Supervisory authorityANSPDCP
Traffic-light rationale — AmberCookie-consent enforcement is confirmed and active; dark patterns, opt-out signal recognition, clean-room rules and cross-context advertising lack confirmed Romania-specific findings in this pass.
D7 · AdTech & Marketing — Full Module Record6 sub-modules · 51 words · 1 traced claims · Re-verified 2026-11-04

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

#

Governed by directly-applicable EU-level AI Act/GDPR; amber reflects genuine EU-wide uncertainty over high-risk AI Act timelines and guidance that also affects Romanian deployers/providers.

Primary frameworkGDPR Article 22; Regulation (EU) 2024/1689 (EU AI Act)
Supervisory authorityANSPDCP
Traffic-light rationale — AmberGoverned by directly-applicable EU-level AI Act/GDPR; amber reflects genuine EU-wide uncertainty over high-risk AI Act timelines and guidance that also affects Romanian deployers/providers.
Periodic update · new data 2026-10-25

Algorithmic, Biometric & Surveillance Governance

Romania's institutional architecture for AI Act oversight advanced through a Government Memorandum adopted on 12 March 2026, which designated the Autoritatea Nationala pentru Administrare si Reglementare in Comunicatii as the national market-surveillance authority for the AI Act and as Romania's single national contact point for AI Act purposes. This designation arrived roughly seven months after the EU-wide deadline of 2 August 2025 for Member States to designate their national competent authorities, placing Romania among the Member States whose institutional build-out for AI Act implementation lagged the formal deadline.

Separately from ANCOM's market-surveillance role, the Autoritatea Nationala de Supraveghere a Prelucrarii Datelor cu Caracter Personal has been notified to the European Commission as one of nine Romanian public authorities responsible for protecting fundamental rights in the context of high-risk AI systems. This gives ANSPDCP a formal statutory role within Romania's AI Act institutional architecture that is distinct from, and complementary to, ANCOM's market-surveillance function: where ANCOM is positioned to oversee market compliance of AI systems placed on the Romanian market, ANSPDCP's role centres on the fundamental-rights dimension of high-risk AI system deployment, a role that naturally intersects with its existing GDPR mandate given the overlap between fundamental-rights protection and personal-data processing concerns inherent in many high-risk AI use cases.

The seven-month gap between the EU's August 2025 deadline and Romania's March 2026 designation is itself a data point on the pace of Romania's regulatory institution-building relative to EU timelines, a pattern that recurs elsewhere in Romania's regulatory landscape in the form of the Data Act implementing law's unresolved consultation-to-adoption timeline.

Outlook

Whether Romania has adopted secondary legislation detailing ANCOM's inspection powers and operational procedures under the AI Act, beyond the foundational 12 March 2026 Memorandum, was not established within the sourcing and remains an open question for subsequent monitoring. As the dual-authority structure, ANCOM for market surveillance and ANSPDCP for fundamental-rights protection, becomes operational, the practical division of labour and referral mechanisms between the two bodies for cases touching both market-compliance and fundamental-rights concerns will be a relevant area to watch.

Periodic update · new data 2026-10-18

Algorithmic, Biometric & Surveillance Governance

Romania's institutional architecture for AI Act oversight advanced through a Government Memorandum adopted on 12 March 2026, which designated the Autoritatea Nationala pentru Administrare si Reglementare in Comunicatii as the national market-surveillance authority for the AI Act and as Romania's single national contact point for AI Act purposes. This designation arrived roughly seven months after the EU-wide deadline of 2 August 2025 for Member States to designate their national competent authorities, placing Romania among the Member States whose institutional build-out for AI Act implementation lagged the formal deadline.

Separately from ANCOM's market-surveillance role, the Autoritatea Nationala de Supraveghere a Prelucrarii Datelor cu Caracter Personal has been notified to the European Commission as one of nine Romanian public authorities responsible for protecting fundamental rights in the context of high-risk AI systems. This gives ANSPDCP a formal statutory role within Romania's AI Act institutional architecture that is distinct from, and complementary to, ANCOM's market-surveillance function: where ANCOM is positioned to oversee market compliance of AI systems placed on the Romanian market, ANSPDCP's role centres on the fundamental-rights dimension of high-risk AI system deployment, a role that naturally intersects with its existing GDPR mandate given the overlap between fundamental-rights protection and personal-data processing concerns inherent in many high-risk AI use cases.

The seven-month gap between the EU's August 2025 deadline and Romania's March 2026 designation is itself a data point on the pace of Romania's regulatory institution-building relative to EU timelines, a pattern that recurs elsewhere in Romania's regulatory landscape this cycle in the form of the Data Act implementing law's unresolved consultation-to-adoption timeline.

Outlook

Whether Romania has adopted secondary legislation detailing ANCOM's inspection powers and operational procedures under the AI Act, beyond the foundational 12 March 2026 Memorandum, was not established within this cycle's sourcing and remains an open question for subsequent monitoring. As the dual-authority structure, ANCOM for market surveillance and ANSPDCP for fundamental-rights protection, becomes operational, the practical division of labour and referral mechanisms between the two bodies for cases touching both market-compliance and fundamental-rights concerns will be a relevant area to watch.

D8 · AI, Biometrics & Automated — Full Module Record6 sub-modules · 88 words · 3 traced claims · Re-verified 2026-11-04

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

#

Age-of-consent position for Romania could not be confirmed against primary text in this pass; treated as open/Probable rather than silently assumed.

Primary frameworkGDPR Article 8
Supervisory authorityANSPDCP
Traffic-light rationale — AmberAge-of-consent position for Romania could not be confirmed against primary text in this pass; treated as open/Probable rather than silently assumed.
D9 · Children's Privacy — Full Module Record5 sub-modules · 102 words · 2 traced claims · Re-verified 2026-11-04

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

#

Enforcement is active and evidenced by multiple 2026 decisions, but the regulator's absolute funding/headcount and any Romania-specific collective-redress mechanism could not be confirmed in this pass.

Primary frameworkGDPR Articles 58, 77-84; Law No. 190/2018 Article 12-16; Law No. 102/2005
Supervisory authorityANSPDCP
Traffic-light rationale — AmberEnforcement is active and evidenced by multiple 2026 decisions, but the regulator's absolute funding/headcount and any Romania-specific collective-redress mechanism could not be confirmed in this pass.
Periodic update · new data 2026-11-04

Enforcement & Redress

Romania's National Supervisory Authority for Personal Data Processing, ANSPDCP, is understood to have fined Auchan România S.A. EUR 8,000 (41,908 lei), announced 30 October 2026, following an administrator-account compromise that allowed unauthorised access to and disclosure of internal-user personal data. The finding is reported to rest on inadequate technical and organisational measures to secure access to administrator-level accounts, engaging the security obligations in Article 5(1)(f) and Article 32 of the GDPR. The decision text itself has not been independently obtained; the figure and the underlying narrative come from secondary press reporting rather than the regulator's own published decision.

In a separate matter concluded around October 2026, ANSPDCP is understood to have fined SC Hayat Medical & Dental SRL on two counts: processing patient personal data without an identifiable lawful basis under Article 5(1), and failing to provide the authority with information it had requested in the course of an investigation, engaging the non-cooperation ground at Article 83(5)(e). Reported penalty figures sit at the EUR 5,000 and EUR 2,000 level across the two counts. As with the Auchan matter, this account is drawn from secondary reporting rather than the primary decision, and the combined penalty structure should be read with that caveat attached.

Outlook

Taken together, these two decisions are consistent with ANSPDCP's standing enforcement cadence rather than a departure from it: the authority has maintained a broadly monthly rhythm of published fines, placing it among the more active data-protection authorities within the EU by count of decisions, and nothing in these two matters points to a change in that posture. The Auchan matter illustrates the authority's continued attention to administrator-account security as a distinct failure mode under the security-of-processing obligation; the Hayat Medical & Dental matter illustrates its willingness to penalise non-cooperation with its own investigations as a distinct ground alongside the underlying lawful-basis finding. Confirmation of either decision's full text would sharpen the picture of how each ground was applied, but is not yet available.

Periodic update · new data 2026-10-25

Enforcement & Redress

ANSPDCP maintained a sustained enforcement cadence within and immediately adjacent to this recency window, issuing at least three identified sanctions across a roughly two-week span in late September and early October 2026, alongside the already-documented March 2026 Renault decision that remains the largest sanction of the year. On 25 September 2026, the authority announced a fine in a decision referencing the sensitivity of biometric data; the fined entity's identity and the exact fine amount were not established from the material retrieved, representing a gap in the available enforcement record for that specific decision. On 2 October 2026, ANSPDCP fined GLOBAL CUSTOMER CARE SERVICES S.R.L. EUR 5,000 following a self-notified cyber-attack, citing breaches of Article 32(1)(b), 32(1)(d) and 32(2). On 7 October 2026, the authority fined a veterinary-hospital operator approximately EUR 1,000 for failing to properly resolve a data subject's access request covering call-recording and CCTV data.

The range of fine amounts across this short window, from roughly EUR 1,000 to EUR 5,000 for the two fully identified October decisions, with the March 2026 Renault decision at EUR 125,000 standing well above both, illustrates that ANSPDCP's enforcement activity spans both high-volume lower-value sanctions against smaller operators and occasional high-value sanctions tied to more significant security failures. The 25 September 2026 biometric-data-referencing decision is notable for the sensitivity of the data category involved but cannot yet be assessed for materiality given the absence of confirmed fine amount or sanctioned entity in the retrieved record.

Viewed together, these decisions confirm a pattern noted elsewhere in the coverage: Article 32 security-of-processing failures, whether arising from cyberattack or inadequate operational controls, are the dominant basis for ANSPDCP sanctions, while data-subject-rights failures such as the veterinary-hospital access-request case represent a secondary but still active enforcement category.

Outlook

The identity of the entity sanctioned on 25 September 2026 and the exact fine amount in that biometric-data-referencing decision remain open items, and confirming them would materially sharpen the enforcement picture for that specific case given the heightened sensitivity typically attached to biometric data processing under Article 9 of the GDPR. Based on the cadence observed across this window, three sanctions within roughly two weeks, continued active enforcement by ANSPDCP in the near term should be anticipated, consistent with the authority's demonstrated pattern of frequent, security-focused sanctioning activity through 2026.

Periodic update · new data 2026-10-18

Enforcement & Redress

ANSPDCP maintained a sustained enforcement cadence within and immediately adjacent to this recency window, issuing at least three identified sanctions across a roughly two-week span in late September and early October 2026, alongside the already-documented March 2026 Renault decision that remains the largest sanction of the year. On 25 September 2026, the authority announced a fine in a decision referencing the sensitivity of biometric data; the fined entity's identity and the exact fine amount were not established from the material retrieved this cycle, representing a gap in the available enforcement record for that specific decision. On 2 October 2026, ANSPDCP fined GLOBAL CUSTOMER CARE SERVICES S.R.L. EUR 5,000 following a self-notified cyber-attack, citing breaches of Article 32(1)(b), 32(1)(d) and 32(2). On 7 October 2026, the authority fined a veterinary-hospital operator approximately EUR 1,000 for failing to properly resolve a data subject's access request covering call-recording and CCTV data.

The range of fine amounts across this short window, from roughly EUR 1,000 to EUR 5,000 for the two fully identified October decisions, with the March 2026 Renault decision at EUR 125,000 standing well above both, illustrates that ANSPDCP's enforcement activity spans both high-volume lower-value sanctions against smaller operators and occasional high-value sanctions tied to more significant security failures. The 25 September 2026 biometric-data-referencing decision is notable for the sensitivity of the data category involved but cannot yet be assessed for materiality given the absence of confirmed fine amount or sanctioned entity in the retrieved record.

Viewed together, these decisions confirm a pattern noted elsewhere in this cycle's coverage: Article 32 security-of-processing failures, whether arising from cyberattack or inadequate operational controls, are the dominant basis for ANSPDCP sanctions, while data-subject-rights failures such as the veterinary-hospital access-request case represent a secondary but still active enforcement category.

Outlook

The identity of the entity sanctioned on 25 September 2026 and the exact fine amount in that biometric-data-referencing decision remain open items, and confirming them would materially sharpen the enforcement picture for that specific case given the heightened sensitivity typically attached to biometric data processing under Article 9 of the GDPR. Based on the cadence observed across this window, three sanctions within roughly two weeks, continued active enforcement by ANSPDCP in the near term should be anticipated, consistent with the authority's demonstrated pattern of frequent, security-focused sanctioning activity through 2026.

D10 · Enforcement & Redress — Full Module Record6 sub-modules · 113 words · 12 traced claims · Re-verified 2026-11-04

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), 44 claim(s) (44 category placement(s)), 37 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 24 Oct 2026: upheld (2 confirmed against the cited source; 7 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 (38 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. 13Data Subject Rightsdeadlines and response windows
Art. 14Data Subject Rightsdeadlines and response windows
Art. 15Data Subject Rightsaccess right
Art. 16Data Subject Rightsrectification and erasure
Art. 17Data Subject Rightsrectification and erasure
Art. 18Data Subject Rightsrestriction and objection
Art. 19Data Subject Rightsrestriction and objection
Art. 20Data Subject Rightsdata portability
Art. 21Data Subject Rightsrestriction and objection
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. 32Controller/Processor Dutiessecurity measures
Art. 33Controller/Processor Dutiesbreach notification
Art. 34Controller/Processor Dutiesbreach notification
Art. 35Controller/Processor Dutiesaccountability and dpia
Art. 37Controller/Processor Dutiesdpo requirements
Art. 38Controller/Processor Dutiesdpo requirements
Art. 39Controller/Processor Dutiesdpo requirements
Art. 44Cross-Border & Adequacytransfer mechanisms
Art. 45Cross-Border & Adequacyadequacy received
Art. 46Cross-Border & Adequacysccs and bcrs
Art. 47Cross-Border & Adequacysccs and bcrs
Art. 48Cross-Border & Adequacydata localisation
Art. 49Cross-Border & Adequacytransfer mechanisms
Art. 77Enforcement & Redressprivate right of action
Art. 78Enforcement & Redressprivate right of action
Art. 79Enforcement & Redressprivate right of action
Art. 80Enforcement & Redresscollective redress and class actions
Art. 81Enforcement & Redressregulator powers and penalties
Art. 82Enforcement & Redressprivate right of action
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties