Data Protection Monitor
Global Privacy & Data Protection Intelligence

Poland Data Protection & Privacy Regulation

PL schema gdpri-v2 trajectory: not yet assessed regulated (omnibus) overlaps: artificial-intelligence

Last updated · 10 categories · 78 claims · 42 sources in the cumulative register

Poland's most material data-protection development this cycle is an unresolved institutional competence dispute over who supervises artificial-intelligence systems that process personal data.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Regulator & Framework, Enforcement & Redress (2 open gaps).

Framework & posture10 of 10 modules active
10 active · 11 binding instruments
Next milestoneNo upcoming dated milestone on record
Record & confidence mix77 claims · 39 sources · machine-compiled
18 Confirmed54 Probable5 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 Poland is covered once, on the European Economic Area (Bloc) page. This page covers Poland’s own layer: implementation, national authorities, national options and local enforcement.

Jurisdiction brief

Latest update · 8 November 2026

Lead Signal

Poland's Supreme Administrative Court has dismissed a cassation appeal brought by two law firm partners and a former partner, leaving in force a fine of PLN 45,697 imposed jointly and severally against them for processing prospective clients' personal data, including health data, without being able to demonstrate valid consent under Article 7(1) of the GDPR. The court's ruling, issued on 6 October 2026, closes off the firm's last avenue of challenge and confirms the data protection authority's original assessment that consent to process health-related information cannot simply be assumed from the fact of a prospective client relationship; it must be capable of being shown. The case sits alongside continuing enforcement activity by the data protection authority against parties who fail to cooperate with its investigatory powers: a Kraków entrepreneur was fined PLN 31,507 under a decision dated 30 September 2026, not yet final as reported, for failing to provide information the authority required under its Article 58(1) powers.

Key regulatory facts for Poland
Key regulatory facts for Poland
Regulatory DimensionPoland Standing Position
JurisdictionPoland (PL)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 78 sourced findings)
Regulator & FrameworkMature, non-derogating GDPR implementation with an active, well-resourced single supervisory authority and 8 years of enforcement practice.
Lawful Processing & Special DataGDPR-aligned lawful basis and consent framework with active enforcement precedent; anonymisation/pseudonymisation guidance is comparatively thin.
Data Subject RightsFull GDPR rights framework in force with confirmed enforcement precedent on erasure/objection; deadlines follow the standard one-month GDPR response window.
Controller/Processor DutiesDeep, multi-year enforcement record across DPIA/accountability, DPO, ROPA, security, breach-notification and retention obligations confirms these duties are actively supervised and litigated up to appellate courts.
Primary Instruments CitedPoland Official Instrument (cms.law poland), VLO Law Firms, EUR-Lex, DataGuidance, Poland Official Instrument (dataguidance.com poland-uodo-fines-court-bailiff-)
Last Confirmed / Updated (42 sources in cumulative register)

#

Mature, non-derogating GDPR implementation with an active, well-resourced single supervisory authority and 8 years of enforcement practice.

Primary frameworkAct of 10 May 2018 on the Protection of Personal Data, implementing Regulation (EU) 2016/679 (GDPR)
Traffic-light rationale — GreenMature, non-derogating GDPR implementation with an active, well-resourced single supervisory authority and 8 years of enforcement practice.

Sub-modules (5)

Regulator and authorityGreen

UODO's President is the GDPR supervisory authority; other bodies (UOKiK, Office of Electronic Communications) can take related but distinct enforcement action.

Claims (6):

  • UODO's President is the competent GDPR supervisory authority in Poland, with powers to conduct compliance audits, issue administrative decisions and publish guidance.
  • The UODO President holds the rank of a government minister, is appointed by the Sejm with the Senate's consent for a four-year renewable term, and acts independently of government instruction on substantive data-protection decisions.
  • UODO President holds minister-equivalent rank under the Act of 10 May 2018, appointed by the Sejm with Senate consent for a four-year renewable term, and cannot receive government instructions on substantive data-protection decisions.
  • UODO's October 2026 decisions were issued by Prezes Mirosław Wróblewski, confirming continuity of the authority's statutory enforcement powers.
  • Urząd Ochrony Danych Osobowych (UODO) — UODO is Poland's single national GDPR supervisory authority.
  • Ustawa z dnia 10 maja 2018 r. o ochronie danych osobowych (UODO Act) — The same person may not serve as President of UODO for more than two four-year terms

Act and instrumentsGreen

Primary instrument is the Act of 10 May 2018, applying GDPR without major derogation.

Claims (2):

  • The Act of 10 May 2018 on the Protection of Personal Data implements the GDPR in Poland and does not contain major derogations from the Regulation.
  • Poland - Data Management Act — Signed by the President on 2026-06-08, expanding UODO's competences and implementing the EU Data Governance Act.

Material scopeGreen

Material scope follows GDPR Art 2 - automated processing and structured manual filing systems of personal data.

Claims (1):

  • As a non-derogating GDPR implementation, Poland's material scope of protected processing mirrors GDPR Article 2 (automated processing and structured filing systems).

Territorial scopeGreen

Territorial scope follows GDPR Art 3 - applies to non-established controllers targeting or monitoring data subjects in Poland/EU.

Claims (1):

  • Poland's territorial scope of application to non-established controllers mirrors GDPR Article 3, extending to entities targeting or monitoring data subjects in Poland.

Regulator registration and filingGreen

No general controller registration regime; however DPO appointments must be notified to UODO within 14 days of appointment.

Claims (2):

  • Controllers and processors must notify the appointment of a DPO to PUODO within 14 days of the appointment.
  • UODO is the competent authority for data-intermediation services and data altruism organisations under the EU Data Governance Act, per Art 34 ust. 2a, added by the Act of 27 March 2026 on data management.

Key findings (1)

  • Draft AI Systems Act would create KRiBSI as primary AI supervisory authority, with UODO retaining only a coordination role. — source on file
Category narrative 75 words

Poland's data protection regime is a GDPR-implementation jurisdiction. The Act of 10 May 2018 on the Protection of Personal Data establishes the Prezes Urzędu Ochrony Danych Osobowych (President of the Personal Data Protection Office, UODO/PUODO) as the sole supervisory authority for GDPR matters, with audit, decision-making and guidance-issuing functions. The Act is described as containing no major derogations from the GDPR, meaning material and territorial scope track the GDPR baseline (Articles 2 and 3) directly.

Periodic update · new data 2026-11-08

UODO remains Poland's single national supervisory authority for the GDPR, a role it has held since the Regulation's application in May 2018. Its competence was expanded by the Data Management Act, signed by the President on 8 June 2026, which also implements the EU Data Governance Act into Polish law. This expansion predates the current reporting window but remains the standing basis on which UODO's broader regulatory and enforcement activity, including the enforcement developments reported separately this period, now rests.

Outlook

No further change to UODO's statutory footing has been identified. The authority's expanded competence under the Data Management Act is expected to continue shaping the scope of its activity going forward.

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

Sources and claims (12)
  1. Confirmed DataGuidance — UODO's President is the competent GDPR supervisory authority in Poland, with powers to conduct compliance audits, issue administrative decisions and publish guidance. observed
  2. Confirmed DataGuidance — The Act of 10 May 2018 on the Protection of Personal Data implements the GDPR in Poland and does not contain major derogations from the Regulation. observed
  3. Probable EUR-Lex — As a non-derogating GDPR implementation, Poland's material scope of protected processing mirrors GDPR Article 2 (automated processing and structured filing systems). observed
  4. Probable EUR-Lex — Poland's territorial scope of application to non-established controllers mirrors GDPR Article 3, extending to entities targeting or monitoring data subjects in Poland. observed
  5. Confirmed IAPP — Controllers and processors must notify the appointment of a DPO to PUODO within 14 days of the appointment. observed
  6. Probable UODO — The UODO President holds the rank of a government minister, is appointed by the Sejm with the Senate's consent for a four-year renewable term, and acts independently of government instruction on substantive data-protection decisions. observed
  7. Probable RecordingLaw — UODO President holds minister-equivalent rank under the Act of 10 May 2018, appointed by the Sejm with Senate consent for a four-year renewable term, and cannot receive government instructions on substantive data-protection decisions. observed
  8. Probable EdLaw Eduverse — UODO is the competent authority for data-intermediation services and data altruism organisations under the EU Data Governance Act, per Art 34 ust. 2a, added by the Act of 27 March 2026 on data management. observed
  9. Confirmed UODO — UODO's October 2026 decisions were issued by Prezes Mirosław Wróblewski, confirming continuity of the authority's statutory enforcement powers. observed
  10. Confirmed UODO — Urząd Ochrony Danych Osobowych (UODO) — UODO is Poland's single national GDPR supervisory authority. observed
  11. Probable CEO.com.pl — Poland - Data Management Act — Signed by the President on 2026-06-08, expanding UODO's competences and implementing the EU Data Governance Act. observed
  12. Probable GDPR.pl — Ustawa z dnia 10 maja 2018 r. o ochronie danych osobowych (UODO Act) — The same person may not serve as President of UODO for more than two four-year terms observed

