GDPR Articles 33-34, Breach Notification
Regulation (EU) 2016/679, Arts. 33-34
In force since .
A breach notification rule binding public and private bodies.
- How the hook was established
- express
- What makes it apply
- Operator establishment, Market targeting, User location, Place of effect
- Audit expectation
- on_request
- Who audits it
- Regulator
- Where the report goes
- Produced on request
What it requires
- Notify AZOP without undue delay and, where feasible, within 72 hours of becoming aware of a personal-data breach affecting a person in Croatia, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons, and notify affected individuals without undue delay where the breach is likely to result in a high risk to them.
- If you process personal data on behalf of a controller, notify the controller without undue delay after becoming aware of a personal data breach (Article 33(2)).
These lines are LexLint's reading of the law's text. Also read by: Agencija za zaštitu osobnih podataka (Croatian Personal Data Protection Agency) (guidance, recorded ).
Who enforces it
Settledness
- As of
- Guidance link
- https://azop.hr/izvjescivanje-o-povredi-osobnih-podataka/
- Guidance body
- Agencija za zaštitu osobnih podataka (Croatian Personal Data Protection Agency)
What it makes you log
Who may demand the log
Regulator
Logging duty
The controller documents every personal data breach, whether or not it is notified; the text names the facts, the effects and the remedial action but no fixed log fields.
- Kind
- Explicit
- As of
- Provision
- Regulation (EU) 2016/679, Art. 33(5)
- Trigger
- security_incident
What this law does
A controller must notify AZOP without undue delay and, where feasible, not later than 72 hours after becoming aware of a personal-data breach, and notify the affected individual without undue delay where the breach is likely to result in a high risk. The Act requires the Agency's annual report to the Croatian Parliament to state the number of controller reports of personal-data breaches received under General Data Protection Regulation (GDPR) Article 33 and the supervisory activities taken on them (Article 17).
When LexLint raises it
When your app profile says your app processes personal data.
Back to the example · Lint your app
Page updated .