Who does the GDPR apply to? 

The GDPR applies to ‘controllers’ and ‘processors. A controller determines the purposes and means of processing personal data. A processor is responsible for processing personal data on behalf of a controller. If you are a processor, the GDPR places specific legal obligations on you; for example, you are required to maintain records of personal data and processing activities. You will have legal liability if you are responsible for a breach. However, if you are a controller, you are not relieved of your obligations where a processor is involved – the GDPR places further obligations on you to ensure your contracts with processors comply with the GDPR. The GDPR applies to processing carried out by organisations operating within the EU. It also applies to organisations outside the EU that offer goods or services to individuals in the EU. The GDPR does not apply to certain activities including processing covered by the Law Enforcement Directive, processing for national security purposes and processing carried out by individuals purely for personal/household activities. 

What is personal data? 

  • Understanding whether you are processing personal data is critical to understanding whether the GDPR applies to your activities
  • Personal data is information that relates to an identified or identifiable individual
  • What identifies an individual could be as simple as a name or a number or could include other identifiers such as an IP address or a cookie identifier, or other factors
  • If it is possible to identify an individual directly from the information you are processing, then that information may be personal data
  •  If you cannot directly identify an individual from that information, then you need to consider whether the individual is still identifiable
  • You should take into account the information you are processing together with all the means reasonably likely to be used by either you or any other person to identify that individual
  • Even if an individual is identified or identifiable, directly or indirectly, from the data you are processing, it is not personal data unless it ‘relates to’ the individual
  • When considering whether information ‘relates to’ an individual, you need to take into account a range of factors, including the content of the information, the purpose or purposes for which you are processing it and the likely impact or effect of that processing on the individual
  • It is possible that the same information is personal data for one controller’s purposes but is not personal data for the purposes of another controller
  • Information which has had identifiers removed or replaced in order to pseudonymise the data is still personal data for the purposes of GDPR
  •  Information which is truly anonymous is not covered by the GDPR. If information that seems to relate to a particular individual is inaccurate (ie it is factually incorrect or is about a different individual), the information is still personal data, as it relates to that individual
  • The GDPR applies to the processing of personal data that is: wholly or partly by automated means; or the processing other than by automated means of personal data which forms part of, or is intended to form part of, a filing system
  • Personal data only includes information relating to natural persons who: can be identified or who are identifiable, directly from the information in question; or who can be indirectly identified from that information in combination with other information
  •  Personal data may also include special categories of personal data or criminal conviction and offences data. These are more sensitive, and you may only process them in more limited circumstances
  • Pseudonymised data can help reduce privacy risks by making it more difficult to identify individuals, but it is still personal data
  • If personal data can be truly anonymised, then the anonymised data is not subject to the GDPR
  • It is important to understand what personal data is in order to understand if the data has been anonymised
  • Information about a deceased person does not constitute personal data and therefore is not subject to the GDPR
  • Information about companies or public authorities is not personal data. However, information about individuals acting as sole traders, employees, partners and company directors where they are individually identifiable and the information relates to them as an individual may constitute personal data

What are identifiers and related factors? 

  • An individual is ‘identified’ or ‘identifiable’ if you can distinguish them from other individuals
  • A name is perhaps the most common means of identifying someone. However whether any potential identifier actually identifies an individual depends on the context
  • A combination of identifiers may be needed to identify an individual
  • The GDPR provides a non-exhaustive list of identifiers, including: name; identification number; location data; and an online identifier
  • ‘Online identifiers’ includes IP addresses and cookie identifiers which may be personal data. Other factors can identify an individual

Can we identify an individual directly from the information we have?

  • If, by looking solely at the information you are processing you can distinguish an individual from other individuals, that individual will be identified (or identifiable)
  • You don’t have to know someone’s name for them to be directly identifiable, a combination of other identifiers may be sufficient to identify the individual
  •  If an individual is directly identifiable from the information, this may constitute personal data

Can we identify an individual indirectly from the information we have (together with other available information)? 

  • It is important to be aware that information you hold may indirectly identify an individual and therefore could constitute personal data
  • Even if you may need additional information to be able to identify someone, they may still be identifiable
  • That additional information may be information you already hold, or it may be information that you need to obtain from another source
  •  In some circumstances there may be a slight hypothetical possibility that someone might be able to reconstruct the data in such a way that identifies the individual. However, this is not necessarily sufficient to make the individual identifiable in terms of GDPR. You must consider all the factors at stake.
  • When considering whether individuals can be identified, you may have to assess the means that could be used by an interested and sufficiently determined person
  • You have a continuing obligation to consider whether the likelihood of identification has changed over time (for example as a result of technological developments)

What is the meaning of ‘relates to’? 

  • Information must ‘relate to’ the identifiable individual to be personal data
  •  This means that it does more than simply identifying them – it must concern the individual in some way
  • To decide whether or not data relates to an individual, you may need to consider: the content of the data – is it directly about the individual or their activities?; the purpose you will process the data for; and the results of or effects on the individual from processing the data
  • Data can reference an identifiable individual and not be personal data about that individual, as the information does not relate to them
  • There will be circumstances where it may be difficult to determine whether data is personal data. If this is the case, as a matter of good practice, you should treat the information with care, ensure that you have a clear reason for processing the data and, in particular, ensure you hold and dispose of it securely
  • Inaccurate information may still be personal data if it relates to an identifiable individual

Further information can be found here: Guide to the UK General Data Protection Regulation (UK GDPR) | ICO