Personal Data Erasure Policy

Clerk: Mrs Sarah Rimell

Address: Illogan Parish Council Community Office, Trevelyan Road, Illogan, TR16 4RG

Telephone: 01209 711433

Email: enquiries@illoganparishcouncil.gov.uk

Adopted: 09.07.2025
Minute Number: GR25/07/11.2

This personal data erasure policy sets out the procedures we have put in place to deal with the erasure of personal data within our organisation.

We are Illogan Parish Council, a council in England. Our contact details are Illogan Parish Council, Illogan Parish Council Community Office, Trevelyan Road, Illogan, TR16 4RG.

We are a data controller for personal data as defined by all applicable data protection and privacy laws including, but not limited to, the retained EU law version of the General Data Protection Regulation ((EU) 2016/679) (the “UK GDPR”), as it forms part of the law of England and Wales, Scotland, and Northern Ireland by virtue of section 3 of the European Union (Withdrawal) Act 2018, the Data Protection Act 2018, the Privacy and Electronic Communications Regulations 2003 as amended, and any successor legislation (the “Data Protection Legislation”).

This policy is binding on all employees, members and volunteers (“User” or “Users”) of Illogan Parish Council (“The Organisation”) in order to protect Personal or other Data (“Personal Data” or “Data”) processed by the organisation.

It applies to all organised filing systems, be they computer based, paper based or any other such method of organising information which are accessible according to specific criteria, whether centralised, decentralised or dispersed on a functional or geographical basis (“Filing Systems”).

1. Definition of Personal Data

1.1. “Personal data” means any information relating to an identified or identifiable individual (“data subject”); an identifiable individual 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 individual.

1.2. Personal data will typically contain information about the individual or their activities.

2. Who is Responsible for Managing Erasure of Personal Data

2.1. Council Officers are responsible for the ongoing compliance monitoring of this and other policies that are designed to achieve compliance with the Data Protection Legislation.

2.2. No user within the organisation shall deviate from this policy without written authorisation from Council Officers.

3. Erasure

3.1. Personal data should be erased when:

  1. 3.1.1. The personal data is no longer necessary for the purpose which it was originally collected or processed for. Normal retention periods are specified in the Privacy Notice.
  2. 3.1.2. The organisation is relying on consent as the lawful basis for processing the data, and the individual withdraws their consent.
  3. 3.1.3. The organisation is relying on legitimate interests as the basis for processing, the individual objects to the processing of their data, and there is no overriding legitimate interest to continue this processing.
  4. 3.1.4. The organisation is processing the personal data for direct marketing purposes and the individual objects to that processing.
  5. 3.1.5. The organisation has processed the personal data unlawfully, i.e. in breach of the lawfulness requirement of the 1st principle.
  6. 3.1.6. The organisation has to do it to comply with a legal obligation; or
  7. 3.1.7. The organisation has processed the personal data to offer information society services to a child.

3.2. The right to erasure does not apply if processing is necessary for one of the following reasons:

  1. 3.2.1. To exercise the right of freedom of expression and information.
  2. 3.2.2. To comply with a legal obligation.
  3. 3.2.3. For the performance of a task carried out in the public interest or in the exercise of official authority.
  4. 3.2.4. For archiving purposes in the public interest, scientific research, historical research or statistical purposes where erasure is likely to render impossible or seriously impair the achievement of that processing; or
  5. 3.2.5. For the establishment, exercise or defence of legal claims.

3.3. The UK GDPR also specifies two circumstances where the right to erasure does not apply to special category data:

  1. 3.3.1. If the processing is necessary for public health purposes in the public interest, for example protecting against serious cross-border threats to health, or ensuring high standards of quality and safety of health care and of medicinal products or medical devices; or
  2. 3.3.2. If the processing is necessary for the purposes of preventative or occupational medicine; for the working capacity of an employee; for medical diagnosis; for the provision of health or social care; or for the management of health or social care systems or services. This only applies where the data is being processed by or under the responsibility of a professional subject to a legal obligation of professional secrecy, for example a health professional.

