NDPR vs NDPA Naming
How NDPA Toolkit uses NDPA 2023 as the current legal term while preserving NDPR in package names, legacy migration context, and SEO.
Short version
The current legal framing is NDPA 2023, enforced by the Nigeria Data Protection Commission (NDPC). The package name remains @tantainnovative/ndpr-toolkit for compatibility and discoverability, but public compliance claims should lead with NDPA 2023.
Rule of thumb
Say NDPA Toolkit for the product and NDPA 2023 compliance for current obligations. Say NDPR only when referring to the npm package name, legacy 2019 regulation, old API names such as NDPRProvider, or SEO/search context.
Usage map
| Term | Meaning | Use it for |
|---|---|---|
| NDPA 2023 | Current law and current compliance claims. | Use for page titles, product positioning, legal obligations, module descriptions, and customer-facing claims. |
| NDPC | Current regulator and guidance owner. | Use for regulator references, GAID 2025 guidance, DCPMI/CAR, breach-notification guidance, and source citations. |
| NDPR | Historical regulation, package identity, and search term. | Use for npm package names, import paths, legacy migration context, old component names, and SEO capture. |
Why the package still says NDPR
The project started when Nigerian data-protection tooling was commonly searched for as NDPR tooling. Renaming the npm package would break existing imports, generated scaffolds, docs links, and installed projects. Keeping the package name stable is a compatibility decision, not a claim that NDPR 2019 is the current legal baseline.
pnpm add @tantainnovative/ndpr-toolkit
import { NDPRConsent } from '@tantainnovative/ndpr-toolkit/presets';Those import paths remain supported. New public copy should explain that the toolkit implements NDPA 2023 and NDPC GAID 2025 workflows.
NDPR 2019 to NDPA 2023 context
NDPR 2019 was the earlier Nigerian data-protection regulation. NDPA 2023 is the current Act and the basis for current toolkit legal citations, module pages, audit scoring, and compliance messaging. GAID 2025 adds implementation detail for areas such as DCPMI designation, Compliance Audit Returns, and breach-notification content.
If you are migrating older NDPR-era implementations, keep your package imports stable, then review current NDPA/NDPC obligations through the Legal Basis & Citations guide and the Legal Sources & Update Governance guide.
SEO boundary
Metadata may include both NDPA and NDPR keywords because users still search for both terms. Titles, descriptions, headings, and schema descriptions should make NDPA 2023 the current compliance term and avoid presenting NDPR as the active statute.