1. What a DPIA is in plain terms
DPIA stands for Data Protection Impact Assessment. It is a structured analysis that describes a processing activity, assesses the risks it may create for individuals and sets out the measures to reduce them. It is not a form to complete for everything: it is reserved for processing that may present a high risk to the rights and freedoms of individuals.
A DPIA does not prove that the processing is perfect. It shows that you thought about the risks before starting, that you decided with awareness and that you applied proportionate measures. If the risk remains high despite those measures, the regulation provides for a further step of prior consultation with the authority, which you should handle with a consultant before starting the processing.
2. When it is mandatory: the high-risk test
The underlying test is simple to state and harder to apply: a DPIA is required when a processing activity is likely to result in a high risk to individuals, taking into account its nature, scope, context and purposes. It depends on what you process, how you process it and on what scale. It is not enough that the processing involves personal data, because almost every company handles some. You need to assess whether the risk is genuinely high.
The regulation cites some typical cases, such as systematic evaluation of personal aspects based on automated processing, large-scale processing of special category data and systematic monitoring of publicly accessible areas. These are not a closed list and do not cover every case. If you decide that no DPIA is needed, document why you consider the risk not to be high, with reasoning that would stand up to scrutiny.
3. The Garante's list: how to read it
The Garante for the protection of personal data (the Garante, Italy's data protection authority) has published a list of types of processing for which a DPIA is required. It is an important orientation tool, but it should be read neither as exhaustive nor as a shortcut. A processing activity not on the list may still require an assessment, and one that appears on it may not require one in a very simple context. Check the most recent version of the text, because the guidance may be updated.
To use it well, compare your processing with the descriptions in the list, not with the generic name of the project. If a project using surveillance technologies, large-scale analysis or profiling resembles one of the entries, resolve the doubt before launching it. Note in the file which entry you considered and why you concluded one way or the other.
4. Factors that raise the risk
Some characteristics of a processing activity almost always increase the risk and deserve particular attention. They are indicators to consider together, not automatic rules: a single factor rarely settles the matter, but a combination of several almost always calls for an assessment. If your project shows two or more, that is the right moment to stop and carry out the analysis before investing in development or purchases.
- Special category data, such as health or biometric data, or data relating to sexual orientation or opinions.
- Vulnerable individuals, for example children, patients or workers in a position of dependency.
- Systematic monitoring of people or spaces, including through cameras or sensors.
- Evaluation or scoring of personal aspects, such as reliability, behaviour or preferences.
- Large-scale processing, by number of people, volume of data or duration.
- Matching of different databases, for purposes not foreseen at the outset.
- Automated decisions that significantly affect the individual.
5. What the assessment must contain
A well-prepared DPIA follows a logical sequence. It is not a form to fill in over a morning: it requires understanding the processing, speaking with the people who run it and writing the conclusions so that an authority or reviewer can follow the reasoning. The regulation sets out the minimum elements, which in practice can be ordered as in the list below. Write in plain language and link each risk to a concrete measure. An assessment that lists generic risks without saying who does what, and with which tools, proves nothing, however long and well formatted it is.
- Describe the processing: purposes, data, individuals involved, suppliers and retention periods.
- Verify necessity and proportionality: does the processing really serve the purpose, and could the same aim be achieved with less data?
- Identify the risks to individuals' rights and freedoms, with their likelihood and severity.
- List the measures planned to reduce each risk, both technical and organisational.
- Assess the residual risk, meaning what remains after the measures, and whether it is acceptable.
- Document the opinion of the DPO, where there is one, and the decisions taken.
6. Who prepares it and which evidence to keep
The DPIA is the controller's responsibility, that is, the company's. It can be prepared internally by people who know the process, with support from a consultant and from your IT supplier for the technical part. If a DPO is in place, they must be consulted, and their opinion should be documented together with the decisions the company takes, including when it chooses to depart from it. The person who signs the assessment must be named.
Keep the document with its date, version and a list of the people who took part. If the processing changes substantially, the assessment must be reviewed. A well-ordered file is the most useful proof in case of inspection: it shows that the risk was considered before the start, not reconstructed after a problem. Keep earlier versions too, with their dates.
7. What to confirm with a consultant or the Garante
Some questions cannot be settled alone. If, after the analysis, the residual risk is still high, the regulation requires prior consultation with the supervisory authority before the processing starts. This step should be handled with a legal adviser or whoever looks after privacy in your company, because timing and procedure need careful management rather than improvisation. Prepare your questions.
Bring the consultant the description of the processing, the risk assessment and the planned measures. Ask them to confirm three things: whether a DPIA is required in your case, whether the judgement on residual risk is correct, and whether there are further obligations for the suppliers involved. Do not rely on generic answers found online for decisions with operational consequences. Also note the answers you receive and the date.
8. How to start
This week, take the most recent project or processing activity that involves sensitive data, new technologies or monitoring of individuals. Compare it with the types on the Garante's list and with the risk factors in this guide. Write a one-page answer: the processing does or does not require a DPIA, and why. Attach it to the record of processing activities, so that the reasoning stays visible.
If the answer is yes, open the file and assign an owner. If it is no, document the assessment anyway. In both cases the decision must be written and dated, because that written record is what shows the doubt was addressed before starting. An unwritten decision, even a correct one, cannot be demonstrated. Keep the note with its date and the name of the person who approved it.
Frequently Asked Questions
Is a DPIA always required for a surveillance camera?
Not always, but monitoring of publicly accessible areas or of individuals is one of the factors that deserve the most attention. It depends on the number of cameras, the areas covered, the purposes and whether the images are linked to other systems. Before installing, assess the case with a consultant and document the conclusion.
If the processing does not require a DPIA, can I simply do nothing?
No. Even when an impact assessment is not mandatory, the processing still needs to be assessed against the regulation's general principles, such as security and data minimisation. Documenting why you concluded that the risk is not high is good practice and protects you if someone asks for an explanation later.
Is a DPIA the same thing as the record of processing activities?
No. The record describes all processing activities in essential form. A DPIA is an in-depth analysis of one or more processing activities that may present high risks, with an assessment of the risks and of the measures. The record is a list; the DPIA is a reasoned analysis. The two are linked, because the information in the record is the basis from which the assessment starts.
Who can carry out the DPIA within the company?
Responsibility lies with the company as controller. Operationally, it can be prepared by an internal person who knows the process, with input from the IT manager and the consultant. You do not need an external expert for every case, but you do need adequate expertise on the processing and its risks. The DPO's opinion, where there is one, must be documented.
How much does a DPIA cost?
The cost depends on the complexity of the processing, the number of suppliers involved and whether in-depth technical checks are needed. There is no standard figure. Ask several consultants for a quote based on your scope and compare what is included: description, risk analysis, measures and final documentation.