INC-20261112-C810

Support ticket export sent to the wrong customer · medium · aware 2026-11-12 04:13:57 UTC

GDPR — personal data breach

Regulation (EU) 2016/679, Article 33
  • Notification to the supervisory authorityArticle 33(1)
    Running falls at a weekend
    in 47h due 2026-11-15 10:13:57 UTC

    Without undue delay and, where feasible, not later than 72 hours after becoming aware of the personal data breach, unless it is unlikely to result in a risk to the rights and freedoms of natural persons. Notified later, it carries the reasons for the delay; the information may be given in phases (Article 33(4)). Telling the people affected (Article 34) has no hour count: without undue delay where the risk to them is high. · Draft it

Record a notification for GDPR — personal data breach
The real moment it went out. The one-month final-report clock runs from this.

What was actually sent

0

Nothing recorded yet. A clock stops when you record the submission, not when you intend to make it.

Evidence

0 files

Nothing attached. Screenshots of the portal acknowledgment, the sent notification, and the technical analysis live here.

PDF, PNG, JPEG or WebP, up to 10 MB. The file itself has to be one of those — the name is not enough.
×
Live demo — signed in as the admin, sample data resets hourly.
Own it — one payment →