Required
Complete “Approx. number of affected data subjects”
Complete “Approx. number of affected data subjects”.
GDPR Art. 33(3)GDPR breach check
Complete “Approx. number of affected data subjects” — Reasons for notification after 72 hours becomes… · A notification made after 72 hours must be…
The entered facts activate 3 published rule paths. Complete “Approx. number of affected data subjects”.
Decision path4DADB6B83ESchema 2025.01.01
A personal-data breach under GDPR has been confirmedYes
Risk to individuals' rights and freedomsHigh
Available notification information is being supplied in phasesNo
Supervisory authority notifiedYes
Notified within 72 hoursNo
Action required
Calculated result Complete “Approx. number of affected data subjects”
Apply the published Article 33 interpretation to the risk assessment, notification content, phased filing, timing, authority notice, and delay record entered here. This scenario is distinct because it produces this exact combination of calculated result, active obligations, deadlines, and required evidence.
Published by ProseIDVersion 2025.01.01
Required
Complete “Authority-notification date, time, and zone”
Complete “Authority-notification date, time, and zone”.
GDPR Art. 33(1)Required
Filed after 72 hours — record and include the reasons for the delay
Filed after 72 hours — record and include the reasons for the delay.
GDPR Art. 33(1)Change the facts
A nearby path produces a different result.
Available notification information is being supplied in phasesNo → Yes
Result becomesPhased reporting is available only when the information cannot be provided at the same time; supply each available part without undue further delay.
Inspect the changed path →Published legal basis
Sources carried by this schema release.
The calculated path is bound to the cited version and sources. It is general information, not a substitute for advice on facts or law outside the schema.
Use your facts
Run the actual workflow.
This page shows one calculated path. Open the maintained workflow to answer with your own facts and, when needed, create a version-bound audit record.