Blue Projects
bd_47a3204f63980039 · schema v1 · pii pii-v1
Full breach record for Blue Projects →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 ANSPDCP (Romania) issued a investigation regarding Blue Projects SRL. A fine of RON 12,734 was imposed. Outcome: Violation Found. GDPR articles: Article 32(1)(b) GDPR, Article 32(1)(d) GDPR, Article 32(2) GDPR.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Apr 3, 2026
Filed
—
Corroborated · see linked filings
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.
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Siteqilinbd_db8dd23c1769e70d2025-11-25 · +129dCandidate
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.
Source ceiling
- data categories
- cross-border scope
- outcome + articles (decisions)
- discovery date
- affected count
- notification clock
See the underlying breach notice, if filed.