#

GDPR-aligned lawful basis and consent framework with active enforcement precedent; anonymisation/pseudonymisation guidance is comparatively thin.

Primary frameworkGDPR Articles 6, 7, 9; Act of 10 May 2018
Traffic-light rationale — GreenGDPR-aligned lawful basis and consent framework with active enforcement precedent; anonymisation/pseudonymisation guidance is comparatively thin.

Sub-modules (4)

Lawful basesGreen

Six GDPR Art 6 lawful bases apply without national variation.

Claims (2):

  • Data controllers in Poland must rely on one of the GDPR Article 6 lawful bases (consent, contract, legal obligation, vital interests, public task, legitimate interests) to process personal data lawfully.
  • Poland (lawful processing) — No PL-specific lawful-basis rule development located this cycle.

Special categoriesAmber

UODO's non-binding employer's guide addresses handling of sensitive/employment data, including restrictions on background checks and social media screening.

Claims (1):

  • UODO's employer's guide sets out restrictive views on collecting candidate and employee data, including that former employers and social media accounts should generally not be used as data sources without specific justification; this guidance is formally non-binding.

Pseudonymisation and anonymisationAmber

No Poland-specific statutory safe-harbour or dedicated UODO guidance on pseudonymisation/anonymisation definitions was identified beyond the GDPR Article 4(5) baseline.

Category narrative 58 words

Lawful bases, consent standards and special-category rules in Poland follow GDPR Articles 6, 7 and 9 directly, given the Act's non-derogating approach. UODO enforcement (e.g. the ClickQuickNow decision) confirms strict application of the Article 7(3) 'easy withdrawal' consent standard. UODO's non-binding employer's guide addresses special-category and employment data handling but is not itself a source of binding law.

Sources and claims (4)
  1. Confirmed EUR-Lex — Data controllers in Poland must rely on one of the GDPR Article 6 lawful bases (consent, contract, legal obligation, vital interests, public task, legitimate interests) to process personal data lawfully. observed
  2. Confirmed EDPB — UODO fined a company over PLN 201,000 for obstructing the exercise of the right to withdraw consent, finding that withdrawal mechanisms must be as easy as giving consent under Article 7(3) GDPR. observed
  3. Probable DataGuidance — UODO's employer's guide sets out restrictive views on collecting candidate and employee data, including that former employers and social media accounts should generally not be used as data sources without specific justification; this guidance is formally non-binding. observed
  4. Uncertain DataGuidance — Poland (lawful processing) — No PL-specific lawful-basis rule development located this cycle. observed

#

Full GDPR rights framework in force with confirmed enforcement precedent on erasure/objection; deadlines follow the standard one-month GDPR response window.

Primary frameworkGDPR Articles 12-22; Act of 10 May 2018
Traffic-light rationale — GreenFull GDPR rights framework in force with confirmed enforcement precedent on erasure/objection; deadlines follow the standard one-month GDPR response window.

Sub-modules (5)

Access rightGreen

Article 15 access right applies without national modification.

Rectification and erasureGreen

UODO has enforced erasure/'right to be forgotten' obligations where controllers processed data of objectors without legal basis.

Claims (1):

  • UODO found that a company unlawfully continued processing personal data of individuals who were not its customers and who had objected to processing, in violation of the right to erasure/'right to be forgotten'.

Restriction and objectionGreen

UODO enforcement confirms the right to object must be operationalised effectively by controllers.

Claims (1):

  • UODO found that a company unlawfully continued processing personal data of individuals who were not its customers and who had objected to processing, in violation of the right to erasure/'right to be forgotten'.

Data portabilityAmber

Article 20 portability right applies without national modification; no PL-specific derogation or guidance beyond GDPR baseline identified.

Deadlines and response windowsGreen

The standard GDPR one-month (extendable to three-month) response window applies to controller responses to data subject requests.

Category narrative 48 words

Poland applies the GDPR Chapter III data subject rights (access, rectification, erasure, restriction, objection, portability) without national derogation. UODO enforcement precedent (ClickQuickNow) confirms active enforcement of the right to object/erasure ('right to be forgotten') where a controller continued processing after an objection was received without a legal basis.

Sources and claims (1)
  1. Confirmed EDPB — UODO found that a company unlawfully continued processing personal data of individuals who were not its customers and who had objected to processing, in violation of the right to erasure/'right to be forgotten'. observed

#

Deep, multi-year enforcement record across DPIA/accountability, DPO, ROPA, security, breach-notification and retention obligations confirms these duties are actively supervised and litigated up to appellate courts.

Primary frameworkGDPR Articles 5, 24-39; Act of 10 May 2018
Traffic-light rationale — GreenDeep, multi-year enforcement record across DPIA/accountability, DPO, ROPA, security, breach-notification and retention obligations confirms these duties are actively supervised and litigated up to appellate courts.

Sub-modules (7)

Accountability & DPIAGreen

UODO enforcement of the accountability principle (Art 5(2)) includes findings on inadequate ROPA and lack of documented risk analysis.

Claims (1):

  • UODO found a mayor's office breached the accountability principle (Article 5(2) GDPR) due to shortcomings in its register of processing activities and absence of risk analysis for publication of council meeting recordings.

DPO requirementsGreen

DPOs must be appointed per Art 37 GDPR conditions and notified to PUODO within 14 days.

Claims (4):

  • Controllers and processors must notify the appointment of a DPO to PUODO within 14 days of the appointment.
  • UODO fined a court bailiff PLN 15,500 on 31 August 2026 for violating GDPR Art. 38(6) (DPO independence) and Art. 37(7) (failure to notify DPO appointment)
  • UODO — PLN 15,500 (court bailiff)
  • UODO — PLN 15,500 (court bailiff; Art.38(6) and Art.37(7) GDPR breaches)

Ropa requirementsGreen

A public-entity controller was fined in part for a deficient register of processing activities lacking recipients and deletion dates.

Claims (1):

  • The first administrative fine imposed on a Polish public entity (PLN 40,000) included findings that its register of processing activities failed to indicate all data recipients or planned deletion dates.

Joint controller arrangementsGreen

Warsaw's administrative court confirmed a controller (Fortum) remained responsible for security even where a processor (Pika) created an unauthorised additional database.

Claims (2):

  • The Provincial Administrative Court in Warsaw confirmed that a controller remains responsible for the security of personal data processing and cannot shift that responsibility entirely to its processor.
  • UODO fined DPD Polska PLN 11 million for violating GDPR Art 28(3) by failing to conclude processing agreements with external carriers, plus inadequate organisational measures.

Security measuresGreen

UODO imposed a €645,000 fine for insufficient technical and organisational security measures following a large-scale data breach.

Claims (1):

  • UODO imposed a €645,000 fine on a company for failing to implement technical means of data protection appropriate to risk, breaching the confidentiality principle of Article 5(1)(f) GDPR, after a breach exposed data of about 2.2 million people.

Breach notificationGreen

Polish courts have upheld UODO fines for failure to notify breaches within the 72-hour window and for failing to communicate breaches to affected individuals.

Claims (4):

  • A Provincial Administrative Court upheld a PLN 16,000 UODO fine against a company for failing to report a data breach, emphasising the obligation to notify UODO within 72 hours of discovering a breach.
  • UODO imposed a further fine of over PLN 85,000 on a healthcare entrepreneur for failing to comply with an order to communicate a personal data breach to affected patients.
  • Under GDPR Art. 33(1), controllers must notify UODO of a personal-data breach without undue delay unless the breach is unlikely to result in a risk to individuals' rights and freedoms; UODO restated this test on 6 October 2026
  • Housing cooperative (unnamed) — NSA upheld a PLN 52,000 UODO fine for failing to report a data breach under GDPR Arts 33-34.

