Ready-to-run compliance workflow
A controller must notify the supervisory authority of a personal-data breach without undue delay and within 72 hours of becoming aware, unless the breach is unlikely to risk individuals' rights. The notification must state the nature, categories and rough number affected, likely consequences, and measures taken; a late filing must carry reasons for the delay.
Testing is free and does not create a Record. Unfinished live attempts are not charged.
What it does
This workflow uses the published release shown above. Later updates cannot silently change the reasoning attached to a completed Record.
Plus 12 further items when relevant.
A structured, version-bound Record containing the submitted facts, release identity, timestamp, and validation result.
Choose the experience
Collect the complete set of relevant facts in one responsive document.
Guide someone one relevant question at a time through the published logic.
Review the required controls and retain evidence of the completed check.
Published legal basis
Article 33
Inspect the publisher, full schema record, release history, and field structure before relying on this interpretation for your own circumstances.
Use this release
Cookies & storage
Essential storage keeps you signed in and secure — it's always on. With your OK we'd also use analytics to see how the product is used and improve it; analytics only runs if you allow it. See our privacy policy.