Kenya Data Protection Act
Check local registration, put handling rules in place and time breach handoffs between processors and controllers.
Nigeria Data Protection Act 2023 and General Application and Implementation Directive (GAID)
Decide which Nigerian registration and audit duties apply, then track how sensitive data is handled and reported.
Controllers and processors within the act’s territorial criteria, with additional duties for designated controllers and processors of major importance.
A documented privacy program, a registration and filing decision, and an operational breach reporting procedure.
Determine classification and filing duties using current NDPC instruments before entering recurring deadlines on your calendar.
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Fill this in with your sponsor and send it to the people who own the work.
Nigeria Data Protection Act kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Classify obligations and set ownership · Privacy counsel + DPO [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
A health platform works out whether its processing meets the Commission’s major-importance criteria. The DPO keeps the classification decision, confirms the filing calendar, and traces each safeguard back to its real system owner.
Check U.S. health-data duties separately if the platform also serves covered U.S. clients.
Section 40 sets this clock where the breach is likely to create a risk to rights and freedoms. Check duties owed to affected people separately.
Official reference (opens in a new tab)Checklist, instructions and 11 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Classify obligations and set ownership | Privacy counsel + DPO | At initiation and when scale or activities change | Set a start date | Applicability matrix; Appointment decision; Audit calendar | Open |
| Document lawful processing and rights | Privacy operations + data owners | Before launch and on request | Set a start date | Processing inventory; Privacy notices; Rights workflow | Open |
| Assess risks and supplier controls | Legal + security | Before high-risk processing or overseas disclosure | Set a start date | Impact assessments; Transfer assessments; Supplier terms | Open |
| Prepare breach notice and keep receipts | Security + controller | At incident | Set a start date | Breach assessment; Notification record | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Map Nigeria activities and processing roles. Check GAID classification, registration, DPO and filing requirements and assign an accountable officer.
Fictional details. Use the same fields with evidence from your work.
A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.
Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.
Fictional details. Use the same fields with evidence from your work.
The signer can explain the basis for each statement and the record reflects the required scope and period.
Give the executed document to the relevant recipient under the engagement or regulation. Use the worksheet to organize review.
Fictional details. Use the same fields with evidence from your work.
Every external deadline links to a real source. Planning targets are visibly marked.
Add approved dates to the team calendar and share them with the people scheduled to deliver or review.
Record purposes, bases and sensitive data handling. Publish notices and test access, correction and other rights across processors.
Fictional details. Use the same fields with evidence from your work.
The entry names a real purpose, matches actual product behavior and links to the legal and vendor decisions behind it.
Use the reviewed register when drafting notices, evaluating changes and deciding which processing needs an impact or transfer assessment.
Fictional details. Use the same fields with evidence from your work.
A reader can understand the intended use and reach the correct rights channel. The notice matches what the service actually does.
Send approved text to the publishing owner and give support teams the version and effective date.
Fictional details. Use the same fields with evidence from your work.
A new case worker can follow the procedure and deliver a test response without inventing missing steps or timings.
Train intake, operational and backup staff. Make the intake instructions and current contact list easy to find.
Assess processing risks, document safeguards and transfer conditions, and obtain assurance about how suppliers follow instructions and report incidents.
Fictional details. Use the same fields with evidence from your work.
The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.
Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.
Fictional details. Use the same fields with evidence from your work.
The register shows actual access paths, the basis for each transfer and a clear release decision.
Share the decision with supplier and access owners so they can implement the conditions before data is available.
Fictional details. Use the same fields with evidence from your work.
The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.
Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.
Document the awareness event and expected risk to rights and freedoms. Determine when notice to the Commission and direct communication are needed.
Fictional details. Use the same fields with evidence from your work.
Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.
Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.
Fictional details. Use the same fields with evidence from your work.
Every open item has a next action and closed items have a verifiable record of closure or delivery.
Use the log at case reviews and provide a restricted copy only where the engagement requires it.