Retention and disposalGreen

UODO found a storage-limitation violation (Art 5(1)(e)) where a public body retained property declarations beyond the statutory 6-year retention period.

Claims (1):

  • UODO found a public body violated the storage-limitation principle (Article 5(1)(e) GDPR) by retaining property declarations from 2010 despite a statutory 6-year retention period.
Category narrative 77 words

UODO enforcement demonstrates active application of accountability, ROPA, breach notification, security and retention obligations. Notable cases include a fine on a municipal mayor for lacking Article 28(3) processing agreements and violating storage-limitation/accountability principles, an entrepreneur fined for failing to communicate a breach to patients, a company fined €645,000 for insufficient technical/organisational security measures following a 2.2 million-record breach, and a joint controller/processor case (Fortum/Pika) confirming that a controller cannot shift responsibility for security entirely to its processor.

No periodic updates recorded in this cycle

Sources and claims (13)
  1. Confirmed EDPB — UODO found a mayor's office breached the accountability principle (Article 5(2) GDPR) due to shortcomings in its register of processing activities and absence of risk analysis for publication of council meeting recordings. observed
  2. Confirmed EDPB — The first administrative fine imposed on a Polish public entity (PLN 40,000) included findings that its register of processing activities failed to indicate all data recipients or planned deletion dates. observed
  3. Confirmed DataGuidance — The Provincial Administrative Court in Warsaw confirmed that a controller remains responsible for the security of personal data processing and cannot shift that responsibility entirely to its processor. observed
  4. Confirmed EDPB — UODO imposed a €645,000 fine on a company for failing to implement technical means of data protection appropriate to risk, breaching the confidentiality principle of Article 5(1)(f) GDPR, after a breach exposed data of about 2.2 million people. observed
  5. Confirmed DataGuidance — A Provincial Administrative Court upheld a PLN 16,000 UODO fine against a company for failing to report a data breach, emphasising the obligation to notify UODO within 72 hours of discovering a breach. observed
  6. Confirmed EDPB — UODO imposed a further fine of over PLN 85,000 on a healthcare entrepreneur for failing to comply with an order to communicate a personal data breach to affected patients. observed
  7. Confirmed EDPB — UODO found a public body violated the storage-limitation principle (Article 5(1)(e) GDPR) by retaining property declarations from 2010 despite a statutory 6-year retention period. observed
  8. Probable https://www.dataguidance.com/news/poland-uodo-fines-court-bailiff-pln-15500-dpo — UODO fined a court bailiff PLN 15,500 on 31 August 2026 for violating GDPR Art. 38(6) (DPO independence) and Art. 37(7) (failure to notify DPO appointment)
  9. Probable VitalLaw — Under GDPR Art. 33(1), controllers must notify UODO of a personal-data breach without undue delay unless the breach is unlikely to result in a risk to individuals' rights and freedoms; UODO restated this test on 6 October 2026 observed
  10. Probable https://www.dataguidance.com/news/poland-uodo-fines-dpd-polska-pln-11m-gdpr-violations — UODO fined DPD Polska PLN 11 million for violating GDPR Art 28(3) by failing to conclude processing agreements with external carriers, plus inadequate organisational measures.
  11. Probable DataGuidance — Housing cooperative (unnamed) — NSA upheld a PLN 52,000 UODO fine for failing to report a data breach under GDPR Arts 33-34. observed
  12. Probable OneTrust DataGuidance — UODO — PLN 15,500 (court bailiff) observed
  13. Probable OneTrust DataGuidance — UODO — PLN 15,500 (court bailiff; Art.38(6) and Art.37(7) GDPR breaches) observed

#

Core transfer mechanisms are harmonised and green at EU level, but Poland-specific friction exists around telecom data-retention law that UODO itself has flagged as inconsistent with EU standards, and this evidence set could not source distinct Polish-issued adequacy decisions (correctly, as this is an EU Commission competence).

Primary frameworkGDPR Chapter V (Articles 44-49); EU Commission adequacy decisions
Traffic-light rationale — AmberCore transfer mechanisms are harmonised and green at EU level, but Poland-specific friction exists around telecom data-retention law that UODO itself has flagged as inconsistent with EU standards, and this evidence set could not source distinct Polish-issued adequacy decisions (correctly, as this is an EU Commission competence).

Sub-modules (6)

Transfer mechanismsGreen

GDPR Chapter V mechanisms apply uniformly; UODO acted as lead supervisory authority in a cross-border complaint from a German data subject.

Claims (1):

  • UODO acted as lead supervisory authority under the GDPR one-stop-shop mechanism in a cross-border complaint originally lodged with the German DPA for Rhineland-Palatinate, because the controller company was established in Poland.

Adequacy receivedAmber

Adequacy decisions are issued at EU Commission level, not by individual Member States; no Poland-specific adequacy-received finding applies distinct from the EU baseline.

Adequacy grantedAmber

Adequacy decisions granted to third countries are issued by the European Commission on behalf of the EU, not individually by Poland.

SCCs and BCRsGreen

Standard Contractual Clauses and BCRs approved by the EDPB/Commission are directly applicable in Poland; no Poland-specific variant identified.

Transfer impact assessmentAmber

TIA requirements follow the EDPB/CJEU Schrems II framework applied uniformly across the EU including Poland; no distinct Polish TIA guidance was located in this research pass.

Data localisationAmber

UODO issued an opinion criticising Polish telecommunications data-retention law as inconsistent with EU standards, raising localisation/retention-adjacent privacy risks.

Claims (1):

  • UODO issued an opinion highlighting the inconsistency of Polish telecommunications data-retention laws with EU standards and associated privacy risks.
Category narrative 87 words

As an EU Member State, Poland relies on the GDPR's harmonised cross-border transfer mechanisms (adequacy decisions issued by the European Commission, SCCs, BCRs, and Article 49 derogations); Poland's UODO does not issue its own third-country adequacy decisions, since that competence sits with the European Commission at EU level. UODO does participate actively in the GDPR one-stop-shop cooperation mechanism as lead or concerned authority in cross-border cases. A distinct localisation-adjacent concern flagged by UODO is Polish telecommunications data-retention law, which UODO's own opinion found inconsistent with EU standards.

Sources and claims (2)
  1. Confirmed EDPB — UODO acted as lead supervisory authority under the GDPR one-stop-shop mechanism in a cross-border complaint originally lodged with the German DPA for Rhineland-Palatinate, because the controller company was established in Poland. observed
  2. Probable DataGuidance — UODO issued an opinion highlighting the inconsistency of Polish telecommunications data-retention laws with EU standards and associated privacy risks. observed

#

Health, employment, education and credit-scoring/data-broker sub-sectors show active supervisory engagement; financial-sector-specific and insurance-specific DP overlays were not surfaced in this research pass.

Primary frameworkGDPR (general); sector legislation (Education Law, Cybersecurity Act/NIS2 implementation, Telecommunications Law) applied alongside UODO oversight
Traffic-light rationale — AmberHealth, employment, education and credit-scoring/data-broker sub-sectors show active supervisory engagement; financial-sector-specific and insurance-specific DP overlays were not surfaced in this research pass.

Sub-modules (7)

Financial sector overlayAmber

No Poland-specific financial-sector DP overlay (e.g. banking-secrecy vs GDPR conflict) was surfaced in this research pass.

Health sector overlayGreen

A healthcare entrepreneur was fined for failing to comply with a UODO order to notify patients of a personal data breach.

Claims (1):

  • UODO fined a healthcare-sector entrepreneur more than PLN 85,000 for failing to comply with an administrative order requiring it to notify affected patients of a personal data breach.

Telecoms and eprivacyAmber

UODO has flagged inconsistency between Polish telecommunications data-retention law and EU standards, and cookie-related guidance exists alongside the ePrivacy Directive framework.

Claims (1):

  • UODO issued an opinion highlighting the inconsistency of Polish telecommunications data-retention laws with EU standards and associated privacy risks.

Employment dataAmber

UODO's non-binding 2018 employer's guide sets restrictive expectations for recruitment and employment-related personal data processing.

Claims (1):

  • UODO's employer's guide sets out restrictive views on collecting candidate and employee data, including that former employers and social media accounts should generally not be used as data sources without specific justification; this guidance is formally non-binding.

