Protecting customer data, and what to do in the first 72 hours
Keep less, limit who can reach it, back it up, delete on schedule. And if it leaks: the GDPR 72-hour notification rule, step by step.
Customer data is the part of your business that does the most damage when it leaks: names, emails, addresses, order histories, sometimes ID documents or health details. The controls that matter most are simple. This guide covers the four that do most of the work, and what the law expects from you in the first days after a breach.
1. Keep less
Data you never collected cannot leak. The GDPR’s data minimisation principle (Article 5) says personal data must be limited to what is necessary for its purpose, and the storage limitation principle says it must not be kept in identifiable form longer than needed.
Start with an inventory. For each system that holds customer data (website, shop, email, accounting, CRM, shared drives, spreadsheets on laptops) write down:
- what data it holds,
- why you need it,
- who can access it,
- how long you keep it.
Then cut. Typical wins:
- Stop collecting fields nobody uses.
- Delete exported spreadsheets once the job they were made for is done.
- Remove copies of ID documents once you have checked them, if you only needed to check them.
- Close old systems properly, including the data inside them.
2. Restrict access
Many leaks start with an ordinary account: a reused password, a phished login, a former employee who still has access.
- One person, one account. No shared logins for the shop admin or the mailbox, so you know who did what.
- Least access. Staff get the access their job needs, not admin by default.
- Two-step sign-in on email, the website admin, the shop, cloud storage and anything holding customer data. Start with email: whoever controls it can reset most other passwords.
- Leavers checklist. Remove access on the person’s last day, including shared passwords they knew.
- Review quarterly. List every account with access to customer data. Remove anything you cannot explain.
- Check your suppliers. Your web host, developer and software providers handle your customers’ data on your behalf. Know who they are and what they can access.
3. Back up, and test it
Ransomware and accidental deletion are breaches too. The EDPB’s breach guidelines treat a loss of access to personal data as an “availability breach”, even if it is temporary.
The UK’s National Cyber Security Centre gives clear, small-business advice:
- Back up everything the business needs to run, including customer information.
- For extra protection, keep two backups: one online and one on a separate storage device.
- Do not leave that device connected when not in use, because some malware spreads to connected drives.
- Protect online backup accounts with two-step sign-in.
- Know how to restore, and check the backup contains what you need.
The NCSC’s principle is worth remembering: with at least one backup offline at any given time, an incident cannot affect all of your backups at once.
A backup you have never restored is a guess. Restore one file and one full system at least once a year.
4. Delete on schedule
Set a retention period for each type of data and put deletion in the calendar. For example:
- Unanswered enquiries: 12 months.
- Customer records: as long as the relationship lasts, plus what tax and accounting rules require.
- Job applications from people you did not hire: a short, fixed period.
Deletion includes backups and exports. Old data in a forgotten folder is still data you are responsible for.
When something goes wrong
What counts as a breach
A personal data breach is any security incident that leads to personal data being lost, destroyed, changed, disclosed or accessed without authorisation. The EDPB groups them into three types:
- Confidentiality: someone sees data they should not (a hacked mailbox, an email sent to the wrong list).
- Integrity: data is changed without authorisation.
- Availability: data is lost or locked (ransomware, a deleted database with no backup).
The 72-hour rule
Article 33 of the GDPR requires the controller to notify the supervisory authority “without undue delay and, where feasible, not later than 72 hours after having become aware of it”. The UK GDPR has the same rule for UK organisations, with the Information Commissioner’s Office (ICO) as the authority.
Key points:
- The clock starts at awareness. The EDPB says you become aware when you have a reasonable degree of certainty that an incident has compromised personal data. You are expected to investigate quickly, not wait.
- You do not need every answer. Article 33(4) allows information to be provided in phases. Send what you know, then update.
- Late is still required. If you notify after 72 hours, you must give reasons for the delay.
- The exception is narrow. You can skip notifying only if the breach is unlikely to result in a risk to people’s rights and freedoms.
- Record every breach. Article 33(5) requires you to document all breaches, including ones you decide not to report, with the facts, effects and action taken.
- Your suppliers must tell you. Article 33(2) requires processors, such as your host or software provider, to notify you without undue delay.
Telling the people affected
If a breach is likely to result in a high risk to individuals, Article 34 requires you to tell them directly, without undue delay. The EDPB notes the main goal is to help people protect themselves, so tell them what happened and what they should do, such as changing a password or watching for phishing.
A first-hours checklist
- Contain. Reset compromised passwords, revoke sessions, take affected systems offline if needed.
- Preserve evidence. Keep logs and do not wipe affected machines before they are examined.
- Assess. What data, how many people, how sensitive, was it encrypted?
- Decide and notify. Authority within 72 hours if there is a risk. Individuals if the risk is high.
- Fix the cause. Then check whether the same weakness exists elsewhere.
- Write it up. Your breach record is required whether or not you reported it.
Prepare this now: who decides, who contacts the authority, where the authority’s reporting form is. At hour 40 is a bad time to look it up.
General guidance, not legal advice.
Where EWC can help
Our tailored cybersecurity assessment looks at the systems that hold your customer data, including access controls and data exposure, and gives you a prioritised plan to close the gaps.
Πηγές
Σε τι βασίζεται αυτό το άρθρο.
6 πηγές- Intersoft Consulting (GDPR text)GDPR Article 33: Notification of a personal data breach to the supervisory authoritygdpr-info.eu
- legislation.gov.ukUK GDPR Article 33: Notification of a personal data breachlegislation.gov.uk
- European Data Protection BoardGuidelines 9/2022 on personal data breach notification under GDPR (version 2.0)edpb.europa.eu
- Intersoft Consulting (GDPR text)GDPR Article 5: Principles relating to processing of personal datagdpr-info.eu
- National Cyber Security Centre (UK)Small organisations guide to cyber security: Backing up your datancsc.gov.uk
- National Cyber Security Centre (UK)Offline backups in an online worldncsc.gov.uk


