Skip to the content
Eureka The General Data Protection Regulation
EN language

Topics

Controllers and processors

Eureka's summary

The controller determines the purposes and means of processing; a processor processes personal data on its behalf. Section 1 of Chapter IV sets their general obligations, from data protection by design to contracts with processors and records of processing activities.

Who is who Three actors in a row. The data subject, a person, is an identified or identifiable natural person; personal data are any information relating to him or her, drawn as a card on a line joining the data subject and the controller. The controller, an office block with a target badge, determines, alone or jointly with others, the purposes and means of the processing of personal data. The processor, the same block with a gear badge, processes personal data on behalf of the controller; a thin arrow runs from the controller to the processor. A note under both says that each may be any natural or legal person, public authority, agency or other body. data subject identified or identifiable natural person personal data controller determines purposes and means processor processes on the controller's behalf person, authority or body
Personal data relate to a natural person, the data subject; the controller determines the purposes and means of processing them, and a processor processes them on the controller's behalf. The act in pictures

Article 4 · Definitions

Article 4 defines the Regulation's terms in 26 points.

‘Personal data’ means ‘any information relating to an identified or identifiable natural person’, the ‘data subject’; the ‘controller’ determines, alone or jointly with others, the purposes and means of the processing, and a ‘processor’ processes personal data on behalf of the controller.

Other defined terms include ‘processing’, ‘profiling’, ‘pseudonymisation’, ‘consent’, ‘personal data breach’, ‘genetic data’, ‘biometric data’, ‘data concerning health’, ‘main establishment’ and ‘cross-border processing’.

Read Article 4

Article 24 · Responsibility of the controller

The controller must implement appropriate technical and organisational measures to ensure, and to be able to demonstrate, that processing complies with the Regulation, taking into account the nature, scope, context and purposes of processing and the risks for the rights and freedoms of natural persons.

The measures must be reviewed and updated where necessary and, where proportionate, include appropriate data protection policies. Adherence to approved codes of conduct or certification mechanisms may be used as an element to demonstrate compliance.

Responsibility of the controller Taking into account the nature, scope, context and purposes of processing and the risks of varying likelihood and severity for the rights and freedoms of natural persons, the controller must implement appropriate technical and organisational measures, which are reviewed and updated where necessary. The measures serve two duties, each drawn with a tick: to ensure that processing complies with the Regulation, and to be able to demonstrate it. Where proportionate, the measures include data protection policies. A 'may' chip: adherence to approved codes of conduct or approved certification mechanisms may be used as an element to demonstrate compliance. taking into account nature, scope, context, purposes and risks controller appropriate technical and organisational measures reviewed and updated where necessary ensure compliance be able to demonstrate it may approved codes of conduct or certification as an element to demonstrate compliance
The controller must put in place appropriate measures, chosen in the light of the processing and its risks, to ensure and to be able to demonstrate that processing complies with the Regulation. The act in pictures

Read Article 24

Article 25 · Data protection by design and by default

Both when determining the means of processing and during the processing itself, the controller must implement appropriate technical and organisational measures, such as pseudonymisation, designed to implement the data-protection principles effectively, taking into account the state of the art, the cost of implementation and the risks.

The controller must also ensure by appropriate measures that, by default, only personal data necessary for each specific purpose are processed (as to amount, extent of processing, storage period and accessibility), and that personal data are not by default made accessible without the individual's intervention to an indefinite number of natural persons.

Data protection by design and default Two panels. By design: both when determining the means of processing and during the processing itself, the controller must implement appropriate technical and organisational measures, such as pseudonymisation, designed to implement the data-protection principles effectively, taking into account the state of the art, the cost of implementation, the nature, scope, context and purposes of processing and the risks. By default: the controller must ensure that only the personal data necessary for each specific purpose are processed, as to the amount collected, the extent of processing, the period of storage and accessibility; a toggle switched off shows that, by default, personal data are not made accessible to an indefinite number of natural persons without the individual's intervention. by design when determining the means and during processing appropriate measures, such as pseudonymisation, that implement the principles by default only the personal data necessary for each specific purpose, as to: amount extent storage period accessibility accessible to an indefinite number of persons not without the individual's intervention
The controller must build data protection into the processing from the start and, by default, process only the personal data needed for each purpose. The act in pictures

Read Article 25

Article 26 · Joint controllers

Where two or more controllers jointly determine the purposes and means of processing, they are joint controllers.

Unless and in so far as Union or Member State law determines their responsibilities, they must set them out in a transparent arrangement, in particular for the rights of the data subject and the information under Articles 13 and 14, and make its essence available to the data subject.

Whatever the arrangement says, the data subject may exercise his or her rights against each of the controllers.

Joint controllers Two controllers who jointly determine the purposes and means of processing are joint controllers. Between them an arrangement sets out their respective responsibilities, in particular for the data subject's rights and the information of Articles 13 and 14, except in so far as Union or Member State law determines them. A thin arrow shows that the essence of the arrangement is made available to the data subject. Two arrows from the data subject to each controller, with a 'may' chip: whatever the arrangement says, the data subject may exercise his or her rights against each of the controllers. jointly determine purposes and means controller controller arrangement respective responsibilities not for: responsibilities set by law its essence data subject may exercise rights against each controller
Controllers who jointly determine the purposes and means of processing must set out their responsibilities in an arrangement, and the data subject may exercise his or her rights against each of them. The act in pictures