Credit and scoringGreen

A data-broker/business-information company was fined roughly €220,000 for failing to provide Article 14 privacy notices to millions of individuals whose data it held in credit/business-verification records.

Claims (1):

  • A Polish data-broker/business-verification company holding over 7.5 million records was fined approximately €220,000 for failing to provide Article 14 GDPR privacy notices to most affected business owners.

educationGreen

UODO commented on a draft amendment to the Education Law, flagging privacy concerns and recommending refinements.

Claims (1):

  • UODO commented on a draft amendment to Poland's Education Law, highlighting privacy concerns and recommending refinements to better protect personal data.

insuranceAmber

No Poland-specific insurance-sector DP overlay was surfaced in this research pass.

Category narrative 71 words

Sectoral overlays in Poland are led by UODO for GDPR compliance, with parallel competences held by UOKiK (competition/consumer protection, including dark-pattern detection) and the Office of Electronic Communications for telecoms. UODO enforcement touches healthcare (breach-notification failures), employment (via non-binding employer guidance), and education (commenting on draft Education Law amendments). A distinct credit-scoring/data-broker enforcement action (a business-information company processing 7.5 million records) resulted in a substantial fine for Article 14 transparency failures.

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

Sources and claims (6)
  1. Confirmed EDPB — UODO fined a healthcare-sector entrepreneur more than PLN 85,000 for failing to comply with an administrative order requiring it to notify affected patients of a personal data breach. observed
  2. Confirmed European Commission — A Polish data-broker/business-verification company holding over 7.5 million records was fined approximately €220,000 for failing to provide Article 14 GDPR privacy notices to most affected business owners. observed
  3. Probable DataGuidance — UODO commented on a draft amendment to Poland's Education Law, highlighting privacy concerns and recommending refinements to better protect personal data. observed
  4. Uncertain Poland Insight — Data Management Act (Poland) — Poland's President signed the Data Management Act in May 2026, implementing the EU Data Governance Act and expanding UODO's competences; the Act had previously passed Parliament (noted 13 April 2026). observed
  5. Confirmed Internetowy System Aktów Prawnych (ISAP), Sejm RP — Data Management Act — 2026-07-23 observed
  6. Confirmed Internetowy System Aktów Prawnych (ISAP), Sejm RP — Ustawa z dnia 27 marca 2026 r. o zarządzaniu danymi (Data Management Act) — 2026-07-23 observed

#

Cookie/consent and direct-marketing enforcement are well evidenced; dark-pattern enforcement is emerging via UOKiK; opt-out signal, clean-room and cross-context advertising sub-modules lack Poland-specific evidence.

Primary frameworkePrivacy Directive 2002/58/EC (as transposed into Polish Telecommunications Law); GDPR Article 6/7 for marketing consent
Traffic-light rationale — AmberCookie/consent and direct-marketing enforcement are well evidenced; dark-pattern enforcement is emerging via UOKiK; opt-out signal, clean-room and cross-context advertising sub-modules lack Poland-specific evidence.

Sub-modules (6)

Cookies and trackersGreen

UODO has published guidance on cookies alongside the ePrivacy Directive framework as transposed into Polish telecommunications law.

Claims (1):

  • UODO has published guidance addressing cookies, alongside guidance on employment data protection and DPIAs.

Dark patternsAmber

UOKiK is developing AI-based tools specifically to detect and combat dark patterns in online commerce.

