ABOUT THIS PROCEDURE We acknowledge that a Data Subject is entitled to submit a request for erasure of their details from time to time (Erasure Request) i.e. the right to be forgotten. The right to make an Erasure Request applies to both (i) external Data Subjects, such as Candidates, Client Contacts, Referees and Supplier Contacts and (ii) internal Data Subjects, such as Applicants and Employees. However, the extent to which we can comply with an Erasure Request shall vary, depending on the type of Data Subject.
EXTERNAL DATA SUBJECTS: Upon receipt of an Erasure Request, we shall: 1. Verify the identity of the Data Subject; and 2. If appropriate, check whether the Data Subject wishes (i) to be erased from our business records or (ii) to remain within our business records but suppressed so that the Data Subject is not contacted by us. If the Data Subject wishes to have their personal data Erased: 1. We shall consider whether there is any lawful reason or legal requirement to retain the personal data as: a. The Conduct of Employment Agencies and Employment Businesses Regulations 2003 require us to keep records of any work-finding services which we have provided for not less than 12 months. b. If we have placed the Data Subject in a permanent role or on a temporary assignment, we will usually retain any relevant personal data for seven years so that we can defend ourselves from any legal claim which may arise and maintain auditable records for tax compliance reasons. 2. We shall within one month of receiving the Erasure Request, confirm the outcome of such Erasure Request, the steps which we have taken and the extent to which any personal data has been retained. 3. If we have retained personal data for any reason, this shall not be used for recruitment purposes and the relevant Data Record shall be [removed from our front-office database system] or [marked as Pending Deletion]. 4. We shall ensure that any (i) joint Data Controller or (ii) third party which is processing relevant Data Subject’s data on our behalf is informed that the Data Subject has made an Erasure Request and takes appropriate steps to comply with such Erasure Request. 5. If the request is manifestly unfounded or excessive, for example, because of its repetitive character, we may charge a reasonable fee, taking into account the administrative costs of erasure, or refuse to act on the request. 6. If we are not going to respond to the request, we shall inform the Data Subject of the reasons for not taking action and of the possibility of lodging a complaint with the ICO. If the Data Subject does not wish to have their personal data erased but would prefer to have their record marked as Do Not Contact, we shall record this in the relevant data record. Once marked as Do Not Contact: 1. The Data Subject’s record shall then be subject to our standard data retention procedures; and 2. Will be deleted after three years or more of inactivity, subject to any legal right or obligation for us to retain the data for compliance purposes.
INTERNAL DATA SUBJECTS: An Internal Data Subject has a limited right to make an Erasure Request where: a) The personal data is no longer necessary for the purpose which we originally collected or processed it; b) We have processed the personal data unlawfully; or c) There is a legal obligation for the personal data to be erased e.g. a court order. If we receive an Erasure Request from any Internal Data Subject: 1. We shall verify the Data Subject’s identity where appropriate. This will not usually be necessary for current employees. 2. We shall acknowledge the request in writing and then, within one month of receiving the Erasure Request, confirm the outcome of such Erasure Request. 3. If appropriate, we shall ensure that any (i) joint Data Controller or (ii) third party which is processing relevant Data Subject’s data on our behalf is informed that the Data Subject has made an Erasure Request and takes appropriate steps to comply with such Erasure Request. 4. If the request is manifestly unfounded or excessive, for example, because of its repetitive character, we may charge a reasonable fee, taking into account the administrative costs of erasure, or refuse to act on the request. 5. If we are not going to respond to the request, we shall inform the Data Subject of the reasons for not taking action and of the possibility of lodging a complaint with the ICO.
ABOUT THIS PROCEDURE This Subject Access Request Procedure sets out our procedure in relation to any Subject Access Request which we may receive from a Data Subject. The Directors are responsible for overseeing this procedure. Any questions about the operation of this procedure should be submitted to a Director.
RECEIVING A SAR Data Subjects have the right to request access to their personal data processed by us. Such requests are called subject access requests (SARs). When a Data Subject makes a SAR, we shall take the following steps: 1. acknowledge the SAR in writing 2. log the date on which the request was received (to ensure that the relevant timeframe of one month for responding to the request is met); 3. confirm the identity of the Data Subject who is the subject of the personal data. For example, we may request additional information from the Data Subject to confirm their identity; 4. search databases, systems, applications and other places where the personal data which are the subject of the request may be held; and 5. confirm to the Data Subject whether or not personal data of the Data Subject making the SAR are being processed.
FEES FOR HANDLING A SAR We shall not usually charge a fee to the Data Subject for carrying out a SAR (i.e. as the previous statutory £10 fee is no longer in force.) If the SAR is manifestly unfounded or excessive, for example, because of its repetitive character, we may charge a reasonable fee, taking into account the administrative costs of providing the personal data.
PROVISION OF INFORMATION If personal data of the Data Subject are being processed, we shall provide the Data Subject with the following information in a concise, transparent, intelligible and easily accessible form, using clear and plain language, in writing or by other (including electronic) means: • the purposes of the processing; • the categories of personal data concerned (for example, contact details, bank account information and details of sales activity); • the recipients or categories of recipient to whom the personal data have been or will be disclosed, in particular recipients overseas (for example, US-based service providers); • where possible, the envisaged period for which the personal data will be stored, or, if not possible, the criteria used to determine that period; • the existence of the right to request rectification or erasure of personal data or restriction of processing of personal data or to object to such processing; • the right to lodge a complaint with the Information Commissioner's Office (ICO); • where the personal data are not collected from the Data Subject, any available information as to their source; • the existence of automated decision-making and meaningful information about the logic involved, as well as the significance and the envisaged consequences of such processing for the Data Subject; and • where personal data are transferred outside the EU, details of the appropriate safeguards to protect the personal data. We shall also, unless there is an exemption, provide the Data Subject with a copy of the personal data processed by us in a commonly used electronic form e.g. PDF documents, unless the Data Subject either did not make the request by electronic means or has specifically requested not to be provided with the copy in electronic form. We shall usually submit the data to the Data Subject within one month of receipt of the request. Before providing the personal data to the Data Subject making the SAR, we shall review the personal data requested to see if they contain the personal data of other Data Subjects. If they do, we may redact the personal data of those other Data Subjects prior to providing the Data Subject with their personal data, unless those other Data Subjects have consented to the disclosure of their personal data.
EXTENDING THE TIME TO RESPOND If the request is complex, or there are a number of requests, we may extend the period for responding by a further two months. If we extend the period for responding, we shall inform the Data Subject within one month of receipt of the request and explain the reason(s) for the delay.
REFUSING A SAR If the SAR is manifestly unfounded or excessive, for example, because of its repetitive character, we may refuse to act on the request. It would be unusual for us to refuse to act upon a SAR but may be appropriate if we consider the SAR to have been made in a vexatious or malicious manner to cause disruption to our business. If we are not going to respond to the SAR, we shall inform the Data Subject of the reason(s) for not taking action and of the right to lodge a complaint with the ICO.
ABOUT THIS PROCEDURE This policy sets out the procedure which we will follow in the event of a Data Breach. The Directors are responsible for overseeing this procedure. Any questions about the operation of this procedure should be submitted to a Director.
WHAT IS A DATA BREACH? A Data Breach may take various forms but often involves the unauthorised disclosure of personal data to a third party. Data Breaches might typically occur when someone: • Accidentally sends personal data to the incorrect party; • Accidentally leaves confidential documents on a train; • Has a laptop containing personal data stolen from their bag or vehicle; • Deliberately extracts information from our database and transfers it out of our business; • Hacks into our computer network to remove confidential or sensitive information; or • Throws away company records without ensuring that they are shredded or otherwise destroyed. A Data Breach could also involve the accidental or unlawful destruction, alteration or loss of access to Personal Data. This means that, for example, deliberate tampering with a Data Record by an employee would be a Data Breach, even if the Personal Data is not transferred anywhere.
PREVENTING DATA BREACHES We take active steps to avoid Data Breaches by: • Training our staff members about the importance of Data Security and the potential financial and reputational damage which can result from a Data Breach; and • Putting in place technical and organisational measures to minimise the risk of a Data Breach occurring. We do however acknowledge that, even if we take active steps to prevent breaches, they may still occur through human error or malicious conduct.
STEPS TO TAKE IN THE EVENT OF A DATA BREACH 1. If you become aware of a Data Breach, you must take action. You must not ignore the issue or try to hide it. You must therefore notify a Director in person or by telephone without delay. If you are unable to speak with a Director, you must speak to the next most senior person in the business. 2. You must preserve all evidence of the Data Breach and do nothing that might compromise any enquiry or investigation in relation to such Data Breach. 3. The relevant Director must arrange for a full investigation into the Data Breach without delay. Whilst the overall responsibility rests with the Director to ensure that this investigation is carried out, any relevant members of staff may be required to co-operate with the investigatory process. 4. The investigation must be carried out as quickly as possible. There is a 72 hour deadline to report the breach to the Information Commissioner’s Office, where applicable. 5. On completion of the initial investigation into the Data Breach, the Director shall keep a record of the investigation and outcome in the company’s central Data Protection file. This information shall be used to determine whether we need to disclose the Data Breach to: a. The Information Commissioner’s Office, which is the supervisory authority in the UK; and/or b. The individual Data Subjects whose Personal Data was the subject of the Data Breach.
NOTIFYING THE INFORMATION COMMISSIONER’S OFFICE Recital 85 of the GDPR gives the following guidance on the risk to rights and freedoms: A personal data breach may, if not addressed in an appropriate and timely manner, result in physical, material or non-material damage to natural persons such as loss of control over their personal data or limitation of their rights, discrimination, identity theft or fraud, financial loss, unauthorised reversal of pseudonymisation, damage to reputation, loss of confidentiality of personal data protected by professional secrecy or any other significant economic or social disadvantage to the natural person concerned. The Director must determine whether the Data Breach is likely to result in a risk to the rights and freedoms of the Data Subjects affected by the breach. In reaching a decision, the Director shall assess the following factors: • Type of breach. • Nature, sensitivity and volume of personal data. • Ease of identification of individuals. • Severity of consequences for individuals. • Special characteristics of the individual (for example, vulnerable individuals may be at greater risk). • Number of individuals affected. The decision as to whether or not to report the breach must be recorded in the company’s Central Data Protection file. If the Director concludes that the Data Breach should be reported to the Information Commissioner’s Office, the ICO’s reporting process at: https://ico.org.uk/for-organisations/report-a-breach/ must be followed. This must happen within 72 hours of the Data Breach occurring. The ICO will typically require the following information: • A description of the nature of the personal data breach including, where possible: • The categories and approximate number of individuals concerned; and • The categories and approximate number of personal data records concerned; • The name and contact details of the data protection officer 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, including, where appropriate, the measures taken to mitigate any possible adverse effects.
NOTIFYING THE INDIVIDUAL The requirement to communicate a breach to individuals is triggered where a breach is likely to result in a high risk to their rights and freedoms. The threshold for communicating a breach to individuals is therefore higher than for notifying the ICO. In practice, where notification to individuals is required, notification to the ICO will always be required. Although the deadline for notifying the ICO is set at 72 hours by law, there is no fixed deadline for notifying individuals. Notification must occur without undue delay. Whether individuals should be notified will depend on the circumstances of the breach. For example, a loss of data which can be confirmed as encrypted and where the encryption key has not been compromised, may represent a very low risk, and would not require notification to individuals (or the ICO). However, even where data is encrypted, if there are no comprehensive backups of the data, then this could have negative consequences for individuals and notification may be appropriate. The following information should be included in a breach notification to individuals: • The name and contact details of the data protection officer (if applicable) or other contact point where more information can be obtained. • 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, actions taken to mitigate any possible adverse effects. After notifying individuals of a Data Breach, it is inevitable that some individuals will have further questions or significant concerns about the security of their data. Whilst there is nothing to stop any individual taking further action after a Data Breach, it is less likely that they will do so if their concerns are dealt with appropriately. With this in mind, any enquiries from affected individuals must be: • Logged in the company’s Central Data Protection record; • Promptly acknowledged in writing; and • Responded to, in full and courteously, without undue delay.
© Copyright 2019-2024. Bond Recruit Ltd. All Rights Reserved