How to Protect Customer Data Under the NDPA 2023: A Restaurant Checklist
By Brandyeast · Updated 2026-11-04 · 4 min read
Every time a customer orders, you collect personal data: a name, a phone number, a delivery address, maybe an email, and a record of what they ate. Nigeria's Data Protection Act 2023 (NDPA) sets rules for how businesses must handle this kind of information. A restaurant is not exempt because it is small. This guide gives a practical checklist, written for restaurant owners, not lawyers. It is general information and not legal advice. For specifics, consult a lawyer or the Nigeria Data Protection Commission (NDPC).
What counts as personal data
- Name, phone number, email and delivery address.
- Order history and favourite dishes.
- Payment references (not full card numbers, which you should never store).
- Photos of staff or customers.
- Staff records: ID, bank details, attendance.
- Chat and call records.
If you can identify a person from the information, it is personal data.
The main ideas in plain words
| Principle | What it means for you |
|---|---|
| Lawful basis | Have a good reason to hold the data: the customer's consent, a contract (their order), or a legal duty. |
| Purpose limit | Use it for what you said you would. Order data is for fulfilling orders, not for selling to others. |
| Data minimisation | Collect only what you need. |
| Accuracy | Fix wrong details when told. |
| Storage limit | Do not keep data longer than needed. |
| Security | Protect it from loss, theft and misuse. |
| Accountability | Be able to show how you comply. |
Consent for marketing
Using a customer's number to take and deliver their order is one thing. Sending them promotions is another. For marketing messages, get clear consent: a box the customer chooses to tick, with wording that says what they will receive. Keep a record of when and how they agreed. Give an easy way to say stop, and obey it. Restorant records marketing consent in the customer record and builds campaign audiences only from those who opted in.
Tell people what you do with their data
Publish a short privacy notice on your page: what you collect, why, who sees it, how long you keep it, and how to contact you to see, correct or delete their data. Plain words, not legal jargon. Link it from your page and checkout, and make sure the text matches what you really do.
Security basics every restaurant can do
- Give each staff member their own login. Never share passwords.
- Use the lowest access that fits the job: a cashier does not need payroll.
- Turn on two-factor sign-in for owner and manager accounts.
- Remove access the day someone leaves.
- Keep phones and tablets locked, and update them.
- Do not keep customer lists in loose notebooks, shared chat groups or personal files.
- Never store card numbers or PINs. Use a payment provider that handles them.
- Back up important records.
Staff and riders
Riders see customer names, phone numbers and addresses. Limit what they see to what they need for the current delivery. Tell staff and riders that they must not copy customer details, share them or use them for personal contact. Put it in their agreement. Restorant's rider app shows only the deliveries assigned to the rider.
If something goes wrong
A data breach means personal data was lost, stolen or exposed. Act fast.
- Contain it: change passwords, remove access, stop the leak.
- Find out what data and whose was involved.
- Notify the Nigeria Data Protection Commission within the time the law requires, which is currently 72 hours for serious breaches. Check the latest rules.
- Tell affected customers if there is a risk to them.
- Record what happened and what you changed.
Do you need to register or appoint someone?
The NDPA requires some organisations, those classed as data controllers or processors of major importance, to register with the NDPC and may require a data protection officer. Whether your restaurant falls in this category depends on the number of people whose data you handle and the nature of it. A single small restaurant often does not, but a chain or a large delivery operation might. Ask a lawyer to check your position, and watch NDPC guidance.
Customer rights
- To know what data you hold on them.
- To correct wrong data.
- To ask for deletion in some cases.
- To object to marketing.
- To move their data in some situations.
Decide who answers such requests, and reply within a reasonable time. A short email address on your page is enough to start.
Be careful with photos and screenshots
Staff often share order screenshots in group chats to coordinate. These can carry names, phone numbers and addresses to people who do not need them. Ask your team to share only the order number and the items, and to delete screenshots after use. The same goes for photos of handwritten order slips or bank alerts with account details.
One-page checklist
- We know what personal data we hold and where.
- We have a plain privacy notice.
- Marketing messages go only to people who agreed.
- Every staff member has their own login.
- Access is removed when staff leave.
- We do not store card details.
- We know what to do after a breach.
- We have asked a professional about registration.
Good data habits protect your customers and your name. To set up a restaurant with separate staff logins and consent records, create a free account. The pricing page shows what is included, and online orders carry a commission of 5%.
Common questions
Does a small restaurant have to follow the NDPA?
Yes. The law applies to anyone handling personal data, whatever the size. What differs is the extra duties, such as registration, for larger operations.