Read Article 26

Article 27 · Representatives of controllers or processors not established in the Union

Where Article 3(2) applies, the controller or processor must designate in writing a representative in the Union, established in one of the Member States where the data subjects concerned are.

This does not apply:

  • to a public authority or body; or
  • to processing which is occasional, does not include large-scale processing of special categories of data or of personal data relating to criminal convictions and offences, and is unlikely to result in a risk to the rights and freedoms of natural persons.

Designating a representative is without prejudice to legal actions against the controller or processor themselves.

Representative in the Union If a controller or processor is not established in the Union and Article 3(2) applies (it offers goods or services to data subjects in the Union or monitors their behaviour there), the controller or processor must designate in writing a representative in the Union, established in one of the Member States where those data subjects are. Not for public authorities or bodies, nor for processing which is occasional, unlikely to result in a risk to the rights and freedoms of natural persons and does not include large-scale processing of special categories of data or of personal data relating to criminal convictions and offences. The representative may be addressed in addition to or instead of the controller or processor; legal actions against the controller or processor themselves remain possible. if: not established in the Union, Article 3(2) applies or controller or processor designates in writing Member State representative in a Member State where the data subjects are not for: public authorities or bodies not for: processing that is occasional, unlikely to result in a risk and without large-scale special-category or criminal data controller or processor still open to legal action
A controller or processor not established in the Union whose processing falls under Article 3(2) must designate in writing a representative in the Union, with two exceptions. The act in pictures

Read Article 27

Article 28 · Processor

The controller must use only processors providing sufficient guarantees to implement appropriate technical and organisational measures.

Processing by a processor must be governed by a written contract or other legal act under Union or Member State law, which stipulates in particular that the processor:

  • acts only on the controller's documented instructions (unless Union or Member State law requires otherwise);
  • ensures confidentiality;
  • takes the measures required under Article 32;
  • assists the controller; and
  • at the end, deletes or returns the data as the controller chooses.

A processor may engage another processor only with the controller's prior specific or general written authorisation and under the same data protection obligations, and remains fully liable to the controller if that other processor fails to fulfil them.

Contract with a processor The controller may use only processors providing sufficient guarantees. Processing by a processor is governed by a contract or other legal act in writing, including in electronic form. It stipulates, in particular, that the processor: (a) processes the data only on documented instructions from the controller, unless required by Union or Member State law; (b) ensures that authorised persons are bound to confidentiality; (c) takes the security measures required by Article 32; (d) respects the conditions for engaging another processor; (e) assists the controller in responding to data subjects' requests; (f) assists the controller with Articles 32 to 36; (g) at the controller's choice deletes or returns all the data at the end of the services; (h) makes available all information needed to demonstrate compliance and allows audits. The processor may engage another processor only with the controller's prior specific or general written authorisation; the same data protection obligations apply to that other processor, and the initial processor remains fully liable to the controller. controller processor contract or legal act in writing only processors with sufficient guarantees it covers, in particular: (a) only documented instructions unless required by Union or Member State law (b) confidentiality (c) security measures (Article 32) (d) conditions for another processor (e) assistance with data subjects' requests (f) assistance with Articles 32 to 36 (g) deletion or return at the end (h) information and audits Processor only with the controller's prior written authorisation another processor same data protection obligations initial processor remains fully liable
The controller may use only processors with sufficient guarantees, under a written contract or other legal act that binds the processor to the points of Article 28(3). The act in pictures

Read Article 28

Article 30 · Records of processing activities

Each controller must keep a record of processing activities under its responsibility containing the information listed in paragraph 1, and each processor a record of all categories of processing carried out on behalf of a controller.

Records must be in writing and made available to the supervisory authority on request.

These obligations do not apply to an enterprise or an organisation employing fewer than 250 persons, unless the processing it carries out:

  • is likely to result in a risk to the rights and freedoms of data subjects;
  • is not occasional; or
  • includes special categories of data (Article 9(1)) or personal data relating to criminal convictions and offences (Article 10).
Records of processing activities A record of processing activities, in writing, including in electronic form. The controller keeps a record of the processing activities under its responsibility; the processor keeps a record of all categories of processing carried out on behalf of each controller. The record is made available to the supervisory authority on request. The obligations do not apply to an enterprise or organisation employing fewer than 250 persons, unless the processing is likely to result in a risk to the rights and freedoms of data subjects, or is not occasional, or includes special categories of data or personal data relating to criminal convictions and offences: any one of these is enough for the obligation to apply. record of processing activities in writing, including in electronic form controller its processing activities processor categories of processing for each controller made available to the supervisory authority on request not for: an enterprise or organisation employing fewer than 250 persons unless the processing: is likely to result in a risk to rights and freedoms or is not occasional or includes special-category or criminal data
Controllers and processors must keep a written record of their processing and show it to the supervisory authority on request; the exception for those employing fewer than 250 persons does not apply in three cases. The act in pictures

Read Article 30

Recitals

  1. 74
  2. 78
  3. 79
  4. 80
  5. 81
  6. 82
Eureka is adding links and definitions…