Data protection

Data breach risk check

Four questions about your incident, a first view of the fine risk and the duties that are now running, above all the 72-hour deadline for notifying the supervisory authority.

Your answers never leave your browser. We do not transmit or store them, and no session recording runs on this page.

Four questions

What happened?

0 of 4 answered
01 What kind of incident is it?
02 How many people are likely to be affected?
03 What kind of data is affected?
04 Have you notified the supervisory authority?
Assessment
Not yet complete Answer the four questions. The assessment appears once all are answered and is calculated on your device.

For orientation only, not legal advice. Whether a fine is imposed, and how high, is decided by the supervisory authority case by case.

The 72-hour rule

The deadline is short, and it often runs before all the facts are known.

01

When it starts

When you, as controller, become aware of the breach. A processor must in turn inform you without undue delay (Art. 33 (2)).

02

How it is counted

In hours, not working days. Weekends and public holidays do not stop the clock (Art. 3 (3) of Regulation (EEC, Euratom) No 1182/71 on time limits).

03

If not everything is known yet

Notify on time anyway. You may provide missing information in phases without undue further delay (Art. 33 (4)).

04

If the deadline has passed

Notify immediately and give reasons for the delay (Art. 33 (1) sentence 2). A late notification is better than none.

Rather look at it together?

In an initial consultation we assess your incident, check the notification duties and help with the report to the supervisory authority. At short notice too, if the clock is running.

Request a quote

This check gives a first orientation and is not legal advice. The fine ranges are rough experience values, not a forecast for your case.