What Happened?
The DPC received a complaint involved in a workplace investigation arising out of allegations made by the complainant against a colleague. The complainant’s employer appointed an independent consultancy firm (the “consultancy company”) to carry out the investigation and the findings of the consultancy company were subject to a review by an independent panel.
Following the workplace investigation's conclusion, the complainant submitted a data access request to their employer, resulting in the provision of several documents. However, the complainant contended that the response was incomplete. Specifically, they argued that the provided witness statements contained factual inaccuracies and certain documents were not provided. Additionally, the complainant accused their employer of disclosing their work performance details, sick leave arrangements, and copies of pay slips to colleagues without consent. Furthermore, the complainant asserted that their employer failed to address requests for rectification of the allegedly inaccurate witness statements.
The DPC was of the view that there were five issues to be examined by it in relation to the complaint, which we can use as guidelines.
1. Access request
The DPC noted that the complainant had made a valid access request and the organisation provided all available information. At the same time, the data controller failed to answer in the timeframe required under the legislation.
Remember, the data controller must respond to a subject access request without undue delay and in any event within one month of receipt of the request.
2. Alleged unauthorised disclosure of the complainant’s personal data
In relation to the disclosure of details regarding the complainant’s work performance, the DPC was of the opinion that such processing was lawful as it was for legitimate business reasons. By contrast, the disclosure of sick leave details, it did not have sufficient information relating to the alleged incident in order to determine whether a breach of the legislation had occurred, which lead to the violation of the GDPR.
Controllers always must have a lawful basis, under data protection legislation to process personal data, including the disclosure of that data to a third party.
3. Fair processing
The data controller failed to provide the information how it complied with its obligations to process the complainant’s data in a fair manner, in relation to each of the alleged disclosures of the complainant’s personal data.
Under the GDPR, personal data must be processed lawfully, fairly and in a transparent manner in relation to the data subject. That principle requires that the data subject be provided with certain information under Articles 13 and 14 of the GDPR in relation to the existence of the processing operation and its purposes. Data subjects should be made aware of risks, rules, safeguards and tights in relation to the processing of their personal data.
4. Right to rectification
Under Article 5 of the GDPR, personal data being processed must be accurate and, where necessary, kept up to date and data controllers are required to ensure that every reasonable step is taken to ensure that personal data that are inaccurate, having regard to the purpose for which they are processed, are erased or rectified without delay.
It was determined that in cases where an opinion is accurately documented and is objectively based on information that the individual providing the opinion reasonably believed to be accurate, the right to rectification does not apply.
5. Retention of the complainant’s personal data
Under the GDPR, not only must a data controller have a lawful basis for initially obtaining an individual’s personal data, but it must also have an ongoing legal basis for the retention of those data in accordance with Article 6, as set out above.
The data controller proved that this data was being retained in order to deal with the complainant’s requests and appeals under various statutory processes.
Tales from the coalface
Each month we look at the most prevalent Data Protection concerns raised by our clients. This month we were asked in what cases the appointment of DPO is mandatory.
A company is obliged to appoint a Data Protection Officer (DPO) under the GDPR if:
1) The processing is carried out by a public authority or body, except for courts acting in their judicial capacity.
If your organisation is a public authority or body, it is mandatory to appoint a DPO. However, courts acting in their judicial capacity are excepted from this requirement. The definition of a public authority or body is determined by national law. Accordingly, public authorities and bodies include national, regional and local authorities, but the concept, under the applicable national laws, typically also includes a range of other bodies governed by public law.
A public task may be carried out, and public authority may be exercised not only by public authorities or bodies but also by other natural or legal persons governed by public or private law, in sectors such as, according to national regulation of each Member State, public transport services, water and energy supply, road infrastructure, public service broadcasting, public housing or disciplinary bodies for regulated professions.
2) The core activities of the controller or the processor consist of processing operations which, by virtue of their nature, their scope, and/or their purposes, require regular and systematic monitoring of data subjects on a large scale.
According to Recital 97 of the GDPR, the core activities of a controller are primary operations that do not include ancillary data processing. In essence, these core activities represent the key operations required to achieve the goals of the controller or processor.
However, ‘core activities’ should not be interpreted as excluding activities where the processing of data forms an inextricable part of the controller’s or processor’s activity. For example, the core activity of a hospital is to provide health care. However, a hospital could not provide healthcare safely and effectively without processing health data, such as patients’ health records. Therefore, processing these data should be considered to be one of any hospital’s core activities and hospitals must therefore designate DPOs.
3) The core activities of the controller or the processor consist of processing on a large scale of special categories of data pursuant to Article 9(1) of the GDPR or personal data relating to criminal convictions and offenses referred to in Article 10 of the GDPR.
The special category of data listed in the Article 9(1) of the GDPR includes racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person’s sex life or sexual orientation.
The GDPR does not define what constitutes large-scale processing. However, the Article 29 Data Protection Working Party (WP29), which has been replaced by the European Data Protection Board (EDPB), provided guidance on factors to consider when determining if processing qualifies as large-scale. These factors include:
The number of data subjects concerned – either as a specific number or as a proportion of the relevant population;
The volume of data and/or the range of different data items being processed
The duration, or permanence, of the data processing activity
The geographical extent of the processing activity.
Processing of travel data of individuals using a city’s public transport system (e.g. tracking via travel cards) or processing of real time geo-location data of customers of an international fast food chain for statistical purposes by a processor specialised in these activities are good examples of large scale of data processing.
Remember that the appointment of a DPO is crucial for ensuring compliance with data protection laws. If your organisation falls into any of the mandatory categories mentioned above, consider appointing a qualified DPO to fulfil this important role.

