Skip to content
Incident response

When something goes wrong, you have the facts and the clock

A regulated organisation reports to a deadline. Checkpoint keeps the record, shows the deadlines and produces the evidence, so you are not drafting under pressure.

Your register

Log an incident with the time someone first suspected it. Every change goes into a history nobody edits, and your notes are stored encrypted.

Log a tabletop exercise too. It shows an auditor the plan was practised, and it never counts as an incident.

The deadlines, worked out for you

Each incident shows the windows which normally apply: 24 hours for a preliminary notice to the Bank of Namibia, 72 hours for a personal data breach notice to the data protection authority, and one month for the impact assessment.

You record each notification when you make it. The page shows what is done, what is due soon and what is overdue.

You are the controller of your visitor data, so you decide whether and when to notify. Checkpoint does not notify an authority for you.

If the problem is on our side

When an incident touches your data, we tell your administrators without undue delay. The notice states what happened, which data and roughly how many people, the likely consequences and what we are doing, so you meet your own deadline.

The notice is sent by a person on our team after a decision, and it is recorded in your audit trail.

The evidence

Your evidence pack includes the incident register with its clocks and the date of your last tabletop exercise. Every entry in the audit trail is linked to the one before it, so a changed or removed entry shows.

Report a problem to us

Send security reports to team@buffranalytics.com. The rules for testing and our fix times are on the security page.

We use privacy-preserving product analytics only after you accept. No visitor names or phone numbers are sent. Essential cookies do not require consent.