Example GDPR Data Mapping Impact Assessment
Example GDPR Data Mapping Impact Assessment
Provided to clients and prospects by Voyager Software Ltd, part of Dillistone Group Plc.
Overview
Process Overview Volume of data Type of data processed
Payroll - Pension
Payroll - SAYE
Payroll - Banking
Retail Mortgages 250 per month Online forms
Hardcopy forms
Term Loans
DPR Impact Assessment)
Monthly processing of Both (if new starters) Core Sage payroll data files Operations Director, MD
payroll information for encrypted. Payslips only through core Sage
staff including password protected. Data application. MD, OD &
commissions, SSP, SMP, directory restricted access. head of tech ops for
leaver and holiday pay. Finance only given network file location.
New starters/leavers sufficient data to do
processed as required. Management accounts.
Processing of Mortgage Both (if new Data directory restricted Mortgage Assessors
applications applicants) access
Password protected
application
Only Mortgage Assessors
have permission
Data flow
Information Owner Observati Actions Compliant? Who are data How do you get it?
ons subjects?
Retail Director
Where does it go through your organisation? How is it stored?
Manually keyed from subject provided data into Manual data held in locked
Sage Payroll, stored on Group drive (encrypted and HR cabinet.
restricted). Payslips sent as password protected
emails. Reports stored on network, relevant data Electronic data in
keyed into online banking for payment. Relevant restricted/encrypted
data keyed into Pension online portal for payment. network location.
Relevant data passed to finance team for
management accounting. Relevant data passed via Restrictions persisted into
Sage to HMRC for FPS submissions. Selected data on and offsite backups.
given to HM Gov for annual earnings survey
Does it leave your Does it leave Observations Actions
organisation? borders?
Partial data is sent to HMRC for No It is assumed that staff Improve visibility of the
reporting purposes (FPS/year have "joined the dots" in data flow to the data
end etc.). some cases where data is subjects but documenting
sent to other processors where it may be sent and
Partial data is sent to Pension (e.g. via SAYE) this should what data is sent.
provider (name, address, NINO, perhaps be more clear
contribution).
Improve visibility of the Compliant Staff know they can Actually most staff not
data flow to the data request access to their aware what this means.
subjects but documenting data via the section in the LOW RISK
where it may be sent and handbook
what data is sent.
Actions Compliant? Right to rectification Observations
Education of staff needed No Staff can self rectify via the Requires picking up and
here HR system. processing of the
automated email to payroll
team from the HR system
to action LOW RISK
Actions Compliant? Right to erasure Observations
Compliant Staff are aware of right via Staff are unlikely to restrict
hand book and hence prevent their
payroll being run! LOW
RISK
Actions Compliant? Right to data portability Observations
Data minimisation has led Compliant Staff can amend their own
to some difficulties with data indirectly via the HR
accounts audits where system.
specific requested data
has to be constructed from Payroll process means
various sources. LOW RISK payslips are distributed
several hours in advance
of cut-off for mistakes to
be rectified.
Compliant
Overview
Data flow
Principles of GDPR
Process Overview
Volume of data
Type of data processed
Description of processing
New/Existing data?
Security
Who can access?
Information Owner
Observations
Actions
Compliant?
Right to be informed
Right of Access
Right to rectification
Right to erasure
Right to restrict processing
Right to data portability
Right to object
Rights regarding automated decision-making and profiling