Start hereClassify obligations and set ownership
~91 days leftOpen step
Guide library
Regulation Africa

Nigeria Data Protection Act

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.

Who it applies to

Controllers and processors within the act’s territorial criteria, with additional duties for designated controllers and processors of major importance.

What you’ll produce

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.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What applies to each entity, product and activity?
Have Legal or Regulatory confirm scope and applicable deadlines for each entity, activity and jurisdiction. Assign owners for incident reporting, filings and lifecycle changes where required.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the 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.

What to review each week

Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.

Kickoff brief to share with your team

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.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Do your operations in Nigeria or processing of people in Nigeria bring you into scope?
  • Is the entity classified as a controller or processor of major importance under current NDPC rules?

Worked scenario

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.

What to read next

  • HIPAA

    Check U.S. health-data duties separately if the platform also serves covered U.S. clients.

DATES AND TRIGGERS

Official milestones

See the deadline calendar
  • 72 hours after awareness

    Report qualifying breaches to NDPC

    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)
The whole journeyabout 91 days across 4 steps
  1. 01Classify obligations and set ownershipPrivacy counsel + DPO · ~21 days
  2. 02Document lawful processing and rightsPrivacy operations + data owners · ~28 days
  3. 03Assess risks and supplier controlsLegal + security · ~28 days
  4. 04Prepare breach notice and keep receiptsSecurity + controller · ~14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 11 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Classify obligations and set ownershipPrivacy counsel + DPOAt initiation and when scale or activities changeSet a start dateApplicability matrix; Appointment decision; Audit calendarOpen
Document lawful processing and rightsPrivacy operations + data ownersBefore launch and on requestSet a start dateProcessing inventory; Privacy notices; Rights workflowOpen
Assess risks and supplier controlsLegal + securityBefore high-risk processing or overseas disclosureSet a start dateImpact assessments; Transfer assessments; Supplier termsOpen
Prepare breach notice and keep receiptsSecurity + controllerAt incidentSet a start dateBreach assessment; Notification recordOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Classify obligations and set ownership

    Who Privacy counsel + DPO When At initiation and when scale or activities change

    Map Nigeria activities and processing roles. Check GAID classification, registration, DPO and filing requirements and assign an accountable officer.

    What to produce

    Applicability matrixSpreadsheet

    Gather first

    • Official rules or contract and version
    • Product, organization or processing facts
    • Jurisdiction and exception criteria

    How to prepare it

    1. Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
    2. Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
    3. Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or decision
    REG-05, determine whether the new processing activity requires an assessment.
    Source and trigger
    Current regulator guidance, high-risk processing indicators
    Facts and evidence
    New dataset includes sensitive attributes. Data map P-024.
    Outcome and rationale
    Assessment required before release. Privacy lead to confirm scope.
    Owner and review
    Product privacy owner, reassess before launch and on new purposes.

    Check before handing it over

    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.

    Appointment decisionMemo

    Gather first

    • Applicable form or requirements
    • Approved scope and supporting records
    • Named signatory and approval route

    How to prepare it

    1. Identify which person can sign and what they must confirm. Gather supporting evidence, dates, responsibility and any required issuer wording.
    2. Draft a signed-document checklist or brief in your organization’s approved format. Reconcile every factual claim against the source evidence and route the draft for review.
    3. Use the applicable official wording or format for the real signed document. File the executed copy with its date, applicable scope and supporting evidence.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document owner
    Accountable executive or authorized signatory
    Scope and date
    Agreed service scope, as of 2026-10-31
    Supporting documents
    Scope v3, final control testing and open issue review
    Review and approval
    Legal and responsibility owner review before signature
    Filed record
    Signed copy plus evidence references

    Check before handing it over

    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.

    Audit calendarSpreadsheet

    Gather first

    • Current obligations, expiry dates or audit window
    • Delivery dependencies and owner availability
    • Official rules or engagement confirmation

    How to prepare it

    1. Separate official due dates, trigger-based clocks and team target dates. Write down the event or rule that starts each clock.
    2. Work backward from each milestone. Include lead time for review and submission, and name the owner and backup.
    3. Cross-check the dates with the source or reviewer and make reminders actionable. Record the next verification point for changing rules.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Milestone
    Quarterly access review approved
    Date and kind
    2026-12-18, internal target
    Trigger or source
    Internal access control schedule v3
    Prerequisite
    Access export by 2026-12-09
    Owner and reminder
    IAM lead, remind one week before
    Status
    Scheduled

    Check before handing it over

    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.

  2. 02

    Document lawful processing and rights

    Who Privacy operations + data owners When Before launch and on request

    Record purposes, bases and sensitive data handling. Publish notices and test access, correction and other rights across processors.

    What to produce

    Processing inventorySpreadsheet

    Gather first

    • Interviews with product, operations and HR
    • System and vendor inventories
    • Applicable processing and recordkeeping rules

    How to prepare it

    1. Create one row per distinct purpose or disclosure. Follow the data from collection to deletion and identify accountable parties, source, storage, recipients and retention.
    2. Record whose data it is, categories, relevant lawful basis or exception, overseas destinations and safeguards where required. Mark gaps and have the appropriate owner confirm each entry.
    3. Reconcile the list with live services and contracts. Keep a last-verified date and refresh it before material changes or new data uses.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and purpose
    P-014, send invoice receipts
    Data and people
    Billing email and amount for customer account contacts
    Roles and basis to verify
    Service company as controller. Contract analysis referenced in L-019.
    Recipients and transfer
    Email provider handles delivery. Supplier assessment V-018.
    Retention and security
    Finance schedule FS-04. Access limited to billing operations.
    Owner and review
    Finance operations, verified 2026-11-12

    Check before handing it over

    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.

    Privacy noticesMemo

    Gather first

    • Approved data map and purposes
    • Applicable disclosures and languages
    • Actual rights, consent and contact channels

    How to prepare it

    1. Write the information a person needs at the point of collection or disclosure. Use the applicable legal checklist to cover who, why, what, recipients, retention and choices.
    2. Match every promise to the real product and supplier configuration. Draft any short collection notice alongside the longer policy and use language appropriate to the audience.
    3. Have privacy and product owners check the draft against the live journey. Publish the approved version, record where it appears and test all contact and choice links.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Audience and moment
    Customer account contact, on the invoice email form
    Plain wording
    We use your billing email to send receipts and help with billing questions.
    Choices and contact
    Link to the applicable privacy request channel.
    Supporting record
    Processing activity P-014 and retention schedule FS-04
    Publish and verify
    Legal approval, web form URL, version and date

    Check before handing it over

    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.

    Rights workflowMemo

    Gather first

    • Covered rights and scope exceptions
    • Intake channels and identity verification rules
    • Systems, vendors and escalation contacts

    How to prepare it

    1. Start from each intake channel. Write who logs the request, verifies the requester and calculates the due date under the applicable rule.
    2. Map tasks to system owners. Include gathering records, searching vendors, deciding exemptions, securing replies and obtaining approval for extensions or denials.
    3. Run a test request end to end. Track timestamps, handoffs and output. Fix gaps and repeat the test before putting the procedure into use.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Trigger
    A verified customer requests access through the support form.
    Triage
    Open a case and record receipt time, jurisdiction and deadline.
    Handoffs
    Billing and customer operations return records using restricted links.
    Quality check
    Reviewer checks redactions, exemptions and controller instructions where applicable.
    Close
    Send the response securely and save delivery evidence and date.

    Check before handing it over

    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.

  3. 03

    Assess risks and supplier controls

    Who Legal + security When Before high-risk processing or overseas disclosure

    Assess processing risks, document safeguards and transfer conditions, and obtain assurance about how suppliers follow instructions and report incidents.

    What to produce

    Impact assessmentsSpreadsheet

    Gather first

    • Processing or service design and affected people
    • Threats, consequences and assessment triggers
    • Risk methodology and current safeguards

    How to prepare it

    1. Screen the activity against the applicable assessment trigger. Describe the real scenario and who or what could be harmed. Record likelihood and consequence using your criteria.
    2. Describe existing safeguards. Decide what reduces the risk and what risk remains after those measures. For a required impact assessment, document necessity, alternatives and consultation where applicable.
    3. Send the result to the person who can approve, change or stop the activity. Set a review trigger and keep evidence of the decision.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and risk
    Account recovery could expose invoices to an impersonator.
    Affected people or assets
    Customer account contacts and invoices
    Current controls
    Recovery uses verified channel. Sampled evidence linked.
    Proposed treatment
    Require a second check for requests to change the billing address.
    Remaining risk and decision
    Moderate under company method. Approval required before launch.
    Owner and review trigger
    Product risk owner, repeat when recovery flow changes

    Check before handing it over

    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.

    Transfer assessmentsSpreadsheet

    Gather first

    • Verified transfer map and remote access paths
    • Recipient contracts and safeguards
    • Current transfer rules, mechanisms and local restrictions

    How to prepare it

    1. Record exporters, importers, roles, countries, data and purposes. Include onward transfers or remote access if relevant to the governing law.
    2. Identify the permitted basis, mechanism or exemption and why it fits. Document safeguards, any required risk assessment and supporting clauses or approvals.
    3. Secure legal review and set triggers for reassessment, such as a new country, recipient or subcontractor. Tie the decision to procurement or product release.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Transfer ID
    XFER-018
    Parties and data
    EU controller to external support provider, ticket metadata
    Country and access
    Remote access from recipient country, limited support staff
    Mechanism and review
    Use applicable transfer mechanism. Legal assessment L-019 pending.
    Controls and approval
    Role restrictions and access logs. No production access until approved.

    Check before handing it over

    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.

    Supplier termsMemo

    Gather first

    • Current agreement and service description
    • Applicable flow-down terms or engagement requirements
    • Contract owner and legal review

    How to prepare it

    1. Make a clause-by-clause worksheet. Quote only what you need to identify the current clause, and record each required subject and unresolved question.
    2. Mark where scope, instructions, evidence, security, subprocessors, incident notice, audit rights or termination affect the work. Route proposed wording to authorized reviewers.
    3. Record the signed or agreed version, responsible parties and the dates you need to revisit it. Save the source agreement in its restricted store.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Party and service
    Northstar hosting provider, production backup
    Clause or requirement
    Incident notification and contacts
    Current position
    General notice terms. No operational escalation contacts listed.
    Change to review
    Add named response channel and request confirmation of the timing.
    Owner, status and record
    Vendor lead, legal review pending, contract register V-018

    Check before handing it over

    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.

  4. 04

    Prepare breach notice and keep receipts

    Who Security + controller When At incident

    Document the awareness event and expected risk to rights and freedoms. Determine when notice to the Commission and direct communication are needed.

    What to produce

    Breach assessmentSpreadsheet

    Gather first

    • Alert or breach report
    • Investigation facts and relevant thresholds
    • Escalation contacts and official reporting clocks

    How to prepare it

    1. Start a case with UTC timestamps for detection, awareness, assessment and containment. Keep known facts separate from estimates and update both as evidence changes.
    2. Identify affected systems, people, data and likely harms. Link your classification, notice decision and the rule that starts each clock.
    3. Record containment, preservation, escalation and notification actions. Capture who approved the decision and set a time to confirm outstanding facts.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Incident ID
    INC-041
    Awareness and facts
    2026-11-13 09:20 UTC. Export link exposed to an unauthorized account.
    Scope and uncertainty
    One confirmed access. Log review for further recipients in progress.
    Decision and reason
    Privacy lead to assess reporting threshold with counsel by 10:30 UTC.
    Actions and status
    Access revoked, logs preserved, next review at 12:00 UTC.

    Check before handing it over

    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.

    Notification recordSpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
    3. Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    REQ-022
    Event and date
    Verified access request received 2026-11-07 UTC
    Owner and target
    Privacy operations, internal review by 2026-11-23
    Decision and status
    Approved response, sent securely
    Completion evidence
    Case delivery record, 2026-11-24
    Follow-up
    None, approved by the reviewer

    Check before handing it over

    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.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes