AWRA OpsHub Search
AWRA Field 05 screens 7 min read

Seventy-Two Hours After a Breach

Kenya’s Data Protection Act gives a controller 72 hours from becoming aware of a breach to tell the Data Commissioner, and the hours do not stop for a weekend. A breach register that counts the clock for you, reminds the right people before it runs out, and refuses to let a late notification go on record without its reasons.

Written by
Washingtone AuraFounder, AWRA OpsHub
Issued
Build
Initial

On a Friday evening a loans officer at a Nakuru SACCO leaves a laptop on a matatu. On it is a spreadsheet of 1,900 members: names, ID numbers, phone numbers and loan balances. Nobody at head office hears about it until Monday at 08:40, when the officer reports it. By lunchtime the question in the room is not what happened but when the clock started, and how long is left on it.

Section 43 of the Data Protection Act answers half of that. Where there is a real risk of harm to the people whose data it is, the data controller notifies the Data Commissioner without delay, and within 72 hours of becoming aware of the breach. A notification made after 72 hours has to carry the reasons for the delay. The other half of the answer is practical: someone has to write down the moment of awareness, count forward from it, and make sure the people who can act are told before the time runs out, not after.

The clock starts at awareness

In AWRA a breach is an entry in the personal-data breach register, with its own reference, such as DB-2026-0004. Two times sit at the top of it. When it happened is optional, because you often do not know. When you became aware is required, cannot be set in the future, and cannot be earlier than the time it happened. Everything else on the record counts from that second time.

The deadlines themselves are never typed in and never stored. They are worked out each time the record is opened, from the awareness time and the rules for the country the breach falls under. That matters on day two, when somebody finds the officer actually phoned a branch manager on Saturday morning. Correct the awareness time, and every clock on the record moves with it. Nobody has to remember to recalculate anything. Awareness is a fact about people rather than about records, and Canada’s product-safety rule turns on the same date, which we looked at in two days from when you knew.

The SACCO’s clocks, counted from Monday 08:40

Became aware Mon 08:40
First reminder Wed 08:40
Second reminder Thu 02:40
Notify the regulator by Thu 08:40
Notify the members No fixed hour
Time to decide and file 72 hours

Had the officer reported it on Friday night, the deadline would have fallen on Monday night, and most of the window would have been spent with the office closed.

Which clocks you get depends on whose data it is

A breach record says whether you hold the data as controller, because it is your own members’ or staff’s data, or as processor, because you handle it for another organization. The two roles owe different people different things, so the record draws different clocks.

You are Who you tell Kenya’s deadline
Controller The Data Commissioner (ODPC) 72 hours from awareness, reasons required if later
Controller The people affected In writing, within a reasonably practical period
Processor The controller you work for 48 hours, where reasonably practicable

Where the law sets no hour count, as with telling the members, the record shows the rule in words and draws no countdown. Pretending “reasonably practical” means a particular number of hours would be giving you legal advice. The same restraint applies across borders. Kenya, Nigeria and South Africa have their rules configured, each checked against the statute or the regulator’s own guidance. A breach under any other country’s law shows no statutory clock configured and asks you to check the law that applies, rather than quietly borrowing Kenya’s 72 hours.

A deadline nobody verified is worse than none, because it reads as advice.

Reminders that go to someone

Every fifteen minutes the register checks each open clock with a fixed hour count. When one has 24 hours left, then 6 hours left, and again once it has passed with nothing recorded, the breach’s owner and everyone allowed to manage breaches get a reminder in the in-app bell. Each one says which breach, which notification and the exact time it is due, and links straight to the record.

Two details make the reminders trustworthy rather than noisy. A stage counts as sent only once at least one person was actually told: if the owner has left and nobody holds the permission, the reminder stays pending and is tried again on the next sweep, rather than being marked done for an empty room. And a breach entered late, already inside the last six hours, gets the six-hour reminder alone, not three alerts at once. Every reminder sent is also written to the breach’s timeline. The reminders sit under Personal Data Breach Notification Deadline in notification settings.

Late is recorded, not hidden

When you record the notification to the regulator, you give the time it was sent, how it was sent and the reference you received. Under Kenyan law, if that time falls after the 72 hours, the record will not save until you write the reasons for the delay, because the Act requires them to go with the notification. The clock then reads met late rather than met, permanently. The register cannot make a late notification on time. What it can do is make sure the reasons were written while the people who know them are still in the room.

Deciding that notification is not needed is recorded the same way. Choose not required, for the regulator or for the people affected, and a reason is mandatory. Six months later, when an auditor or the ODPC asks why the members were never written to, the answer is on the record in the words of the person who decided, with the date beside it.

It records the filing. You make it.

The register never sends anything to a regulator. The ODPC takes breach reports through its own e-services portal, and that is where your notification goes. The record holds what you sent and when, so that it can be handed over later. Its timeline is append-only: every change, decision, note and reminder is a line that nothing edits or deletes afterwards. Each record downloads as a PDF, and the whole register downloads as a spreadsheet with each breach’s regulator clock. For who owes what under the Act in the first place, see controller or processor.

Five questions to settle before the next breach

Who writes down the moment we became aware?

The common answer

Whoever is handling it.

What it costs you

Then the 72 hours are counted from a time nobody can reconstruct.

Who is told when 24 hours are left?

The common answer

The person handling it remembers.

What it costs you

A Thursday deadline found on Friday.

Are we controller or processor for this data?

The common answer

Not sure.

What it costs you

A processor has 48 hours to tell its client, who then has 72 of its own.

Where is the reason we decided not to tell the people affected?

The common answer

In an email thread.

What it costs you

The evidence leaves with whoever wrote it.

If we notify late, where are the reasons?

The common answer

We will explain if asked.

What it costs you

The Act wants them with the notification, not afterwards.

The short version

Record the moment you became aware before anything else, and let the clock be counted from it rather than from memory. Make sure more than one person is told at 24 hours and at 6 hours. Write down every decision not to notify, and every reason for a late one, at the time. Then file through the ODPC’s own portal and record that you did.

More we can add

From the record to the filing

The register, the clocks, the reminders and the evidence trail are in place. These are the extensions organizations ask for next, and we can add them to your workspace.

A filing-ready layout

The breach record laid out in the order the ODPC’s breach form asks for it, plus a draft written notice to the people affected built from the same fields.

Clocks for more countries

Statutory rules for Uganda, Tanzania and Rwanda, each checked against the statute before it appears as a countdown.

A breach opened from an incident

A security incident that turns out to involve personal data starting its breach record directly, carrying the times and details across.

See AWRA security operations

Incidents, anomaly rules and the security controls around your workspace, alongside the breach register.

Explore security operations

Frequently asked questions

When does the 72-hour clock start under Kenya’s Data Protection Act?

When the data controller becomes aware of the breach, not when the breach happened. The hours are elapsed hours, so a weekend inside the window counts in full. In AWRA the awareness time is required on every breach record and every deadline is counted from it.

Does AWRA file the breach notification with the ODPC for us?

No. The register records and reminds. You notify the Data Commissioner through the ODPC’s own e-services portal, then record the time, method and reference on the breach so the evidence stays together.

Who gets the deadline reminders?

The breach’s owner and everyone allowed to manage breaches, in the in-app bell, when 24 hours are left, when 6 hours are left and once the deadline has passed with nothing recorded.

What if we notify the regulator after 72 hours?

For a Kenyan breach the record will not save the late notification until the reasons for the delay are written down, because the Act requires them to accompany it. The clock then shows the notification as met late.

We handle data for a client. Which deadline applies to us?

Mark the breach as processor and name the controller. Kenya’s rule is that a processor tells the controller without delay and, where reasonably practicable, within 48 hours. The record draws that clock instead of the regulator’s.

Share this article

LinkedIn X WhatsApp

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center