- Enforcing jurisdiction
- Poland · Geography does not establish applicable law.
- Confirmed applicable legislation
- Privacy topics
Toyota Bank Poland S.A. – €18,000 Fine (Poland, 2024)
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.
Toyota Bank Poland was fined for failing to notify authorities about a data breach in a timely manner. An employee mistakenly sent personal data to the wrong client, and the bank's late notification was deemed a violation. This case highlights the importance of prompt reporting in data breaches.
What happened
Toyota Bank failed to notify the Data Protection Authority about a data breach involving personal data sent to the wrong client.
Who was affected
A customer whose personal data was mistakenly sent to another client was affected.
What the authority found
The Data Protection Authority found Toyota Bank violated GDPR by not reporting the data breach within the required timeframe.
Why this matters
This case emphasizes the need for companies to act quickly in reporting data breaches to protect customer information and comply with legal obligations.
View original scraped data
Original imported citations before automated processing; the processing history does not establish independent verification.
Source checks
Linked-source text retrieved.
Automated check recorded — 13 March 2026.
No issues were reported by that automated check.
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
Toyota Bank Poland S.A. (controller) is a bank established under Polish law. On 31 March 2021 an employee of the controller, by mistake, sent a letter with personal data of the data subject to another client. The letter contained personal data from the loan agreement concluded between the data subject and the controller, specifically: name, surname, bank account number, address, national ID number (PESEL), ID number. The (incorrect) addressee picked-up and opened the letter. Eventually, the controller took the letter back by sending a courier. The controller registered the incident within the internal register and performed a risk assessment. During the risk assessment, the controller took into account European Union Agency for Cybersecurity (ENISA) data breach guideline https://www.enisa.europa.eu/publications/dbn-severity ENISA Recommendations for a methodology of the assessment of severity of personal data breaches. According to the controller, the breach affected only one person, the letter was swiftly retrieved and the (incorrect) addressee was the controller’s client and helped to solve the problem. Because of that, the controller assigned the breach a low-risk level. Hence, the controller did not notify the DPA. Nevertheless, the controller decided to inform the data subject about the breach by sending a letter. The data subject filed a complaint with the DPA, claiming the controller unlawfully disclosed their personal data. During the complaint proceedings, on 7 September 2022, the controller notified the DPA about the breach. The notification was done almost 18 months after the breach. The controller explained the late notification with the minor risk assigned to the breach. As a consequence of late data breach notification, the DPA initiated ex officio proceedings regarding the violation of Article 33(1) GDPR. According to DPA, the controller failed to adequately assess the risk of the data breach. The DPA emphasised that the data subject interests should be the main reference when conducting a data breach risk assessment. Disclosed personal data contained the national ID number (PESEL) and other personal data. As such, it might be used for many unauthorised purposes, especially identity theft or fraud, and cause material or non-material damage to data subject. The DPA based it argumentation on [https://www.edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-92022-personal-data-breach-notification-under_en EDPB Guidelines 9/2022] and [https://www.edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-012021-examples-regarding-personal-data-breach_en EDPB Guidelines 01/2021] and jurisprudence of Polish administrative and regional court on cases where the disclosure of a national ID number (PESEL) was involved. Also, the (incorrect) addressee did not qualify as a trusted party, since the controller was unable to anticipate the addressee’s further actions with disclosed personal data. Consequently, the data breach was more serious, and posed a higher risk, compared to the risk identified by the controller. Because of that, the controller was obliged to notify the DPA, not only the data subject. In conclusion, the DPA found a violation of Article 33(1) GDPR and imposed a fine of Є18,000 (PLN 78,575.40).
Related Enforcement Actions (0)
No other enforcement actions found for Toyota Bank Poland S.A. in PL
This is the only recorded action for this entity in this jurisdiction.
Details
Fine Date
12 March 2024
Authority
Urząd Ochrony Danych Osobowych
Fine Amount
€18,000
GDPRhub ID
gdprhub-8099About this data
Cite as: Cookie Fines. Toyota Bank Poland S.A. - Poland (2024). Retrieved from cookiefines.eu
Last updated: