DATA BREACH INCIDENT POLICY

  1. Introduction

  2. This Policy sets out the obligations of SocialCru Ltd, a company registered in the United Kingdom under number 10233218, whose registered office is at Suite 15, Cue House, Chapel Lane, Stockton Heath, Warrington. WA46LL (“the Company”) regarding the handling and reporting of data breaches and personal data breaches in accordance with EU Regulation 2016/679 General Data Protection Regulation (“GDPR”).

  3. The GDPR defines “personal data” as any information relating to an identified or identifiable natural person (a “data subject”); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier, or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural, or social identity of that natural person.

  4. The GDPR defines a “personal data breach” as a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data transmitted, stored, or otherwise processed.

  5. The Company is under a duty to report certain types of personal data breach directly to the UK’s supervisory authority, the Information Commissioner’s Office (“ICO”). The Company is also required to inform individual data subjects in the case of breaches that present a high risk of adversely affecting their rights and freedoms.

  6. All personal data collected, held, and processed by the Company will be handled in accordance with the Company’s Data Protection Policy.

  7. The Company has in place procedures for the detection, investigation, and reporting of data breaches. This Policy applies to all data breaches (including personal data breaches) within the Company and is designed to assist in both the handling of such breaches and in determining whether or not they must be reported to the ICO and/or to data subjects.

  8. The Company’s Data Protection Officer, Alex Gibson, 0800 0496 212 is responsible for the implementation of this Policy, for overseeing the handling of all data breaches, and for ensuring that this Policy is adhered to by all staff.

  9. Scope of Policy

  10. This Policy relates to all formats of data (including personal data and sensitive personal data (known as “special category” under the GDPR)) collected, held, and processed by the Company.

  11. This Policy applies to all staff of the Company, including but not limited to employees, agents, contractors, consultants, temporary staff, casual or agency staff, or other suppliers or data processors working for or on behalf of the Company.

  12. This Policy applies to all data breaches, whether suspected or confirmed.

  13. Data Breaches

  14. For the purposes of this Policy, a data breach means any event or action (accidental or deliberate) which presents a threat to the security, integrity, confidentiality, or availability of data.

  15. Incidents to which this Policy applies may include, but not be limited to:

  16. the loss or theft of a physical data record;

  17. the loss or theft of computer equipment (e.g. laptop), mobile devices (e.g. smartphone or tablet), portable data storage devices (e.g. USB drive), or other data storage devices;

  18. equipment failure;

  19. unauthorised access to, use of, or modification of data (or inadequate access controls allowing unauthorised access, use, or modification);

  20. unauthorised disclosure of data;

  21. human error (e.g. sending data to the wrong recipient);

  22. unforeseen circumstances such as fire or flood;

  23. hacking, phishing, and other ‘blagging” offences whereby information is obtained by deception;

  24. Internal Reporting

  25. If a data breach is discovered or suspected, members of staff should complete a Data Breach Report Form (available from Alex Gibson) and send the completed form to the Company’s Data Protection Officer.

  26. A completed Data Breach Report Form should include full and accurate details about the incident including, but not limited to (where applicable):

  27. the time and date of the breach;

  28. the time and date the breach was discovered;

  29. the type(s) of data involved;

  30. where the breach involves personal data, the categories(s) of data subject to which the personal data relates (e.g. customers, employees etc.);

  31. whether or not any sensitive personal data is involved;

  32. how many data subjects are likely to be affected (if known);

  33. Where appropriate, members of staff should liaise with their line manager when completing a Data Breach Report Form.

  34. If a data breach occurs or is discovered outside of normal working hours, it should be reported as soon as is reasonably practicable.

  35. Unless and until instructed to by the Company’s Data Protection Officer, members of staff should not take any further action with respect to a data breach. In particular, individual members of staff should not take it upon themselves to notify affected data subjects, the ICO, or any other individuals or organisations.

  36. Initial Management and Recording

  37. Upon receipt of a Data Breach Report Form (or upon being notified of a data breach in any other way), the Company’s Data Protection Officer shall begin by determining whether the data breach is still occurring. If this is the case, appropriate steps shall be taken immediately to minimise the effects of the data breach and to stop it.

  38. Having established the above, the following steps shall then be taken with respect to the data breach:

  39. undertake an initial assessment of the data breach, liaising with the relevant staff and departments where appropriate, to establish the severity of the data breach;

  40. contain the data breach and, to the extent reasonably practicable, recover, amend, or restrict the availability of (e.g. by changing or revoking access permissions or by temporarily making the data unavailable electronically) the affected data;

  41. determine whether anything further can be done to recover the data and/or other losses, and to limit the damage caused by the breach;

  42. establish who needs to be notified initially (including, if physical records or equipment have been lost or stolen, the police) as part of the initial containment;

  43. determine, in liaison with the relevant staff and departments, the best course of action to resolve and remedy the data breach; and

  44. record the breach and the initial steps taken above in the Company’s Data Breach Register.

  45. Having completed the initial steps described above, the Company’s Data Protection Officer shall proceed with investigating and assessing the data breach as described in Part 6, below.

  46. Investigation and Assessment

  47. The Company’s Data Protection Officer shall begin an investigation of a data breach as soon as is reasonably possible after receiving a Data Breach Report Form (or being notified in any other way) and, in any event, within 24 hours of the data breach being discovered and/or reported.

  48. Investigations and assessments must take the following into account:

  49. the type(s) of data involved (and, in particular, whether the data is personal data or sensitive personal data);

  50. the sensitivity of the data (both commercially and personally);

  51. what the data breach involved;

  52. what organisational and technical measures were in place to protect the data;

  53. what might be done with the data as a result of a breach (including unlawful or otherwise inappropriate misuse);

  54. where personal data is involved, what that personal data could tell a third party about the data subjects to whom the data relates;

  55. the category or categories of data subject to whom any personal data relates;

  56. the number of data subjects (or approximate number if calculating an exact number is not reasonably practicable) likely to be affected by the data breach;

  57. the potential effects on the data subjects involved;

  58. the potential consequences for the Company;

  59. the broader consequences of the data breach, both for data subjects and for the Company;

  60. The results of the investigation and assessment described above must be recorded in the Company’s Data Breach Register.

  61. Having completed the investigation and assessment described above, the Company’s Data Protection Officer shall determine the parties to be notified of the breach as described in Part 7, below.

  62. NotificationThe Company’s Data Protection Officer shall determine whether to notify one or more of the following parties of the breach:

  63. affected data subjects;

  64. the ICO;

  65. the police;

  66. the Company’s insurers;

  67. affected commercial partners;

  68. When considering whether (and how) to notify individual data subjects in the event of a personal data breach, the following should be considered:

  69. the likelihood that data subjects’ rights and freedoms as set out in the GDPR (and the Company’s Data Protection Policy) will be adversely affected;

  70. whether there is a legal or contractual requirement to notify;

  71. whether measures in place to protect the affected personal data (e.g. pseudonymisation or encryption) have been applied, thereby rendering the data unusable to any unauthorised parties;

  72. whether measures have been taken following the data breach that will ensure that a high risk to the rights and freedoms of affected data subjects is no longer likely to occur;

  73. the benefits to data subjects’ of being notified (e.g. giving them the opportunity to mitigate the risks posed by the data breach);

  74. whether notifying individuals will involve disproportionate effort (in which case a public communication or other widely available notice may suffice, provided that affected data subjects will still be informed effectively);

  75. the best way of notifying data subjects, taking into account the urgency of the situation and the security of the possible methods;

  76. any special considerations applicable to certain categories of data subject (e.g. children or vulnerable people);

  77. the information that should be provided to affected data subjects;

  78. how to make it easy for affected data subjects to contact the Company to find out more about the data breach;

  79. further assistance that the Company should provide to the affected data subjects, where appropriate;

  80. the risks of over-notifying – not all data breaches require notification and excessive notification may result in disproportionate work and numbers of enquiries from individuals;

  81. When individual data subjects are to be informed of a data breach, those individuals must be informed of the breach without undue delay. Individuals shall be provided with the following information:

  82. a user-friendly description of the data breach, including how and when it occurred, the personal data involved, and the likely consequences;

  83. clear and specific advice, where relevant, on the steps individuals can take to protect themselves;

  84. a description of the measures taken (or proposed to be taken) to address the data breach including, where relevant, measures taken to mitigate any possible adverse effects;

  85. contact details for the Company’s Data Protection Officer from whom affected individuals can obtain further information about the data breach.

  86. When considering whether (and how) to notify the ICO of a data breach, the following should be considered:

  87. the risk and potential harm to data subjects, their rights, and freedoms – harm can include (but is not limited to) financial harm, physical harm, loss of control over personal data, discrimination, identity theft or fraud, damage to reputation, and emotional distress;

  88. the volume of personal data involved – the ICO should be notified if a large volume of data is involved and there is a real risk of data subjects suffering harm as a result, however it may also be appropriate to notify the ICO if a smaller amount of high-risk data is involved;

  89. the sensitivity of the data involved – the more sensitive the personal data is, the less the volume of it is relevant and if the data breach presents a significant risk of data subjects suffering substantial detriment or distress, the ICO should be notified.

  90. If the ICO is to be notified of a data breach, this must be done within 72 hours of becoming aware of the breach, where feasible. This time limit applies even if complete details of the data breach are not yet available. The ICO must be provided with the following information:

  91. the category or categories and the approximate number of data subject whose personal data is affected by the data breach;

  92. the category or categories and the approximate number of personal data records involved;

  93. the name and contact details of the Company’s Data Protection Officer the individual or department within the Company from which the ICO can obtain further information about the data breach;

  94. a description of the likely consequences of the data breach; and

  95. a description of the measures taken (or proposed to be taken) to address the data breach including, where relevant, measures taken to mitigate any possible adverse effects.

  96. The police may have been contacted at an earlier point in the data breach procedure (see 5.2), however further investigation may reveal that the data breach resulted from a criminal act, in which case the police should be further informed.

  97. Records must be kept of all data breaches, regardless of whether notification is required. The decision-making process surrounding notification should be documented and recorded in the Company’s Data Breach Register.

  98. Evaluation and Response

  99. When the steps set out above have been completed, the data breach has been contained, and all necessary parties notified, the Company’s Data Protection Officer shall conduct a complete review of the causes of the data breach, the effectiveness of the measures taken in response, and whether any systems, policies, or procedures can be changed to prevent data breaches from occurring in the future.

  100. Such reviews shall, in particular, consider the following with respect to data (and in particular, personal data) collected, held, and processed by the Company:

  101. where and how data is held and stored;

  102. the current organisational and technical security measures in place to protect data and the risks and possible weaknesses of those measures;

  103. the methods of data transmission for both physical and electronic data and whether or not such methods are secure;

  104. the level of data sharing that takes place and whether or not that level is necessary;

  105. whether any data protection impact assessments need to be conducted or updated;

  106. staff awareness and training concerning data protection;

  107. Where possible improvements and/or other changes are identified, the Company’s Data Protection Officer shall liaise with the relevant staff  with respect to the implementation of such improvements and/or changes.

  108. Policy Review and Implementation

  109. This Policy will be updated as necessary to reflect current best practice, official guidance, and in line with current legislation.

  110. This Policy shall be deemed effective as of 9.06.2020. No part of this Policy shall have retroactive effect and shall thus apply only to matters occurring on or after this date.

  111. This Policy has been approved and authorised by:

  112. Name:

  113. Alex Gibson

  114. Position:

  115. Director

  116. Date:

  117. 9.06.2020

  118. Due for Review by:

  119. 9.06.2021