Understanding Your Role: GDPR Data Controller vs Data Processor

16 mins read



Brief Overview of GDPR and Its Importance

The General Data Protection Regulation (GDPR) is a game-changing data protection law that came into force in the European Union in 2018. It revolutionized the way businesses handle personal data, giving individuals unprecedented control over their information. The GDPR applies not only to companies based in the EU, but also to those outside the EU that offer goods or services to, or monitor the behavior of, EU residents.

The GDPR has far-reaching implications for businesses of all sizes, across all industries. It impacts everything from marketing strategies to data management systems, and even business models. For this reason, understanding the GDPR and its requirements is not just important—it’s essential for any business that handles personal data.

The Need for Businesses to Understand Their Roles Under GDPR

One of the key aspects of the GDPR is that it distinguishes between two main roles: the data controller and the data processor. Each has its own set of responsibilities under the regulation, and failing to comply with these responsibilities can result in hefty fines—up to €20 million or 4% of the company’s annual global turnover, whichever is higher.

It’s therefore crucial for businesses to understand which role they play in the processing of personal data. Misunderstanding or misidentifying your role can lead to compliance issues and potential legal repercussions.

Introduction to Data Controllers and Data Processors

A data controller is the entity that determines the purposes and means of processing personal data, while a data processor is the entity that processes personal data on behalf of the controller.

In simple terms, if your business decides why and how personal data should be processed, you are a data controller. If you process personal data on behalf of another organization, you are a data processor. It’s worth noting, however, that these roles are not mutually exclusive—a single business can be both a data controller and a data processor, depending on the circumstances.

Understanding Data Protection Under GDPR

Data Protection and Privacy as Fundamental Rights

At the heart of the GDPR is the principle that data protection is a fundamental right. This means that individuals have the right to control their personal data and how it is used. This is a significant shift from previous data protection laws, which often placed the emphasis on businesses and their interests.

This change in focus has wide-ranging implications for businesses. It means that they must put the rights and interests of individuals at the center of their data processing activities. This can require significant changes in the way businesses collect, store, and use personal data.

The Main Objectives of GDPR

The GDPR has several key objectives. These include:

  1. To harmonize data protection laws across the EU, making it easier for non-European companies to comply.
  2. To give individuals more control over their personal data.
  3. To require businesses to be more transparent about how they collect, use, and store personal data.
  4. To hold businesses accountable for protecting personal data.

Understanding these objectives can help businesses to navigate the complexities of the GDPR, and to ensure that their data processing activities are compliant.

Under the GDPR, personal data is defined as any information relating to an identified or identifiable natural person. This can include a wide range of data, from names and email addresses to IP addresses and cookies. It also includes sensitive data, such as health information or information about a person’s race or ethnic origin.

Importantly, the GDPR introduces new rights for individuals in relation to their personal data. These include the right to access their data, the right to have their data corrected or deleted, and the right to object to the processing of their data. Businesses must ensure that they have systems in place to comply with these rights.

Role of the Data Controller

Definition of a Data Controller Under GDPR

A data controller, as defined by the GDPR, is an entity that determines the purposes for which and the means by which personal data is processed. If an organization decides why and how personal data is to be collected and processed, they are deemed as a data controller under GDPR. The data controller could be an individual, a company, a government department, or a service provider.

Key Responsibilities of a Data Controller

Data Protection Principles

Data controllers are required to comply with the data protection principles outlined in the GDPR. These principles require that personal data be:

  1. Processed lawfully, fairly, and transparently.
  2. Collected for specific, explicit, and legitimate purposes.
  3. Adequate, relevant, and limited to what is necessary.
  4. Accurate and kept up to date.
  5. Stored only as long as necessary.
  6. Processed in a manner that ensures appropriate security.

Rights of Data Subjects

The GDPR grants certain rights to data subjects (the individuals whose data is being processed). These rights include the right to be informed, the right of access, the right to rectification, the right to erasure (‘right to be forgotten’), the right to restrict processing, the right to data portability, the right to object, and rights in relation to automated decision making and profiling. As a data controller, it is your responsibility to ensure these rights are respected and facilitated.

Data Protection Impact Assessments (DPIAs)

Under certain circumstances, data controllers are required to conduct a Data Protection Impact Assessment (DPIA). This is an exercise that helps controllers identify and minimize the data protection risks of a project. DPIAs are mandatory for processing that is likely to result in a high risk to individuals.

Real-World Examples of Data Controllers

Real-world examples of data controllers can range from a small business owner who collects customer information for marketing purposes to large corporations like Facebook or Google that collect and process user data at a large scale. Government departments that process personal data of citizens are also data controllers.

Role of the Data Processor

Definition of a Data Processor Under GDPR

A data processor, as defined by the GDPR, is an entity that processes personal data on behalf of a data controller. The processing must be done based on the instructions of the data controller. A data processor could be a third-party service such as a payroll company, an IT service provider, or a cloud service provider.

Key Responsibilities of a Data Processor

Processing Under the Instruction of the Controller

Data processors must only process personal data based on the instructions of the data controller. They are not allowed to use the data for their own purposes.

Security Measures

Data processors are required to implement appropriate technical and organizational measures to ensure the security of the personal data they process. This includes protecting the data against unauthorized or unlawful processing and accidental loss, destruction, or damage.


If a data processor engages another processor (a sub-processor) to carry out specific processing activities, they must obtain prior specific or general written authorization from the data controller. They also need to ensure that the sub-processor is contractually obligated to provide the same level of data protection.

Real-World Examples of Data Processors

Real-world examples of data processors can include IT companies that provide infrastructure or software services to other businesses, payroll companies that process payroll data for other businesses, or a marketing agency that carries out marketing campaigns for a client and processes personal data on their behalf. Cloud service providers like Amazon Web Services or Google Cloud are also examples of data processors as they provide infrastructure for storing and processing data.

Distinguishing Between Data Controllers and Data Processors

Criteria to Determine Whether an Entity is a Controller or Processor

Determining whether an entity is a controller or processor involves assessing who has the power to determine the purposes for which and the means by which personal data is processed. If an organization decides on the ‘why’ and ‘how’ of data processing, it is a controller. If an organization only processes personal data on behalf of another entity and does not decide on the ‘why’ and ‘how’, it is a processor.

The Significance of the Relationship Between Controllers and Processors

The relationship between controllers and processors is crucial in the context of GDPR. While both have responsibilities under the regulation, the data controller has the primary responsibility for ensuring the processing is compliant with GDPR. The controller must only use processors who provide sufficient guarantees to implement appropriate technical and organizational measures to meet the requirements of GDPR.

Cases Where Businesses Could Be Both a Controller and a Processor

There are instances where a business could be both a controller and a processor. For example, a company might act as a data controller when it collects and determines the purposes and means of processing customer data. The same company might act as a data processor when it processes employee data on behalf of another company for payroll processing.

Requirements for Each Role, Legal Obligations and Compliance

The GDPR imposes distinct responsibilities on data controllers and data processors. Understanding these obligations is crucial for all businesses handling personal data.

Data Protection By Design (Article 25)

Data controllers, under Article 25, must ensure that data protection is integral to all data processing activities. This principle, known as ‘Data Protection by Design’, necessitates that controllers adhere to the following requirements:

  • Process data in a manner that meets the GDPR principles.
  • Ensure that only necessary data is collected and processed.
  • Limit access to personal data.

Data processors do not share these responsibilities.

Record Keeping (Article 30)

The GDPR mandates record-keeping for both data controllers and processors. Controllers are required to maintain records of processing activities, including:

  • Controller name and contact details.
  • Purposes of processing.
  • Categories of personal data.
  • Categories of recipients of the data.
  • Details of third country transfers.
  • Expected time limits for erasure.
  • Security measures implemented.

