Handling EU customers’ data and unsure where to start? This gdpr compliance checklist covers the essentials: know what data you hold, pick a lawful basis, secure it, document it, and be ready to report a breach within 72 hours.
This checklist is part of the wider topic of business data privacy, and it focuses on the steps for EU personal data.
| Item | Value |
|---|---|
| Maximum fine | Up to €20 million or 4 percent of global revenue, whichever is higher |
| Countries in the EEA | 30 countries (the 27 EU members plus Norway, Iceland and Liechtenstein) |
| Breach notification to the supervisory authority | Within 72 hours |
| Lawful bases for processing (Article 6) | Six conditions |
These figures come from Scrut’s GDPR checklist and GDPR.eu’s checklist. They can change, so check the source before you rely on them.
Does GDPR apply to your business?
GDPR is not limited to companies based in Europe. It covers any business that handles the personal data of people in the European Economic Area, which Scrut’s guide describes as 30 countries: the 27 EU members, plus Norway, Iceland and Liechtenstein.
Scrut lists three situations where you must comply:
- You offer goods or services to people in the EEA, even without charging money.
- You monitor the behavior of EEA residents, such as through tracking cookies.
- You process data on behalf of a company based in the EEA.
For a business outside the EU, the test is targeting. Copla’s guide says regulators read signals together, such as an EU language or euro pricing, delivery to EU countries, named EU customers and tracking of visitors’ behaviour. It adds that a website that is merely reachable from the EU is not enough.
Next, work out your role. A controller decides why and how personal data is processed, while a processor, such as a cloud provider or payroll vendor, acts on the controller’s behalf. Both carry obligations.
Map your data and keep records
Start with an information audit. GDPR.eu advises that you determine what information you process and who has access to it. The ICO, the UK regulator, says a data-mapping exercise can help you find out what personal data your organisation holds and where it is, as set out in its documentation guide.
Then record what you found. A useful record of processing covers these points:
- Your organisation’s name and contact details, plus any joint controllers, representative or data protection officer.
- The purposes of the processing.
- The categories of individuals and of personal data.
- The categories of recipients, such as suppliers.
- Any transfers to countries outside your own jurisdiction, with the safeguards in place.
- Retention schedules and a description of your security measures.
That list follows the ICO’s explanation of what to document under Article 30, which is UK guidance but mirrors the EU rule. Records must be kept in writing, and most organisations find electronic records easier to keep current.
Not every business has to keep a full record. GDPR.eu says organisations with at least 250 employees or higher-risk processing must keep an up-to-date, detailed list and be ready to show it to regulators. Smaller organisations should still do the exercise because it makes the other requirements easier.

Pick a lawful basis and tell people
Processing is illegal under the GDPR unless you can justify it under one of six conditions in Article 6, according to GDPR.eu. Choose a basis for each activity and write down your reasoning.
Consent carries extra obligations, including giving people the ongoing opportunity to revoke it. If you rely on legitimate interests, GDPR.eu says you must be able to show you have carried out a privacy impact assessment.
Your privacy policy is where you explain this. Article 12 requires that you tell people you are collecting their data and why, in a concise, transparent, intelligible and easily accessible form, using clear and plain language. Cover how the data is processed, who has access to it and how you keep it safe.
Regulators do check this. According to Copla, the European Data Protection Board launched a coordinated enforcement action in March 2026 in which 25 data protection authorities are contacting controllers to test the transparency duties in Articles 12 to 14. A privacy notice nobody has revisited in years is a weak point.
Secure the data and prepare for a breach
Build data protection by design into everything you do with personal data. GDPR.eu advises that you encrypt, pseudonymize or anonymize personal data wherever possible, and that you write an internal security policy.
That policy should give staff guidance on:
- Email security and passwords.
- Two-factor authentication.
- Device encryption.
- VPNs.
Run a data protection impact assessment when processing is likely to result in a high risk to people’s rights and freedoms. Know in advance who will carry it out and how.
For breaches, GDPR.eu states that you must notify the supervisory authority within 72 hours. You must also tell affected people quickly unless the breach is unlikely to put them at risk. Write a breach plan before you need one, with named owners and contact details for the regulator.
As of Copla’s guide, updated in November 2026, Article 33 still says 72 hours. Plan your breach process around that deadline.
Vendors, accountability and enforcement
Name someone who is accountable for GDPR compliance across your organisation, and appoint a Data Protection Officer if one is necessary. If your organisation is outside the EU, GDPR.eu says to appoint a representative within one of the EU member states.
Sign a data processing agreement with any third party that processes personal data for you. That includes analytics software, email services and cloud servers, and most services publish a standard agreement you can review.
Smaller teams can scale these steps down; the guide to data privacy compliance for small business shows how. If you also serve customers in California, read about ccpa compliance for small business for that separate law.
The cost of getting it wrong is real. Scrut notes that fines can reach €20 million or 4 percent of global revenue, whichever is higher. In 2025, it reports, TikTok faced a €530 million fine for transferring European user data to China without adequate safeguards, and LinkedIn was penalized €310 million for processing personal data without a proper legal basis, as described in Scrut’s guide.
Frequently asked questions
Does a small business need a record of processing?
Show answer
It depends on the regime and the risk. GDPR.eu says organisations with at least 250 employees or higher-risk processing must keep one, and smaller ones should still assess their data. Under the UK rules, the ICO says organisations with fewer than 250 employees only need to document processing that is not occasional, could risk individuals’ rights, or involves special category or criminal conviction data. The ICO page notes its guidance is under review following the Data (Use and Access) Act, so check for updates.
How fast must you report a data breach?
Show answer
Within 72 hours to the supervisory authority, according to GDPR.eu. As of Copla’s November 2026 update, Article 33 still says 72 hours and the proposed change is not law.
What is the maximum GDPR fine?
Show answer
The ceiling is whichever is higher of a fixed euro amount or a share of global revenue, as Scrut’s guide explains. The exact figures are in the summary table near the top.
Do you need a lawyer to use this checklist?
Show answer
GDPR.eu states that its checklist is not legal advice and recommends speaking with an attorney specialized in GDPR compliance who can apply the law to your circumstances. This article is educational only and works the same way.



