🕑 Estimated reading time: 5 minutes  |  Last updated: May 18, 2026

A compliant privacy policy (or privacy notice) tells people, in clear language, who you are, what personal data you collect, why, on what lawful basis, who you share it with, whether it leaves the country, how long you keep it, how you protect it, and how they can exercise their rights or complain. Under the Nigeria Data Protection Act 2023 and the GDPR, it must be accurate, easy to find and kept up to date. Copying another company’s policy is one of the most common, and most risky, mistakes.

Person sitting front of laptop

Be honest: when did you last read a privacy policy all the way through? Most of us scroll past walls of legal text, and many businesses write them that way on purpose, or more often, copy one from a competitor and change the name at the top. That is a problem, because a privacy policy is not decoration. Under data protection law, it is a promise you are legally bound to keep, and regulators read them.

This guide explains what a privacy notice needs to contain under the Nigeria Data Protection Act 2023 (NDPA) and the GDPR, and how to make it genuinely useful.

Why It Matters

Transparency is one of the core data protection principles. People have a right to know what happens to their information. A misleading or incomplete notice can mean that your consent is invalid, that your processing is unlawful, and that you face complaints or penalties. Regulators, including the Nigeria Data Protection Commission, often start investigations by comparing what a company says in its policy with what it actually does.

What Your Privacy Notice Must Include

1. Who you are

Your organisation’s legal name, address and contact details, and the contact details of your data protection officer if you have one.

2. What data you collect

Be specific: names, phone numbers, BVN or NIN, delivery addresses, payment information, device identifiers, location data, CCTV images and so on. If you collect sensitive data, such as health or biometric information, say so clearly.

3. Where you get it from

Directly from customers, from their use of your app or website, from partners, credit bureaus, social media or public sources.

4. Why you use it, and your lawful basis

For each main purpose, such as processing orders, preventing fraud, marketing or improving your service, explain the lawful basis: consent, contract, legal obligation, legitimate interests and so on. A simple table works well here.

5. Who you share it with

Name categories of recipients, such as payment processors, delivery companies, cloud providers, analytics and advertising partners, regulators and law enforcement where required.

6. International transfers

If data leaves Nigeria or the EU, say where it goes and what safeguards protect it.

7. How long you keep it

State retention periods or the criteria you use, for example “for six years after the end of your contract to meet tax obligations.”

8. How you protect it

A short description of your security measures, without giving away details useful to attackers.

9. People’s rights

Explain the rights to access, correct, delete, object, restrict processing, data portability and withdraw consent, and exactly how to exercise them.

10. Automated decisions

If you use automated decision-making with significant effects, such as instant loan approvals, explain the logic involved and how people can request human review.

11. Cookies and tracking

Either explain them in the policy or link to a separate cookie notice.

12. Complaints

Tell people they can complain to you and to the relevant regulator, such as the NDPC in Nigeria.

13. Updates

Include the date the policy was last updated, and explain how you will tell people about significant changes.

Making It Readable

Common Mistakes

A Simple Process to Get It Right

  1. Map your data: what you collect, why, where it goes and how long you keep it.
  2. Decide the lawful basis for each purpose.
  3. Draft in plain language using the checklist above.
  4. Have someone outside the project read it and tell you what they understood.
  5. Get legal review if you process sensitive data or operate in several countries.
  6. Publish it prominently and link it at every point of collection.
  7. Review it at least once a year and whenever your processing changes.

Write a policy that reflects what you actually do

A good privacy policy does two jobs: it satisfies the law, and it earns trust. Treat it as an honest explanation to your customers rather than a legal shield, keep it accurate, and it will protect your business far better than pages of copied boilerplate ever could.

Frequently Asked Questions

Is a privacy policy legally required in Nigeria?

The NDPA requires controllers to give data subjects specified information about processing. A privacy notice is the standard way to do that.

Can I use a free online template?

Templates can be a starting point, but the final policy must reflect what you actually do.

Do I need a separate cookie policy?

Not necessarily, but cookie information must be clear and accessible, and non-essential cookies usually need consent.

Leave a Reply

Your email address will not be published. Required fields are marked *