Processors must maintain similar records, but they do not need to specify time limits for erasure or describe categories of personal data. Importantly, these record-keeping requirements do not apply to processors or controllers with fewer than 250 employees, unless the data is especially sensitive.

Reporting Requirements (Article 33)

Data controllers must report data breaches to a supervisory authority within 72 hours of awareness, unless the risk to data subjects is minimal. Data processors, on the other hand, must report data breaches to controllers “without undue delay”. However, processors are not required to report to supervisory authorities.

Data Security (Article 32)

Both data controllers and processors must implement appropriate measures to secure personal data. These measures should consider the costs, the purposes and scope of processing, and the risks to data subjects.

Notification of Data Breaches to Affected Individuals (Article 34)

If a data breach poses a risk to data subjects, data controllers are required to communicate this in plain language to the affected individuals. Processors, however, are not obliged to do so.

Data Protection Impact Assessments (Article 35)

Data controllers must conduct data protection impact assessments for activities that could pose a high risk to data subjects. This could apply when handling special categories of data or using new technologies. Data processors do not have this requirement.

Data Protection Officers (Article 37)

Both data controllers and processors must appoint a Data Protection Officer if they are a public body, process monitored data on a large scale, or handle certain categories of data.

Cooperation With Supervisory Authorities

Both data controllers and processors must cooperate with supervisory authorities—regulatory bodies ensuring GDPR compliance across Member States.


Data controllers and processors can be held liable for different breaches. Data processors may face penalties for violating their service contract or the GDPR. Data controllers can be liable for breaching the GDPR, failing to exercise due care when selecting data processors, or not having a valid service contract with their data processors.

Conclusion: Embracing Your Role for GDPR Compliance

In the era of digital transformation, data is the lifeblood of businesses. However, with the power of data comes the responsibility of protecting it. The GDPR brings clarity and accountability to this process by defining the roles of data controllers and data processors. Understanding these roles and the obligations associated with them is crucial to operating within the law and maintaining the trust of your customers.

As a data controller, your responsibilities are significant but so too are the benefits. You are in a position to dictate the ‘why’ and ‘how’ of data processing, which enables you to harness the power of data for your business objectives. However, this authority comes with the obligation to ensure that data protection principles are adhered to, data subjects’ rights are respected, and comprehensive records of processing activities are maintained.

As a data processor, you may not have the same control over the data, but your role is equally important. Your focus should be on processing data securely and efficiently, adhering strictly to the instructions of the data controller, and ensuring you report any data breaches promptly.

Understanding the differences between these roles is just the first step. The real challenge lies in implementing the necessary measures to ensure compliance. This includes investing in training and technology, maintaining clear communication with all stakeholders, and fostering a culture of data protection within your organization.

Remember, GDPR compliance is not a one-time task but an ongoing commitment. It requires you to continually monitor your data handling practices and make adjustments as needed. It’s about more than just avoiding fines; it’s about respecting the rights of your customers and maintaining their trust. In doing so, you will not only be meeting your legal obligations but also strengthening your business’s reputation and performance.

Frequently Asked Questions

What are the implications if a data processor fails to comply with the GDPR?

A data processor that does not comply with the GDPR may face severe consequences. The processor could be subject to fines of up to €20 million or 4% of global annual turnover, whichever is higher. Additionally, if a data breach or violation occurs due to their non-compliance, they could be held liable for damages suffered by data subjects. In such a scenario, the data controller may also choose to terminate their contract with the processor, leading to a potential loss of business. Furthermore, non-compliance could severely tarnish the reputation of the processor, causing loss of trust among its clients and potential clients.

How can a data controller ensure that a data processor is GDPR-compliant?