3.4. The organisation may refuse to comply with a request if it is:

  1. 3.4.1. Manifestly unfounded. A request may be manifestly unfounded if:
    1. 3.4.1.1. The individual clearly has no intention to exercise their right of erasure. For example, an individual makes a request, but then offers to withdraw it in return for some form of benefit from the organisation; or
    2. 3.4.1.2. The request is malicious in intent and is being used to harass the organisation with no real purposes other than to cause disruption.
  2. 3.4.2. Excessive. A request may be excessive if:
    1. 3.4.2.1. It repeats the substance of previous requests; or
    2. 3.4.2.2. It overlaps with other requests.
  3. 3.4.3. Council Officers shall decide if a request is manifestly unfounded or excessive on a case-by-case basis. The organisation does not have a blanket policy on refusal.
  4. 3.4.4. All requests should be considered in the context in which it is made.
  5. 3.4.5. If a request is refused Council Officers should document why they consider the request is manifestly unfounded or excessive.

3.5. In the event of the right to erasure not being applicable or the organisation refusing the request to erase, Council Officers will inform the individual without undue delay and within 28 days of receipt of the request and provide:

  1. 3.5.1. The reasons the organisation is not taking action.
  2. 3.5.2. The individual’s right to make a complaint to the ICO; and
  3. 3.5.3. The individual’s ability to seek to enforce this right through a judicial remedy.

4. Time Limits

4.1. Council Officers must respond to an erasure request without undue delay and at the latest within 28 calendar days with confirmation of erasure or reasons for refusal.

4.2. The time limit to respond starts on receipt of the request or, if later, on receipt of any information requested to confirm the requestor’s identity.

4.3. Council Officers can extend the time to respond by a further two months if the request is complex or they have received a number of requests from the individual. Council Officers must let the individual know within 28 calendar days of receiving their request and explain why the extension is necessary.

4.4. If Council Officers has doubts about the identity of the person making the request, they can ask for more information to identify them. They should only request information that is necessary to confirm identity. Council Officers must inform the individual without undue delay and within 28 calendar days that they need more information to confirm identity.

5. Users Role in Erasure Requests

5.1. The organisation has a legal responsibility to identify that an individual has made a request.

5.2. The UK GDPR does not specify how to make a valid request. A request can be made verbally or in writing. It can also be made to any part of the organisation and does not have to be to a specific person or contact point.

5.3. Users should be aware that requests can be made via email, or social media.

5.4. A request does not have to include the phrase “request for erasure” or Article 17 of the UK GDPR.

5.5. Users must notify in writing Council Officers immediately and in any case within 1 working day of a request to erase.

5.6. No user should action the erasure request and erase data without first informing and getting authorisation from Council Officers.

5.7. Users must provide all timely assistance to Council Officers.

5.8. Obstruction of a lawful erasure by a user will be addressed via the relevant disciplinary procedure.

6. Erasure of Data

6.1. When data is to be erased either because it is no longer required to fulfil the purpose for which it was collected or because there has been a valid request to erase from the data subject in question, Council Officers shall ensure that:

  1. 6.1.1. Paper based personal data is crosscut shredded or disposed of via a secure disposal contractor who supplies a certificate of destruction; and / or
  2. 6.1.2. Electronic records are removed from backup systems as well as live systems.
    1. 6.1.2.1. The organisation is aware that when data is deleted from the live system it will remain within the backup environment for a certain period of time until it is overwritten.
    2. 6.1.2.2. For erasure where the data is no longer required this time delay is acceptable and backups can be allowed to run to normal schedule as the data will be erased from them in due course.
    3. 6.1.2.3. For data that has been requested to be erased Council Officers must confirm to the requester what will happen to their data when their erasure request is fulfilled, including in respect of backup systems, an indication should be given of how long it will take to purge from the backups. Council Officers should then ensure that the data on the backup is “beyond use” and that the data within the backup is not used for any other purpose.

6.2. Council Officers must ensure that data that has been erased is not accidentally reintroduced in the event of a backup being restored.

6.3. When actioning erasure Council Officers shall ensure that the relevant data is erased from the entire filing system paying particular attention to file location whether centralised, decentralised or dispersed on a functional or geographical basis.

7. Updates to this Policy

7.1. This policy shall be reviewed annually by Council Officers and the Governance Review Committee.

7.2. This policy shall be reviewed if Illogan Parish Council makes changes to the organisation’s Privacy Notice or if there are changes to how the organisation processes data or the data protection legislation changes.

7.3. This policy was last updated on 9th July 2025.

8. Implementation

8.1. This policy takes effect from 10th July 2025 and is not retroactive.

Record of Review

Reviewed Reviewed By Amendments Minute Number
25.02.26 Governance Review Committee “England” was amended to read “the UK”. GR26/02/22.2