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

A data subject access request (DSAR) is a request by an individual for a copy of the personal data an organisation holds about them, plus information about how it is used. Under the GDPR you generally have one month to respond, and Nigeria’s Data Protection Act also gives individuals a right of access that organisations must honour promptly. To handle one well: log it, verify identity, search all systems, review for other people’s data and legal exemptions, and send a clear, complete response on time.

Stack of papers marked with colorful sticky tabs

It usually arrives without warning. An email from a former employee, a message from an unhappy customer, sometimes a formal letter from a lawyer: “Please provide all personal data you hold about me.” For a small business, the first reaction is often panic. Where would we even start?

The good news is that handling a data subject access request (DSAR) is very manageable if you follow a clear process. This guide walks through it step by step, using the Nigeria Data Protection Act 2023 (NDPA) and the EU and UK GDPR as reference points.

What People Are Entitled To

The right of access lets individuals find out whether you process their personal data and, if you do, get a copy of it along with key information, such as:

It covers data in emails, CRM systems, spreadsheets, HR files, CCTV footage, call recordings, chat logs and even handwritten notes held in organised files.

How Long Do You Have?

Under the GDPR, you must respond without undue delay and within one month of receiving the request, extendable by up to two further months for complex or numerous requests if you tell the person within the first month. In Nigeria, the NDPA gives individuals a right of access, and the NDPC expects organisations to respond promptly and within the timelines set out in its guidance; build your process around the one-month benchmark and check the latest NDPC requirements. Requests are usually free, although you may be able to charge a reasonable fee or refuse if a request is manifestly unfounded or excessive.

A Step-by-Step Process

Step 1: Recognise and log the request

People rarely use the phrase “data subject access request.” A WhatsApp message saying “send me everything you have on me” counts. Train front-line staff to spot requests and pass them to a named person immediately, and record the date received; that is when the clock starts.

Step 2: Verify identity, proportionately

You must not hand someone else’s data to an impostor. Ask for reasonable verification, but do not demand more than necessary: if the request comes from the email address on the customer’s account, a confirmation step may be enough. Ask quickly; in many regimes the deadline can pause while you wait for genuinely necessary information.

Step 3: Clarify if needed

If you hold a lot of data, you can ask the person to specify what they are interested in, but you cannot force them to narrow a request.

Step 4: Search everywhere

Make a list of systems and search them all: email accounts, shared drives, HR and payroll, CRM, accounting, customer support tickets, website and app databases, marketing tools, CCTV, messaging apps used for work, and data held by processors such as outsourced call centres. This is where a good data map pays off.

Step 5: Review before you send

Not everything you find must be disclosed. Check for:

Be careful not to over-redact; regulators take a dim view of responses that withhold more than necessary.

Step 6: Respond clearly

Provide the data in a clear, accessible format, usually electronic if the request was made electronically, along with the supporting information listed above. A short covering letter explaining what you are providing and any redactions will prevent follow-up complaints.

Step 7: Keep a record

Record what was requested, what you searched, what you provided, what you withheld and why. If the person complains to the NDPC or another regulator, this record is your best defence.

The Special Case of Employee Requests

DSARs from current or former employees, often during disputes, can be the most demanding because they involve large email volumes and references to colleagues. Use search tools carefully, involve HR and legal early, and remember that the purpose of the request does not usually matter: even if it is a fishing expedition ahead of a claim, it must still be handled properly.

Common Mistakes to Avoid

Prepare Before the First Request

  1. Create a simple DSAR procedure and response template.
  2. Name a responsible person and a backup.
  3. Map where personal data lives in your organisation.
  4. Make sure your contracts require processors to help you respond.
  5. Delete data you no longer need; the less you hold, the easier requests become.

Build a repeatable process for access requests

A data subject access request is not an accusation; it is a person exercising a legal right. Handle it promptly, respectfully and thoroughly, and it will usually end there. Handle it badly, and it can become a complaint to the regulator. A little preparation turns a stressful surprise into a routine task.

Frequently Asked Questions

Can I refuse a DSAR?

Only in limited circumstances, such as manifestly unfounded or excessive requests, and you must explain why and tell the person about their right to complain.

Do I have to include emails that mention the person?

Their personal data within those emails is generally in scope, subject to redaction of other people’s information and applicable exemptions.

Can someone make a request on another person’s behalf?

Yes, if they are authorised, for example a lawyer or parent. Check the authority before disclosing.

Leave a Reply

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