Data controllers have a responsibility to ensure that their data processors are compliant with the GDPR. This can be accomplished through several means. Firstly, the controller should have a written contract with the processor, explicitly outlining the duties and obligations of the processor. Regular audits and inspections can be conducted to verify that the processor is adhering to these obligations. Controllers can also request documentation or evidence of the processor’s data protection policies and procedures. Additionally, the controller can require the processor to obtain certifications or seals that demonstrate compliance with GDPR.

Can a company play dual roles as both a data controller and a data processor?

Yes, a company can indeed act as both a data controller and a data processor, but it’s essential to understand that these roles would apply to different sets of data and different processing activities. For instance, a company could act as a controller when it determines the purposes and means of processing its employee data or customer data. Simultaneously, the same company could act as a processor when it processes customer data on behalf of another company, such as a client for whom it provides services.

Do data processors have rights under GDPR?

While the GDPR primarily focuses on the rights of data subjects and the obligations of controllers and processors, it does provide certain protections for data processors. For instance, a processor has the right to a clear and precise contract detailing its responsibilities and relationship with the controller. In the event of a dispute, the processor also has the right to due process and can contest any fines or penalties if it believes it has adhered to GDPR regulations.

How does GDPR regulate data transfer outside the EU?

The GDPR imposes strict regulations on transferring personal data outside the European Union to ensure that the high level of data protection within the EU is not undermined. Both data controllers and processors must ensure that any data transferred outside of the EU is adequately protected. This can be achieved through various mechanisms, such as Standard Contractual Clauses (SCCs), Binding Corporate Rules (BCRs), or by transferring data to countries that the EU has deemed to provide an adequate level of data protection.

Are there exceptions to the GDPR for small businesses?

The GDPR applies to all organizations that process the personal data of EU residents, regardless of their size. However, there are some provisions that offer some flexibility for small and medium-sized enterprises (SMEs). For instance, SMEs are exempt from the obligation to keep records of their processing activities unless the processing is not occasional, could result in a risk to the rights and freedoms of individuals, or concerns special categories of data or criminal convictions and offenses.

What differentiates a Data Protection Officer (DPO) from a data controller?

A Data Protection Officer (DPO) is a distinct role mandated under the GDPR for certain types of organizations. The DPO is responsible for overseeing the data protection strategy of an organization and its implementation to ensure compliance with GDPR requirements. The DPO acts as an independent advocate for the proper care and use of customer’s information and must be able to perform their duties without any interference. They provide advice on data protection obligations, monitor the organization’s compliance with GDPR and other data protection laws, handle data protection inquiries from data subjects and authorities, and can be involved in other issues, such as dealing with data protection impact assessments.

The role of a data controller, on the other hand, is not a designated position, but rather a role that an organization plays with respect to personal data. A data controller is an entity that determines the purposes and means of processing personal data. They have obligations to ensure that data subjects’ rights are protected and that data is processed in accordance with the GDPR. So, while a DPO monitors and advises on an organization’s data protection activities, the data controller is responsible for the actual implementation of those activities.

Note that an organization acting as a data controller could appoint a DPO (or might be required to appoint one, depending on the nature and scale of data processing), but they are distinct roles with different responsibilities under the GDPR.

What is the significance of ‘Data Protection by Design and by Default’ for data controllers and processors?

‘Data Protection by Design and by Default’ is a significant concept within the GDPR. It means that organizations should incorporate data privacy features and data protection principles in the design of their projects and systems. Also, the default settings in their systems and services should be the most privacy-friendly.

For data controllers, this means they need to consider data privacy during the initial design stages of new systems, services, or products that involve processing personal data. They also have to ensure that, by default, only the necessary amount of personal data is collected and processed, access to personal data is limited, and the data retention time is minimal.

Data processors, on the other hand, must ensure that they process personal data in accordance with the controller’s instructions, which should include the principles of ‘Data Protection by Design and by Default.’ The processor must implement appropriate technical and organizational measures to ensure that processing will meet the requirements of the GDPR and safeguard the rights of the data subjects.

