Regulatory Updates for Poland
National acts, decrees, guidance and enforcement, and the EU law that applies in Poland, newest first, checked against the official sources.
Updates
5 October 2026GuidancePoland
UODO Explains When a Personal Data Breach Need Not Be Reported
Poland's UODO says a breach of data already public in the CEIDG register may not need reporting, while PESEL numbers, health and financial data usually mean a risk and a report. Every breach still needs a documented risk assessment in the breach register.
5 October 2026GuidancePoland
UKNF Tells Polish Financial Firms to Review SaaS Use and ICT Supplier Risk Under DORA
Poland’s UKNF recommends that financial market entities review their SaaS services in eight areas after attacks on software suppliers. Results should be documented and key findings go to the management body.
22 September 2026AdoptedEuropean Union
Commission Sets eID Assurance Levels for Cross-Border Health Data Under the EHDS
Implementing Regulation (EU) 2026/2099 applies from 26 March 2027. Patients and health professionals in MyHealth@EU exchanges need eID at eIDAS level substantial, rising to high from 2030 for patients and 2032 for staff. Providers must accept EUDI Wallet attributes from 2029.
21 September 2026GuidanceEuropean Union
EDPB Takes Comments Until 13 November on When GDPR Regulators Should Issue Fines
EDPBEuropean Data Protection Board Guidelines 04/2026 set a five-step method for regulators deciding whether to fine under the GDPRGeneral Data Protection Regulation. Minor infringements generally lead to no fine. Others carry a strong presumption of one. Comments close on 13 November 2026.
18 September 2026AdoptedEuropean Union
Commission Sets EHDS Dataset Metadata Rules in Implementing Regulation 2026/2098
Health data holders will have to describe EHDS datasets with HealthDCAT-AP metadata, including access rights, personal-data status and provenance. Implementing Regulation 2026/2098 was adopted on 18 September 2026 and applies from 26 March 2029.
18 September 2026AdoptedEuropean Union
Commission Sets 24-hour Incident Reporting and Compliance Checks for MyHealth@EU
Implementing Regulation (EU) 2026/2083 sets MyHealth@EU cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. requirements from 26 March 2027: compliance checks before exchange and every five years, and notice of significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. within 24 hours.
17 September 2026GuidanceEuropean Union
EDPB Adopts Final Guidelines on How the DSA and the GDPR Work Together
On 17 September 2026 the EDPB adopted the final version of its Guidelines 3/2025 on the DSA and the GDPR. They set how platforms handle age assurance, recommender systems and special-category data, and say a DPIA is likely mandatory when systemic risks are found.
11 September 2026In forceEuropean Union
CRA Reporting Duties Now Apply, and ENISA’s Single Reporting Platform Is Live
Since 11 September 2026 manufacturers must report actively exploited vulnerabilitiesA vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. Under the CRA, manufacturers must send an early warning within 24 hours of becoming aware of one in their product, through the single reporting platform. and severe incidents under the CRACyber Resilience Act. ENISAEuropean Union Agency for Cybersecurity runs the Single Reporting Platform for this. The main security requirements apply from 11 December 2027.
3 September 2026GuidanceEuropean Union
Advocate General Says EU Law Precludes Parts of Belgium’s Traffic Data Retention Law
AG Szpunar proposed on 3 September 2026 that EU law precludes several requirements in Belgium's 2022 data retention law. General retention could pass only with watertight separation of data categories. The opinion does not bind the Court, and judgment is still to come.
13 August 2026EnforcementPoland
UODO Inspects MyDr and Tells Clinics They Must Report a Processor’s Breach
After the MyDr medical records leak, Poland's UODO said clinics as controllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it. must assess and report a breach that happened at their processorA person, public authority, agency or other body that processes personal data on behalf of a controller. The processing must be governed by a contract or another binding legal act under Union or Member State law meeting GDPR Article 28(3), and the processor must follow the applicable documented-instruction requirements.. It is inspecting MyDr and has ordered more health data inspections to the end of 2026. It says the leak affects 19 million Poles.
31 July 2026GuidanceEuropean Union
ESAs Tell Financial Entities to Adjust ICT Risk Controls for Frontier AI Models
EBAEuropean Banking Authority, EIOPA and ESMA issued statement JC 2026 25 on 31 July 2026. It encourages financial entities to adjust DORADigital Operational Resilience Act ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. processes for frontier AIArtificial Intelligence models through prevention, detection and management. Its annex adds no new requirements. CTPPCritical ICT Third-Party Service Provider oversight will cover it in 2027.
27 July 2026AdoptedPoland
Poland’s Act on AI Systems Creates KRiBSI as Its AI Act Market Surveillance Authority
Poland published its Act on AI systems on 27 July 2026. It creates KRiBSI as market surveillance authority and single contact point. Enforcement chapters apply three months after publication, and UODO says KRiBSI starts work in November.
24 July 2026In forceEuropean Union
AI Omnibus Moves High-Risk AI Act Dates to December 2027 and August 2028
Regulation (EU) 2026/1744 moves AI ActArtificial Intelligence Act high-risk requirements to 2 December 2027 for Annex III and 2 August 2028 for Annex I. Legacy generative systems must meet Article 50(2) by 2 December 2026, when two new prohibitions also apply.
23 July 2026In forcePoland
Poland Gives UODO Data Governance Act Powers, with Fines Up to PLN 2 Million
Poland's Act on data management (Dz.U. 2026 poz. 548) has applied since 23 July 2026. It makes the UODO President the authority for data intermediation servicesA service that sets up commercial relationships for data sharing between an undetermined number of data subjects or data holders and data users, by technical, legal or other means. Providers must notify the competent authority and stay neutral about the data they intermediate. and data altruismThe voluntary sharing of data, based on data subjects' consent or data holders' permission, without a reward beyond cost compensation, for objectives of general interest such as healthcare, climate, mobility, official statistics or scientific research. Organisations can register as recognised data altruism organisations., with fines up to PLN 2,000,000.
22 July 2026AdoptedEuropean Union
Commission Updates EU Digital Identity Wallet Standards in Regulation 2026/1731
Implementing Regulation (EU) 2026/1731, published on 22 July 2026, amends four EU Digital Identity Wallet acts. It adds portrait warnings, limits wallets to ENISAEuropean Union Agency for Cybersecurity-listed cryptographic mechanisms and updates specifications. Some duties start on 11 August 2028.
20 July 2026AdoptedEuropean Union
Commission Sets AI Act Procedures for Proceedings Against General-Purpose AI Providers
Implementing Regulation (EU) 2026/1755 of 20 July 2026 sets how the Commission runs AI ActArtificial Intelligence Act proceedings against general-purpose AIAn AI model with significant generality that can competently perform a wide range of distinct tasks, as defined in AI Act Article 3(63). Article 3(66) separately defines a general-purpose AI system based on such a model that can serve a variety of purposes. Provider requirements depend on the model and applicable transitional provisions, including Article 111(3) for models already on the market. model providers. It can demand access to source code and model weights, order interim measures, and fine within five years.
20 July 2026GuidanceEuropean Union
Commission Guidelines Explain AI Act Transparency Duties as the 2 December Date Nears
The Commission's Article 50 guidelines explain the AI ActArtificial Intelligence Act transparency duties that have applied since 2 August 2026. They say providers of existing generative AIArtificial Intelligence systems have until 2 December 2026 for the marking duty in Article 50(2). Chatbot disclosure has no such delay.
13 July 2026EnforcementPoland
UODO Reprimands a Polish Hospital and Its Email Provider Over Unchecked Guarantees
UODO reprimanded a Sosnowiec hospital and its email provider, announced on 13 July 2026. The hospital did not verify the processorA person, public authority, agency or other body that processes personal data on behalf of a controller. The processing must be governed by a contract or another binding legal act under Union or Member State law meeting GDPR Article 28(3), and the processor must follow the applicable documented-instruction requirements.'s guarantees or its own email risk. The processorA person, public authority, agency or other body that processes personal data on behalf of a controller. The processing must be governed by a contract or another binding legal act under Union or Member State law meeting GDPR Article 28(3), and the processor must follow the applicable documented-instruction requirements. had declared ISO/IEC 27001Information Security, Cybersecurity and Privacy Protection: Information Security Management Systems: Requirements certification but ran no risk analysis.