City of Antwerp
bd_c279b26fb2346a06 · schema v1 · pii pii-v1
Full breach record for City of Antwerp →Regulator's decision — not a breach notification
This record is a regulator's decision, not the organisation's own breach notice. Breach-notification fields (discovery date, notification clock) are structurally absent — what this source establishes is the outcome and the provisions the decision cites.
The APD/GBA (Belgium) issued a investigation regarding City of Antwerp. Outcome: Violation Found. GDPR articles: Article 5(1)(f) GDPR, Article 5(2) GDPR, Article 24(1) GDPR, Article 25(1) GDPR, Article 32(1) GDPR, Article 32(2) GDPR, Article 35(1) GDPR, Article 35(2) GDPR, Article 35(3) GDPR, Article 35(7) GDPR, Article 38(1) GDPR, Article 39(1) GDPR.
P pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Dec 13, 2023
Filed
—
No linked breach filing · watching
Compliance clocks stay unassessable until a breach filing is linked. This record is the regulator's action, not a breach notice. Dashed segments fill in automatically when corroboration arrives.
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
If an SEC 8-K, state-AG notice or victim statement lands, DisclosureLens merges it into an incident and links it here.
Source ceiling
- data categories
- cross-border scope
- outcome + articles (decisions)
- discovery date
- affected count
- notification clock
See the underlying breach notice, if filed.