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 · 51 claims · 43 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, Algorithmic, Biometric & Surveillance Governance (2 open gaps).

Framework & posture10 of 10 modules active
10 active · 11 binding instruments
Next milestoneNo upcoming dated milestone on record
Record & confidence mix56 claims · 31 sources · machine-compiled
12 Confirmed27 Probable10 Contested / unverified
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-11-17

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 · 8 November 2026

Lead Signal

Romania's data protection authority, ANSPDCP, has fined ING Bank N.V. Amsterdam - Sucursala Bucuresti EUR 5,000 for breaches of Article 32(1)(b), 32(1)(d), 32(2) and 32(4) of the GDPR, following unauthorised employee access to clients' banking data. The sanction, dated 5 November 2026, is understood to have been reported through Romanian legal press rather than confirmed yet through an individually retrieved ANSPDCP press release, so the finding is framed with appropriate caution pending a primary-source statement from the regulator itself. The breach centres on inadequate technical and organisational measures around internal access controls: the provisions cited concern the security of processing, the ability to restore availability and access to data, and the regular testing and evaluation of the effectiveness of security measures, pointing to a case about who inside the bank could see client data and how that access was controlled rather than about an external intrusion.

Key regulatory facts for Romania
Key regulatory facts for Romania
Regulatory DimensionRomania Standing Position
JurisdictionRomania (RO)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 51 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, EUR-Lex, EUR-Lex, Wolf Theiss, ANCOM (Autoritatea Națională pentru Administrare și Reglementare în Comunicații)
Last Confirmed / Updated (43 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.

Sub-modules (4)

Lawful basesGreen

The six GDPR Article 6 lawful bases apply directly in Romania without a national supplementary list.

Claims (1):

  • Data controllers in Romania must rely on lawfulness under GDPR Article 6(1)(a)-(f) as the exhaustive set of lawful bases for processing personal data.

Special categoriesGreen

Special categories follow GDPR Article 9 directly; ANSPDCP enforcement practice (e.g., health-data breach fines) confirms active application of the Art 9 regime to employee medical data.

Claims (2):

  • ANSPDCP fined Continental Automotive Products SRL after an Excel file containing employees' medical data (special-category data under GDPR Article 9) was repeatedly distributed internally without adequate technical and organisational measures.
  • Romania (ANSPDCP) — Not found for Romania this cycle: the specific national condition under GDPR Art 9(2) relied on for biometric-data processing was not located, though a 25 Sept 2026 fine announcement references biometric-data risk.

Pseudonymisation and anonymisationAmber

No Romania-specific statutory safe harbour beyond GDPR Articles 4(5) and 25/32 was identified; EDPB-level guidance on pseudonymisation (under public consultation in 2025) is the applicable reference framework absent national supplementation.

Category narrative 51 words

Romania applies the GDPR's Article 6 lawful bases and Article 9 special-category regime directly, with Law 190/2018 not materially derogating from the EU baseline on consent standards. National case law referred to the CJEU (Orange România) clarified the standard for valid, freely-given, specific and informed consent in a Romanian telecoms context.

No periodic updates recorded in this cycle

Sources and claims (4)
  1. Confirmed EDPB — Data controllers in Romania must rely on lawfulness under GDPR Article 6(1)(a)-(f) as the exhaustive set of lawful bases for processing personal data. observed
  2. Confirmed EUR-Lex — In a reference from the Tribunalul București concerning collection and storage of identity-document copies by a mobile telecoms provider, the CJEU examined whether a tick-box declaration and contract signature satisfy the GDPR/Directive 95/46 consent standard, and addressed the burden of proof for valid consent. observed
  3. Confirmed DataGuidance — ANSPDCP fined Continental Automotive Products SRL after an Excel file containing employees' medical data (special-category data under GDPR Article 9) was repeatedly distributed internally without adequate technical and organisational measures. observed
  4. Uncertain The DPO — Romania (ANSPDCP) — Not found for Romania this cycle: the specific national condition under GDPR Art 9(2) relied on for biometric-data processing was not located, though a 25 Sept 2026 fine announcement references biometric-data risk. observed

#

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 JURIDICE.ro — 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.

Sub-modules (7)

Accountability & DPIAGreen

ANSPDCP recommends DPIAs and ROPA maintenance in sector guidance (e.g., 2024 election-processing recommendations invoking GDPR Articles 5, 6 and 9 plus a DPIA duty for political-entity controllers).

Claims (1):

  • ANSPDCP's October 2024 election-processing recommendations require political entities acting as controllers under GDPR Article 4(7) to conduct a Data Protection Impact Assessment and maintain records of processing activities.

DPO requirementsGreen

DPO appointment thresholds follow GDPR Articles 37-39 directly; Romania's election guidance explicitly reminds political-entity controllers to appoint a DPO where required.

Claims (1):

  • ANSPDCP guidance reminds political-entity controllers processing personal data during elections to appoint a Data Protection Officer where the GDPR Article 37 threshold is met.

Ropa requirementsGreen

ROPA duties follow GDPR Article 30 directly; ANSPDCP guidance for electoral-processing controllers explicitly requires maintenance of records of processing activities.

Claims (1):

  • ANSPDCP guidance requires organisations processing personal data during elections to maintain records of data processing activities consistent with GDPR Article 30.

Joint controller arrangementsAmber

Joint-controller allocation follows GDPR Article 26 directly; no Romania-specific supplementary rule identified in this research pass.

Security measuresAmber

ANSPDCP found Hora Credit IFN and Continental Automotive Products to have failed to implement appropriate technical and organisational security measures under GDPR Articles 25 and 32.

Claims (3):

  • ANSPDCP found that Hora Credit IFN S.A. did not take sufficient security measures for personal data, according to Articles 25 and 32 of the GDPR, so as to avoid unauthorised disclosure of personal data to third parties.
  • GLOBAL CUSTOMER CARE SERVICES S.R.L. — ANSPDCP fined the operator EUR 5,000 on 2 October 2026 for breaching Art 32(1)(b),(d) and Art 32(2) GDPR, following a self-notified cyber-attack.
  • Renault Commercial Roumanie S.R.L. — ANSPDCP's largest 2026 fine, EUR 125,000 (decision March 2026), for breaches of Art 32(1)(b),(d) and 32(2) combined with Art 28(1), after a cyberattack on a processor-administered application led to unauthorised publication of personal data.

Breach notificationAmber

Breach notification follows GDPR Article 33's 72-hour rule; ANSPDCP has separately fined a controller for failing to notify a security incident within 72 hours, and has opened investigations directly from breach notifications submitted by controllers (Continental, UiPath).

Claims (1):

  • ANSPDCP fined Hora Credit IFN S.A. for failing to notify the supervisory authority of a security incident within 72 hours from the date it became aware of it, per GDPR Article 33.

Retention and disposalAmber

Retention/disposal follows GDPR Article 5(1)(e) storage-limitation principle directly; no Romania-specific statutory retention schedule beyond sectoral rules was identified in this research pass.

Category narrative 56 words

Accountability, DPIA, security-of-processing, breach notification and retention duties in Romania follow GDPR Articles 5, 24-25, 30, 32-35 directly. ANSPDCP's enforcement docket (Hora Credit IFN, Continental Automotive, UiPath) repeatedly cites Articles 25, 32 and 33, confirming active supervision of security measures and the 72-hour breach-notification duty; failure to notify within 72 hours has itself been separately sanctioned.

Periodic update · new data 2026-10-18

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.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (7)
  1. Confirmed DataGuidance — ANSPDCP's October 2024 election-processing recommendations require political entities acting as controllers under GDPR Article 4(7) to conduct a Data Protection Impact Assessment and maintain records of processing activities. observed
  2. Probable DataGuidance — ANSPDCP guidance reminds political-entity controllers processing personal data during elections to appoint a Data Protection Officer where the GDPR Article 37 threshold is met. observed
  3. Probable DataGuidance — ANSPDCP guidance requires organisations processing personal data during elections to maintain records of data processing activities consistent with GDPR Article 30. observed
  4. Confirmed EDPB — ANSPDCP found that Hora Credit IFN S.A. did not take sufficient security measures for personal data, according to Articles 25 and 32 of the GDPR, so as to avoid unauthorised disclosure of personal data to third parties. observed
  5. Confirmed EDPB — ANSPDCP fined Hora Credit IFN S.A. for failing to notify the supervisory authority of a security incident within 72 hours from the date it became aware of it, per GDPR Article 33. observed
  6. Probable ANSPDCP (dataprotection.ro) — GLOBAL CUSTOMER CARE SERVICES S.R.L. — ANSPDCP fined the operator EUR 5,000 on 2 October 2026 for breaching Art 32(1)(b),(d) and Art 32(2) GDPR, following a self-notified cyber-attack. observed
  7. Confirmed ANSPDCP — Renault Commercial Roumanie S.R.L. — ANSPDCP's largest 2026 fine, EUR 125,000 (decision March 2026), for breaches of Art 32(1)(b),(d) and 32(2) combined with Art 28(1), after a cyberattack on a processor-administered application led to unauthorised publication of personal data. observed

#

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.

Sub-modules (6)

Transfer mechanismsGreen

Transfer mechanisms (adequacy, SCCs, BCRs, Article 49 derogations) are the standard EU-wide GDPR Chapter V toolkit; no Romania-specific instrument identified.

Claims (1):

  • ANSPDCP cooperated as lead supervisory authority under Article 60 GDPR one-stop-shop with the German Land of North Rhine-Westphalia's data protection authority (and consulted France, Denmark and Spain) in a cross-border case against Microstockr SRL, a Romania-based controller.

Adequacy receivedGreen

Adequacy decisions are adopted by the European Commission for the EU as a whole; Romania does not receive or grant adequacy independently as an EU Member State.

Claims (1):

  • As an EU Member State, Romania is bound by European Commission adequacy decisions adopted under GDPR Article 45 for the EU as a whole rather than adopting independent national adequacy findings.

Adequacy grantedGreen

Same as adequacy_received — adequacy is an EU-level competence, not exercised individually by Romania.

SCCs and BCRsGreen

ANSPDCP applies the EU Standard Contractual Clauses and BCR framework as adopted at EU level; no Romania-specific SCC variant identified.

Transfer impact assessmentAmber

TIA obligations follow the EDPB's EU-wide post-Schrems II guidance; no Romania-specific TIA supplementary requirement identified.

Data localisationGreen

No general data-localisation mandate identified for Romania beyond sector-specific retention/record-keeping rules under national law.

Category narrative 72 words

As an EU Member State, Romania does not operate an independent adequacy regime; cross-border transfer mechanisms (adequacy decisions, SCCs, BCRs, derogations) are governed exclusively at EU level under GDPR Chapter V and apply uniformly in Romania. ANSPDCP participates in EU one-stop-shop cross-border cooperation (Article 60 GDPR), as demonstrated in the UiPath and Microstockr cases where ANSPDCP acted as lead or cooperating authority with other EU DPAs (Germany's NRW authority, France, Denmark, Spain).

No periodic updates recorded in this cycle

Sources and claims (2)
  1. Confirmed EDPB — ANSPDCP cooperated as lead supervisory authority under Article 60 GDPR one-stop-shop with the German Land of North Rhine-Westphalia's data protection authority (and consulted France, Denmark and Spain) in a cross-border case against Microstockr SRL, a Romania-based controller. observed
  2. Confirmed EUR-Lex — As an EU Member State, Romania is bound by European Commission adequacy decisions adopted under GDPR Article 45 for the EU as a whole rather than adopting independent national adequacy findings. observed

#

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.

Sub-modules (7)

Financial sector overlayAmber

ANSPDCP sanctioned non-bank lender Hora Credit IFN S.A. for GDPR violations in loan-agreement data processing, including insufficient security measures and late breach notification.

Claims (1):

  • ANSPDCP sanctioned non-bank lender Hora Credit IFN S.A. for GDPR violations in the collection and processing of personal data for concluding and executing consumer loan agreements, including insufficient security measures and a 72-hour breach-notification failure.

Health sector overlayAmber

No dedicated Romanian health-sector DP statute was identified in this pass; health-data breaches (e.g., Continental Automotive medical-data case) are handled under general GDPR Article 9 rules rather than a distinct sectoral instrument.

Telecoms and eprivacyGreen

ePrivacy/cookie rules in Romania are implemented via Law No. 506/2004 (transposing Directive 2002/58/EC), enforced by ANSPDCP alongside GDPR consent standards, as seen in the Microstockr cookie-consent decision.

Claims (1):

  • Romania's ePrivacy cookie-consent obligation under Article 5(3) of Directive 2002/58/EC is transposed by Law No. 506/2004 and enforced by ANSPDCP with a consent standard aligned to GDPR Articles 4(11) and 6(1)(a).

Employment dataAmber

The ECHR Grand Chamber's Bărbulescu v. Romania judgment establishes that Romanian and EU law require employers to give employees prior notice of the nature and extent of monitoring before accessing their communications.

Claims (1):

  • The ECHR Grand Chamber, in Bărbulescu v. Romania, held that an employer's monitoring of an employee's electronic communications was unlawful because the employer did not give the employee prior notice of the nature and extent of the monitoring, aligning Romanian workplace-monitoring practice with Council of Europe, Romanian and EU law transparency requirements.

Credit and scoringAmber

No dedicated Romanian credit-scoring statute distinct from GDPR Article 22 was identified; the Hora Credit IFN case concerned general processing compliance rather than automated credit-scoring specifically.

educationAmber

No dedicated Romanian education-sector DP overlay was identified in this research pass.

insuranceAmber

No dedicated Romanian insurance-sector DP overlay was identified in this research pass.

Category narrative 63 words

Sectoral overlays identified in Romania include financial-sector consumer-credit processing (Hora Credit IFN, an IFN/non-bank lender, sanctioned under GDPR for loan-processing data handling) and employment/workplace-monitoring rules shaped by the Grand Chamber ECHR Bărbulescu v. Romania judgment, which imposes transparency conditions on employer monitoring of employee communications. No dedicated Romanian health-sector, education-sector, or insurance-sector DP statute distinct from GDPR was identified in this research pass.

Periodic update · new data 2026-10-25

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.

1 earlier distinct update
Periodic update · new data 2026-10-18

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.

Sources and claims (4)
  1. Confirmed EDPB — ANSPDCP sanctioned non-bank lender Hora Credit IFN S.A. for GDPR violations in the collection and processing of personal data for concluding and executing consumer loan agreements, including insufficient security measures and a 72-hour breach-notification failure. observed
  2. Confirmed EDPB — Romania's ePrivacy cookie-consent obligation under Article 5(3) of Directive 2002/58/EC is transposed by Law No. 506/2004 and enforced by ANSPDCP with a consent standard aligned to GDPR Articles 4(11) and 6(1)(a). observed
  3. Confirmed IAPP — The ECHR Grand Chamber, in Bărbulescu v. Romania, held that an employer's monitoring of an employee's electronic communications was unlawful because the employer did not give the employee prior notice of the nature and extent of the monitoring, aligning Romanian workplace-monitoring practice with Council of Europe, Romanian and EU law transparency requirements. observed
  4. Probable Wolf Theiss — On 2 July 2026, ANCOM launched a public consultation (closed 3 August 2026) on a draft law establishing measures for application of the EU Data Act, designating competent authorities and establishing an enforcement/sanctions framework; not yet adopted. observed

#

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.

Sub-modules (6)

Cookies and trackersAmber

ANSPDCP enforced the active-consent cookie standard against Microstockr SRL, finding that consent obtained via pre-existing account/contract mechanisms did not meet the 'free, specific, informed and unambiguous' standard required for storing/accessing information on user terminal equipment.

Claims (1):

  • ANSPDCP found that Microstockr SRL failed to obtain valid cookie consent under Article 5(3) of Directive 2002/58/EC (as transposed by Law No. 506/2004) because the consent mechanism did not constitute a free, specific, informed and unambiguous active indication of the user's wishes.

Dark patternsAmber

No dedicated Romanian dark-patterns prohibition distinct from GDPR/DSA fair-processing principles was identified in this research pass.

Opt out signalsAmber

No Romania-specific recognition mandate for Global Privacy Control or DAA-style opt-out signals was identified in this research pass.

Clean rooms and dcrAmber

No Romania-specific clean-room or data-collaboration-room regulatory framework was identified in this research pass.

Cross context advertisingAmber

Cross-context advertising in Romania is governed by the general GDPR consent/legitimate-interest framework; no Romania-specific 'sale'/'share' concept analogous to US state law was identified.

Direct marketingAmber

Direct marketing consent/suppression follows the ePrivacy opt-in standard under Law No. 506/2004 and GDPR Article 21(3) objection rights; no additional Romania-specific suppression registry was identified in this research pass.

Category narrative 51 words

Cookie/tracker consent in Romania follows the ePrivacy Directive as transposed by Law No. 506/2004, enforced by ANSPDCP with the same GDPR-aligned active-consent standard applied in the Microstockr decision (rejecting pre-ticked or passive consent mechanisms). No Romania-specific dark-patterns statute, clean-room regime, or GPC/DAA opt-out-signal mandate distinct from EU-wide DSA/GDPR frameworks was identified.

No periodic updates recorded in this cycle

Sources and claims (1)
  1. Confirmed EDPB — ANSPDCP found that Microstockr SRL failed to obtain valid cookie consent under Article 5(3) of Directive 2002/58/EC (as transposed by Law No. 506/2004) because the consent mechanism did not constitute a free, specific, informed and unambiguous active indication of the user's wishes. observed

#

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.

Sub-modules (6)

Profiling restrictionsGreen

Profiling restrictions follow GDPR Article 22 directly; no Romania-specific expansion or narrowing identified.

Automated decision making transparencyGreen

ADM transparency obligations follow GDPR Articles 13(2)(f), 14(2)(g) and 15(1)(h) directly.

AI risk assessmentsAmber

The EU AI Act's high-risk system obligations (Chapter III, Annex III — covering biometrics, employment, education, law enforcement) apply directly in Romania; however, the general application date of 2 August 2026 for high-risk rules is subject to a pending Commission Digital Omnibus proposal to adjust timelines linked to the availability of harmonised standards and Commission guidance.

Claims (5):

  • The EU AI Act's obligations for high-risk AI systems (Annex III, including biometrics, education, employment and law enforcement use cases) were due to apply from 2 August 2026, but delayed availability of harmonised standards, common specifications and Commission guidance, along with delayed designation of national competent authorities, has led to a Commission proposal to link entry into application to the availability of supporting compliance measures.
  • On 12 March 2026 the Romanian Government adopted a Memorandum designating ANCOM as the national AI Act market-surveillance authority and single national contact point, roughly seven months after the EU's 2 August 2025 deadline.
  • ANSPDCP 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.
  • ANSPDCP / Authority for the Digitalisation of Romania (ADR) — ANSPDCP is among nine national public authorities Romania notified to the European Commission under Art 77(2) AI Act; the list was published by ADR, not on ANSPDCP's own news page.
  • Romania has not yet adopted the national implementing legislation giving ANCOM and sectoral authorities (ASF, BNR, ANSPDCP, ADR) formal AI Act inspection and sanctioning powers; ANCOM publicly confirmed it cannot sanction non-compliance until that law enters into force.

Biometric regimeAmber

Biometric data processing is governed by GDPR Article 9(1) (biometric data for unique identification as a special category) and, from August 2026, EU AI Act Annex III high-risk rules for biometric identification/categorisation systems; no Romania-specific biometric statute was identified.

Claims (2):

  • ANSPDCP — Contravention fine of 26,236 lei (€5,000) for unlawful biometric fingerprint data processing.
  • ANSPDCP — Contravention fine of 26,236 lei (€5,000) for processing employees' biometric fingerprint data for access control/timekeeping without a legal basis; communiqué does not name the sanctioned operator, though press commentary identified it as Tip Top Food Industry SRL.

Genetic dataAmber

Genetic data is a GDPR Article 9(1) special category; no Romania-specific genetic-data statute was identified in this research pass.

State surveillance carveoutsAmber

National-security/state-surveillance carve-outs follow the general GDPR Article 2(2)(d)/23 framework; no Romania-specific surveillance statute was identified in this research pass.

Category narrative 88 words

Profiling/ADM restrictions in Romania follow GDPR Article 22 directly. The EU AI Act (Regulation (EU) 2024/1689) applies uniformly in Romania as a directly-applicable EU regulation; its high-risk-system obligations (covering biometrics, employment, education and law enforcement use cases under Annex III) were originally due to enter application on 2 August 2026, but a Commission Digital Omnibus proposal is under negotiation to delay/adjust that timeline pending finalisation of Commission guidance on high-risk classification. No Romania-specific biometric or state-surveillance carve-out statute distinct from GDPR/AI Act was identified in this research pass.

Periodic update · new data 2026-10-25

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.

1 earlier distinct update
Periodic update · new data 2026-10-18

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.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (7)
  1. Probable EDPB/EDPS — The EU AI Act's obligations for high-risk AI systems (Annex III, including biometrics, education, employment and law enforcement use cases) were due to apply from 2 August 2026, but delayed availability of harmonised standards, common specifications and Commission guidance, along with delayed designation of national competent authorities, has led to a Commission proposal to link entry into application to the availability of supporting compliance measures. observed
  2. Probable Mararu & Mararu — On 12 March 2026 the Romanian Government adopted a Memorandum designating ANCOM as the national AI Act market-surveillance authority and single national contact point, roughly seven months after the EU's 2 August 2025 deadline. observed
  3. Probable ANSPDCP — ANSPDCP 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. observed
  4. Probable ANSPDCP (Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal) — ANSPDCP — Contravention fine of 26,236 lei (€5,000) for unlawful biometric fingerprint data processing. observed
  5. Probable ANSPDCP (Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal) — ANSPDCP — Contravention fine of 26,236 lei (€5,000) for processing employees' biometric fingerprint data for access control/timekeeping without a legal basis; communiqué does not name the sanctioned operator, though press commentary identified it as Tip Top Food Industry SRL. observed
  6. Confirmed Authority for the Digitalisation of Romania (ADR) — ANSPDCP / Authority for the Digitalisation of Romania (ADR) — ANSPDCP is among nine national public authorities Romania notified to the European Commission under Art 77(2) AI Act; the list was published by ADR, not on ANSPDCP's own news page. observed
  7. Probable ANCOM (Autoritatea Națională pentru Administrare și Reglementare în Comunicații) — Romania has not yet adopted the national implementing legislation giving ANCOM and sectoral authorities (ASF, BNR, ANSPDCP, ADR) formal AI Act inspection and sanctioning powers; ANCOM publicly confirmed it cannot sanction non-compliance until that law enters into force. observed

#

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.

Sub-modules (5)

Age verificationAmber

GDPR Article 8 permits Member States to set the digital age of consent between 13 and 16; this research pass could not confirm from primary text whether Romania set a national derogation below the 16-year default.

Claims (1):

  • GDPR Article 8 sets the default digital age of consent for information-society services at 16, allowing Member States to lower it by national law to not below 13; a Romania-specific statutory derogation could not be confirmed in this research pass.

Minor profiling bansAmber

No dedicated Romanian minor-profiling ban distinct from GDPR Article 22/Recital 71 was identified in this research pass.

Education settingsAmber

No dedicated Romanian education-sector children's-data statute was identified in this research pass.

Dependent adultsAmber

No dedicated Romanian dependent-adults (elderly/incapacitated) data-protection statute distinct from GDPR general capacity/consent rules was identified in this research pass.

Category narrative 102 words

GDPR Article 8 sets the EU default digital age of consent at 16, with Member States permitted to lower it to no less than 13. This research pass did not locate a definitive, authoritative confirmation that Romania has enacted a statutory derogation lowering the age of consent below the GDPR default; Law No. 190/2018 summaries reviewed did not surface an explicit age-of-consent provision, so Romania's position is treated as Probable-default (16) rather than Confirmed pending direct verification of the Law 190/2018 text or ANSPDCP guidance. No dedicated Romanian minor-profiling ban, education-sector-specific DP rule, or dependent-adults DP statute distinct from GDPR was identified.

No periodic updates recorded in this cycle

Sources and claims (2)
  1. Uncertain IAPP — GDPR Article 8 sets the default digital age of consent for information-society services at 16, allowing Member States to lower it by national law to not below 13; a Romania-specific statutory derogation could not be confirmed in this research pass. observed
  2. Uncertain IAPP — Absent a confirmed national derogation, controllers offering information-society services directly to children in Romania must obtain parental/guardian consent for children below the GDPR Article 8 default age of 16. observed

#

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.

Sub-modules (6)

Regulator powers and penaltiesGreen

ANSPDCP exercises corrective and sanctioning powers under GDPR Article 58(2) and applies the Article 83 fining tiers via Law No. 190/2018 Article 12 and Law No. 102/2005 Article 16 procedural rules.

Claims (4):

  • ANSPDCP applies corrective measures under GDPR Article 58(2) and administrative fines under GDPR Article 83, procedurally implemented through Law No. 190/2018 Article 12 and Law No. 102/2005 Article 16 (including paragraphs (3), (5), (6) and (7) governing sanctions imposed by decision of the ANSPDCP president in cross-border cases).
  • ANSPDCP fined SC Hayat Medical & Dental SRL EUR 5,000/2,000 (investigation concluded October 2026) for unlawful processing of patient data and failure to cooperate with an ANSPDCP information request.
  • ANSPDCP fined Auchan România S.A. EUR 8,000, announced 30 October 2026, after an administrator-account compromise exposed internal-user personal data due to inadequate access-security measures.
  • ANSPDCP — ING Bank N.V. Amsterdam - Sucursala București, EUR 5,000, for breach of GDPR Art. 32(1)(b), 32(1)(d), 32(2) and 32(4) following unauthorised employee access to clients' banking data.

Enforcement activity indexAmber

ANSPDCP issued at least two significant fines in January 2026 alone (an individual website operator for RON 50,890 and Continental Automotive Products SRL for RON 76,366), continuing an active multi-year enforcement pattern including a 2023 €70,000 fine against UiPath SRL.

Claims (9):

  • On 30 January 2026, ANSPDCP fined an individual RON 50,890 (approx. €10,000) for GDPR violations including publishing identity cards online and failing to respond to a data-deletion request.
  • On 19 January 2026, ANSPDCP fined Continental Automotive Products SRL RON 76,366 (approx. €15,000) for GDPR violations of Articles 32(1)(b) and 32(2) following a data-breach notification involving employees' medical data.
  • ANSPDCP / MyConnector Platform S.R.L. — ANSPDCP fined MyConnector Platform S.R.L. 31,451 lei (approx. 6,000 EUR) in October 2026 for failing to implement adequate technical and organisational security measures, after a test-server attack exposed real user personal data including national ID numbers.
  • Continental Automotive Products SRL — RON 76,336 for GDPR Article 32 violations
  • evita-teparii.ro operator — Four fines and three corrective measures
  • Roumasport — EUR 10,000 for a GDPR breach
  • Unnamed entity (ANSPDCP decision 25 Sept 2026) — ANSPDCP announced a fine on 25 September 2026 in a case referencing the sensitivity of biometric data; fined entity and exact amount not confirmed in the retrieved excerpt.
  • ANSPDCP — Fined Continental Automotive Products SRL a total of RON 76,366 (RON 25,455 for Art 5(2) minimisation/accountability breach + RON 50,911 for Art 32(1)(b)/(2) security-of-processing breach), after internal circulation of employees' medical certificate data via Excel without adequate technical/organisational measures.
  • ANSPDCP — Fined Roumasport S.R.L. (operator of the Decathlon retail chain in Romania) RON 50,920 (€10,000) for insufficient technical and organisational security measures (Art 32(1)(b)/(2) jo Art 24(1) GDPR), following repeated cyberattacks exposing customer personal data; official decision dated 30 December 2025.

Regulator funding and capacityAmber

No specific Romania-level funding/headcount figures for ANSPDCP were located in this research pass.

Collective redress and class actionsAmber

No Romania-specific collective-redress or class-action mechanism for data protection claims distinct from GDPR Article 80 representative-action provisions was identified in this research pass.

Private right of actionGreen

Private right of action follows GDPR Articles 79 and 82 directly (judicial remedy and compensation); the Bărbulescu case illustrates individual recourse to the ECHR for a Romanian workplace-monitoring dispute, evidencing an operative multi-forum redress landscape.

Claims (1):

  • A Romanian employee successfully pursued an individual complaint to the European Court of Human Rights (Bărbulescu v. Romania) after domestic courts failed to strike an appropriate balance between his privacy rights and his employer's business interests, illustrating the multi-forum redress avenues (domestic courts, ANSPDCP, ECHR) available to Romanian data subjects.

Recent developments 180dAmber

Within the last 180 days, ANSPDCP issued fines against an individual for GDPR violations (30 January 2026, RON 50,890) and against Continental Automotive Products SRL (19 January 2026, RON 76,366) for a medical-data breach; at EU level, the EDPB published its 2025 Annual Report (9 April 2026) reporting €1.15bn in aggregate EU DPA fines for 2025, and the Commission continued negotiating a Digital Omnibus delaying/adjusting EU AI Act high-risk timelines relevant to Romanian AI deployers.

Claims (3):

  • On 30 January 2026, ANSPDCP fined an individual RON 50,890 (approx. €10,000) for GDPR violations including publishing identity cards online and failing to respond to a data-deletion request.
  • On 19 January 2026, ANSPDCP fined Continental Automotive Products SRL RON 76,366 (approx. €15,000) for GDPR violations of Articles 32(1)(b) and 32(2) following a data-breach notification involving employees' medical data.
  • The EDPB's 2025 Annual Report, published 9 April 2026, reported that EU national DPAs collectively issued approximately €1.15 billion in fines during 2025, with 414 cross-border cases created and 572 final One-Stop-Shop decisions under Article 60 GDPR — the cooperative framework in which ANSPDCP participates.
Category narrative 113 words

ANSPDCP actively exercises GDPR Article 58 investigative and corrective powers and Article 83 fining powers; recent 2026 decisions include fines against an individual website operator (RON 50,890) and Continental Automotive Products SRL (RON 76,366) for data-breach-related violations, continuing a pattern of enforcement seen in earlier UiPath SRL (€70,000), Hora Credit IFN and Association of Owners cases. EU-level context: EDPB reported that in 2025 EU DPAs collectively issued approximately €1.15 billion in fines, with 414 cross-border cases and 572 final One-Stop-Shop decisions, reflecting the cooperative enforcement architecture Romania participates in via Article 60 GDPR. No Romania-specific collective-redress mechanism or private right of action distinct from GDPR Articles 79-82 was identified in this research pass.

Periodic update · new data 2026-11-04

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.

2 earlier distinct updates
Periodic update · new data 2026-10-25

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

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.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (15)
  1. Confirmed EDPB — ANSPDCP applies corrective measures under GDPR Article 58(2) and administrative fines under GDPR Article 83, procedurally implemented through Law No. 190/2018 Article 12 and Law No. 102/2005 Article 16 (including paragraphs (3), (5), (6) and (7) governing sanctions imposed by decision of the ANSPDCP president in cross-border cases). observed
  2. Confirmed DataGuidance — On 30 January 2026, ANSPDCP fined an individual RON 50,890 (approx. €10,000) for GDPR violations including publishing identity cards online and failing to respond to a data-deletion request. observed
  3. Confirmed DataGuidance — On 19 January 2026, ANSPDCP fined Continental Automotive Products SRL RON 76,366 (approx. €15,000) for GDPR violations of Articles 32(1)(b) and 32(2) following a data-breach notification involving employees' medical data. observed
  4. Confirmed IAPP — A Romanian employee successfully pursued an individual complaint to the European Court of Human Rights (Bărbulescu v. Romania) after domestic courts failed to strike an appropriate balance between his privacy rights and his employer's business interests, illustrating the multi-forum redress avenues (domestic courts, ANSPDCP, ECHR) available to Romanian data subjects. observed
  5. Confirmed EDPB — The EDPB's 2025 Annual Report, published 9 April 2026, reported that EU national DPAs collectively issued approximately €1.15 billion in fines during 2025, with 414 cross-border cases created and 572 final One-Stop-Shop decisions under Article 60 GDPR — the cooperative framework in which ANSPDCP participates. observed
  6. Probable GDPR Complet — ANSPDCP / MyConnector Platform S.R.L. — ANSPDCP fined MyConnector Platform S.R.L. 31,451 lei (approx. 6,000 EUR) in October 2026 for failing to implement adequate technical and organisational security measures, after a test-server attack exposed real user personal data including national ID numbers. observed
  7. Probable ANSPDCP (dataprotection.ro) — ANSPDCP fined SC Hayat Medical & Dental SRL EUR 5,000/2,000 (investigation concluded October 2026) for unlawful processing of patient data and failure to cooperate with an ANSPDCP information request. observed
  8. High JURIDICE.ro — Continental Automotive Products SRL — RON 76,336 for GDPR Article 32 violations observed
  9. High ANSPDCP — evita-teparii.ro operator — Four fines and three corrective measures observed
  10. High Mararu & Mararu — Roumasport — EUR 10,000 for a GDPR breach observed
  11. Probable JURIDICE.ro — ANSPDCP fined Auchan România S.A. EUR 8,000, announced 30 October 2026, after an administrator-account compromise exposed internal-user personal data due to inadequate access-security measures. observed
  12. Uncertain The DPO — Unnamed entity (ANSPDCP decision 25 Sept 2026) — ANSPDCP announced a fine on 25 September 2026 in a case referencing the sensitivity of biometric data; fined entity and exact amount not confirmed in the retrieved excerpt. observed
  13. Probable JURIDICE.ro — ANSPDCP — ING Bank N.V. Amsterdam - Sucursala București, EUR 5,000, for breach of GDPR Art. 32(1)(b), 32(1)(d), 32(2) and 32(4) following unauthorised employee access to clients' banking data. observed
  14. Probable Financiarul.ro — ANSPDCP — Fined Continental Automotive Products SRL a total of RON 76,366 (RON 25,455 for Art 5(2) minimisation/accountability breach + RON 50,911 for Art 32(1)(b)/(2) security-of-processing breach), after internal circulation of employees' medical certificate data via Excel without adequate technical/organisational measures. observed
  15. Confirmed ANSPDCP (Romanian National Supervisory Authority for Personal Data Processing) — ANSPDCP — Fined Roumasport S.R.L. (operator of the Decathlon retail chain in Romania) RON 50,920 (€10,000) for insufficient technical and organisational security measures (Art 32(1)(b)/(2) jo Art 24(1) GDPR), following repeated cyberattacks exposing customer personal data; official decision dated 30 December 2025. observed
No categories match.

No categories match your current search or filter selection.

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-17. A year-precision row is never promoted into a tighter band.

Envelope: baseline resolved at jurisdiction_json.baseline; 10 categories, 57 sub-module(s), 51 claim(s) (51 category placement(s)), 43 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