What is personal data: holographic human figure surrounded by glowing data records and identifiers

What Is Personal Data? A Guide for DSAR Teams

What is personal data? Personal data is any information relating to an identified or identifiable natural person, as defined in Article 4(1) of the UK GDPR. It is the question behind every data subject access request (DSAR), every records review and every decision about what to disclose.

The definition is a single sentence, yet it decides what the law protects, who it protects and what an individual can ask to see. This guide takes it apart one phrase at a time. For each phrase it explains what the phrase means, where the difficult cases sit and why it matters for data protection and information governance teams handling DSARs.

Key points

  • Personal data is any information relating to an identified or identifiable natural person.
  • Four tests apply: it is information, it relates to a person, the person is identifiable and the person is a living individual.
  • Identifiability does not need a name. Reference numbers, usernames and online identifiers can all identify a person.
  • The definition sets the scope of a DSAR, so it shapes every search, scoping and redaction decision.

What is personal data under the UK GDPR?

Personal data is any information relating to an identified or identifiable natural person, known as the data subject. This is the definition in Article 4(1) of the UK GDPR. Information counts as personal data only when four tests are met: it is information, it relates to a person, that person is identifiable, and that person is a living individual.

The definition is deliberately broad. It is written to protect people whatever technology, format or business process is involved, so most information an organisation holds about a living individual is likely to fall within it.

Each part of the sentence asks a different question. Together they give data protection teams a repeatable way to test any piece of information.

Phrase The question it asks Example
Any information Is there information of any kind, in any format? An email, a call recording, a database field
Relating to Is the information about the person? A performance review, a complaint file
Identified or identifiable Can the person be singled out, directly or indirectly? A name, an employee number, an online identifier
Natural person Is the individual a living human being? A customer, an employee, a patient

What does any information mean in the personal data definition?

Any information means the definition covers data of every kind and in every format. Facts, opinions, images and recordings can all be personal data. It does not matter whether the information is accurate, sensitive or held digitally. If it relates to an identifiable living person, the definition is likely to apply.

The word any is deliberate, and it has four practical effects.

  • Format does not matter. Written notes, emails, database entries, call recordings, CCTV footage, photographs and chat messages can all be personal data.
  • Content does not matter. A manager’s opinion of an employee is information about that employee, so it can be personal data of the employee.
  • Sensitivity does not matter. A work email address is personal data in the same way a health record is. Special category data, such as health or biometric data, simply carries extra safeguards.
  • Accuracy does not matter. Information that is wrong or out of date is still personal data, which is why individuals can ask for it to be corrected.

For a DSAR, this breadth is the first source of workload. The duty to search is not limited to the obvious systems. It reaches shared drives, mailboxes, collaboration tools and paper files wherever the organisation holds information about the requester.

That is why data volume, rather than legal analysis, is so often the hardest part of a request.

What does relating to mean for personal data?

Relating to is the test of whether information is about a person. Information relates to an individual when it is about them by content, when it is used to evaluate or influence them by purpose, or when it is likely to affect them by effect. The test applies to information, not to whole documents.

This is where most real disagreements arise. A meeting note about a restructure may mention several people. A single email may contain one paragraph about the requester and nine about something else.

The Information Commissioner’s Office (ICO) explains that the content of an email is only personal data if it reveals something about a person or affects them. A name combined with a corporate email address is personal data in its own right.

The Court of Justice of the European Union took a wide view of the same concept in the Nowak case in 2017. It ruled that an exam script and the examiner’s comments on it both counted as personal data of the candidate. The comments could also be information about the examiner. One item of information can therefore relate to more than one person at the same time.

The practical point for DSAR teams is that relevance is decided passage by passage. A document can hold personal data of the requester, personal data of colleagues and information that is not personal data at all. Each part needs a decision, and each decision needs a recorded reason.

When is a person identified or identifiable?

An identifiable person is someone who can be identified, directly or indirectly, from the information alone or combined with other information. Identifiers include a name, an identification number, location data and an online identifier. A person is identified when they can already be distinguished from others, for example by name.

The second limb, identifiable, is the one that catches organisations out. Identifiability does not depend on a name. A customer number, an employee ID, an IP address or a job title in a small team can each point to one individual.

