Privacy incident log

Log

That an information incident was logged, who is handling it, and what you actually did.

No field for the people affected, and none for what was exposed

A privacy incident log that lists affected individuals and the categories of data involved is a second copy of the breach, kept in a browser, by the organization that just had one. So there is no field for either, and none will be added. The row carries a short label, dates, who is handling it internally, and what was done — which is the administration, and the administration is what goes missing.

CompliMaint makes no breach determination

Whether something is a breach, whether it is notifiable, to whom, and by when are legal questions with jurisdiction-specific answers and real deadlines attached to them. This product answers none of them, states no reporting period, assigns no severity and notifies nobody. The date on a row is one you set to come back to it.

Related governance tools: Information asset register · Incident report · Corrective action tracker

A dated record that an incident was logged and what you did. No affected individuals, no data categories, no exposed data, no breach or notification-duty determination, no severity rating and no deadline. Everything runs on your device.

Questions people ask

Should I list who was affected?
No, and there is no field for it. Keep the people affected, the data involved and anything exposed out of this log entirely — it is not built to hold them and must never become a second copy of the incident.
Does it tell me whether I have to notify anybody?
No. CompliMaint makes no breach determination and no notification-duty determination, and states no reporting deadline. That is a question for somebody who knows your obligations.
Does it rate severity?
No. It assigns no severity and applies no classification. A rating from a free tool would be read as an assessment of something it has never seen.
Does anything get sent when I log an incident?
No. Nothing is sent from this product, to anybody, ever. The log stays in this browser.