⚠️ When to Use This Template: A DPIA is required for processing that is likely to result in a high risk to individuals' rights and freedoms. This includes:
- New technologies or systems processing personal data
- Large-scale processing of special category data (e.g., health data)
- Systematic monitoring or profiling
- Processing that could result in discrimination or exclusion
Step 1: Identify the Need for a DPIA
Screening Questions
Answer these questions to determine if a DPIA is required:
Does the processing involve special category data (e.g., health data) or criminal conviction data on a large scale?
Does the processing involve systematic monitoring of publicly accessible areas on a large scale?
Does the processing use new technologies or innovative applications?
Does the processing involve profiling or automated decision-making with significant effects?
Does the processing involve processing children's data on a large scale?
Does the processing prevent data subjects from exercising their rights or accessing services?
Does the processing combine or match datasets from different sources?
Does the processing involve data about vulnerable data subjects?
Step 2: Describe the Processing
Step 3: Consultation Process
3.1 Internal Consultation
3.2 Data Subject Consultation
Step 4: Assess Necessity and Proportionality
Necessity and Proportionality Assessment
Step 5: Identify and Assess Risks
Assessing Risk: Consider risks to individuals' rights and freedoms, not just organisational risks. Think about:
- Physical, material, or non-material damage
- Loss of control over personal data
- Discrimination or identity theft
- Financial loss or damage to reputation
- Loss of confidentiality
- Unauthorised reversal of pseudonymisation
- Economic or social disadvantage
Risk Assessment Matrix
Likelihood: Low / Medium / High
Severity: Minimal / Significant / Severe
Overall Risk: Low / Medium / High
| Risk Description |
Likelihood |
Severity |
Overall Risk |
Affected Individuals |
| [e.g., Unauthorized access to sensitive health data] |
[Low/Med/High] |
[Min/Sig/Sev] |
[Low/Med/High] |
[Service users] |
| [Risk 2] |
|
|
|
|
| [Risk 3] |
|
|
|
|
| [Add more rows as needed] |
|
|
|
|
Step 6: Identify Measures to Mitigate Risks
Risk Mitigation Measures
For each risk identified above, document mitigation measures:
| Risk |
Mitigation Measures |
Responsible Person |
Residual Risk |
Status |
| [Risk 1] |
[e.g., Encryption, access controls, MFA, security monitoring] |
[Name/Role] |
[Low/Med/High] |
[Planned/ In Progress/ Complete] |
| [Risk 2] |
|
|
|
|
| [Risk 3] |
|
|
|
|
Security Measures
Specific technical and organisational measures to protect personal data:
Encryption in transit (TLS 1.3)
Encryption at rest (AES-256)
Multi-factor authentication
Role-based access controls
Regular security audits/penetration testing
Staff training on data protection and security
Incident response procedures
Regular backups with secure storage
Secure disposal procedures
Step 7: Sign Off and Record Outcomes
Approvals
| Role |
Name |
Date |
Signature/Approval |
| Prepared By: |
[Name] |
[Date] |
|
| Data Protection Officer: |
[DPO Name] |
[Date] |
|
| Approved By (Senior Management): |
[Name & Title] |
[Date] |
|
Step 8: Integrate Outcomes into Project Plan
Integration and Monitoring
Appendices
Supporting Documentation
Attach or reference supporting documents:
- Data flow diagrams
- System architecture diagrams
- Consultation responses
- Security assessment reports
- Privacy notices
- Data Processing Agreements
- Other relevant documentation