Claims (2):

  • UOKiK (Poland's Office of Competition and Consumer Protection) is developing AI-based tools to detect and combat dark patterns in online commerce.
  • UOKiK opened dark-patterns proceedings against seven bookmakers in August 2026, a consumer-protection action distinct from UODO's data-protection remit.

Opt out signalsAmber

No Poland-specific finding on Global Privacy Control or DAA-style opt-out signal recognition was surfaced.

Clean rooms and dcrAmber

No Poland-specific clean-room/data-collaboration-room rule was surfaced.

Cross context advertisingAmber

No Poland-specific cross-context advertising ('sale'/'share' style) rule was surfaced; general GDPR consent/legitimate-interest rules for advertising apply.

Direct marketingGreen

UODO enforcement confirms strict standards for direct-marketing consent withdrawal mechanisms.

Claims (1):

  • UODO fined a company over PLN 201,000 for obstructing the exercise of the right to withdraw consent, finding that withdrawal mechanisms must be as easy as giving consent under Article 7(3) GDPR.
Category narrative 72 words

Cookie and tracker consent in Poland follows the ePrivacy Directive framework as transposed into Polish Telecommunications Law, supplemented by UODO cookie guidance. UOKiK (the competition/consumer authority) is separately developing AI tools to detect and combat dark patterns in online commerce. UODO enforcement against obstructive consent-withdrawal mechanisms (ClickQuickNow) is directly relevant to direct-marketing consent practices. Poland-specific findings on opt-out signals (GPC/DAA), clean rooms, and cross-context advertising were not surfaced in this research pass.

Sources and claims (3)
  1. Confirmed DataGuidance — UODO has published guidance addressing cookies, alongside guidance on employment data protection and DPIAs. observed
  2. Probable DataGuidance — UOKiK (Poland's Office of Competition and Consumer Protection) is developing AI-based tools to detect and combat dark patterns in online commerce. observed
  3. Probable Wirtualnemedia.pl — UOKiK opened dark-patterns proceedings against seven bookmakers in August 2026, a consumer-protection action distinct from UODO's data-protection remit. observed

#

AI governance framework is actively in development (draft law, not yet finalised) with UODO's competence recognised but cooperation rules incomplete; biometric/genetic/surveillance-carveout sub-modules lack dedicated Poland-specific evidence.

Primary frameworkGDPR Article 22; Regulation (EU) 2024/1689 (EU AI Act) as implemented via Poland's draft AI implementing law (KRiBSI)
Traffic-light rationale — AmberAI governance framework is actively in development (draft law, not yet finalised) with UODO's competence recognised but cooperation rules incomplete; biometric/genetic/surveillance-carveout sub-modules lack dedicated Poland-specific evidence.

Sub-modules (6)

Profiling restrictionsGreen

GDPR Article 22 restrictions on solely automated decision-making with legal/similarly significant effects apply without national derogation.

Claims (1):

  • Poland applies GDPR Article 22's restriction on decisions based solely on automated processing, including profiling, that produce legal or similarly significant effects, without national derogation.

Automated decision making transparencyGreen

Transparency obligations for automated decision-making follow GDPR Articles 13-15 without Poland-specific variation identified.

Claims (2):

  • Poland applies GDPR Article 22's restriction on decisions based solely on automated processing, including profiling, that produce legal or similarly significant effects, without national derogation.
  • UODO has published guidance on AI-tool use in data processing addressing automated decision-making under GDPR Article 22, profiling, and LLM use in HR and customer-service contexts; the guidance is not binding in the same manner as a regulation but carries significant weight in enforcement proceedings, per secondary commentary.

AI risk assessmentsAmber

Poland's Council of Ministers adopted a draft law implementing the EU AI Act, establishing KRiBSI as the national market surveillance authority, with UODO recognised as having exclusive supervisory competence over high-risk AI systems, though the draft reportedly lacks detailed cooperation rules.

Claims (4):

  • Poland's Council of Ministers adopted a draft law implementing the EU AI Act, establishing KRiBSI as the national market surveillance authority to supervise AI compliance and support innovation.
  • Poland's draft AI implementing law recognises UODO's exclusive supervisory competence over high-risk AI systems, but commentary indicates the draft lacks detailed inter-authority cooperation rules and explicit protection of fundamental rights.
  • KRiBSI (Commission for the Development and Safety of Artificial Intelligence) — The Act of 3 July 2026 on AI Systems establishes KRiBSI as Poland's sole AI Act market-surveillance authority and single point of contact, with composition drawing representatives from UOKiK, KNF, KRRiT and UKE, appointed for a five-year term by the Sejm; UODO holds an advisory (non-voting) role, which UODO has publicly criticised.
  • Poland (draft Act on Artificial Intelligence Systems) — Draft AI Systems Act (Council of Ministers, 31 March 2026) creates KRiBSI as primary AI authority; UODO criticised its own relegation to advisory role; competence split for AI decisions involving personal data unresolved as of May 2026.

Biometric regimeAmber

No Poland-specific biometric data regime (facial recognition/fingerprint/gait) finding was surfaced in this research pass.

Genetic dataAmber

No Poland-specific genetic data regime finding was surfaced beyond the GDPR Article 9 special-category baseline.

State surveillance carveoutsAmber

No Poland-specific state-surveillance carveout/national-security exemption finding was surfaced in this research pass.

Key findings (1)

  • UODO's exclusive high-risk-AI supervisory competence recognised in draft, but cooperation rules and fundamental-rights protections undetailed. — source on file
Category narrative 82 words

Profiling and automated decision-making restrictions in Poland follow GDPR Article 22 directly. The dominant recent development is Poland's implementation of the EU AI Act: the Council of Ministers adopted a draft law designating KRiBSI as the national market surveillance authority for AI, and the draft recognises UODO's exclusive supervisory competence over high-risk AI systems, though commentary notes the draft law lacks detailed inter-authority cooperation rules and explicit fundamental-rights protections. Poland-specific biometric-regime, genetic-data, and state-surveillance-carveout findings were not surfaced in this research pass.

Periodic update · new data 2026-10-25

Poland has enacted its national implementing framework for the EU AI Act through the Act of 3 July 2026 on AI Systems. The centrepiece of this law is the establishment of a new institutional body, referred to by the acronym KRiBSI (the Commission for the Development and Safety of Artificial Intelligence), which the Act designates as Poland's sole market-surveillance authority for AI systems and its single point of contact for AI Act purposes. The law also establishes a national supervision, conformity-assessment, and regulatory-sandbox framework around KRiBSI's role.

The composition of KRiBSI is notable for drawing representatives from several existing sectoral regulators rather than concentrating authority in a single pre-existing body. Representatives are drawn from UOKiK (the competition and consumer-protection authority), KNF (the financial-supervision authority), KRRiT (the broadcasting regulator), and UKE (the electronic-communications regulator), with members appointed by the Sejm for a five-year term. This multi-sectoral composition suggests an institutional design intended to bring cross-sectoral regulatory expertise to bear on AI-system oversight, spanning competition, financial, broadcasting, and telecommunications concerns.

What is conspicuously absent from KRiBSI's voting membership is the Office for Personal Data Protection, UODO, Poland's dedicated data-protection authority. UODO is reported to hold only an advisory, non-voting role on KRiBSI, notwithstanding that a very substantial proportion of AI-system risk in practice arises precisely from how such systems process personal data, whether through training, inference, or profiling. UODO is understood to have publicly criticised this arrangement. The practical effect is that the authority with the deepest institutional expertise in personal-data risk assessment sits outside the body making binding market-surveillance decisions about AI systems, even where those decisions will frequently turn on personal-data processing questions that fall squarely within UODO's traditional area of competence.

This is a structurally significant arrangement for how algorithmic governance and data-protection oversight will interact in Poland going forward. Decisions by KRiBSI about AI-system conformity, risk classification, or market restriction will be taken by a voting body that does not include the national data-protection regulator as a full member, which creates a structural question about how personal-data-specific input reaches KRiBSI's decision-making in a way that actually influences outcomes, as opposed to being heard only in an advisory capacity that carries no formal weight in the final vote.

Outlook

The precise working division of competence between KRiBSI and UODO, once implementing appointments to KRiBSI are made and the body becomes operationally active, has not yet been established and remains an open institutional question. Given UODO's reported public criticism of its advisory-only status, there is a live possibility that this division of labour becomes a point of ongoing institutional tension rather than settling quietly, though no particular resolution should be assumed. Confirmation of how KRiBSI's early decisions actually treat personal-data-related AI-system risk, once the body begins operating, is the key item to watch in subsequent reporting periods.

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

Sources and claims (6)
  1. Probable EUR-Lex — Poland applies GDPR Article 22's restriction on decisions based solely on automated processing, including profiling, that produce legal or similarly significant effects, without national derogation. observed
  2. Probable DataGuidance — Poland's Council of Ministers adopted a draft law implementing the EU AI Act, establishing KRiBSI as the national market surveillance authority to supervise AI compliance and support innovation. observed
  3. Uncertain DataGuidance — Poland's draft AI implementing law recognises UODO's exclusive supervisory competence over high-risk AI systems, but commentary indicates the draft lacks detailed inter-authority cooperation rules and explicit protection of fundamental rights. observed
  4. Probable Glacis — KRiBSI (Commission for the Development and Safety of Artificial Intelligence) — The Act of 3 July 2026 on AI Systems establishes KRiBSI as Poland's sole AI Act market-surveillance authority and single point of contact, with composition drawing representatives from UOKiK, KNF, KRRiT and UKE, appointed for a five-year term by the Sejm; UODO holds an advisory (non-voting) role, which UODO has publicly criticised. observed
  5. Probable EDPB — Poland (draft Act on Artificial Intelligence Systems) — Draft AI Systems Act (Council of Ministers, 31 March 2026) creates KRiBSI as primary AI authority; UODO criticised its own relegation to advisory role; competence split for AI decisions involving personal data unresolved as of May 2026. observed
  6. Uncertain CEO.com.pl — UODO has published guidance on AI-tool use in data processing addressing automated decision-making under GDPR Article 22, profiling, and LLM use in HR and customer-service contexts; the guidance is not binding in the same manner as a regulation but carries significant weight in enforcement proceedings, per secondary commentary. observed

#

Age-verification-for-adult-content legislation is a live, not-yet-fully-effective development; the precise Article 8 age-of-consent figure for Poland could not be confirmed with a dedicated primary-source citation in this pass, and minor-profiling-ban / dependent-adult sub-modules lack direct evidence.

Primary frameworkGDPR Article 8; Act of 10 May 2018; draft act on age verification for online adult content
Traffic-light rationale — AmberAge-verification-for-adult-content legislation is a live, not-yet-fully-effective development; the precise Article 8 age-of-consent figure for Poland could not be confirmed with a dedicated primary-source citation in this pass, and minor-profiling-ban / dependent-adult sub-modules lack direct evidence.

Sub-modules (5)

Age verificationAmber

Poland's Council of Ministers adopted a draft act requiring age verification for online adult content to protect minors.

Claims (1):

  • Poland's Council of Ministers adopted a draft act requiring age verification for online adult content specifically to protect minors.

Minor profiling bansAmber

No Poland-specific ban on profiling of minors distinct from the general GDPR Article 22/Recital 71 baseline was surfaced.

Education settingsGreen

UODO commented on a draft amendment to the Education Law, flagging privacy concerns relevant to pupil data processing.

Claims (1):

  • UODO commented on a draft amendment to Poland's Education Law, highlighting privacy concerns and recommending refinements to better protect personal data.

Dependent adultsAmber

No Poland-specific dependent-adults (elderly/mentally incapacitated) data protection finding was surfaced in this research pass.

Category narrative 91 words

Poland's Act of 10 May 2018 is described as containing no major derogations from the GDPR, and no Poland-specific lower age-of-consent provision under GDPR Article 8 was located in this research pass, implying the GDPR default age of 16 applies absent an identified national derogation. Separately, Poland's Council of Ministers adopted a draft act requiring age verification for online adult content specifically to protect minors, and UODO has engaged with the Ministry of Education on draft Education Law amendments touching pupil data. No Poland-specific minor-profiling ban or dependent-adults-specific finding was surfaced.

Sources and claims (2)
  1. Probable DataGuidance — Poland's Council of Ministers adopted a draft act requiring age verification for online adult content specifically to protect minors. observed
  2. Uncertain DataGuidance — Because the Act of 10 May 2018 does not contain major derogations from the GDPR, Poland is presumed to apply the GDPR default age of 16 for a child's own consent to information-society services under Article 8, absent an identified national derogation lowering that age. observed

#

UODO exhibits sustained, escalating enforcement activity with judicial oversight (both upholding and overturning decisions), indicating a mature and active enforcement ecosystem; collective-redress mechanisms specific to Poland were not confirmed in this pass.

Primary frameworkGDPR Articles 58, 83, 84; Act of 10 May 2018
Traffic-light rationale — GreenUODO exhibits sustained, escalating enforcement activity with judicial oversight (both upholding and overturning decisions), indicating a mature and active enforcement ecosystem; collective-redress mechanisms specific to Poland were not confirmed in this pass.

Sub-modules (6)

Regulator powers and penaltiesGreen

UODO holds full GDPR Article 58 corrective powers including administrative fines, applied against both private companies and public bodies.

Claims (9):

  • UODO's corrective powers include the power to order breach communication to data subjects and to impose administrative fines in addition to or instead of other Article 58(2) GDPR measures.
  • UODO imposed a PLN 15,000 fine on a company for failing to provide the supervisory authority with access to personal data and information necessary for performance of its tasks in a cross-border complaint.
  • Poland - UODO enforcement against RKW association — PLN 10,082 fine for infringing UODO's Art. 58(1)(a)/(e) information-and-access powers
  • Poland - UODO enforcement against Kraków entrepreneur — PLN 31,507 fine (case DKE.561.7.2026), not final
  • UODO fined an administrator 29,112 PLN on 5 October 2026 for non-execution of a prior UODO order, under GDPR Art 83.
  • UODO fined DPD Polska PLN 11 million on 23 February 2026 for breach of GDPR Art 28(3) (failure to conclude processor agreements with external carriers) and related organisational failures.
  • Poland public authorities and cultural institutions — Administrative fines on public authorities and bodies are capped at PLN 100,000 (approx. EUR 23,555), and at PLN 10,000 for cultural institutions, under national provisions supplementing GDPR Art. 83(7)
  • Poland - UODO enforcement against RKW association — PLN 10,082 fine for infringing UODO's Art. 58(1)(a)/(e) information-and-access powers by failing to respond to requests concerning an election-related app
  • Poland - UODO enforcement against Kraków entrepreneur — PLN 31,507 fine (case DKE.561.7.2026) for failing to provide information requested in an investigation into two websites; not final

Enforcement activity indexGreen

Multiple significant fines and court decisions occurred within the last 12 months, spanning breach notification, security, transparency and election-related data misuse.

Claims (12):

  • UODO fined the Minister of Justice PLN 100,000 for unlawful access and misuse of judges' personal data.
  • The Provincial Administrative Court in Warsaw overturned UODO's PLN 27 million fine against Poczta Polska concerning personal data processing during the 2020 postal presidential elections.
  • UODO fined the Nawrocki Presidential Electoral Committee PLN 35,582 for unlawfully disclosing personal data during a press conference.
  • UODO's 2026 fining decisions to date total close to PLN 7 million, the largest (~PLN 5.9M) against Restaurant Partner Polska (Glovo) for unlawfully requiring users to upload ID-card scans, breaching the data-minimisation principle.
  • UODO — 2025 marked a record year with over PLN 64 million in fines, including the three largest penalties in Polish DP history (Poczta Polska PLN 27m, Bank ING PLN 18.4m, McDonald's PLN 16.9m), all under challenge or not yet final.
  • UODO fined DPD Polska PLN 11 million (announced 23 February 2026) for GDPR Art. 28(3) violations and inadequate organisational measures
  • UODO decided on 16 September 2026 to open wider inspections of health-data processing, running until end-2026, in the context of a data leak affecting up to 1.3 million customers of an online sales platform (over 50 complaints and 2,000 controller notifications received by 17 September 2026).
  • UODO fined a Kraków-based entrepreneur PLN 31,507 on 30 September 2026 for failing to provide information UODO needed to investigate two websites, including the controller's identity and possible transfers of data outside Poland and the EU/EEA.
  • Law firm partners (unnamed) — NSA dismissed a cassation appeal on 2026-10-06, leaving in force a PLN 45,697 fine against two partners and a former partner, jointly and severally liable, for processing prospective clients' personal data including health data without demonstrating consent under GDPR Art 7(1).
  • Kraków entrepreneur (unnamed) — UODO President imposed a PLN 31,507 fine (decision DKE.561.7.2026, not final as of report date) for failing to provide information UODO required under Art 58(1) investigatory powers.
  • UODO — PLN 11,000,000+ (DPD Polska)
  • UODO — PLN 11,000,000+ (DPD Polska; two fines: PLN 6.251m Art.28(3) GDPR; PLN 5.209m Art.24(2),29,32(4) GDPR)

Regulator funding and capacityAmber

Historical EU Commission data show Poland's DPA received one of the highest complaint volumes in the EU/EEA (around 12,000 complaints in the 2018-2019 period), indicating substantial caseload relative to peer authorities; more current staffing/budget figures were not located in this pass.

Claims (1):

  • Between 25 May 2018 and 30 November 2019, Poland's data protection authority was among the highest-volume EU/EEA authorities, registering around 12,000 complaints in that period.

Collective redress and class actionsAmber

No Poland-specific collective-redress or class-action mechanism for data protection claims was surfaced in this research pass.

Private right of actionGreen

GDPR Articles 79/82 provide for judicial remedies and compensation; Polish administrative courts (Provincial Administrative Court in Warsaw, Supreme Administrative Court) actively review UODO decisions on appeal by both controllers and complainants.

Claims (1):

  • Polish administrative courts, including the Provincial Administrative Court in Warsaw and the Supreme Administrative Court, actively review and can uphold or overturn UODO's administrative fine decisions on appeal.

Recent developments 180dGreen

Within the last 180 days, Poland signed an amended Cybersecurity Act (19 February 2026) aligning with NIS2, and progressed the Data Management Act implementing the EU Data Governance Act with UODO's President as competent authority; a draft AI implementing law naming KRiBSI as AI market surveillance authority was also adopted by the Council of Ministers.

Claims (6):

  • Poland's amended Cybersecurity Act, aligning with the NIS2 Directive and imposing new compliance deadlines and reporting obligations for key and important entities, was signed on 19 February 2026.
  • Poland's Parliament passed the Data Management Act to ensure full application of the EU Data Governance Act, designating UODO's President as the competent authority.
  • Housing cooperative (Poland) — On 26 August 2026 the Supreme Administrative Court (NSA) upheld a UODO fine of PLN 52,000 against a housing cooperative for failing to notify a personal-data breach (PESEL number, name, address) within the GDPR Art 33 framework.
  • UODO's first private-CCTV GDPR penalty (26,711 PLN) became final on 22 August 2026, relying on a narrow household-exemption interpretation.
  • Provincial Administrative Court (Warsaw) — UODO's PLN 27 million fine against Poczta Polska for processing personal data during the 2020 postal presidential elections.
  • UODO — Employee-monitoring practices (keystroke logging, screen capture, GPS tracking, email monitoring) and HR health-data processing.
Category narrative 127 words

UODO has broad GDPR Article 58 corrective powers, including administrative fines, which it has used extensively across public and private sector controllers since 2019. Recent 12-month enforcement activity (to August 2026) includes a PLN 100,000 fine on the Minister of Justice for unlawful access to judges' personal data, a PLN 35,582 fine on a presidential electoral committee, upheld fines against Fortum/Pika for a breach affecting over 90,000 individuals, and a Provincial Administrative Court decision overturning a PLN 27 million fine against Poczta Polska (illustrating active judicial review of UODO decisions). Poland's amended Cybersecurity Act (signed 19 February 2026) and the Data Management Act (implementing the EU Data Governance Act, with UODO's President as competent authority) are recent developments within the last 180 days materially affecting UODO's remit.

Periodic update · new data 2026-11-08

The Supreme Administrative Court dismissed a cassation appeal on 6 October 2026, leaving in force a fine of PLN 45,697 against two law firm partners and a former partner, held jointly and severally liable, for processing prospective clients' personal data, including health data, without being able to demonstrate consent as required under Article 7(1) of the GDPR. The decision was reported on 2 November 2026 and finally resolves the matter in the authority's favour.

Separately, UODO's President imposed a fine of PLN 31,507 on a Kraków entrepreneur under decision DKE.561.7.2026, dated 30 September 2026, for failing to provide information the authority had required in the exercise of its investigatory powers under Article 58(1) of the GDPR. That decision was reported as not yet final at the time of reporting.

Taken together, these two matters show an authority actively exercising both its substantive enforcement powers, in the health-data consent case, and its procedural, investigatory enforcement powers, in the non-cooperation case, within the same period.

Outlook

The health-data consent fine is now final and closes that matter. The non-cooperation fine's finality remains to be confirmed; if it is not challenged or is upheld, it will stand as a further marker of the authority's willingness to sanction non-cooperation with its investigatory powers independent of the underlying processing question.

5 earlier distinct updates
Periodic update · new data 2026-11-04

Poland's data protection authority is understood to have issued two separate penalties this period grounded in its supervisory information-and-access powers rather than in findings on substantive data-processing conduct. The first, a decision dated 18 May 2026 against an association referred to as RKW and reported moving into enforcement on 26 October 2026, imposed a fine of PLN 10,082 for failing to respond to requests for information concerning an election-related application, relying on Article 58(1)(a) and (e) of the General Data Protection Regulation. The second, reported on 30 September 2026 under case reference DKE.561.7.2026, imposed a fine of PLN 31,507 on a Kraków-based entrepreneur for failing to provide information sought during an investigation into two websites; this decision is understood not yet to be final. In each case, the regulator's inquiry into the underlying data-processing conduct, the election-related application in the first matter and the two websites in the second, appears to remain open rather than resolved; the fines imposed so far address only the entities' non-cooperation with the authority's information-gathering process.

Outlook

Whether the RKW decision has become final or is subject to appeal, and whether the Kraków entrepreneur's fine will survive any appeal period, remain open at this time. The more significant development to watch for is whether either investigation progresses beyond a cooperation-based penalty to a substantive determination on the underlying processing activity, which would represent a materially different stage of enforcement than what has been confirmed so far.

Periodic update · new data 2026-10-25

UODO's enforcement activity in the period leading into this cycle shows a sustained and active supervisory posture across two distinct types of action. On 16 September 2026, UODO decided that wider inspections of health-data processing were warranted, a decision taken in the context of a data breach reported to have affected up to 1.3 million customers of an online sales platform. By 17 September 2026, UODO had received more than 50 complaints and over 2,000 controller notifications connected to that matter. UODO announced that the resulting additional inspections of health-data processing would continue through the end of 2026, indicating a sustained, sector-wide supervisory effort rather than a single, time-limited inquiry confined to the triggering breach alone.

Separately, on 30 September 2026, UODO imposed an administrative fine of PLN 31,507 on a Kraków-based entrepreneur. The fine was imposed specifically for the entrepreneur's failure to provide information UODO needed to investigate two websites, including the identity of the controller operating them and whether personal data had been transferred outside Poland and the EU/EEA. This is a cooperation-failure penalty rather than a substantive-breach penalty: the entrepreneur was fined not for the underlying data-processing conduct itself, but for obstructing UODO's ability to investigate that conduct, which is itself a distinct category of enforcement risk that controllers and their advisers should not overlook relative to substantive compliance failures.

Taken together, these two actions illustrate that UODO's enforcement cadence spans both proactive sector-wide inspection activity, triggered by a specific large-scale breach but extending beyond it, and targeted penalties for individual non-cooperation, suggesting an authority willing to use both tools concurrently rather than relying on one enforcement mechanism to the exclusion of the other.

Outlook

The health-data inspection sweep announced on 16 September 2026 is due to continue through the end of 2026; whether it has produced, or will produce, any formal enforcement decision within that window has not yet been confirmed and should be treated as an open item for subsequent reporting periods. The cooperation-failure fine imposed on 30 September 2026 stands as a concluded enforcement action but leaves open whether the underlying substantive investigation into the two websites' data-transfer practices will itself produce a further enforcement outcome once the entrepreneur's required cooperation, if provided, is assessed.

Periodic update · new data 2026-10-18

UODO's two most recently confirmed enforcement decisions, both dated shortly before this cycle's window, illustrate the authority's current approach to Article 83 administrative fines and are carried here for continuity. In a decision published 5 October 2026, UODO fined an administrator 29,112 PLN for failing to execute a prior UODO order to fulfil an information obligation toward a complainant. This is a procedurally distinct basis for a fine: rather than penalising the original substantive violation, UODO imposed the penalty specifically for non-compliance with its own prior administrative order, under GDPR Article 83 as applied by UODO. The structural significance of this decision is that it demonstrates UODO treats non-execution of its orders as an independently sanctionable act, meaning a controller already subject to a UODO order faces compounding exposure if it does not comply, rather than resolving its position through continued inaction.

Separately, UODO's first-ever penalty specifically addressing private home-CCTV GDPR non-compliance, a 26,711 PLN fine, became final after the subject did not appeal to the Provincial Administrative Court. This decision's final status (as opposed to still being subject to appeal) is itself significant for enforcement-and-redress tracking: a final UODO decision represents the conclusion of the administrative enforcement path, with judicial review having been available but not pursued. UODO's underlying legal reasoning relied on a narrow interpretation of the household exemption under GDPR, grounded in a Court of Justice of the European Union ruling dated 11 December 2014, under which private surveillance extending beyond the strictly personal or household sphere can fall within GDPR's scope rather than being excluded from it. The 11 December 2014 CJEU precedent concerned a private individual's CCTV system that also captured a public street, establishing that household-exemption coverage does not extend to surveillance capturing space beyond the purely personal domain; UODO's reliance on this reasoning for a private home-CCTV case indicates the authority continues to apply this narrow household-exemption standard to residential surveillance enforcement.

Both decisions, while dated outside the current reporting window itself (5 October and 22 August 2026 respectively, against a window opening 11 October 2026), are carried forward here because they represent UODO's most recent confirmed exercises of its Article 83 enforcement powers and establish the baseline against which any decision dated inside the window would be read. No dated development specifically inside the 11-18 October 2026 window was located for the enforcement-and-redress module this cycle.

Outlook

The enforcement-and-redress posture to watch is whether UODO issues further decisions applying the same two reasoning patterns evident in these two carried-forward cases: fines for non-execution of prior orders, and a narrow household-exemption standard for private surveillance. No specific forthcoming decision or inspection-plan item dated inside the window was confirmed this cycle, so the module's trajectory remains one of continuity with UODO's established enforcement practice rather than a new development.

Periodic update · new data 2026-10-11

UODO's 2026 enforcement record shows continued high intensity across multiple sectors, punctuated by one significant judicial reversal. UODO fined DPD Polska PLN 11 million in a decision announced 23 February 2026, for violations of GDPR Article 28(3) concerning processor obligations and for inadequate organisational measures — among the largest Polish data-protection fines to date. UODO also fined Restaurant Partner Polska, the company operating the Glovo delivery platform in Poland, almost PLN 5.9 million for requiring users to upload scans of their identity cards without a legal basis, a finding that the practice breached the data-minimisation principle; UODO ordered erasure of the scans already collected as part of the decision.

Smaller enforcement actions continued through the year: a PLN 15,500 fine against a court bailiff on 31 August 2026 for DPO-related violations, and a PLN 31,507 fine against a Kraków-based entrepreneur on 30 September 2026, not yet final, for failing to cooperate with UODO's proceedings.

The most consequential development for the durability of UODO's enforcement record, however, is judicial rather than administrative: the Provincial Administrative Court in Warsaw overturned UODO's PLN 27 million fine against Poczta Polska, a decision reported 11 March 2026, concerning Poczta Polska's processing of personal data during the 2020 postal presidential election. This was one of UODO's largest-ever fines, and its reversal by a court — with appeal status unresolved — demonstrates that UODO's highest-value and most politically sensitive enforcement decisions remain genuinely contestable rather than final once issued. Separately, national law caps administrative fines on public authorities and bodies at PLN 100,000, and at PLN 10,000 for cultural institutions, a standing variance from the general GDPR Article 83 fine ceiling that constrains UODO's leverage against public-sector controllers specifically.

Outlook

The Poczta Polska reversal is the single development most likely to shape UODO's enforcement posture going forward: whether UODO appeals, and whether the Provincial Administrative Court's reasoning is echoed in future challenges to large UODO fines, will determine whether 2026's run of high-value enforcement actions continues at the same pace or faces increasing judicial resistance. The continuing cadence of smaller, more procedurally straightforward fines — DPO violations, non-cooperation — suggests that UODO's core day-to-day enforcement activity is not itself destabilised by the setback in the Poczta Polska case.

Periodic update · new data 2026-09-28

Poland's data-protection enforcement environment continues on an escalating trajectory into 2026. Secondary reporting characterises 2025 as a record enforcement year for UODO, with over PLN 64 million in fines issued across the year; this figure has not yet been directly corroborated against UODO's own published annual report, and its precise official total remains an open question. Regardless of that outstanding corroboration, 2026 enforcement activity has already produced a large individual decision that reinforces the escalating-intensity picture: UODO fined DPD Polska PLN 11 million on 23 February 2026 following an ex officio inspection of courier-delivery data processing. The penalty was split between deficient governance of data-processing agreements, at PLN 6.251 million, and inadequate technical and organisational access controls, at PLN 5.209 million, indicating UODO's willingness to impose substantial fines across multiple distinct GDPR failure categories within a single decision.

A second material 2026 decision, against a delivery platform (Glovo), imposed a fine of almost PLN 5.9 million for requiring users to upload ID-card scans for anti-fraud purposes without a legal basis, in breach of the data-minimisation principle, with UODO ordering erasure of the collected scans. Both decisions are Probable-confidence findings resting on law-firm and vendor secondary reporting rather than a directly retrieved primary UODO decision page, a sourcing gap that, if closed, would allow these findings to move toward Confirmed status.

Alongside the fine-driven enforcement track, Poland implemented Directive (EU) 2020/1828 in August 2024, amending the Polish Class Actions Act to permit authorised consumer organisations to bring representative GDPR actions seeking injunctive relief and compensation. This collective-redress mechanism is a standing feature of the enforcement-and-redress landscape rather than a new development this cycle, but it means UODO's own administrative fining power now operates alongside a private collective-litigation route as a second enforcement channel available to affected data subjects.

Outlook

Corroboration of UODO's official 2025 total-fines figure against its own published annual report is the most useful confirmation to watch for, given the current reliance on secondary reporting. Continued 2026 enforcement volume, and any use of the August 2024 collective-redress mechanism in a GDPR-specific representative action, would both be significant markers of how Poland's dual administrative-and-collective enforcement architecture is maturing in practice.

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

Sources and claims (29)
  1. Confirmed EDPB — UODO's corrective powers include the power to order breach communication to data subjects and to impose administrative fines in addition to or instead of other Article 58(2) GDPR measures. observed
  2. Confirmed EDPB — UODO imposed a PLN 15,000 fine on a company for failing to provide the supervisory authority with access to personal data and information necessary for performance of its tasks in a cross-border complaint. observed
  3. Probable DataGuidance — UODO fined the Minister of Justice PLN 100,000 for unlawful access and misuse of judges' personal data. observed
  4. Probable DataGuidance — The Provincial Administrative Court in Warsaw overturned UODO's PLN 27 million fine against Poczta Polska concerning personal data processing during the 2020 postal presidential elections. observed
  5. Probable DataGuidance — UODO fined the Nawrocki Presidential Electoral Committee PLN 35,582 for unlawfully disclosing personal data during a press conference. observed
  6. Confirmed European Commission — Between 25 May 2018 and 30 November 2019, Poland's data protection authority was among the highest-volume EU/EEA authorities, registering around 12,000 complaints in that period. observed
  7. Confirmed DataGuidance — Polish administrative courts, including the Provincial Administrative Court in Warsaw and the Supreme Administrative Court, actively review and can uphold or overturn UODO's administrative fine decisions on appeal. observed
  8. Confirmed DataGuidance — Poland's amended Cybersecurity Act, aligning with the NIS2 Directive and imposing new compliance deadlines and reporting obligations for key and important entities, was signed on 19 February 2026. observed
  9. Confirmed DataGuidance — Poland's Parliament passed the Data Management Act to ensure full application of the EU Data Governance Act, designating UODO's President as the competent authority. observed
  10. Probable UODO — Poland - UODO enforcement against RKW association — PLN 10,082 fine for infringing UODO's Art. 58(1)(a)/(e) information-and-access powers observed
  11. Probable CEO.com.pl — Poland - UODO enforcement against Kraków entrepreneur — PLN 31,507 fine (case DKE.561.7.2026), not final observed
  12. Confirmed UODO — UODO fined an administrator 29,112 PLN on 5 October 2026 for non-execution of a prior UODO order, under GDPR Art 83. observed
  13. Probable CEO.com.pl — UODO fined DPD Polska PLN 11 million on 23 February 2026 for breach of GDPR Art 28(3) (failure to conclude processor agreements with external carriers) and related organisational failures. observed
  14. Probable DataGuidance — Housing cooperative (Poland) — On 26 August 2026 the Supreme Administrative Court (NSA) upheld a UODO fine of PLN 52,000 against a housing cooperative for failing to notify a personal-data breach (PESEL number, name, address) within the GDPR Art 33 framework. observed
  15. Probable DataGuidance — UODO's 2026 fining decisions to date total close to PLN 7 million, the largest (~PLN 5.9M) against Restaurant Partner Polska (Glovo) for unlawfully requiring users to upload ID-card scans, breaching the data-minimisation principle. observed
  16. Confirmed https://cms.law/en/int/publication/gdpr-enforcement-tracker-report/poland — UODO — 2025 marked a record year with over PLN 64 million in fines, including the three largest penalties in Polish DP history (Poczta Polska PLN 27m, Bank ING PLN 18.4m, McDonald's PLN 16.9m), all under challenge or not yet final.
  17. Probable GazetaPrawna.pl — UODO's first private-CCTV GDPR penalty (26,711 PLN) became final on 22 August 2026, relying on a narrow household-exemption interpretation. observed
  18. Probable https://www.dataguidance.com/jurisdiction/poland — Provincial Administrative Court (Warsaw) — UODO's PLN 27 million fine against Poczta Polska for processing personal data during the 2020 postal presidential elections.
  19. Probable VLO Law Firms — UODO — Employee-monitoring practices (keystroke logging, screen capture, GPS tracking, email monitoring) and HR health-data processing. observed
  20. Probable https://www.dataguidance.com/news/poland-uodo-fines-dpd-polska-pln-11m-gdpr-violations — UODO fined DPD Polska PLN 11 million (announced 23 February 2026) for GDPR Art. 28(3) violations and inadequate organisational measures
  21. Probable CMS Law — Poland public authorities and cultural institutions — Administrative fines on public authorities and bodies are capped at PLN 100,000 (approx. EUR 23,555), and at PLN 10,000 for cultural institutions, under national provisions supplementing GDPR Art. 83(7) observed
  22. Probable Gibson Dunn — UODO decided on 16 September 2026 to open wider inspections of health-data processing, running until end-2026, in the context of a data leak affecting up to 1.3 million customers of an online sales platform (over 50 complaints and 2,000 controller notifications received by 17 September 2026). observed
  23. Probable https://ceo.com.pl/en/polish-data-protection-authority-fine-uodo-cooperation-2026/ — UODO fined a Kraków-based entrepreneur PLN 31,507 on 30 September 2026 for failing to provide information UODO needed to investigate two websites, including the controller's identity and possible transfers of data outside Poland and the EU/EEA.
  24. Probable UODO — Poland - UODO enforcement against RKW association — PLN 10,082 fine for infringing UODO's Art. 58(1)(a)/(e) information-and-access powers by failing to respond to requests concerning an election-related app observed
  25. Probable CEO.com.pl — Poland - UODO enforcement against Kraków entrepreneur — PLN 31,507 fine (case DKE.561.7.2026) for failing to provide information requested in an investigation into two websites; not final observed
  26. Probable Poland Insight — Law firm partners (unnamed) — NSA dismissed a cassation appeal on 2026-10-06, leaving in force a PLN 45,697 fine against two partners and a former partner, jointly and severally liable, for processing prospective clients' personal data including health data without demonstrating consent under GDPR Art 7(1). observed
  27. Probable https://ceo.com.pl/en/polish-data-protection-authority-fine-uodo-cooperation-2026/ — Kraków entrepreneur (unnamed) — UODO President imposed a PLN 31,507 fine (decision DKE.561.7.2026, not final as of report date) for failing to provide information UODO required under Art 58(1) investigatory powers.
  28. Probable OneTrust DataGuidance — UODO — PLN 11,000,000+ (DPD Polska) observed
  29. Probable OneTrust DataGuidance — UODO — PLN 11,000,000+ (DPD Polska; two fines: PLN 6.251m Art.28(3) GDPR; PLN 5.209m Art.24(2),29,32(4) GDPR) 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), 78 claim(s) (78 category placement(s)), 42 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 24 Oct 2026: upheld (3 confirmed against the cited source; 4 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 (37 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 Rightsrectification and erasure
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 & Adequacyadequacy granted
Art. 47Cross-Border & Adequacysccs and bcrs
Art. 48Cross-Border & Adequacysccs and bcrs
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. 82Enforcement & Redressprivate right of action
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties