72 hours go fast
at 3 a.m.

Alertify runs the GDPR, NIS2, DORA, CRA and AI Act reporting clocks in your Slack or Teams incident channel, and warns the channel before a window closes.

Watch one incident run

A simulated incident with invented names and times.

inc-2291-payments-api Simulated

Time since the team became aware 20 h 01 min

Each regime starts its clock at a different moment.

One incident can open several clocks at once. Alertify keeps them apart, so that nobody in the channel must do the arithmetic at night.

Regime	The clock starts when	4 h	24 h	72 h	Days	1 month
GDPR Art. 33	You are aware of a personal data breach			Notify the authority
NIS2 Art. 23	You are aware of a significant incident		Early warning	Incident notification		Final report
DORA Art. 19 and RTS	You classify the incident as major	Initial notification	Initial notification at the latest	Intermediate report		Final report
CRA Art. 14	You are aware of an exploited vulnerability or a severe incident		Early warning	Notification	Final report, 14 days after a fix	Final report, severe incident
AI Act Art. 73	You are aware of a serious incident				2, 10 or 15 days, by severity

Regime

The clock starts when

4 h

24 h

72 h

Days

1 month

GDPR Art. 33

You are aware of a personal data breach

Notify the authority

NIS2 Art. 23

You are aware of a significant incident

Early warning

Incident notification

Final report

DORA Art. 19 and RTS

You classify the incident as major

Initial notification

Initial notification at the latest

Intermediate report

Final report

CRA Art. 14

You are aware of an exploited vulnerability or a severe incident

Early warning

Notification

Final report, 14 days after a fix

Final report, severe incident

AI Act Art. 73

You are aware of a serious incident

2, 10 or 15 days, by severity

This table is a draft until our legal check is complete. Window lengths come from each regulation and its technical standards. A later report counts from the report before it. National law and sector guidance can add to them. The start moment is a legal decision, so a named person in your channel confirms it and Alertify does not decide it.

Four things it does in the channel

/alertify start: Asks five short questions and proposes the regimes that apply. A named person confirms each start moment before a clock runs.
Warnings: One message in the channel at 50%, 75% and 90% of each window. At 90% the owner also gets a direct message.
@Alertify status: Anyone in the channel can ask. The answer gives the open clocks, the owner of each one, and the time that remains.
/alertify export: A timestamped record of who confirmed what, and when each report was filed. For your file, and for the regulator if they ask.

Alertify keeps the time and nothing about your incident.

A bot in the incident channel must earn its place there, so Alertify is designed to store as little as possible.

It keeps

The start moment of each clock
The regime and the channel
Who confirmed, and when
When each report was filed

It does not keep

The messages in your channel
What happened, or to whom
Personal data from the breach
Files, logs or screenshots

Do you handle incidents for clients? DPO firms, MSSPs and incident-response lawyers get their own early access.

See the partner page