The DPA reprimanded a controller for not appropriately clarifying whether its processing operations were based on consent or a contract.
What Happened?
Following the implementation of the GDPR in 2018, the controller reassessed its legal basis for processing personal data and began primarily relying on contractual necessity under Article 6(1)(b) GDPR or legitimate interest under Article 6(1)(f) GDPR, instead of consent, for magazine subscriptions.
However, the controller missed updating the registration form on one of its webshops, Magasinshoppen. The webshop's registration form included a checkbox with the text, "I accept the subscription terms. By doing so, I consent to the processing of personal data within the Bonnier Group." Additionally, the subscription terms stated, "When ordering, you agree that your personal data, including email address, mobile phone number for calls and text messages, and any other digital addresses, may be stored and used within Bonnier for digital services, marketing, and for statistical and analytical purposes." Information on the right to withdraw consent was also provided.
After the DPA's inspection began, the controller immediately corrected the information in their webshop's registration process. Now, instead of presenting a consent request or consent information text, the data subject is asked to agree to the subscription terms (i.e., the terms of purchase) and confirm they have read the controller’s data protection policy.
What does it mean for your organisation?
When collecting personal data from a data subject, the controller is required under Article 13(1)(c) of the GDPR to inform the data subject about the legal bases for processing. Article 12(1) of the GDPR mandates that the controller provide this information in a concise, clear, intelligible, and easily accessible form, using plain language.
In the described case, the DPA determined that the text next to the checkbox on the controller’s website gave the impression that the legal basis for processing personal data was consent under Article 6(1)(a) of the GDPR. This impression was further reinforced by the subscription terms and the provided information on the right to withdraw consent. Since the controller actually based its processing on contract (Article 6(1)(b) GDPR) and legitimate interests (Article 6(1)(f) GDPR), the DPA found that the controller violated Article 13(1)(c) GDPR by indicating an incorrect legal basis.
Thus, the main lesson that should be taken form this case is to regularly review not only your policies and procedures, but also other documents where data protection information can be met, loke terms & conditions, agreements, notices etc. This also includes updating all references that can be already out-of-date or replaced by another document. It is good practice to review your documentation and audit website once per year, which you can do by yourself or with the help of our specialists.
Tales from the coalface
Each month we look at the most prevalent Data Protection concerns raised by our clients. This month, we were asked whether an individual can be a data controller.
Article 4 of the GDPR says that ‘controller’ means the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data. Therefore, the absence of legal entity status does not preclude the recognition of any person or group of people as the data controller.
The EDPB's Guidelines 07/2020 on the concepts of controller and processor in the GDPR clarify that non-legal entities can be data controllers. However, when companies and public bodies appoint a specific individual to ensure compliance with data protection rules, this person acts on behalf of the legal entity, which remains the ultimate controller responsible for any infringements. Similarly, if a particular department or unit within an organisation oversees compliance for certain processing activities, it does not become the controller; the organisation as a whole retains that role.
For example, if the marketing department of Company ABC independently manages an advertising campaign, deciding its nature, means (e-mail, social media, etc.), target customers, and data usage, Company ABC is still considered the controller. This is because the campaign is launched by the company and occurs within its business activities and purposes.
Thus, the main threshold for deciding whether the natural person or group of people without legal entity status can be the data controller is establishing who determines the purposes and means of the processing of personal data
The same the EDPB Guidelines clarify that an assessment of controllership, or joint controllership, is a factual assessment. This is because the concept of a controller is a functional concept, which aims to “allocate responsibilities according to the actual roles of the parties”. “One should look at the specific processing operations in question and understand who determines them by first considering the following questions: "why is this processing taking place?” and “who decided that the processing should take place for a particular purpose?
With respect to the means of processing, a controller must determine the essential rather than the non-essential means of processing. The EDPB indicates that essential means are means that are closely linked to the purpose and the scope of the processing, such as the type of personal data which are processed, the duration of the processing, the categories of recipients and the categories of data subjects.
For example, in its matter of Archbishop of Dublin, the DPC considered each of the data processing separately to establish whether the Archbishop and the parish priest are joint controllers or the Archbishop is sole controller with respect to different processing activities.
On the hand, in its Case study 17, the DPC established that the investigator (deemed by the data controller as an independent data controller) was provided a list of individuals to interview in order to compile the report and from the terms of reference, interviews are listed as the primary means of gathering information to compile their report. The DPC also noted the investigator was precluded from deciding on or implementing any sanction arising from the findings of the report. Based on this information, the DPC found the investigator as a data processor on behalf of the data controller and noted that the data controller failed to provide a contract between them and the investigator as required under Article 28(3) of the GDPR.
In other words, if a natural person determines "whose" personal data and "which" personal data are being processed, for how long, and who shall have access to them, they are likely to be found as a data controller. Otherwise, joint controllership or status as a data processor might be considered more appropriate.

