The Nigeria Data Protection Act (NDPA) 2023 is Nigeria's first standalone data protection statute. It replaced the 2019 NDPR regulation, created the Nigeria Data Protection Commission (NDPC) as an independent regulator, and applies to every organization that processes the personal data of people in Nigeria — including organizations based outside the country. Three years in, the NDPC is enforcing at an accelerating pace, and 2026 has brought sharper scrutiny to fintech, healthcare, and government-facing processors. Non-compliance can cost up to 2% of annual gross revenue or NGN 10 million, whichever is greater. This guide walks through what the Act actually requires in practice, and the gaps we most often find when assessing Nigerian organizations.
What the Act actually requires
The NDPA is deliberately modeled on the GDPR, but it is its own law with its own regulator. Five obligations do most of the compliance work in practice:
- A documented lawful basis for every processing activity — consent, contract, legal obligation, vital interests, public interest, or legitimate interest (Section 25).
- A Data Protection Officer (DPO) for controllers and processors of "major importance", who must operate independently and report to the highest management level (Section 31).
- Data subject rights that must be operational: access, rectification, erasure, restriction, portability, objection, and protection from automated decision-making (Part IV).
- Breach notification to the NDPC without undue delay and no later than 72 hours, with affected individuals notified when the breach creates high risk (Section 40).
- Records of processing activities (ROPA), data protection impact assessments (DPIAs) for high-risk processing, and documented cross-border transfer safeguards (Sections 28, 29, 43).
The compliance checklist we use
When we assess an organization, we work through a structured checklist. Each item maps to a specific provision of the Act:
Governance & accountability
- Appoint a DPO where required under Section 31.
- Register with the NDPC as a controller or processor of major importance, if applicable.
- Maintain a record of processing activities (ROPA).
- Conduct DPIAs for high-risk processing activities.
- Publish a data protection policy and assign clear ownership.
Lawful processing & consent
- Identify and document the lawful basis for every processing activity.
- Where consent is the basis, make it freely given, specific, informed, and unambiguous.
- Implement a mechanism to withdraw consent at any time.
- Treat sensitive personal data only on the permitted grounds in Section 30.
Security safeguards & breach response
- Implement proportionate technical and organizational measures (Section 27): encryption, access controls, monitoring, testing.
- Bind processors with data processing agreements that include security obligations.
- Document a breach response procedure with the 72-hour NDPC timeline.
- Keep a breach register for every incident, including those below the notification threshold.
What non-compliance costs
The NDPC enforces through administrative sanctions, enforcement notices, suspension of processing, audits, and referral for criminal prosecution. The headline penalties:
| Violation | Penalty |
|---|---|
| Non-compliance by a controller of major importance | Up to 2% of annual gross revenue or NGN 10,000,000, whichever is greater |
| Non-compliance by other controllers/processors | Up to 2% of annual gross revenue or NGN 2,000,000, whichever is greater |
| Failure to register where required | Administrative sanctions; possible suspension of processing |
| Failure to notify a breach within 72 hours | Fines and enforcement notices |
| Obstruction of an NDPC investigation | Criminal prosecution and additional fines |
Building compliance that lasts
Compliance is not a one-off project. Organizations that pass an audit and then stop drift back within a quarter. A sustainable program treats every obligation as a tracked risk with an owner, a deadline, and evidence:
- Put every NDPA obligation into your risk register with a named owner and attached evidence.
- Re-run DPIAs whenever processing changes materially, and review existing ones annually.
- Train staff at onboarding and annually — on data handling, subject requests, and breach recognition.
- Review processor agreements and request evidence of processor compliance on a regular cycle.
- Automate tracking: spreadsheet compliance stops scaling the moment requests, vendors, or systems grow.