The UK GDPR also lists factors specific to a person, such as their physical, genetic, mental, economic, cultural or social identity. Any of these can make a person identifiable when combined with other details.

Two related terms are often confused.

  • Pseudonymised data is data where direct identifiers are replaced, for example with a reference number, but the organisation can still link it back to a person. The ICO is clear that pseudonymised data remains personal data. It is a security measure, not a way out of the law.
  • Anonymised data is data where individuals can no longer be identified by any reasonably available means. Truly anonymised data falls outside the UK GDPR, but the ICO warns that the bar is high and many datasets described as anonymised are not.

For a DSAR, this phrase drives the search method. The requester will usually give a name, but the team must also search by every other identifier it holds for that person. These include account numbers, email addresses, employee references and system usernames. Records that carry no name but are linked to the requester by an identifier are still within scope.

Who is a natural person under data protection law?

A natural person is a living human being. The UK GDPR protects natural persons only. Information about a company or other legal entity is not personal data, and information about a deceased person is generally not personal data either. Information about a sole trader, employee or director can be personal data when it concerns them as an individual.

The phrase draws two clear lines.

  • Legal entities are excluded. A limited company has no data subject rights. However, the people who work for it do. A named individual’s work email address is personal data, while a generic company address may not be.
  • The deceased are generally excluded. Other duties, such as confidentiality, may still apply to their records, but the UK GDPR data subject rights are not normally available on their behalf.

The natural person test also reminds teams that data subject rights belong to individuals wherever they sit in relation to the organisation. Employees, former employees, customers, patients, applicants, volunteers and website visitors are all natural persons. Each can make a request.

A third party can make a request for someone else, provided they have the appropriate authority. A solicitor or a family member acting with written consent is a common example. The data subject is still the person whose personal data is being requested, and the organisation must be satisfied that the authority is genuine before it discloses anything.

How to decide whether information is personal data in five steps

To decide whether information is personal data, test it against the four parts of the UK GDPR definition in order, then record the reasoning. Check that it is information, that it relates to a person, that the person is identifiable and that they are a living individual.

Step 1: Identify the information and where it sits

Name the specific item you are assessing, such as an email thread, a spreadsheet column or a recording. Note the system it is held in. Assess passages, not whole files.

Step 2: Ask whether it relates to a person

Check content, purpose and effect. Is the passage about the individual? Is it used to evaluate or influence them? Is it likely to affect them? A yes to any one is enough.

Step 3: Test whether the person is identifiable

Consider every identifier held, including names, reference numbers, usernames and online identifiers. Ask whether the information can be linked back to one person, even if that needs a second dataset.

Step 4: Confirm the person is a living individual

Rule out companies and other legal entities. Rule out deceased individuals. Treat sole traders, directors and employees as individuals when the information concerns them personally.

Step 5: Record the decision and the reason

Write down the outcome and the reasoning in one or two sentences. A clear record supports the response if the requester, the ICO or a court later challenges it. It also keeps decisions consistent between colleagues.

Why does the personal data definition matter for a DSAR?

The personal data definition sets the scope of a DSAR. The right of access gives an individual confirmation of processing, a copy of their personal data and supplementary information about how it is used. Only information that meets the definition is in scope, so the wider the reading, the wider the search, review and redaction.

Knowing what is personal data is therefore the first judgement in every request. The right of access is the right that makes the other data subject rights usable. The ICO describes it as a fundamental right that helps people understand how and why their information is used and check that it is used lawfully. It covers all the personal information held about the person, including information that has been observed or inferred.

The right is to personal data, not automatically to whole documents. In practice, many teams supply the relevant documents with other people’s information protected, because that is the simplest way to give a clear and complete copy.

The scale of the task is well documented. The Data Protection Network surveyed 412 practitioners in autumn 2026. Of those surveyed, 83% reported a rise in DSAR volumes and 62% said requests had become significantly more complex. Practitioners also cited the volume of data to be searched (77%) and unstructured data such as email (63%). Only 30% cited applying exemptions.

The survey was voluntary and leaned towards larger organisations, so it indicates what practitioners experience rather than measuring every organisation. Its reading is that scale of data, not legal difficulty, is the main pressure.

The definition therefore shapes all four stages of a DSAR.

  • Discovery: apply the breadth of any information and search by every identifier held.
  • Scoping: reduce the volume before anyone reads it, by removing duplicates and de threading email.
  • Redacting: apply relating to, keeping what concerns the requester and protecting other individuals.
  • Disclosure: provide the personal data securely and keep a record of what was released and why.

How do manual spreadsheets compare with the ProvePrivacy platform for DSARs?

Manual spreadsheets record DSARs but do not manage them. The ProvePrivacy platform is a GDPR compliance platform that manages the case from intake to disclosure, with deadline tracking, scoping tools, a built in redaction tool, secure disclosure and an audit trail. Both depend on your own teams to find the data in your systems.

DSAR task Manual spreadsheets and email ProvePrivacy platform
Finding the data Your teams search your own systems Your teams search your own systems, and the platform picks up from what has been gathered
Tracking deadlines Dates entered and checked by hand Case workflow with 30 day deadline tracking
Reducing volume Everything gathered goes to review Email de threading, file de duplication and content filtering before redaction
Redacting Page by page, by hand Built in redaction tool with AI based detection across thousands of pages in one run, with your team making the final check
Recording exemptions Notes held in separate files Reasons for exempting material captured and added to the audit log
Sending the response Attachments sent by email Secure, time bound download portal, with access closing once delivery is confirmed
Reporting Manual counts for managers and boards MI dashboards for volume, processing time, exemptions and timeliness

How does ProvePrivacy help you apply the personal data definition?

ProvePrivacy is a GDPR compliance platform that helps data protection teams manage data subject rights from first request to final disclosure. The ProvePrivacy platform tracks deadlines, scopes and redacts the material your team gathers, and delivers the response through a secure portal. Each decision is recorded for audit.

The definition of personal data is only useful if it is applied the same way every time. ProvePrivacy supports that in four ways.

  • Case management. Requests are logged in one workflow with deadline tracking, a timeline of progress and a UK GDPR exemptions assessment framework.
  • Scoping and redaction. Email conversations are de threaded, duplicate files are removed and content is filtered to a reasonable volume. The built in redaction tool then processes thousands of pages in one run, with your team in control of the final check.
  • Secure disclosure. The response goes to the data subject through a time bound download portal. The recipient proves control of their mailbox with a one time code, and access closes once delivery is confirmed.
  • Evidence. Exemption reasons, decisions and results are recorded in the case audit log, and MI dashboards show volumes, processing times and timeliness.

On the full platform, the Record of Processing Activities (RoPA) also helps teams know where personal data sits before a request arrives. ProvePrivacy is used by organisations including East of England Ambulance Service and Anglia Ruskin University, and it is live in one day with unlimited users.

Finding the data in your own systems still happens on your side. ProvePrivacy takes over from there, so your team spends its time on judgement, not on copying, tracking and chasing.

Frequently asked questions about personal data

Is an email address personal data?

An email address is personal data when it identifies, or can be used to identify, an individual. A work address that combines a person’s name with a company domain is personal data. A generic address, such as a shared team inbox, may not be, depending on whether it can be linked to an individual.

Is pseudonymised data still personal data?

Yes. Pseudonymised data is personal data because the organisation can still link the reference back to an individual. Pseudonymisation is a security measure that reduces risk. Only data that is truly anonymised, so that nobody can reasonably re identify the person, falls outside the UK GDPR.

Is information about a deceased person personal data?

Generally no. The UK GDPR protects living individuals only, so the data subject rights do not normally apply to a deceased person. Other duties, such as confidentiality, may still apply, and some records may also contain personal data of living relatives.

Does a DSAR give the requester a right to whole documents?

A DSAR gives the requester a right to their personal data, not automatically to every document that mentions them. Teams often supply the relevant documents with other people’s information protected, because that is the simplest way to give a clear and complete copy.

What is the difference between personal data and special category data?

Special category data is a subset of personal data that carries extra protection. It includes information about health, race, sexual orientation and biometric data used for identification. All special category data is personal data, but most personal data is not special category data.

Sources

Related reading: the complete DSAR process hub for data protection teams, data subject access requests and sensitive personal data.

Last updated 19 November 2026

Manage personal data and privacy risks

Scroll to Top

Contact us

If you would like to ask more questions or to arrange training, complete the form below and we will respond shortly.

Prefer to schedule a 15 minute call? Schedule call today >>

See our Privacy Statement for more details.