DPA case 154/2025 – Complaint Upheld (Belgium, 2025)

Complaint Upheld
Autorité de Protection des Données29 September 2025Belgium
final
Complaint Upheld

General GDPR enforcement action

This case relates to broader data protection obligations, not specifically to cookie or consent banner compliance. It is not included in cookie statistics or the Risk Calculator.

A company mistakenly revealed the email addresses of 450 individuals in a mass email, leading to a complaint about a data breach. The Data Protection Authority warned the company for not having sufficient safeguards to prevent this error. This incident underscores the importance of following proper procedures when handling personal data.

What happened

A company accidentally exposed the email addresses of many individuals in a satisfaction survey email.

Who was affected

Approximately 450 individuals whose email addresses were visible to each other.

What the authority found

The Data Protection Authority found the company violated GDPR by not having adequate technical and organizational measures in place.

Why this matters

This case serves as a warning for companies to ensure they have strong data protection practices to avoid breaches.

GDPR Articles Cited
Automatically processed
Art. 25 GDPR
Art. 32 GDPR
Art. 5(1)(f) GDPR
View original scraped data
Art. 5(1)(f) GDPR
Art. 25(GDPR)
Art. 32(GDPR)

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

Source checks

Secondary-source text retrieved.

Automated check recorded — 18 October 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

Full Legal Summary
Detailed

In February 2025, the data subject received an email from the controller regarding a satisfaction survey. The data subject discovered that the e-mail addresses of approximately 450 individuals and companies, as well as his own e-mail address, were visible in the "cc" field of the e-mail. The controller performed a risk analysis and concluded that a notification to the DPA was not required but informed the affected data subjects by email. The data subject then lodged a complaint with the DPA complaining about this data breach. The controller claimed that even though it had an appropriate program for sending such emails and had established procedures for its employees to follow but the e-mail giving rise to the complaint was sent without regard to internally established procedures. According to the controller, this incident was the result of an individual error by an employee who did not follow internal procedures. The DPA held that the fact that such a personal data breach occurred implies that the technical and organisational measures that the controller had in place may have been insufficient to avoid such a breach. Nevertheless, it found that this breach did not meet the criteria of high general or personal impact to the affected data subjects. It issued a warning to the controller for the violation of Article 5(1)(f), Article 25 GDPR and Article 32 GDPR. The DPA issued a prima facie decision according to a procedure prior to the decision on the merits, in order to inform the controller that it may have committed a breach of the provisions of the GDPR and to give it the opportunity to comply with the aforementioned provisions.

Outcome

Complaint Upheld

A data subject complaint that was upheld by the DPA.

Related Enforcement Actions (0)

No other enforcement actions found for DPA case 154/2025 in BE

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

Details

Decision Date

29 September 2025

Authority

Autorité de Protection des Données

GDPRhub ID

gdprhub-9527

About this data

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

Cite as: Cookie Fines. DPA case 154/2025 - Belgium (2025). Retrieved from cookiefines.eu

Report Inaccuracy

Last updated: