Menu

Aims

Swift aims to ensure that all personal data collected about staff, learner, parents, visitors and other individuals is collected, stored and processed in accordance with the General Data Protection Regulation (GDPR) and the expected provisions of the Data Protection Act 2018 (DPA 2018) as set out in the Data Protection Bill.

This policy applies to all personal data, regardless of whether it is in paper or electronic format.


Legislation and Guidance

This policy meets the requirements of the GDPR and the expected provisions of the DPA 2018. It is based on guidance published by the Information Commissioner’s Office (ICO) on the GDPR and the ICO’s code of practice for subject access requests.
It also reflects the ICO’s code of practice for the use of surveillance cameras and personal information.



Definitions

Business purposes

The purposes for which personal data may be used by us:

Personnel, administrative, financial, regulatory and business development purposes.

Business purposes include the following:

  • Compliance with our legal, regulatory and corporate governance obligations and good practice
  • Gathering information as part of investigations by regulatory bodies or in connection with legal proceedings or requests
  • Ensuring business policies are adhered to (such as policies covering email and internet use)
  • Operational reasons, such as recording transactions, training and quality control, ensuring the confidentiality of commercially sensitive information, security vetting, credit scoring and checking
  • Investigating complaints
  • Checking references, ensuring safe working practices, monitoring and managing staff access to systems and facilities and staff/learner absences, administration and assessments

✓ Monitor staff/learner conduct, disciplinary matters

✓ Marketing our business

✓ Improving service


Personal data

Any information relating to an identified, or identifiable, individual.

This may include the individual’s:

  • Name (including initials)
  • Contact details
  • Identification number
  • Prior learning
  • Location data
  • CV
  • Online identifier, such as a username

It may also include factors specific to the individual’s physical, physiological, genetic, mental, economic, cultural or social identity.


Special categories of personal data

Personal data which is more sensitive and so needs more protection, including information about an individual’s:

  • Racial or ethnic origin
  • Political opinions
  • Religious or philosophical beliefs
  • Trade union membership
  • Health – physical or mental
  • Sexual orientation
  • Criminal offences or related proceedings


Processing

Anything done to personal data, such as collecting, recording, organising, structuring, storing, adapting, altering, retrieving, using, disseminating, erasing or destroying.

Processing can be automated or manual.


Data subject

The identified or identifiable individual whose personal data is held or processed.


Data controller

A person or organisation that determines the purposes and the means of processing of personal data.


Data processor

A person or other body, other than an employee of the data controller, who processes personal data on behalf of the data controller.


Personal data breach

A breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to personal data.



The Data Controller

Swift processes personal data relating to parents, learners, staff, visitors and others, and therefore is a data controller.

Swift is registered as a data controller with the ICO and will renew this registration annually or as otherwise legally required.


Roles and Responsibilities

This policy applies to all staff employed by Swift and to external organisations or individuals working on our behalf. Staff who do not comply with this policy may face disciplinary action.


Board of Directors
The Board of Directors has overall responsibility for ensuring that Swift complies with all relevant data protection obligations.


Data Protection Officer

The Data Protection Officer (DPO) is responsible for overseeing the implementation of this policy, monitoring our compliance with data protection law, and developing related policies and guidelines where applicable.

They will provide a report of their activities directly to the Board of Directors and, where relevant, report to the board their advice and recommendations on Leaping Man data protection issues.

The DPO is also the first point of contact for individuals whose data Leaping Man processes, and for the ICO.
Full details of the DPO’s responsibilities are set out in their job description.


Compliance Process & Data Manager
The Compliance Process & Data Manager acts as the representative of the data controller on a day-to-day basis.


All Staff
Scope:
This policy applies to all staff. You must be familiar with this policy and comply with its terms. This policy supplements our other polices relating to internet and email use. We may supplement or amend this policy by additional policies and guidelines from time to time. Any new or modified policy will be circulated to staff before being adopted.
Staff are responsible for:

Collecting, storing and processing any personal data in accordance with this policy

  • Informing their business unit of any changes to their personal data, such as a change of address
  • Contacting the DPO in the following circumstances:

o With any questions about the operation of this policy, data protection law, retaining personal data or keeping personal data secure
o If they have any concerns that this policy is not being followed
o If they are unsure whether or not they have a lawful basis to use personal data in a particular way
o If they need to rely on or capture consent, draft a privacy notice, deal with data protection rights invoked by an individual, or transfer personal data outside the European Economic Area
o If there has been a data breach
o Whenever they are engaging in a new activity that may affect the privacy rights of individuals
o If they need help with any contracts or sharing personal data with third parties


Data protection Principles

The GDPR is based on data protection principles that Swift must comply with.

The principles say that personal data must be:

  • Processed lawfully, fairly and in a transparent manner 
  • Collected for specified, explicit and legitimate purposes
  • Adequate, relevant and limited to what is necessary to fulfil the purposes for which it is processed
  • Accurate and, where necessary, kept up to date
  • Kept for no longer than is necessary for the purposes for which it is processed
  • Processed in a way that ensures it is appropriately secure

This policy sets out how Swift aims to comply with these principles.


Collecting Personal Data
Lawfulness, Fairness and Transparency

We will only process personal data where we have one of 6 ‘lawful bases’ (legal reasons) to do so under data protection law:

  • The data needs to be processed so that Swift can fulfil a contract with the individual, or the individual has asked Swift to take specific steps before entering into a contract
  • The data needs to be processed so that Swift can comply with a legal obligation
  • The data needs to be processed to ensure the vital interests of the individual eg, to protect someone’s life
  • The data needs to be processed so that Swift, as a government funded training provider, can perform a task in the public interest, and carry out its official functions
  • The data needs to be processed for the legitimate interests of Swift or a third party (provided the individual’s rights and freedoms are not overridden)
  • The individual (or their parent/carer when appropriate in the case of a learner) has freely given clear consent

For special categories of personal data, we will also meet one of the special category conditions for processing which are set out in the GDPR and Data Protection Act 2018.

Whenever we first collect personal data directly from individuals, we will provide them with the relevant information required by data protection law.


Limitation, Minimisation and Accuracy
We will only collect personal data for specified, explicit and legitimate reasons. We will explain these reasons to the individuals when we first collect their data.
If we want to use personal data for reasons other than those given when we first obtained it, we will inform the individuals concerned before we do so, and seek consent where necessary.
Staff must only process personal data where it is necessary in order to do their jobs.
When staff no longer need the personal data they hold, they must ensure it is deleted or anonymized. This will be done in accordance with the Swift’s Centre Archive Policy.


Sharing Personal Data
We will not normally share personal data with anyone else, but may do so where:

  • There is an issue with a learner or parent/carer that puts the safety of our staff and other learners at risk
  • We need to liaise with other agencies – we will seek consent as necessary before doing this
  • Our clients, suppliers or contractors need data to enable us to provide services to our staff and learners – for example, IT companies.

When doing this, we will:

  • Only appoint suppliers or contractors which can provide sufficient guarantees that they comply with data protection law
  • Establish a data sharing agreement with the client, supplier or contractor, either in the contract or as a standalone agreement, to ensure the fair and lawful processing of any personal data we share
  • Only share data that the client, supplier or contractor needs to carry out their service, and information necessary to keep them safe while working with us

We will also share personal data with law enforcement and government bodies where we are legally required to do so, including for:

  • The prevention or detection of crime and/or fraud
  • The apprehension or prosecution of offenders
  • The assessment or collection of tax owed to HMRC
  • In connection with legal proceedings
  • Where the disclosure is required to satisfy our safeguarding obligations
  • Research and statistical purposes, as long as personal data is sufficiently anonymised, or consent has been provided

We may also share personal data with emergency services and local authorities to help them to respond to an emergency situation that affects any of our learners or staff.

Where we transfer personal data to a country or territory outside the European Economic Area, we will do so in accordance with data protection law.


Subject Access Requests and other rights of individuals
Subject Access Requests

Individuals have a right to make a ‘subject access request’ to gain access to personal information that Swift holds about them. This includes:

  • Confirmation that their personal data is being processed
  • Access to a copy of the data
  • The purposes of the data processing
  • The categories of personal data concerned
  • Who the data has been, or will be, shared with
  • How long the data will be stored for, or if this isn’t possible, the criteria used to determine this period
  • The source of the data, if not the individual
  • Whether any automated decision-making is being applied to their data, and what the significance and consequences of this might be for the individual

