Privacy Policy

Background

The General Data Protection Regulation (GDPR) is based around six principles of handling of personal data. We must comply with all six principles as a business; otherwise we shall be in breach of the GDPR. We understand that the principles give people specific rights in relation to their personal information and place certain obligations on those organisations that are responsible for processing it.

Aim

The GDPR requires that we must take appropriate measures against unauthorised or unlawful processing and against accidental loss, destruction of or damage to personal data. This policy sets out how we deal with a data security breach.

What is a personal data breach?

The Information Commissioner’s Office states that a personal data breach can be broadly defined as a security incident that has affected the confidentiality, integrity or availability of personal data. In short, there will be a personal data breach whenever any personal data is lost, destroyed, corrupted or disclosed; if someone accesses the data or passes it on without proper authorisation; or if the data is made unavailable and this unavailability has a significant negative effect on individuals.

Action to be taken in the event of a data breach

1. Containment and recovery

The immediate priorities are to:

• Contain the breach.
• Assess the potential adverse consequences for individuals, based on how serious or substantial these are, and how likely they are to happen.
• To limit the scope.

In the event of a security incident or breach, staff must immediately inform Sue Rao the Data Protection Officer (DPO).

Sue Rao will take the lead on investigating the breach. In the event where Sue is absent for whatever reason, Bozena Grzelak will take the lead on investigating a breach.

Steps to take where personal data has been sent to someone not authorised to see it:

• Inform the recipient not to pass it on or discuss it with anyone else.
• Inform the recipient to destroy or delete the personal data they have received and get them to confirm in writing that they have done so.
• Explain to the recipient the implications if they further disclose the data.
• Where relevant, inform the data subjects whose personal data is involved what has happened so that they can take any necessary action to protect themselves.

2. Assessing the risk

Perhaps most important is an assessment of potential adverse consequences for individuals, how serious or substantial these are and how likely they are to happen.

Examples of the type of questions to consider:

3. Notifying the ICO and individuals, where relevant

a) Who is responsible?

In our business, Sue Rao, DPO is the point of contact for staff and the ICO on this policy and on all matters relating to data protection.

Sue Rao, DPO is also responsible for notifying the ICO and individuals (where applicable) of relevant personal data breaches.

b) What breaches do we need to notify the ICO about?

When a personal data breach has occurred, we need to establish the likelihood and severity of the resulting risk to people’s rights and freedoms. If it’s likely that there will be a risk then we must notify the ICO; if it’s unlikely then we don’t have to report it.

If we decide we don’t need to report the breach, we need to be able to justify this decision, and we should document it.

c) When to notify the ICO and dealing with delays

Notifiable breaches must be reported to the ICO without undue delay, but not later than 72 hours after becoming aware of it.

If we don’t comply with this requirement, we must be able to give reasons for the delay.

In some instances it will not always be possible to investigate a breach fully within 72 hours to understand exactly what has happened and what needs to be done to mitigate it. Where that applies we should provide the required information in phases, as long as this is done without undue further delay.

d) Breach information to the ICO

When reporting a breach, we will provide the following information:

• a description of the nature of the personal data breach including, where possible:
  1. the categories and approximate number of individuals concerned.
  2. the categories and approximate number of personal data records concerned.
• our contact person, Sue Rao, DPO.
• a description of the likely consequences of the personal data breach.
• a description of the measures taken, or proposed to be taken, to deal with the personal data breach, including, where appropriate, the measures taken to mitigate any possible adverse effects.

e) Individuals

Where notification to individuals may also be required, Sue Rao, DPO will assess the severity of the potential impact on individuals as a result of a breach and the likelihood of this occurring. Where there is a high risk, we will inform those affected as soon as possible, especially if there is a need to mitigate an immediate risk of damage to them.

g) Information to individuals

Sue Rao, DPO will consider who to notify, what we are going to tell them and how we are going to communicate the message. This will depend to a large extent on the nature of the breach but will include the name and contact details of our data protection officer (where relevant) or other contact point where more information can be obtained; a description of the likely consequences of the personal data breach; and a description of the measures taken, or proposed to be taken, to deal with the personal data breach and including, where appropriate, of the measures taken to mitigate any possible adverse effects.

The breach need not be reported to individuals if:

• We have implemented appropriate technical and organisational protection measures, and those measures were applied to the personal data affected by the personal data breach.
• We have taken subsequent measures which ensure that the high risk to the rights and freedoms of data subjects is no longer likely to materialise.
• It would involve disproportionate effort (in this case a public communication may be more appropriate).

In the case of a breach affecting individuals in different EU countries, we are aware that the ICO may not be the lead supervisory authority. Where this applies, Sue Rao, DPO should establish which European data protection agency would be the lead supervisory authority for the processing activities that have been subject to the breach.

h) Third parties

In certain instances Sue Rao, DPO may need to consider notifying third parties such as the police, insurers, professional bodies, bank or credit card companies who can assist in reducing the risk of financial loss to individuals.

i) Document all decisions

Sue Rao, DPO must document all decisions that we take in relation to security incidents and data breaches, regardless of whether or not they need to be reported to the ICO.

4. GDPR representative in EEA (EU)

Ms Joanna Piotrowska has been appointed by ABC School of English as our EEA (EU) representative. Ms Piotrowska is an associate of Callan Method Organisation and had her own Callan school in Krakow for 25 years.

5. Evaluate our response and mitigation steps

We investigate the cause of any breach, decide on remedial action and consider how we can mitigate it. As part of that process we also evaluate the effectiveness of our response to incidents or breaches. To assist in this evaluation we consider:

• What personal data is held, where and how it is stored.
• Risks that arise when sharing with or disclosing to others.
• This includes checking the method of transmission to make sure it‘s secure and that we only share or disclose the minimum amount of data necessary.
• Weak points in our existing security measures such as the use of portable storage devices or access to public networks.
• Whether or not the breach was a result of human error or a systemic issue and determine how a recurrence can be prevented – whether this is through better processes, further training or other corrective steps.
• Staff awareness of security issues and look to fill any gaps through training or advice.
• The need for a Business Continuity Plan for dealing with serious incidents.
• The group of people responsible for reacting to reported breaches of security.

6. Review

This policy is dated 21st February 2024 and will be reviewed in 12 months.