Data subject categories are the groups of people whose personal data you process: customers, prospects, staff, job applicants and so on. The GDPR requires you to describe them for each processing activity in your records of processing. They answer a simple question that your register, your contracts and your risk assessments keep coming back to: whose data is this?
What is a data subject?
Under Article 4(1) GDPR, personal data is any information relating to an identified or identifiable natural person. That person is the data subject. A data subject is always a living individual, never a company: the contact person at a business customer is a data subject, the business itself is not.
A data subject category groups data subjects who are in the same position towards your organisation. The GDPR gives no fixed list; you describe the groups that occur in your own processing.
Where does the GDPR require them?
In your records of processing (Article 30)
Article 30(1)(c) GDPR requires a controller’s records of processing activities to contain “a description of the categories of data subjects and of the categories of personal data”. So for every processing activity in your register, you state whose data it concerns and which data you use.
Many small businesses think they are exempt because they have fewer than 250 employees. The exemption in Article 30(5) does not apply to processing that is not occasional, such as payroll, customer administration or invoicing, so in practice almost every business keeps a register. See GDPR register: do I need one?.
In a data processing agreement (Article 28)
When a processor works for you, the agreement must set out, among other things, “the type of personal data and categories of data subjects” (Article 28(3) GDPR). The processor’s own register under Article 30(2) does not list the data subjects, but the agreement does. See What is a processing agreement?.
In a data breach notification (Article 33)
When you notify a personal data breach to the supervisory authority, you describe “where possible, the categories and approximate number of data subjects concerned” (Article 33(3)(a) GDPR). A register that already names the groups per process makes that description much faster.
In a DPIA
A data protection impact assessment describes the processing, including whose data it concerns. In their guidelines on DPIAs (WP248, endorsed by the EDPB), the European supervisory authorities list data about vulnerable data subjects, such as children, employees, patients and elderly people, as one of the criteria that point to a high risk.
Data subject categories, personal data categories and special categories
Three terms that sound alike but mean different things:
- Data subject categories: whose data. For example customers, job applicants, patients.
- Categories of personal data: which data. For example contact details, payment data, a CV.
- Special categories of personal data: the sensitive types in Article 9 GDPR, such as health data, religious beliefs or trade union membership, which you may only process under a specific exception.
A recruitment process, for example, concerns the data subject category job applicants, the personal data categories contact details, CV and interview notes, and normally no special categories.
Examples for small and medium-sized businesses
| Processing activity | Typical data subject categories |
|---|---|
| Customer administration and invoicing | Customers, contact persons at business customers |
| Newsletter and promotion | Customers, prospects, newsletter subscribers |
| Web shop accounts | Registered users |
| Website analytics and contact form | Website visitors |
| Payroll and personnel files | Staff |
| Recruitment | Job applicants |
| Keeping files after departure | Former staff |
| Working with freelancers or interns | External contributors, interns |
| Care or treatment | Patients |
Sector-specific groups such as guests, students, tenants or members belong in the list when they are the people you actually deal with.
How do you choose the right categories?
- Work per processing activity. List the categories for each process, not once for the whole company. The same person can fall into different categories in different processes.
- Name the real group. “Customers” is not enough for a newsletter that also goes to prospects, and “staff” is wrong for a recruitment process.
- Be specific where the risk differs. Name children, patients or other vulnerable groups separately, because they change the assessment of the processing.
- Keep it consistent. Use the same names in your register, your privacy policy and your processing agreements.
- Review when things change. A new service, a new target group or a new system can add a category.
GDPRWise suggests the processes, data items and data subject categories for your sector and prints them in your GDPR register and privacy policy.