GDPR Compliance for Businesses: A Step-by-Step Checklist (and What Companies Actually Get Fined For)
GDPR compliance means knowing what personal data you hold and why, telling people about it, keeping it safe and answering their requests on time. There is no certificate to buy and no approval to wait for.
The rules are the same for a two-person web shop and a bank, but the work isn’t. A small business with customer emails, a payroll and a contact form can cover the basics in a few days, and keep them up with a few hours a year.
This guide gives you the checklist, then shows what companies are actually fined for, using the 3,094 fines in our GDPR fines tracker. The pattern is useful. Most fines aren’t for exotic mistakes. They’re for unanswered emails, missing paperwork and websites nobody updated.
We rewrote this page in November 2026; the old version was from 2024. The law, the fines data and the pending EU reforms were checked on 16 November 2026. This is a practical guide, not legal advice.
Does the GDPR apply to your business?
Almost certainly, if you have customers, staff or website visitors in Europe. The GDPR applies when:
- your business is established in the EU or the EEA (Norway, Iceland, Liechtenstein), wherever the data is processed;
- you are based elsewhere but offer goods or services to people in the EU, or monitor what they do there, for example with tracking cookies or ad profiles.
There is no small-business exemption. A sole trader with a customer list is a “controller” just like a multinational. Size only changes a few duties, such as keeping formal records (step 9 below), and it counts when a regulator sets a fine.
Personal data means anything that identifies a living person directly or indirectly: names, email addresses, phone numbers, IP addresses, customer IDs, photos, CCTV footage. Data about companies isn’t personal data, but the name and email of your contact at that company is.
Two roles matter. You are a controller for data you decide to collect and use (your customers, your staff). You are a processor when you handle data on a client’s behalf, as a web agency, payroll bureau or SaaS provider does. Many businesses are both, and processors have their own, shorter list of duties.
The UK has its own version, the UK GDPR, which is still very close to the EU text. The differences are in the UK section below.
The GDPR compliance checklist, step by step
Work through these in order. The first two steps decide most of the rest.
- Map your data. List what personal data you hold, where it sits (CRM, mailbox, accounting software, spreadsheets, backups), who can see it, who you share it with and how long you keep it. A spreadsheet is fine. Most businesses find data they forgot about, usually in old mailboxes and exports.
- Choose a lawful basis for each purpose. The GDPR gives six (Article 6). Consent is only one of them, and often not the best: you don’t need consent to deliver an order (contract), keep invoices (legal obligation) or prevent fraud (legitimate interests). Consent is the right basis for things like marketing emails to new contacts, and it must be freely given and as easy to withdraw as to give.
- Write a privacy notice people can understand. Article 13 lists what it must say: who you are, what you collect, why, on which lawful basis, who receives it, whether it leaves the EU, how long you keep it, and what rights people have. A notice copied from a template that mentions services you don’t use is a common finding in fines.
- Sort out cookies and trackers. Analytics, ad pixels and embedded videos usually need consent before they load, under the ePrivacy rules that sit next to the GDPR. Our cookie consent guide covers what a banner must do. Be careful with trackers on pages about health, money or children: sending those page visits to an ad platform has led to fines on its own.
- Sign contracts with your processors. Your hosting company, email marketing tool, payroll provider and cloud storage all process data for you. Article 28 requires a written contract with set terms, usually called a data processing agreement (DPA). Big providers publish one that applies automatically; check that you have it and keep a copy.
- Secure the data. Article 32 asks for security that fits the risk, without a fixed list. In practice: multi-factor sign-in on email and admin accounts, software updates (including your website’s plugins), limited access, encrypted laptops and phones, backups you have tested, and dummy data instead of real customer records on test systems.
- Be ready for requests. People can ask for a copy of their data, a correction, deletion or an end to marketing, and you have one month to answer. Name a person and an inbox for it. Our guide to data subject rights explains each right from the other side.
- Have a breach plan. If personal data is lost, stolen, sent to the wrong person or exposed, you have 72 hours from becoming aware of it to report it to your data protection authority, unless it is unlikely to put anyone at risk (Article 33). If the risk to people is high, you must tell them too. Log every breach, including the ones you don’t report.
- Keep records of your processing. Article 30 requires a written record of what you process and why. The exemption for businesses under 250 staff is narrower than it looks: it falls away when processing is not occasional, which payroll and a customer database never are. Your data map from step 1 is most of this record already.
- Check data that leaves Europe. Sending personal data outside the EEA needs a legal route. US providers certified under the EU–US Data Privacy Framework are covered for now; for others, standard contractual clauses are the usual tool. The chapter on transfers to the US below has the details.
- Make someone responsible and train the team. Staff handle most of the data and cause most of the mistakes: the wrong attachment, the open CC list, the shared password. A short yearly briefing and a named person to ask cover a lot. If you employ people, our page on employee data under the GDPR covers your obligations as an employer.
Three extra duties apply only to some businesses: a data protection officer, impact assessments and an EU representative. They have their own section below.
What companies actually get fined for
Our tracker has collected 3,094 GDPR fines from May 2018 to 16 October 2026. The big ones make the news (the ten largest add up to about two thirds of the €8.3 billion total), but they are rare. The median fine is €8,000. More than half of all fines are €10,000 or less, and 85% are €100,000 or less.
That is the realistic picture for a small or medium business: a five-figure fine, usually after a complaint from a customer, an employee or a neighbour, plus an order to fix the problem. The reasons repeat.
Two recent cases show how ordinary the triggers are. In July 2026 Romania’s authority fined the online retailer HOMELUX €15,000 after hackers got into a website that ran an outdated version of its platform, helped by weak passwords that weren’t changed afterwards (ANSPDCP). In Poland a fertility clinic sent one patient a payment confirmation that named another patient’s genetic test, decided the slip wasn’t worth reporting and was fined PLN 40,000, about €9,400 (UODO).
Notice what the table doesn’t contain. Very few fines are for missing a certificate, a policy binder or an expensive tool. They are for things that a named person, a calendar reminder and an updated website would have prevented. Not cooperating with the regulator is a category of its own, and it is the cheapest one to avoid: answer their letters.
Is there a GDPR certificate or approval you need?
No. Nobody approves your business before you start processing data, and no certificate is required by law. People often search for “GDPR approval” expecting a licence of some kind, and a whole industry is happy to sell them one.
What exists is voluntary. Article 42 lets approved bodies certify specific processing operations, and the EDPB has approved one scheme valid across the EU, Europrivacy, first in 2022 and in an updated version in April 2026 (Opinion 14/2026; see the EDPB’s register of certification mechanisms). A certificate can help you show clients and regulators that you take this seriously. It does not make you compliant and does not reduce your responsibility (Article 42(4)).
A few formalities do exist:
- Prior consultation: if an impact assessment shows a high risk you can’t reduce, you must consult your authority before you start (Article 36). Few small businesses ever get there.
- DPO contact details: if you appoint a data protection officer, you must publish their contact details and tell your authority (Article 37(7)).
- UK fee: in the UK, most businesses that process personal data must pay the ICO’s yearly data protection fee and appear on its public register. That is a fee, not an approval.
If someone sells you an official “GDPR certificate” for €99, what you have bought is a PDF.
Do you need a DPO, an impact assessment or an EU representative?
Most small businesses need none of the three. Check each one anyway, because the tests are about what you do, not how big you are.
A data protection officer (Article 37) is required if you are a public body, if your core business involves regular and systematic monitoring of people on a large scale (tracking, profiling, many CCTV sites), or if your core business is processing sensitive data such as health data on a large scale. A small dental practice usually isn’t large-scale; a hospital is. Some countries add their own triggers: Germany, for example, requires a DPO once 20 people regularly handle personal data. The DPO must be independent, so the owner or IT manager usually can’t do it; Polish and Italian authorities have fined organisations for exactly that, or for not notifying the DPO’s details.
An impact assessment (DPIA, Article 35) is needed before processing that is likely to be high-risk: large-scale sensitive data, systematic monitoring, new technology such as facial recognition, or combining data sets about people. Each national authority publishes a list of processing that always needs one.
An EU representative (Article 27) is needed by businesses with no establishment in the EU that are covered by the GDPR anyway, for example a US online shop that ships to Europe. The exception is occasional, low-risk processing that doesn’t involve sensitive data at scale.
Sending personal data to the US
Your CRM, newsletter tool, cloud storage and help desk probably count. If a provider stores your customers’ or staff’s data in the US, or can reach it from there, that is a transfer under Chapter V of the GDPR, and it needs a legal route.
First, look the provider up on the Data Privacy Framework list. Since 10 July 2023, US companies certified under the EU–US Data Privacy Framework (DPF) count as offering adequate protection, so the transfer itself needs no extra contract. The DPF list is kept by the US Department of Commerce. The EDPB’s FAQ for European businesses asks for two checks there: the certification must be active (companies renew it every year, and the list also shows those that dropped out), and it must cover the data you send. Staff data counts as HR data, which not every certification includes. Save a dated screenshot of the entry. It’s your proof if a regulator asks.
UK businesses rely on the UK Extension to the DPF, in force since 12 October 2023, so the provider’s entry must show that it joined the extension too.
Not on the list? Use standard contractual clauses. The European Commission’s standard contractual clauses (SCCs) are the usual route. Look for them in the provider’s data processing agreement, and ask if they’re missing. SCCs come with a short written transfer impact assessment: can US authorities get at this data, and what protects it? For the US that got easier in 2023, when the EDPB said the safeguards the US adopted for the DPF, including the new redress mechanism, apply to all data sent there, whatever the transfer tool. If a provider only stores your files, encrypting them with keys only you hold is the measure the EDPB’s recommendations accept as effective.
File-sharing and file-transfer tools follow the same rules. No official “GDPR-compliant” label exists for a tool (see the certificate chapter above); what decides is a processing agreement, where the files are stored and, for a US provider, one of the two routes above.
What gets fined. Our GDPR fines tracker lists 21 fines for unlawful transfers out of Europe, about €2.1 billion in total. Meta’s €1.2 billion in 2023, for Facebook users’ data sent to the US, is still the largest fine in the tracker. Uber was fined €290 million in 2024 for keeping European drivers’ data, including ID documents and in some cases medical data, on US servers for more than two years without any transfer tool. China is the other big theme: TikTok’s €530 million in 2025 was mainly for staff in China accessing European users’ data.
Will the DPF last? It is in force today, and transfers under it are lawful. The record is the worry. The EU Court of Justice struck down both earlier deals, Safe Harbor in 2015 and Privacy Shield in 2020. The General Court upheld the DPF on 3 September 2025, and the appeal against that judgment (C-703/25 P) is pending. Then, on 29 June 2026, the US Supreme Court ruled in Trump v. Slaughter that the President may remove FTC commissioners at will, and the FTC’s independence is one of the pillars the EU’s decision rests on. The EDPB asked the Commission on 31 July 2026 to assess whether the ruling affects the framework. The Commission says it is analysing the judgment, and noyb, the group behind both earlier cases, has announced a lawsuit of its own.
Plan for the day it falls. When Privacy Shield went in 2020, there was no grace period. Mark in your data map which providers you use only under the DPF, ask them now whether SCCs take over automatically, and decide which data you’d rather keep with an EU provider. Two deals have fallen already; planning for a third is bookkeeping, not paranoia.
Doing it on a small budget
GDPR compliance for a small business is mostly time, not money. The expensive parts are fixing old problems (an outdated website, a CRM nobody cleaned up) and specialist help when you process sensitive data.
The free material from regulators is better than most paid templates:
- the EDPB’s data protection guide for small business, available in most EU languages;
- your national authority’s own checklists and model notices (France’s CNIL, Ireland’s DPC and the UK’s ICO publish good ones);
- the GDPR text itself, which is easier to read than its reputation suggests.
Paid tools make sense for cookie consent on a busy website and for handling requests at volume. They don’t replace the data map, the lawful bases or the person who answers the inbox. A tool that promises full compliance by itself is selling the wrong thing.
UK businesses: what's different
The UK GDPR still matches the EU rules on almost everything in the checklist. The differences that matter for day-to-day compliance:
- The data protection fee. Most controllers pay the ICO £52 a year (turnover up to £632,000 or no more than 10 staff), £78 (up to £36 million or 250 staff) or £3,763 for larger organisations (ICO). The fees rose to these levels in February 2025.
- A complaints procedure. Since 19 June 2026, under the Data (Use and Access) Act 2025, every controller must give people a way to complain to it directly about its use of their data, acknowledge a complaint within 30 days and deal with it without undue delay.
- Other changes from the same Act ease some rules on cookies, research and legitimate interests. They don’t change the basic checklist.
A UK business that also sells into the EU needs to follow both, and may need an EU representative.
What's changing in 2026 and 2027
Two EU reform packages would lighten some duties. Neither is in force yet, so plan with today’s rules.
Records for small mid-caps (Omnibus IV). The Commission proposed in May 2025 to free organisations with fewer than 750 staff from keeping processing records unless their processing is likely to be high-risk. Parliament and Council reached a provisional deal on 9 June 2026 that extends the relief to “small mid-caps” with fewer than 1,000 employees. The Parliament’s final vote is scheduled for 23 November 2026 (Legislative Observatory), after which the Council must adopt it and it must be published. Even then, the data map in step 1 stays useful: you can’t write a privacy notice or answer an access request without it.
Breach reporting (Digital Omnibus). The Commission’s November 2025 proposal would require reporting to the authority only for breaches likely to cause a high risk, give 96 hours instead of 72, and route reports through a single EU entry point. The Council agreed its position on 21 October 2026 and kept those changes; the Parliament hasn’t adopted its position yet. Until the new rules apply, report within 72 hours.
Procedure. From 2 April 2027 a new EU regulation (2025/2518) sets common procedures for cross-border complaints. It changes how authorities handle cases, not what you have to do.
Frequently Asked Questions
Some people found answers to these questions helpful
What does GDPR compliance mean for a business?
It means processing personal data lawfully and being able to show it: knowing what data you hold and why, having a lawful basis for each use, telling people in a privacy notice, signing contracts with processors, keeping data secure, answering requests within a month and reporting serious breaches within 72 hours.
Does the GDPR apply to small businesses?
Yes. There is no exemption by size. Businesses with fewer than 250 staff have a narrow exemption from keeping processing records, which most lose because their processing is regular, and fines take size and turnover into account.
Is there an official GDPR certification or approval?
No approval or certificate is required. Certification under Article 42 is voluntary; the EU-wide Europrivacy seal is one approved scheme. A certificate doesn't prove full compliance and doesn't reduce your responsibility.
How much can a GDPR fine be?
Up to €20 million or 4% of worldwide annual turnover, whichever is higher, for the most serious breaches, and up to €10 million or 2% for others. Real fines are mostly far lower: the median in our tracker of 3,094 fines is €8,000.
Do I need a data protection officer?
Only if you are a public body, or your core activities involve large-scale regular monitoring of people or large-scale processing of sensitive data. Some countries add triggers of their own; Germany requires one when 20 or more people regularly process personal data.
Does the GDPR apply to US and other non-EU companies?
Yes, if they offer goods or services to people in the EU or monitor their behaviour there, for example with tracking for advertising. Such companies usually also need to appoint an EU representative.