Subject access requests must be submitted in writing, either by letter, email or fax to the DPO. They should include:

  • Name of individual
  • Correspondence address
  • Contact number and email address
  • Details of the information requested

If staff receive a subject access request, they must immediately forward it to the DPO.


Learners and Subject Access Requests
Personal data about a learner belongs to that learner, and not the learner's parents or carers. For a parent or carer to make a subject access request with respect to their child, the child must either be unable to understand their rights and the implications of a subject access request, or have given their consent.

Young people aged 12 and above are generally regarded to be mature enough to understand their rights and the implications of a subject access request. Therefore, most subject access requests from parents or carers of learners at Swift may not be granted without the express permission of the learner. This is not a rule and a learner’s ability to understand their rights will always be judged on a case-by-case basis.


Responding to Subject Access Requests (SAR)
When responding to requests, we:

  • May ask the individual to provide 2 forms of identification
  • May contact the individual via phone to confirm the request was made
  • Will respond without delay and within 1 month of receipt of the request
  • Will provide the information free of charge
  • May tell the individual we will comply within 3 months of receipt of the request, where a request is complex or numerous. We will inform the individual of this within 1 month, and explain why the extension is necessary


We will not disclose information if it:

  • Might cause serious harm to the physical or mental health of the learner or another individual
  • Would reveal that the learner is at risk of abuse, where the disclosure of that information would not be in the learner’s best interests
  • Is contained in adoption or parental order records
  • Is given to a court in proceedings concerning the learner

If the request is unfounded or excessive, we may refuse to act on it, or charge a reasonable fee which takes into account administrative costs.

A request will be deemed to be unfounded or excessive if it is repetitive or asks for further copies of the same information.

When we refuse a request, we will tell the individual why, and tell them they have the right to complain to the ICO.


Other Data Protection Rights of the individual

In addition to the right to make a subject access request (see above), and to receive information when we are collecting their data about how we use and process it (see section 7), individuals also have the right to:

  • Withdraw their consent to processing at any time
  • Ask us to rectify, erase or restrict processing of their personal data, or object to the processing of it (in certain circumstances)
  • Prevent use of their personal data for direct marketing
  • Challenge processing which has been justified on the basis of public interest
  • Request a copy of agreements under which their personal data is transferred outside of the European Economic Area
  • Object to decisions based solely on automated decision making or profiling (decisions taken with no human involvement, that might negatively affect them)
  • Prevent processing that is likely to cause damage or distress
  • Be notified of a data breach in certain circumstances
  • Make a complaint to the ICO
  • Ask for their personal data to be transferred to a third party in a structured, commonly used and machine-readable format (in certain circumstances)

Individuals should submit any request to exercise these rights to the DPO. If staff receive such a request, they must immediately forward it to the DPO.


CCTV
We use CCTV in various locations around the academies to ensure it remains safe. We will adhere to the ICO’s code of practice for the use of CCTV.
We do not need to ask individuals’ permission to use CCTV, but we make it clear where individuals are being recorded. Security cameras are clearly visible and accompanied by prominent signs explaining that CCTV is in use.
Any enquiries about the CCTV system should be directed to the DPO.


Photographs and videos
As part of Swift activities, we may take photographs and record images of individuals within our two academies.

We will obtain written consent from parents/carers or learners aged 18 and over, for photographs and videos to be taken of learners for communication, marketing and promotional materials.
Where we need parental consent, we will clearly explain how the photograph and/or video will be used to both the parent/carer and learner. Where we don’t need parental consent, we will clearly explain to the learner how the photograph and/or video will be used.

Uses may include:

  • Within the academies on notice boards and in academy brochures, newsletters, etc.
  • Outside of Swift by external agencies such as a professional photographer, newspapers, campaigns
  • Online on our Swift website or social media pages

Consent can be refused or withdrawn at any time. If consent is withdrawn, we will delete the photograph or video and not distribute it further.
When using photographs and videos in this way we will not accompany them with any other personal information about the learner, to ensure they cannot be identified.
See our Child Protection and Safeguarding Policy for more information on our use of photographs and videos.


Data Protection by design and default
We will put measures in place to show that we have integrated data protection into all of our data processing activities, including:

  • Appointing a suitably qualified DPO, and ensuring they have the necessary resources to fulfil their duties and maintain their expert knowledge
  • Only processing personal data that is necessary for each specific purpose of processing, and always in line with the data protection principles set out in relevant data protection law (see section 6)
  • Completing privacy impact assessments where the Swift’s processing of personal data presents a high risk to rights and freedoms of individuals, and when introducing new technologies (the DPO will advise on this process)
  • Integrating data protection into internal documents including this policy, any related policies and privacy notices
  • Regularly training members of staff on data protection law, this policy, any related policies and any other data protection matters; we will also keep a record of attendance
  • Regularly conducting reviews and audits to test our privacy measures and make sure we are compliant
  • Maintaining records of our processing activities, including:
    o For the benefit of data subjects, making available the name and contact details of Swift and DPO and all information we are required to share about how we use and process their personal data (via our privacy notices)
    o For all personal data that we hold, maintaining an internal record of the type of data, data subject, how and why we are using the data, any third-party recipients, how and why we are storing the data, retention periods and how we are keeping the data secure


Data Security and Storage of Records
We will protect personal data and keep it safe from unauthorised or unlawful access, alteration, processing or disclosure, and against accidental or unlawful loss, destruction or damage.
In particular:

  • Paper-based records and portable electronic devices, such as laptops and hard drives that contain personal data are kept under lock and key when not in use
  • Papers containing confidential personal data must not be left on office and classroom desks, on staffroom tables, pinned to notice/display boards, or left anywhere else where there is general access
  • Where personal information needs to be taken off site, staff must sign it in and out from the Swift main office
  • Passwords that are at least 8 characters long containing letters and numbers are used to access academy computers, laptops and other electronic devices. Staff and learners are reminded to change their passwords at regular intervals
  • Encryption software is used to protect all portable devices and removable media, such as laptops and USB devices
  • Where we need to share personal data with a third party, we carry out due diligence and take reasonable steps to ensure it is stored securely and adequately protected (see section 8)


Disposal of Records

Personal data that is no longer needed will be disposed of securely. Personal data that has become inaccurate or out of date will also be disposed of securely, where we cannot or do not need to rectify or update it.

For example, we will shred or incinerate paper-based records, and overwrite or delete electronic files. We may also use a third party to safely dispose of records on the Swift’s behalf. If we do so, we will require the third party to provide sufficient guarantees that it complies with data protection law.


Personal Data Breaches

We will make all reasonable endeavours to ensure that there are no personal data breaches. In the unlikely event of a suspected data breach, we will follow the procedure set out in appendix 1. When appropriate, we will report the data breach to the ICO within 72 hours. Such breaches in Swift context may include, but are not limited to: 

  • Safeguarding information being made available to an unauthorised person 
  • The theft of a Swift laptop containing non-encrypted personal data about learners


Training
All staff are provided with data protection training as part of their induction process.
Data protection will also form part of continuing professional development, where changes to legislation, guidance or Swift’s processes make it necessary.


Monitoring arrangements

The DPO is responsible for monitoring and reviewing this policy.
This policy will be reviewed and updated if necessary when the Data Protection Bill receives royal assent and becomes law (as the Data Protection Act 2018) – if any changes are made to the bill that affect our practice. Otherwise, or from then on, this policy will be reviewed every year and shared with the Board of Directors.


Links with other policies
This data protection policy is linked to our:

  •  Safeguarding Policy 
  • Centre Archive Policy 
  • Visitors Policy
  • IT Security Policy 
  • Social Media Policy


