Enforcing jurisdiction
Poland · Geography does not establish applicable law.
Confirmed applicable legislation
Privacy topics

mBank – €932,230 Fine (Poland, 2024)

€932,230Urząd Ochrony Danych Osobowych20 August 2024Poland
final
Fine

Privacy enforcement record

This record is classified outside cookie consent. Subject classification does not confirm an applicable law. It is not included in cookie statistics or the Risk Calculator.

mBank was fined EUR 932,230 for not notifying customers about a data breach involving their personal information sent to another bank. This ruling stresses the importance of transparency in data breaches.

What happened

mBank failed to notify customers after their personal data was mistakenly sent to another bank.

Who was affected

Clients of mBank whose personal data was included in the documents were affected by the breach.

What the authority found

The Polish DPA ruled that mBank violated GDPR by not assessing the risks and failing to notify affected customers.

Why this matters

This decision highlights the need for financial institutions to have clear procedures for handling data breaches. Companies must prioritize customer notification and risk assessment to comply with data protection laws.

Recorded legal citations
Automatically processed
Art. 34 GDPR
Art. 4(12) GDPR
View original scraped data
Art. 4(12) GDPR
Art. 34 GDPR

Original imported citations before automated processing; the processing history does not establish independent verification.

National Law Articles
AI-identified
171 para 5 of the Banking law (prawo bankowe)`

Source checks

Linked-source text retrieved.

Review needed — 5 March 2026.

Processing notes: national law identified, amount discrepancy.

Retrieved text may be a secondary summary or an announcement. These automated statuses do not establish that the original decision was read or that the record received an independent legal review. How we check sources

Full Legal Summary
Detailed

mBank (the controller) entrusted a third-party to perform processing activities (a processor). The processor’s employee, erroneously, sent the controller’s clients documents to another bank. The documents contained the following personal data: name, surname, national identification number (PESEL), financial data (clients’ assets), account number, ID number. According to the controller, the other bank sent back all the documents. The documents’ integrity was not affected, yet it was probable that the other bank’s employees read the documents. As the documents confidentiality was violated, a data breach under Article 4(12) GDPR occurred. Nevertheless, the controller was of the opinion that the risk posed by the breach was minimised by the statutory bank secrecy. Because of that, the controller didn't see a reason to notify the data subjects in accordance with Article 34 GDPR. However, the controller notified the Polish DPA (UODO) about the data breach. During the following proceedings, the DPA requested the controller to notify the data subjects involved about the breach under Article 34 GDPR. The controller asked the DPA to reconsider their request. The controller emphasised the documents were shared with the other bank, the controller’s business partner, which should be treated as “a trusted party”. That was because the other bank, together with the controller, were part of banking sector in Poland. As such, both the controller and the other bank pursue highly regulated business activity, in particular in the field of data protection and cybersecurity. For this reason, the breach didn’t pose “a significant risk of negative consequences for the data subjects”. In addition the other bank’s employees made a statement confirming they didn’t possess the documents’ copies and were unable the identity of the data subjects. Moreover, the other bank’s employees were aware of duties associated with the bank secrecy, as well the liability for its breach under Article 171 para 5 of [https://isap.sejm.gov.pl/isap.nsf/download.xsp/WDU19971400939/U/D19970939Lj.pdf the Banking law] (Prawo bankowe). The DPA found the controller violated Article 34 GDPR. The controller correctly identified the incident as the data breach under Article 4(12) GDPR. However, the controller failed to assess the risk of the data breach. Due to the character of data disclosed, the breach posed a high risk to rights and freedoms of data subjects, inter alia, an identity theft or banking frauds. Although the data was shared erroneously with the other bank, the status of the bank didn’t automatically mean it was “a trusted party”. The bank secrecy and the statements of the other bank’s employees were not a sufficient safeguard against a future misuse of the data. The DPA stressed there was no formal relationship between the controller and the other bank, nor internal procedures implemented to handle incidents of that kind. The controller also didn’t prove the knowledge of the other bank’s data protection safeguards in place, especially implemented policies. Hence, the controller had no authority to enforce the statements in practice, and consequently no safeguards to minimise the risk posed by the data breach. Furthermore, the controller failed to reassess the risk of the data breach, as requested by the DPA. For the DPA the conduct of that kind meant the controller disregarded their duties, especially the duty to protect the data subjects. The DPA fined the controller PLN 4,053,173 (€928,498.06) and ordered to notify the data subjects involved about the data breach and its consequences, in line with Article 34 GDPR.

Related Enforcement Actions (0)

No other enforcement actions found for mBank in PL

This is the only recorded action for this entity in this jurisdiction.

Details

Fine Date

20 August 2024

Authority

Urząd Ochrony Danych Osobowych

Fine Amount

€932,230

4,053,173 PLN

GDPRhub ID

gdprhub-8277

About this data

Data: GDPRhub (noyb.eu)
Licensed under CC BY-NC-SA 4.0
Automatically normalized and classified

Cite as: Cookie Fines. mBank - Poland (2024). Retrieved from cookiefines.eu

Report Inaccuracy

Last updated: