X (Data Subject) – €1,000 Fine (Belgium, 2026)

€1,000Autorité de Protection des Données28 April 2026Belgium
final
Fine

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 Belgian NGO was fined for not responding to a person's request to erase their personal data. The organization claimed it had not received the request properly but was still held accountable. This case serves as a reminder for organizations to have clear processes for handling data requests.

What happened

A Belgian NGO failed to respond to a person's request to erase their personal data.

Who was affected

A person who requested the erasure of their personal data from the NGO.

What the authority found

The authority decided to impose a €1,000 fine on the NGO for not addressing the erasure request in a timely manner.

Why this matters

This case highlights the importance of having effective procedures for managing data requests. Organizations should ensure they are responsive to such requests to avoid penalties.

GDPR Articles Cited

AI-verified

Art. 17(GDPR)
Art. 31(GDPR)
Art. 56(GDPR)
Art. 83(GDPR)
Art. 58(2)(i) GDPR
View original scraped data
Art. 17(GDPR)
Art. 31(GDPR)
Art. 56(GDPR)
Art. 58(2)(i) GDPR
Art. 83(GDPR)

Original data from scraper before AI verification against source document.

National Law Articles

AI-identified

Art.100 LCA

Entities Involved

X (Data Subject)
Foundation Y (Data Controller)
Source verified 7 May 2026
articles corrected
Full Legal Summary
Detailed

On 28 August 2022, a data subject lodged a complaint with the French DPA against an NGO (the controller), concerning an alleged failure to respond to an erasure request. On 15 March 2023, the French DPA initiated a procedure to identify the lead supervisory authority, in accordance with Article 56 GDPR. The Belgian DPA declared itself the lead supervisory authority. On 24 April 2023, both parties were informed of the deadlines for submitting written submissions. No submissions were filed by either party. On 7 July 2025, the DPA scheduled a hearing for 30 October 2025, but neither party attended. On 7 November 2025, the controller requested a copy of the case file, which was sent on 14 November 2025. On the same day, the controller informed the DPA that it had erased the data subject’s personal data and provided proof. On 27 January 2026, the DPA informed the controller of its intention to impose an administrative fine against it. On 11 February 2026, the controller responded that it had not effectively received the registered letters or postal notices, as they had arrived during holiday or absence periods. It also claimed that it had not become aware of the erasure request earlier because the data subject had not used the official channel. The controller further stated that it had acted immediately after becoming aware of the case and argued that even a €1,000 fine would constitute a significant burden for a non-profit organisation with no employees. On 18 February 2026, the DPA asked the controller to submit its 2025 financial documents. By 23 March 2026, the DPA had not received a response. * Resolution of the underlying erasure complaint: The DPA noted that, on 14 November 2025, the controller had erased the data subject’s personal data and therefore considered the erasure-related matter resolved. * Violation of Article 31 GDPR and subsequent administrative fine calculation: However, the DPA found a violation of Article 31 GDPR. The controller had failed to a

Related Enforcement Actions (0)

No other enforcement actions found for X (Data Subject) in BE

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

Details

Fine Date

28 April 2026

Authority

Autorité de Protection des Données

Fine Amount

€1,000

GDPRhub ID

gdprhub-9977

About this data

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

Cite as: Cookie Fines. X (Data Subject) - Belgium (2026). Retrieved from cookiefines.eu

Report Inaccuracy

Last updated: