Guide Data Privacy Compliance

GDPR compliance: requirements and checklist for businesses

The EU General Data Protection Regulation (GDPR) has applied since 25 May 2018, yet many organisations still struggle to keep their privacy obligations up to date: lawful bases that were never documented, breach procedures that misread the 72-hour rule, and processing records nobody has touched in years. This guide sets out what the GDPR requires, which obligations apply to every controller and which are triggered by specific processing, and the evidence you should be able to produce.

29 April 2026
9 min read
Updated 18 November 2026
Key takeaways
  • The GDPR applies to processing in the context of an EU establishment, and to non-EU organisations that offer goods or services to people in the EU or monitor their behaviour there. EU customers or a website reachable from the EU are not, on their own, the test.
  • Every processing activity needs a lawful basis under Article 6, plus an Article 9 condition for special category data, identified and documented before processing starts.
  • Reportable breaches go to the supervisory authority without undue delay and, where feasible, within 72 hours. Every breach must be logged, including those you do not report.
  • Rights requests must be answered within one month, extendable by two further months where necessary. They are normally free, but manifestly unfounded or excessive requests can be charged for or refused.
  • Fines of up to €20 million or 4% of worldwide annual turnover are ceilings, not tariffs. The UK GDPR is a separate regime, and EU to UK transfers are covered by an EU adequacy decision.

Who the GDPR applies to

Article 3 sets the territorial scope in two limbs. Under Article 3(1), the GDPR applies to processing carried out in the context of the activities of an establishment of a controller or processor in the EU, regardless of where the processing itself takes place. Under Article 3(2), it also applies to controllers and processors with no EU establishment when their processing relates to offering goods or services to individuals who are in the Union, or to monitoring their behaviour as far as that behaviour takes place in the Union.

Two points are often misunderstood. The test looks at where individuals are and what the organisation does, not at their nationality or residence. And a website that can be reached from the EU is not enough on its own: recital 23 looks for an apparent intention to offer services to people in the EU, such as EU languages or currencies, delivery to member states or references to customers there. A London or New York software company that sells subscriptions to users in the Netherlands with euro pricing and Dutch onboarding is likely to be caught by Article 3(2). The same company with a few EU sign-ups to an English-only, sterling-priced service needs a closer look before concluding either way.

For UK organisations, two regimes can apply side by side. The UK GDPR and the Data Protection Act 2018 govern processing in the UK and are enforced by the ICO. The EU GDPR applies in addition where Article 3 brings your processing into scope, for example through an EU subsidiary or by targeting people in the EU. This guide covers the EU GDPR.

EU representative (Article 27)

A non-EU controller or processor caught by Article 3(2) must generally designate, in writing, a representative established in one of the member states where the individuals concerned are. Article 27(2) exempts public authorities and processing that is occasional, does not include large-scale processing of special category or criminal offence data, and is unlikely to result in a risk to individuals. The representative is a contact point for authorities and individuals. It is not a DPO, and appointing one does not shift the controller's or processor's own responsibilities.

The GDPR assigns obligations by role, and roles are decided per processing activity. A controller determines the purposes and the essential means of processing. A processor processes personal data on a controller's behalf and on its documented instructions. Where two or more organisations jointly determine purposes and means, they are joint controllers under Article 26 and must agree who does what. A supplier can be your processor for the service it delivers and an independent controller for data it uses for its own purposes, such as its own billing, product analytics or fraud prevention. Contracts should reflect the roles as they actually are: calling a supplier a processor in a contract does not make it one.

Special category data

The GDPR applies stricter rules to special category data: health data, biometric data used to identify someone, genetic data, racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, and data concerning sex life or sexual orientation. Processing it requires a condition under Article 9 on top of an Article 6 lawful basis. Criminal convictions and offences data has its own rules in Article 10. Healthcare organisations, HR teams and any platform collecting health-related information should review their Article 9 conditions carefully.

The six lawful bases for processing

Every processing activity must rest on one of the six lawful bases in Article 6(1). The choice matters because it shapes which rights apply and what you must tell individuals. Organisations often default to consent where another basis fits better. Consent is only valid if it is freely given, which is hard to show where there is a clear imbalance of power, such as between employer and employee.

1
Consent
The individual has given freely given, specific, informed and unambiguous consent. Suited to genuinely optional processing such as some marketing. Consent must be as easy to withdraw as to give.
2
Contract
Processing is necessary to perform a contract with the individual, or to take steps at their request before entering into one. Covers processing customer data to deliver a service they have bought.
3
Legal obligation
Processing is necessary to comply with a legal obligation under EU or member state law. Covers payroll tax records, anti-money laundering checks and other legally required activities.
4
Vital interests
Processing is necessary to protect someone's life. A narrow basis, relevant in emergencies where no other basis is available.
5
Public task
Processing is necessary for a task carried out in the public interest or in the exercise of official authority, with a basis in EU or member state law. Applies mainly to public bodies.
6
Legitimate interests
Processing is necessary for the legitimate interests of the controller or a third party, unless those interests are overridden by the interests or rights of the individual. Not available to public authorities for processing in the performance of their tasks.

Legitimate interests requires a three-part test, documented before processing starts: identify the legitimate interest, show that the processing is necessary for it, and balance it against the interests, rights and freedoms of the individuals, taking their reasonable expectations into account. If the balance cannot be shown on paper, choose another basis or change the processing.

The obligations themselves, and the evidence a supervisory authority or customer will ask for, are covered in GDPR obligations in practice: records of processing, security, processor contracts, DPIAs, breach notification, DPOs, international transfers and data subject rights.

The fine structure

Article 83 sets two maximum levels. Infringements of the obligations of controllers and processors in Articles 25 to 39, which include records, security, breach notification, DPIAs, DPOs and processor contracts, can lead to fines of up to €10 million or 2% of total worldwide annual turnover of the preceding financial year, whichever is higher. Infringements of the basic principles, the conditions for lawful processing and consent, the special category rules, data subject rights and the transfer rules, and failure to comply with an order of a supervisory authority, can lead to fines of up to €20 million or 4%, whichever is higher.

These are ceilings, not automatic amounts. Article 83(2) requires authorities to weigh factors such as the nature, gravity and duration of the infringement, intent or negligence, action taken to mitigate the damage, the degree of cooperation, previous infringements and the categories of data affected. Cooperation and mitigation can count in your favour, but they guarantee nothing.

Fines are not the only tool. Under Article 58, authorities can issue warnings and reprimands, order processing to be brought into compliance, impose temporary or permanent limitations including bans, and order the suspension of data flows to third countries. Individuals can also claim compensation for material or non-material damage under Article 82. Many authorities, including the Dutch Autoriteit Persoonsgegevens, publish their decisions, which show where enforcement attention is going.

Getting your programme in order

If your programme has not been reviewed recently, start with an inventory of processing. A current record makes everything else easier: lawful basis reviews, DPIAs, privacy notices, rights requests and breach response all depend on knowing what you process, why, and where it goes.

  • Confirm whether and how the GDPR applies to you: EU establishments, targeting of people in the EU, monitoring of behaviour in the EU. If you are outside the EU and caught by Article 3(2), check whether you need an Article 27 representative.
  • Build or update your RoPA and record the lawful basis, and any Article 9 condition, for each activity.
  • Review privacy notices against what you actually do today, not what you planned when they were written.
  • Map suppliers by role. Put Article 28 contracts in place for genuine processors, and data sharing or joint controller arrangements where the supplier is a controller.
  • Write a breach procedure covering processor notification, the risk assessment, the 72-hour target, communication to individuals and a log of every incident.
  • Set up a rights request procedure with an owner, identity checks and a log, and test it with a simulated request.
  • Screen new and changed processing for DPIA triggers, and record the outcome even when no DPIA is needed.
  • List your international transfers and the mechanism for each: adequacy, SCCs with a transfer assessment, or another Chapter V tool.
  • Agree retention periods and check that deletion actually happens.
  • Check the Article 37 criteria for a DPO, and name an accountable owner either way.

Our audits and compliance team works with organisations at every stage of building a GDPR programme, from initial gap assessments to ongoing DPO advisory support.

The authoritative text of the GDPR, Regulation (EU) 2016/679, is on EUR-Lex. The European Data Protection Board publishes guidelines, recommendations and opinions on topics such as consent, breach notification, transfers and controller and processor roles at edpb.europa.eu. These interpret the GDPR rather than bind organisations directly, although the EDPB can adopt binding decisions in specific disputes under Article 65. The current list of adequacy decisions is on the European Commission website.

Frequently asked questions

Does the GDPR automatically apply to a UK or other non-EU business with EU customers?

No. Without an EU establishment, the GDPR applies under Article 3(2) only where your processing relates to offering goods or services to people who are in the EU, or to monitoring their behaviour in the EU. Having some customers in the EU, or a website that can be reached from the EU, is not enough on its own; what matters is whether you target people in the EU, for example through EU languages, currencies or delivery. UK businesses that are caught must comply with the EU GDPR alongside the UK GDPR and will usually need an EU representative under Article 27.

What is the difference between a DPO and an EU representative?

A DPO (Articles 37 to 39) is an independent adviser, internal or external, who monitors compliance, advises on DPIAs and acts as a contact point for the supervisory authority. An EU representative (Article 27) is a person or company established in the EU that a non-EU controller or processor designates as its contact point for authorities and individuals. They have different triggers and purposes, so an organisation may need both, one or neither. Neither role takes over the controller's or processor's own legal responsibilities.

What are the maximum fines for GDPR infringements?

Article 83 sets two ceilings: up to €10 million or 2% of total worldwide annual turnover, whichever is higher, for infringements such as record-keeping, security and breach notification failures; and up to €20 million or 4% for infringements of the basic principles, lawful basis, data subject rights or transfer rules. Actual fines depend on the factors in Article 83(2), such as gravity, duration, intent, mitigation and cooperation. Authorities can also issue warnings, reprimands, processing bans and orders to inform affected individuals.

Ryland Deakin
About the author
Lead Consultant, Cyvra · CISM · CompTIA Security+ · MCP

Ryland has delivered cybersecurity, compliance, and IT management programmes for regulated organisations across the UK and the Netherlands for over 20 years. View full profile

Talk to Cyvra

Not sure where your GDPR programme has gaps?

We run data protection gap assessments and provide DPO advisory support for organisations in the Netherlands and UK.

Disclaimer: This article is for general informational purposes only and does not constitute legal, regulatory, or professional advice. Cyvra makes no warranty as to the accuracy or completeness of this content, which may not reflect the most current regulatory developments. Readers should seek independent legal and regulatory advice appropriate to their specific circumstances. Cyvra accepts no liability for any loss arising from reliance on this content.