Promintal

Data Breach Response Procedure

What we do when personal data is lost, stolen, disclosed or accessed without authorisation.

PROMINTAL LTDEffective 20 November 2026Next review November 2027Audience: Internal

What counts as a personal data breach

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

  • an email containing personal data sent to the wrong person;
  • a lost or stolen laptop or phone;
  • a compromised account or phishing attack;
  • a misconfigured system that exposes data publicly;
  • accidental deletion of data with no backup;
  • a breach at one of our suppliers affecting our data.

Step 1: Report immediately

Anyone who discovers or suspects a breach must tell the Data Protection Lead at once, by phone and by email to info@promintal.co.uk, even outside working hours and even if unsure. Do not try to investigate on your own or delete evidence.

Record: what happened, when it happened and when it was discovered, what data and how many people are affected, and what has been done so far.

Step 2: Contain and recover (first hours)

  • Recall or ask recipients to delete misdirected emails, and confirm deletion in writing.
  • Reset passwords, revoke sessions and access tokens, and enforce multi-factor authentication.
  • Remotely lock or wipe lost devices.
  • Close the exposure: fix permissions, take down public links, isolate affected systems.
  • Restore lost data from backups where possible.
  • Preserve logs and evidence.

Step 3: Assess the risk (within 24 hours)

The Data Protection Lead assesses the likely risk to individuals, considering the type and sensitivity of the data, volume, how easily people can be identified, whether data was encrypted, the likely consequences (such as fraud, identity theft, distress or discrimination) and how many people are affected.

Risk to individualsICOIndividuals
Unlikely to result in a riskDo not notify; record in the breach logNo notification needed
Likely to result in a riskNotify within 72 hours of becoming awareConsider notifying
Likely to result in a high riskNotify within 72 hours of becoming awareNotify without undue delay

Step 4: Notify the ICO (within 72 hours)

Report online at ico.org.uk or by phone on 0303 123 1113. If not all details are known within 72 hours, report what is known and provide the rest in phases. Include:

  • the nature of the breach, categories and approximate numbers of individuals and records;
  • the Data Protection Lead’s contact details;
  • the likely consequences;
  • the measures taken or proposed to deal with it and reduce harm.

Step 5: Tell affected individuals

Where the breach is likely to result in a high risk, tell the people affected without undue delay, in plain language: what happened, the likely consequences, what we are doing, what they can do to protect themselves (for example changing passwords or watching for phishing), and who to contact.

When we are a processor

If the breach affects data we process for a client, we notify that client without undue delay and in any case within 24 hours of becoming aware, with the information they need to meet their own obligations. The client decides whether to notify the ICO and individuals.

When a supplier has a breach

If a processor tells us of a breach affecting our data, we follow this procedure from Step 3.

Step 6: Record and learn

Every breach, including those not reported to the ICO, is recorded in the breach log: facts, effects, actions taken, the notification decision and the reasons. Within 30 days the Data Protection Lead reviews the root cause and agrees actions to prevent a repeat, such as training, process or technical changes.

Key contacts

WhoContact
Data Protection Leadinfo@promintal.co.uk
Information Commissioner’s Officeico.org.uk · 0303 123 1113
Action Fraud (cyber crime)actionfraud.police.uk · 0300 123 2040
PSNI (Northern Ireland)101, or 999 in an emergency

Questions about this document: info@promintal.co.uk. Other documents are listed on our Privacy & GDPR page.