Data Protection Impact Assessment
Data Protection Impact Assessment
Pursuant to Article 35(4) of the General Data Protection Regulation (GDPR), the Irish Data
Protection Commission adopts the following list specifying the types of processing operations
subject to the requirement for a Data Protection Impact Assessment (DPIA). This list further
specifies the requirement set out in Article 35(1) GDPR and, as such, this list is not exhaustive
of the instances in which a DPIA will be required. The list is also without prejudice to the
requirement to conduct a DPIA pursuant to Article 35(3) GDPR.
The list is intended to encompass both national and cross-border data processing and reflects
feedback received during public consultation. The list has also been approved by the European
Data Protection Board (EDPB) where it includes processing operations relating to the provision
of goods and services to individuals or the monitoring of their behaviour in several Member
States or which may substantially affect the free movement of data within EU.
1. GDPR Article 35(1) requires a DPIA to be conducted in cases where a type of processing
is likely to result in a high risk to the rights and freedoms of individuals, taking into
account the nature, scope, context and purposes of the type of processing. This is likely
to be the case if the processing involves new technologies.
2. GDPR Article 35(3) states that DPIAs are mandatory in a number of processing
scenarios. These arise where a data controller performs automated decision-making
based on personal data profiling, large scale processing of special categories of data or
systematic monitoring of publicly accessible areas on a large scale.
1
The Irish Data Protection Act 2018, Section 84 transposing Article 27 of the Law Enforcement Directive
also requires that a DPIA shall be conducted where certain processing, in particular using new
technology, is likely to result in a high risk to the rights and freedoms of individuals, and when
conducted for law enforcement purposes.
In addition, the Working Party 29 Guidelines WP248 (WP29 DPIA Guidelines which were
endorsed by the European Data Protection Board on 25 May 2018) state that in most cases, a
data controller will require a DPIA when processing meets two of the criteria listed in the WP29
DPIA Guidelines (as set out on pages 9-11). However, in some cases, the WP29 DPIA Guidelines
considers that processing meeting only one of these criteria requires a DPIA. The criteria
developed in the WP29 DPIA Guidelines were applied in the development and approval of this
list to support the consistent application of the GDPR.
As a controller, under the GDPR an organisation will need to assess, decide and document
whether a DPIA is necessary for each proposed data processing operation. Records of
processing operations should include relevant risk information including reasons why a DPIA
needs to be carried out, or not.
If an organisation does need to complete a DPIA, the DPC has published guidance on the steps
to follow. The guidance is available at http://gdprandyou.ie/dataprotection-impact-
assessments-dpia/
1) Use of personal data on a large-scale for a purpose(s) other than that for which it was
initially collected pursuant to GDPR Article 6(4).
2) Profiling vulnerable persons including children to target marketing or online services at
such persons.
3) Use of profiling or algorithmic means or special category data as an element to
determine access to services or that results in legal or similarly significant effects.
4) Systematically monitoring, tracking or observing individuals’ location or behaviour.
5) Profiling individuals on a large-scale.
6) Processing biometric data to uniquely identify an individual or individuals or enable or
allow the identification or authentication of an individual or individuals in combination
with any of the other criteria set out in WP29 DPIA Guidelines.
7) Processing genetic data in combination with any of the other criteria set out in WP29
DPIA Guidelines.
8) Indirectly sourcing personal data where GDPR transparency requirements are not being
met, including when relying on exemptions based on impossibility or disproportionate
effort.
9) Combining, linking or cross-referencing separate datasets where such linking
significantly contributes to or is used for profiling or behavioural analysis of individuals,
particularly where the data sets are combined from different sources where processing
was/is carried out for difference purposes or by different controllers.
10)Large scale processing of personal data where the Data Protection Act 2018 requires
“suitable and specific measures” to be taken in order to safeguard the fundamental
rights and freedoms of individuals.
This list does not remove the general requirement to carry out proper and effective risk
assessment and risk management of proposed data processing operations nor does it exempt
the controller from the obligation to ensure compliance with any other obligation of the GDPR
or other applicable legislation. Furthermore, it is good practice to carry out a DPIA for any
major new project involving the use of personal data, even if there is no specific indication of
likely high risk.
With reference to point 1 above, where an organisation wishes to use personal data for
purposes other than for which it was originally collected, Article 6(4) of the GDPR requires the
organisation to do a compatibility test. That test should take into account any links between
the original and new purposes, the context in which the data was collected (in particular the
relationship between the individual and the organisation, the type of personal data involved
(i.e. special categories of data), the possible consequences for individuals of the further
processing, and if appropriate safeguards exist (i.e. encryption or pseudonymisation).
Further information and references
• Further information on risk, systematic processing, vulnerable data subjects and new
technology is available in EDPB Guidelines WP 248 rev.01 “Guidelines on Data Protection
Impact Assessment (DPIA) and determining whether processing is ‘likely to result in a high risk’
for the purposes of Regulation 2016/679”