Appendix 1: Personal data breach procedure
This procedure is based on guidance on personal data breaches produced by the ICO.

  • On finding or causing a breach, or potential breach, the staff member or data processor must immediately notify the DPO
  • The DPO will investigate the report, and determine whether a breach has occurred. To decide, the DPO will consider whether personal data has been accidentally or unlawfully:
    o Lost
    o Stolen
    o Destroyed
    o Altered
    o Disclosed or made available where it should not have been
    o Made available to unauthorised people
  • The DPO will alert the Board of Directors
  • The DPO will make all reasonable efforts to contain and minimise the impact of the breach, assisted by relevant staff members or data processors where necessary. (Actions relevant to specific data types are set out at the end of this procedure)
  • The DPO will assess the potential consequences, based on how serious they are, and how likely they are to happen
  • The DPO will work out whether the breach must be reported to the ICO. This must be judged on a case-by-case basis. To decide, the DPO will consider whether the breach is likely to negatively affect people’s rights and freedoms, and cause them any physical, material or non-material damage (e.g. emotional distress), including through:
    o Loss of control over their data
    o Discrimination
    o Identify theft or fraud
    o Financial loss
    o Unauthorised reversal of pseudonymisation (for example, key-coding)
    o Damage to reputation
    o Loss of confidentiality

o Any other significant economic or social disadvantage to the individual(s) concerned if it’s likely that there will be a risk to people’s rights and freedoms, the DPO must notify the ICO.

  • The DPO will document the decision (either way), in case it is challenged at a later date by the ICO or an individual affected by the breach. Documented decisions are stored in a secure folder in Swifts Business Operation System, BIS and BOS
  • Where the ICO must be notified, the DPO will do this via the ‘report a breach’ page of the ICO website within 72 hours. As required, the DPO will set out:

o A description of the nature of the personal data breach including, where possible:

  • The categories and approximate number of individuals concerned
  • The categories and approximate number of personal data records concerned

o The name and contact details of the DPO
o A description of the likely consequences of the personal data breach
Supportive Welfare Impact Focused Trust
Supportive Welfare Impact Focused Trust
o A description of the measures that have been, or will be taken, to deal with the breach and mitigate any possible adverse effects on the individual(s) concerned

  • If all the above details are not yet known, the DPO will report as much as they can within 72 hours. The report will explain that there is a delay, the reasons why, and when the DPO expects to have further information. The DPO will submit the remaining information as soon as possible
  • The DPO will also assess the risk to individuals, again based on the severity and likelihood of potential or actual impact. If the risk is high, the DPO will promptly inform, in writing, all individuals whose personal data has been breached. This notification will set out:

o The name and contact details of the DPO

o A description of the likely consequences of the personal data breach

o A description of the measures that have been, or will be, taken to deal with the data breach and mitigate any possible adverse effects on the individual(s) concerned

  • The DPO will notify any relevant third parties who can help mitigate the loss to individuals – for example, the police, insurers, banks or credit card companies
  • The DPO will document each breach, irrespective of whether it is reported to the ICO. For each breach, this record will include the:

o Facts and cause

o Effects

o Action taken to contain it and ensure it does not happen again (such as establishing more robust processes or providing further training for individuals)


Records of all breaches will be stored in a secure folder on Dropbox – LEMA/LML IT & Digital/ LML Swift (Folder: Data Protection Breach – Log)

  • The DPO and Operations Director of the affected business unit will meet to review what happened and how it can be stopped from happening again. This meeting will happen as soon as reasonably possible


Actions to Minimise the Impact of Data Breaches
We will take the actions set out below to mitigate the impact of different types of data breach, focusing especially on breaches involving particularly risky or sensitive information. We will review the effectiveness of these actions and amend them as necessary after any data breach.

Sensitive information being disclosed via email (including safeguarding records)

  • If special category data (sensitive information) is accidentally made available via email to unauthorised individuals, the sender must attempt to recall the email as soon as they become aware of the error
  • Members of staff who receive personal data sent in error must alert the sender and the DPO as soon as they become aware of the error
  • If the sender is unavailable or cannot recall the email for any reason, the DPO will ask the IT department to recall it
  • In any cases where the recall is unsuccessful, the DPO will contact the relevant unauthorised individuals who received the email, explain that the information was sent in error, and request that those individuals delete the information and do not share, publish, save or replicate it in any way
  • The DPO will ensure we receive a written response from all the individuals who received the data, confirming that they have complied with this request
  • The DPO will carry out an internet search to check that the information has not been made public; if it has, we will contact the publisher/website owner or administrator to request that the information is removed from their website and deleted


Monitoring and Review

  • The Senior Management Team will be responsible for monitoring and reviewing the Policy.
  • Monitoring will include assessing how this policy is working in practice, reviewing this annually, and considering and taking action to address any issues
Swift

© Swift 2024

built by: huzzah!