DPIA
DPIA
DPIAs should consider compliance risks, but also broader risks to the rights and freedoms of individuals,
including the potential for any significant social or economic disadvantage. The focus is on the potential
for harm – to individuals or to society, whether it is physical, material or non-material.
To assess the level of risk, a DPIA must consider both the likelihood of harm and the severity of any
impact on individuals.
A DPIA does not have to indicate that all risks have been eradicated. But it should help in
documenting and assessing whether or not any remaining risks are justified
1
Table of Contents
DATA PROTECTION IMPACT ASSESSMENT REPORT........................................................................ 1
Description of the processing operations ........................................................................................... 1
When should a DPIA be conducted? ................................................................................................. 1
1. Description of the processing operations ..................................................................................... 3
2. DESCRIBE THE PROCESSING .................................................................................................. 5
A. Data Map ................................................................................................................................. 6
B. The purpose of the processing ................................................................................................ 7
C. Nature of the processing .......................................................................................................... 7
D. Scope of the processing .......................................................................................................... 8
E. Context of the processing ........................................................................................................ 9
F. Consultation Process ............................................................................................................. 10
G. Necessity & Proportionality .................................................................................................... 11
H. Security .................................................................................................................................. 13
3. IDENTIFY & ASSESS RISKS .................................................................................................... 15
4. RISK MITIGATION ..................................................................................................................... 20
5. APPROVAL & SIGN OFF .......................................................................................................... 21
APPENDIX A – PRINCIPLES OF DATA PROTECTION ........................................................................ 22
APPENDIX B –PRIVACY RISKS ............................................................................................................ 24
APPENDIX C – ASSESSING RISK ........................................................................................................ 26
APPENDIX D – RAR RETURN SPREADSHEET ................................................................................... 27
2
1. Description of the processing operations
Name of Data Controller/ Data Processors:
Data controller: Committee of Student with Disabilities Fund (CSDF)
Data processor: Higher education Institutions (HEIs)
Postal Address: 10190-00200, NAIROBI KENYA
Email Address: studentempowerment.co.ke
Telephone Number: +254711034678
Under the KENYAN DATA PROTECTION ACT, 2019, DPIAs are mandatory for any new high-risk
processing projects. The DPIA process allows organizations to make informed decisions about the
acceptability of data protection and communicate effectively with the individuals affected.
Project or process:
Aggregated data is used for statistical and policy
purposes.
3
Required personal and special category data for
the purposes of determining FSD allocations is
requested and gathered on data subjects from
the Higher Education Institutions (HEIs). The
CSDF issues a excel template file to HEIs i.e.,
‘Resource Allocation Return’ (RAR). HEIs use
this template to gather the data during the
Summary of processing: academic year. HEIs forward their completed
return to the CSDF at the end of the academic
year. CSDF solely uses the data collected to
model FSD allocations for HEIs for the next
calendar year. The collated file is then
anonymised and saved on the drive and may be
used for non-personalised reporting of data on
FSD.
Need for a DPIA? Refer to risk The CSDF is responsible for processing sensitive
assessment findings. personal student data, including Special
Category Data.
- Data Sharing Agreements with
participating HEIs
Documentation which is relevant to - Annual FSD guidelines to Kenyan HEIs
this DPIA. - Internal standard operational procedures
pertaining to administration of FSD
(Allocations Modelling, RAR Verifications)
4
2. DESCRIPTION OF THE PROCESSING
Description of how and why the CSDF plan to use the personal data. Description includes
the purpose, scope and context of the processing.
Systems funding staff members who prepare FSD allocations process the personal
data collected.
The CSDF issues a ‘Resource Allocation Return’ template to HEIs at the beginning
ofthe academic year requesting HEIs to complete during the academic year. Data
collected include student reference number, information about student’s disability/s,
details of supports that were provided and costs incurred by the HEIs during the
academic year. Information such as level of the course attended, mode of study full
time/part time is required for statistical and policy purposes.
The spreadsheets are structured and specific tools such as drop-down lists and
formulae are implemented to ensure that the information is complete and consistent,
meeting the applicable standards. Once completed, HEIs password protect their
completed file and submits the return to the CSDF. The CSDF checks and verifies
the data for completeness and consistency, following an internal standard
operational procedure. The individual RARs are then collated into one file and
allocations are modelled.
5
A. Data Map
The data map outlines the flow of data between the participants, relevant
parties, processors and systems.
6
B. The purpose of the processing
□ Personal
Categories of personal data is being used
□ Special Category
□ Criminal
7
D. Scope of the processing
8
E. Context of the processing
Question Answer
9
Yes. If a student does not provide their personal
Could refusing participation impact the details, the institution cannot receive funding
individuals use of a service or application
of their rights? under the FSD in respect of such student’s
needs. However, institutions can provide
supports outside of the scope of FSD.
Are there any current issues of public Not that we are aware of.
concern that you should factor in? e.g.
monitoring of publicly accessible areas
Are you signed up to any approved code Not that we are aware of
of conduct or certification scheme (once
any have been approved)?
F. Consultation Process
The consultation process aim to incorporate the views of data subjects (where appropriate),internal
stakeholders (including DPO within participation organizations), external stakeholders and
independent experts.
Question Answer
Comments:
Are there any other data controllers □ Controllers
involved in this processing relationship? □ Joint Controllers
Comments:
Do you need to engage with these □ Yes
controllers? □ No
Comments:
Are there any data processors involved in □ Yes
this processing relationship? □ No
Comments:
Do you need to engage with these □ Yes N/A
processors? □ No
10
Data Processing Agreement Vendor Assurance Assessment
□ Yes □ Yes
□ No □ No
What measures do you take to ensure
processors comply?
Question Answer
□ Consent
□ Contract
□ Legal obligation
What is your lawful basis for processing?
□ Vital interests
□ Public task
□ Legitimate interests
□ Consent
□ Employment
□ Vital interests
□ Legitimate interests by foundation, association of non-profit
If applicable, what is your lawful basis for □ Publicly available information
processing special categories of data? □ Legal claims
□ Public interest
□ CSDFlthcare
□ Public interest regarding public CSDFlth
□ Archiving, research, or statistical purposes in public interest
Comments:
Is there any other legislation which
Data Protection Act 2019
supports this processing? e.g. Data □ Yes
Protection Act 2019, Statutory □ No
instruments, or other regulations.
11
Does the processing achieve your
Yes.
purpose?
How will you prevent data being used for The senior manager responsible for overseeing
a different purpose than for which it was the RAR collection process is aware of the
collected? i.e. function creep
sensitivity of the data and data protection
requirements. The relevant staff members are
also aware of these requirements and cognizant
that it is not permissible to use data for other
purposes.
12
The CSDF carry out checks of returns received
and liaises with institutions where issues are
identified. A standard operational procedure is in
place for processing of RAR returns.
□ Adequacy agreement
□ Standard contractual clauses
□ Binding corporate rules
If applicable, how will you safeguard the
□ Approved code of conduct
international transfer of personal data?
□ Approved certification mechanism
□ Approved ad-hoc contracts
□ Derogation
H. Security
Question Answer
13
Previously FSD related returns with
personal data were sent to the CSDF by
Are there prior concerns over this type of email. To reduce the risk to security of the
processing or security flaws? data, HEIs are now requested to submit
returns using the CSDFnet FileSend
facility
and use passwords agreed individually
between each institution and the CSDF.
The CSDF will explore the possibility
What is the current state of technology in this of implementing a portal to support
area? FSD operation, within its new CRM or
grantmanagement solution.
Is there new technology being used or new
No.
processing being conducted as part of the
project? e.g. new software to analyse data or new
methods of data collection etc.
14
3. IDENTIFICATION & ASSESSMENT OF RISKS
To effectively assess risks, the information provided in the previous sections should be reviewed and assessed against the principles of data protection (see
Appendix A) and universal privacy risks (Appendix B). Appendix C provides guidance on assessing risks.
If any of the risks outlined cannot be managed and the residual risk remains high, the Data Protection Commissioner must be contacted before moving
forward with the project, this is a requirement under Kenyan Data protection 2019 ACT.
Likelihood
Risk Level
Residual
1. Lawful, Fair & Transparent: Personal data is processed
Severity
Risk No. Mitigating Action
lawfully, fairly and in a transparent manner.
Risk
CSDF legislation is being updated.
Reasona
Minimal
CSDF legislation is not updated (CSDF Act 2020), the legal
1.1
Low
Low
ble
basis is not considered sufficient.
Reasonable
basis as FSD Guidelines are updated for the new
Medium
Information about data processing is not sufficiently
Some
1.2 academic year. Feedback received from the HEIs and
Low
transparent from the data subject’s point of view.
other stakeholders is considered.
Likelihood
Risk Level
2. Purpose limitation: Personal data is only collected for pre-
Residual
Severity
Risk No. specified, explicit and legitimate purposes and not for further Mitigating Action
processed if this is incompatible with those purposes.
Risk
That the student’s data will be further processed by the CSDF. The CSDF do not use the data except for the purpose Low
Remote
15
place to prevent further processing incompatible with the
purposes for which the data is being collected.
Likelihood
Risk Level
Residual
Severity
Risk No. and limited to what is necessary in relation to the purposes for Mitigating Action
which they are processed.
Risk
A review of the template is undertaken on annual basis Low
to ensure that only necessary data is collected.
That student data that is not required for FSD modelling
3.1
purposes will be forwarded to the CSDF for processing. RAR returns are checked upon receipt and if additional
Some
additional data deleted.
Residual
Severity
Risk No. Mitigating Action
necessary, kept up to date.
Risk
Thorough checks are undertaken by the CSDF staff to Low
That inaccurate or incorrect data on the data subject will be ensure that the data provided is complete and consistent
4.1
collected and stored by the CSDF. in order to mitigate this risk. Where issues are identified,
clarifications / corrections are requested from the HEIs.
Low
Low
16
5. Storage Limitation: Personal data shall be kept in a form
Likelihood
Risk Level
which permits identification of data subjects for no longer than
Residual
Severity
Risk No. Mitigating Action
is necessary for the purposes for which the personal data are
processed.
Risk
Low
That the student’s personal data will be kept for longer than
required
5.1
Identifying data are being removed by the CSDF
oncemodelling of allocations is completed.
Mitigating actions
Remote
Adherence to the CSDF’s data retention policy
Some
Low
6. Security, Integrity and Confidentiality: Personal data
Likelihood
Risk Level
Residual
Risk No. shall be processed in a manner that ensures appropriate Mitigating Action
Severity
security of the personal data.
Risk
Controls are implemented to safeguard against any Low
improper sharing or processing of data within the
CSDF. Only authorised CSDF staff members have
That the data subject’s information might be shared or
access to thedata and they are aware of the data
6.1 processed by persons who do not have the correct authority
protection implications, in line with the standard
Reasonable
17
protected using a password agreed separately with each
individual HEI.
Reasonable Likelihood
Risk Level
7. Accountability: It should be demonstrable that personal
Residual
Severity
Risk No. Mitigating Action
data is processed in line with data protection principles.
Risk
FSD Guidelines are circulated on annual basis, CSDF Low
That information available to external stakeholders about FSD engages with the sector via the DAWN group. The DPIA
7.1
Medium
and the relevant data processing is not sufficient. report and a data collection notice will be made available
Some
on the CSDF website.
Likelihood
Risk Level
Residual
Risk No. request for access, rectification, portability, or erasure of their Mitigating Action
Severity
personal data or to object to the processing method.
Risk
The CSDF might not be able to support the right to Low
erasure and the right to object. Other data subjects’
That data subjects will not be able to exercise their rights over rights will be supported.
8.1
their data.
Remote
The CSDF will be transparent about the above
Some
limitationsto data subjects’ rights.
Low
9. Transfers to Third Countries: Personal data shall only be Likelihood
Risk Level
passed on to within Kenya as an adequate level of privacy
Residual
Severity
Risk No. Mitigating Action
protection.
Risk
Low
The data is not intended to be provided to subjects outside All staff who has access to FSD data is aware of the
9.1
Kenya. applicable restrictions in place.
Remote
Some
Low
18
Access to data is restricted to authorised CSDF staff
members only. Password protection is applied on files
that are being sent between the CSDF and the HEIs.
Likelihood
Risk Level
Residual
Severity
Risk No. 10. Other risks. Mitigating Action
Risk
10.1 No FSD specific other risks have been identified.
19
4. RISK MITIGATION
20
5. APPROVAL & SIGN OFF
Comments:
Business Owner
21
APPENDIX A – PRINCIPLES OF DATA PROTECTION
The starting point of a DPIA is to identify the relevant privacy principles. Based on research from
different sources, several privacy principles are identified, which are relevant to an assessment of the
design of a new system or change in existing processing of personal data or another use of existing
systems and related data processing.
1. Lawfulness, fairness and transparency: Personal data shall be processed lawfully, fairly and in
a transparent manner.
2. Purpose limitation: Personal data shall be collected for specified, explicit and legitimate
purposes and not further processed in a manner that is incompatible with those purposes; further
processing for archiving purposes in the public interest, scientific or historical research purposes
or statistical purposes shall, in accordance with Article 89(1) of the GDPR, not be considered to
be incompatible with the initial purposes.
Will this new project/processing activity involve data being processed in a manner for which it
was not collected?
Have we been transparent about any extra processes? Is the processing still lawful?
3. Data minimisation: Personal data shall be adequate, relevant and limited to what is necessary in
relation to the purposes for which they are processed.
4. Accuracy: Personal data shall be accurate and, where necessary, kept up to date; every
reasonable step must be taken to ensure that personal data that are inaccurate, having regard to
the purposes for which they are processed, are erased or rectified without delay?
Are there measures which guarantee the accuracy and correctness of the personal data
processed within the information system?
Can data be updated, where required?
How often is data updated? Is this frequently enough?
5. Storage Limitation: Personal data shall be kept in a form which permits identification of data
subjects for no longer than is necessary for the purposes for which the personal data are
processed; personal data may be stored for longer periods insofar as the personal data will be
processed solely for archiving purposes in the public interest, scientific or historical research
purposes or statistical purposes in accordance with Article 89(1) subject to implementation of the
appropriate technical and organisational measures required by this Regulation in order to
safeguard the rights and freedoms of the data subject.
22
6. Integrity and Confidentiality: Personal data shall be processed in a manner that ensures
appropriate security of the personal data, including protection against unauthorised or unlawful
processing and against accidental loss, destruction or damage, using appropriate technical or
organisational measures.
7. Accountability: The responsible entities also known as “controllers” take measures to implement
programs to eliminate or mitigate privacy risks on strategic, tactical and operational level.
Assurance of these measures includes the proof of monitoring of these risks, internal and/or
external audit and potentially reporting to external stakeholders like privacy authorities or data
protection regulators.
8. Rights of Individuals: Citizens and consumers have the right request for access, rectification,
portability, or erasure of their personal data or to oppose the processing method. The individual
may ask which authorities have been provided with personal data and which authorities have
received their personal data.
Does the system impose restrictions on the ability to comply with valid subject right requests?
23
APPENDIX B –PRIVACY RISKS
There are a range of different ways that an individual’s data privacy can be compromised or put at risk
by a new project. The types of risk range from the risk of causing distress, upset or inconvenience to
risks of financial loss or physical harm. There are equally as many kinds of data privacy-related risks
to organisations, related to compliance issues and commercial factors.
You should include an assessment of the security risks, including sources of risk and the potential
impact of each type of breach (including illegitimate access to, modification of or loss of personal
data).
Non-compliance with legislation can lead to sanctions, fines and reputational damage.
Problems which are only identified after the project has launched are more likely to require
expensive fixes.
The use of biometric information or potentially intrusive tracking technologies may cause
increased concern and cause people to avoid engaging with the organisation.
Information which is collected and stored unnecessarily or is not properly managed so that
duplicate records are created, is less useful to the business.
Data losses which damage individuals could lead to claims for compensation.
Public distrust about how information is used can damage an organisation’s reputation and
lead to loss of business.
24
Examples of Compliance Risks
25
APPENDIX C – ASSESSING RISK
Consider the potential impact on individuals and any harm or damage your processing may cause –
whether physical, emotional or material. In particular, look at whether the processing could contribute
to:
You should include an assessment of the security risks, including sources of risk and the potential
impact of each type of breach (including illegitimate access to, modification of or loss of personal
data).
To assess whether the risk is a high risk, you need to consider both the likelihood and severity of the
possible harm. Harm does not have to be inevitable to qualify as a risk or a high risk. It must be more
than remote, but any significant possibility of very serious harm may still be enough to qualify as a
high risk. Equally, a high probability of widespread but more minor harm may still count as high risk.
You must make an objective assessment of the risks. It is helpful to use a structured matrix to think
about likelihood and severity of risks:
26
APPENDIX D – RAR RETURN SPREADSHEET
Blank RAR
Return.xlsx
27