At a glance
- Understanding your role in relation to the personal data you are processing is crucial in ensuring compliance with the UK GDPR and the fair treatment of individuals.
- Your obligations under the UK GDPR will vary depending on whether you are a controller, joint controller or processor.
- The ICO has the power to take action against controllers and processors under the UK GDPR.
- Individuals can bring claims for compensation and damages against both controllers and processors.
- You should take the time to assess, and document, the status of each organisation you work with in respect of all the personal data and processing activities you carry out.
- Whether you are a controller or processor depends on a number of issues. The key question is – who determines the purposes for which the data are processed and the means of processing?
- Organisations that determine the purposes and means of processing will be controllers regardless of how they are described in any contract about processing services.
The following checklists set out indicators as to whether you are a controller, a processor or a joint controller. The more boxes you tick, the more likely you are to fall within the relevant category.
Are we a controller?
☐ We decided to collect or process the personal data.
☐ We decided what the purpose or outcome of the processing was to be.
☐ We decided what personal data should be collected.
☐ We decided which individuals to collect personal data about.
☐ We obtain a commercial gain or other benefit from the processing, except for any payment for services from another controller.
☐ We are processing the personal data as a result of a contract between us and the data subject.
☐ The data subjects are our employees.
☐ We make decisions about the individuals concerned as part of or as a result of the processing.
☐ We exercise professional judgement in the processing of the personal data.
☐ We have a direct relationship with the data subjects.
☐ We have complete autonomy as to how the personal data is processed.
☐ We have appointed the processors to process the personal data on our behalf.
Are we a joint controller?
☐ We have a common objective with others regarding the processing.
☐ We are processing the personal data for the same purpose as another controller.
☐ We are using the same set of personal data (eg one database) for this processing as another controller.
☐ We have designed this process with another controller.
☐ We have common information management rules with another controller.
Are we a processor?
☐ We are following instructions from someone else regarding the processing of personal data.
☐ We were given the personal data by a customer or similar third party, or told what data to collect.
☐ We do not decide to collect personal data from individuals.
☐ We do not decide what personal data should be collected from individuals.
☐ We do not decide the lawful basis for the use of that data.
☐ We do not decide what purpose or purposes the data will be used for.
☐ We do not decide whether to disclose the data, or to whom.
☐ We do not decide how long to retain the data.
☐ We may make some decisions on how data is processed, but implement these decisions under a contract with someone else.
☐ We are not interested in the end result of the processing.
- What are ‘controllers’ and ‘processors’?
- How do you determine whether you are a controller or processor?
- What does it mean if you are a controller?
- What does it mean if you are a processor?
- What does it mean if you are joint controllers?
- In more detail
Controllers are the main decision-makers – they exercise overall control over the purposes and means of the processing of personal data.
If two or more controllers jointly determine the purposes and means of the processing of the same personal data, they are joint controllers. However, they are not joint controllers if they are processing the same data for different purposes.
Processors act on behalf of, and only on the instructions of, the relevant controller.
You should be able to differentiate between controllers, joint controllers and processors so you understand which UK GDPR obligations apply to which organisation.
To determine whether you are a controller or processor, you will need to consider your role and responsibilities in relation to your data processing activities.
If you exercise overall control of the purpose and means of the processing of personal data – ie, you decide what data to process and why – you are a controller.
If you don’t have any purpose of your own for processing the data and you only act on a client’s instructions, you are likely to be a processor – even if you make some technical decisions about how you process the data.
Controllers shoulder the highest level of compliance responsibility – you must comply with, and demonstrate compliance with, all the data protection principles as well as the other UK GDPR requirements. You are also responsible for the compliance of your processor(s).
The Information Commissioner’s Office (ICO) and individuals may take action against a controller regarding a breach of its obligations.
Controllers in the UK must pay the data protection fee, unless they are exempt.
Processors do not have the same obligations as controllers under the UK GDPR and do not have to pay a data protection fee. However, if you are a processor, you do have a number of direct obligations of your own under the UK GDPR.
Both the ICO and individuals may take action against a processor regarding a breach of those obligations.
Joint controllers must arrange between themselves who will take primary responsibility for complying with UK GDPR obligations, and in particular transparency obligations and individuals’ rights. They should make this information available to individuals.
However, all joint controllers remain responsible for compliance with the controller obligations under the UK GDPR. Both the ICO and individuals may take action against any controller regarding a breach of those obligations.