What does ‘Right to Data Portability’ mean, and how does it relate to data controllers and processors?

The ‘Right to Data Portability’ is one of the rights granted to data subjects under the GDPR. It allows individuals to obtain and reuse their personal data for their own purposes across different services. It also allows them to move, copy, or transfer personal data easily from one IT environment to another in a safe and secure way, without affecting its usability.

Data controllers are directly responsible for complying with this right. If a data subject requests it, the controller must provide the data subject’s personal data in a structured, commonly used, and machine-readable format. If technically feasible, the data subject can also request that the data be transferred directly from one controller to another.

Data processors are not directly responsible for the ‘Right to Data Portability’ as they do not interact with data subjects. However, they must assist the data controller in fulfilling these requests, which could include providing the necessary technical means to enable the transfer of personal data.

How does the concept of ‘Consent’ work under the GDPR for data controllers and processors?

Under the GDPR, ‘Consent’ of the data subject means any freely given, specific, informed, and unambiguous indication of the data subject’s wishes by which they, by a statement or by a clear affirmative action, signify agreement to the processing of personal data relating to them.

Data controllers must be able to demonstrate that the data subject has consented to the processing of their personal data. This means that some form of explicit and verifiable action must be taken by the data subject to indicate their consent. The controller also has the responsibility to provide clear and easily accessible information about how the data subject’s data will be used before consent is given. If the data subject is a child, the controller has to verify the age and obtain parental consent.

Data processors, on the other hand, don’t typically obtain consent directly as they process personal data based on the instructions of the data controller. However, they need to ensure they have received valid instructions from the data controller, which could include obtaining the necessary consent.

What are the steps to take if a data breach occurs?

If a data breach occurs, both data controllers and data processors have roles to play. The data processor, upon discovering the breach, must notify the data controller “without undue delay.”

The data controller, upon becoming aware of the breach, must report it to the relevant supervisory authority within 72 hours, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons. When the breach is likely to result in a high risk to these rights and freedoms, the controller must also communicate the breach to the data subjects without undue delay.

The notification to the supervisory authority must at least:

  • describe the nature of the personal data breach including, where possible, the categories and approximate number of data subjects concerned, and the categories and approximate number of personal data records concerned;
  • communicate the name and contact details of the Data Protection Officer or other contact point where more information can be obtained;
  • describe the likely consequences of the personal data breach;
  • describe the measures taken or proposed to be taken by the controller to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects.

How does GDPR affect data transfer outside the EU?

Under the GDPR, data controllers and processors must ensure that personal data is protected and GDPR-compliant when it’s transferred outside the European Economic Area (EEA).

Transfers of personal data can occur if the European Commission has decided that the third country, a territory, or one or more specified sectors within that third country, or the international organization in question ensures an adequate level of data protection. If there’s no adequacy decision, personal data can still be transferred if the data controller or processor has provided appropriate safeguards, and on condition that enforceable data subject rights and effective legal remedies for data subjects are available.

Examples of such safeguards include Binding Corporate Rules, Standard Contractual Clauses, and certain certification mechanisms.

What does a data processing agreement need to contain?

A data processing agreement (DPA) is a contract between a data controller and a data processor that outlines how personal data will be handled between the two parties. The GDPR requires a DPA to include certain elements:

  • the subject matter and duration of the processing;
  • the nature and purpose of the processing;
  • the type of personal data and categories of data subjects;
  • the obligations and rights of the controller;
  • how the processor will assist the controller in ensuring compliance with their obligations, including with respect to security, breach notifications, impact assessments, and consultations with supervisory authorities;
  • guarantees that the processor will only act on the instructions of the controller;
  • provisions ensuring the deletion or return of the data after the end of the services;
  • commitments of the processor to ensure the security of the personal data.

The DPA also needs to specify the terms under which the data processor will engage sub-processors, if at all.

Leave a Reply

Upwork Reviews




0 $0.00
%d bloggers like this: