The General Data Pro­tec­tion Reg­u­la­tion (GDPR) defines how personal data should be handled and es­tab­lishes a uniform data pro­tec­tion framework across the EU. Since Brexit, the UK has its own version, the UK GDPR, which applies alongside the Data Pro­tec­tion Act 2018. UK busi­nesses that serve customers in the EU often have to comply with both. The following GDPR summary outlines the key prin­ciples, explains what applies in the UK and includes a practical GDPR checklist for your business.

Key Takeaways

The GDPR at a glance:

  • The GDPR is an EU reg­u­la­tion that has applied directly and uniformly in all member states since 25 May 2018.
  • It protects in­di­vidu­als’ personal data and grants rights such as access, cor­rec­tion, and deletion.
  • In the UK, the UK GDPR and the Data Pro­tec­tion Act 2018 apply; the EU GDPR also applies to UK companies that offer goods or services to people in the EU or monitor their behaviour.
  • Core prin­ciples include law­ful­ness, purpose lim­it­a­tion, data min­im­isa­tion, and storage lim­it­a­tion.
  • Website operators need a clear privacy policy, valid consent for tracking, and ap­pro­pri­ate security measures.
  • Vi­ol­a­tions can lead to fines of up to €20 million (EU GDPR) or £17.5 million (UK GDPR), or 4% of global annual turnover, whichever is higher.

Why the GDPR is a reg­u­la­tion and not a directive

To un­der­stand how the GDPR works in practice, it’s important to look at the type of EU law it rep­res­ents. The General Data Pro­tec­tion Reg­u­la­tion is, as the name suggests, a reg­u­la­tion, not a directive. This dis­tinc­tion is crucial because it de­term­ines how the law is applied across the European Union.

What is an EU reg­u­la­tion?

An EU reg­u­la­tion is a legal act that is binding in its entirety and directly ap­plic­able in all member states. This means:

  • the same rules apply in every EU country
  • no national im­ple­ment­a­tion is required
  • companies must comply im­me­di­ately once the reg­u­la­tion applies

For the GDPR, this resulted in a uniform legal framework for data pro­tec­tion across the EU, which came fully into effect on 25 May 2018.

What is an EU directive?

A directive works dif­fer­ently. It sets goals and re­quire­ments that EU countries must achieve, but allows them to decide how to implement these rules in national law. This often leads to:

  • different in­ter­pret­a­tions across countries
  • varying national laws
  • legal frag­ment­a­tion

Before the GDPR, data pro­tec­tion in Europe was based on the Data Pro­tec­tion Directive (1995). Each country im­ple­men­ted it dif­fer­ently, which created in­con­sist­en­cies and legal un­cer­tainty.

Why the GDPR replaced the directive

The EU in­tro­duced the GDPR to eliminate these dif­fer­ences and create a con­sist­ent standard. Because it is a reg­u­la­tion, companies face the same core re­quire­ments across all EU markets, cross-border business becomes easier from a legal per­spect­ive, and en­force­ment is more con­sist­ent. At the same time, the GDPR still includes “opening clauses”, which allow member states to define certain details at the national level, for example in areas such as em­ploy­ment data rules or data pro­tec­tion officer re­quire­ments.

What this means for busi­nesses

For companies, the shift from directive to reg­u­la­tion has practical con­sequences:

  • You cannot rely on national dif­fer­ences to reduce com­pli­ance re­quire­ments
  • GDPR ob­lig­a­tions apply directly and uniformly across the EU
  • If you operate in­ter­na­tion­ally, you can build one com­pli­ance framework instead of many
Note

In short, the GDPR created a single, en­force­able rulebook for data pro­tec­tion in Europe, replacing a patchwork of national laws. This is why the EU General Data Pro­tec­tion Reg­u­la­tion is often described as a corner­stone of modern data pro­tec­tion law.

GDPR and UK GDPR: what applies in the UK?

When the UK left the EU, the EU GDPR was carried over into UK law. Since 1 January 2021, the UK has applied its own version, the UK GDPR, together with the Data Pro­tec­tion Act 2018. In terms of content, both regimes are still very similar: the prin­ciples, lawful bases, data subject rights and the role of the data pro­tec­tion officer largely cor­res­pond to the EU GDPR.

There are, however, some important dif­fer­ences:

  • Data (Use and Access) Act 2025: This act amended the UK GDPR, the Data Pro­tec­tion Act 2018 and the Privacy and Elec­tron­ic Com­mu­nic­a­tions Reg­u­la­tions (PECR). Most of its data pro­tec­tion pro­vi­sions have applied since 5 February 2026. Among other things, it in­tro­duced “re­cog­nised le­git­im­ate interests” as a new lawful basis, relaxed some rules on automated decision-making and created new ex­emp­tions from cookie consent.
  • Com­plaints procedure: Since 19 June 2026, or­gan­isa­tions must give in­di­vidu­als a way to make data pro­tec­tion com­plaints directly to them, ac­know­ledge com­plaints within 30 days and respond without undue delay.
  • Su­per­vis­ory authority: In the UK, data pro­tec­tion is enforced by the In­form­a­tion Com­mis­sion­er’s Office (ICO). Since 30 September 2026, it has been con­sti­tuted as the In­form­a­tion Com­mis­sion but continues to operate as the ICO.
  • Fines: Under the UK GDPR, fines can reach up to £17.5 million or 4% of global annual turnover, whichever is higher.
  • Data pro­tec­tion fee: Most or­gan­isa­tions that process personal data in the UK as a con­trol­ler must pay an annual data pro­tec­tion fee to the ICO unless an exemption applies.

Personal data can currently continue to flow freely from the EU to the UK: in December 2025, the European Com­mis­sion renewed its adequacy decision for the UK. It is valid until 27 December 2031.

Website Builder
From idea to website in record time with AI
  • Intuitive website builder with AI as­sist­ance
  • Create cap­tiv­at­ing images and texts in seconds
  • Domain, SSL and email included

What is the goal of the GDPR?

The General Data Pro­tec­tion Reg­u­la­tion is designed to address one central challenge, namely how personal data should be handled in a digital, data-driven economy. At its core, the GDPR has several key ob­ject­ives.

1. Protect in­di­vidu­als and their personal data

The primary goal of the GDPR is to protect the fun­da­ment­al rights and freedoms of in­di­vidu­als, es­pe­cially their right to data pro­tec­tion. In practice, this means giving people more control over how their personal data is collected, used, and shared. The reg­u­la­tion in­tro­duces clear rights, including:

  • the right to access personal data
  • the right to correct in­ac­cur­ate data
  • the right to delete data (right to be forgotten)
  • the right to object to certain types of pro­cessing

These rights ensure that in­di­vidu­als are no longer passive data sources but active par­ti­cipants in how their in­form­a­tion is used.

2. Create a con­sist­ent data pro­tec­tion framework across the EU

A second key objective of the EU General Data Pro­tec­tion Reg­u­la­tion is to harmonise data pro­tec­tion laws across all EU member states. Before the GDPR, different national laws created legal un­cer­tainty and made cross-border business more complex. The GDPR es­tab­lishes a single, unified framework that applies across the entire EU.

For busi­nesses, this means:

  • one con­sist­ent set of rules instead of multiple national laws
  • clearer legal ex­pect­a­tions
  • easier expansion across EU markets

3. Enable the free flow of data within the EU

The GDPR is not only about re­stric­tion. It also aims to ensure the free movement of personal data within the EU, as long as pro­tec­tion standards are met. This balance is essential because strong data pro­tec­tion builds trust, and that trust, in turn, enables digital services and in­nov­a­tion to develop and scale.

4. Strengthen ac­count­ab­il­ity and re­spons­ib­il­ity

Another important goal is to make or­gan­isa­tions directly re­spons­ible for how they handle data. To achieve this, the GDPR requires companies to document their data pro­cessing activ­it­ies, implement ap­pro­pri­ate technical and or­gan­isa­tion­al safe­guards, and be able to demon­strate com­pli­ance at any time. This shift toward ac­count­ab­il­ity is a key element of the GDPR.

5. Adapt data pro­tec­tion to modern tech­no­lo­gies

Finally, the GDPR is designed to be tech­no­logy-neutral and future-proof. It applies re­gard­less of how data is processed, whether through:

  • cloud systems
  • mobile apps
  • AI-driven analytics
  • or tra­di­tion­al databases

This ensures that the reg­u­la­tion remains relevant as new tech­no­lo­gies emerge.

What this means in practice

Taken together, these goals show that the GDPR is not just about re­strict­ing data use, but about creating a balanced framework that protects in­di­vidu­als, sets clear rules for busi­nesses, and supports in­nov­a­tion within defined bound­ar­ies. In short, the GDPR aims to balance data pro­tec­tion, business needs, and digital in­nov­a­tion within a single legal framework.

Key GDPR prin­ciples

The GDPR is built on several core prin­ciples that every company must follow:

  • Law­ful­ness and trans­par­ency: Data must be processed legally and trans­par­ently
  • Purpose lim­it­a­tion: Data may only be used for clearly defined purposes
  • Data min­im­isa­tion: Only necessary data may be collected
  • Accuracy: Data must be kept up to date
  • Storage lim­it­a­tion: Data must not be stored longer than necessary
  • Integrity and con­fid­en­ti­al­ity: Data must be protected against un­au­thor­ised access

These prin­ciples form the found­a­tion of the GDPR and guide all com­pli­ance measures.

Who does the GDPR apply to?

The General Data Pro­tec­tion Reg­u­la­tion applies to a wide range of or­gan­isa­tions, re­gard­less of where they are located. It covers:

  • companies based in the EU
  • companies outside the EU that process data of people in the EU
  • or­gan­isa­tions that monitor user behaviour within the EU

This broad scope is one of the most important aspects of the GDPR.

What this means for UK companies

For UK-based busi­nesses, the key concept is the EU GDPR’s ex­tra­ter­rit­ori­al scope. Since Brexit, the UK is no longer part of the EU, so the EU GDPR can apply to your company even if you have no es­tab­lish­ment in an EU member state. Under Article 3 of the EU GDPR, a UK company must comply if it processes personal data of in­di­vidu­als in the EU and its activ­it­ies are related to:

  • offering goods or services to people in the EU
  • mon­it­or­ing their behaviour within the EU

Offering goods or services to EU users

If your business actively targets customers in the EU, the GDPR applies. It also applies even if your service is free. Typical examples include:

  • selling products to EU countries
  • offering SaaS tools or digital services to EU users
  • dis­play­ing prices in euros or shipping to EU addresses
  • running marketing campaigns aimed at EU audiences

For example, a UK-based e-commerce store that ships to Germany must comply with the EU GDPR.

Mon­it­or­ing user behaviour

The GDPR also applies if you track or analyse how EU users behave online. This includes:

  • website analytics
  • cookies and tracking tech­no­lo­gies
  • be­ha­vi­our­al ad­vert­ising
  • user profiling

For example, a UK website using tracking tools to analyse visitors from France falls under the EU GDPR.

No physical presence in the EU required

One of the most important points for UK companies:

  • You do not need an office, employees, or servers in the EU
  • Your company size does not matter
  • Even small busi­nesses and startups can be affected

The GDPR focuses on where the user is located, not where your company is based.

When the GDPR does not apply

Not every UK company is auto­mat­ic­ally subject to the EU GDPR. It typically does not apply if:

  • you do not target EU users
  • you do not monitor EU user behaviour
  • EU visitors only access your site in­cid­ent­ally

For example, a UK blog that is ac­cess­ible worldwide but does not target EU users is usually not subject to the EU GDPR. For its UK readers, however, the UK GDPR still applies.

Practical impact for UK busi­nesses

If the EU GDPR applies to your company, you must comply with the same rules as EU busi­nesses. This includes:

  • having a lawful basis for data pro­cessing
  • providing a clear privacy policy
  • enabling user rights such as access and deletion
  • im­ple­ment­ing data pro­tec­tion measures
  • ap­point­ing a rep­res­ent­at­ive in the EU (Article 27 EU GDPR), unless an exemption applies, for example for oc­ca­sion­al, low-risk pro­cessing

At the same time, your ob­lig­a­tions under the UK GDPR and the Data Pro­tec­tion Act 2018 continue to apply. Failure to comply can lead to sig­ni­fic­ant fines and re­stric­tions on operating in the EU market.

What this means in practice

For UK companies, the EU GDPR fun­da­ment­ally changes how you think about data. It is not tied to where your business is located, but to where your users are. This means the reg­u­la­tion can apply as soon as you engage with in­di­vidu­als in the EU, re­gard­less of whether you have a physical presence there. In practice, if your business collects, processes, or analyses data from EU users in a mean­ing­ful way, the EU GDPR is likely to apply in addition to the UK GDPR.

What has changed since 2018?

The core GDPR rules remain unchanged, but en­force­ment and in­ter­pret­a­tion have evolved sig­ni­fic­antly.

1. Con­sist­ent en­force­ment and sub­stan­tial fines

Au­thor­it­ies are actively enforcing GDPR rules. According to DLA Piper’s annual GDPR fines survey, European su­per­vis­ory au­thor­it­ies issued fines totalling around €1.2 billion in 2025 alone.

2. More focus on trans­par­ency and consent

Reg­u­lat­ors in­creas­ingly scru­tin­ise:

  • cookie consent mech­an­isms
  • tracking tech­no­lo­gies
  • dark patterns in user in­ter­faces

3. New reg­u­lat­ory de­vel­op­ments (2025–2026)

The EU is currently working on updates to its digital laws through the Digital Omnibus ini­ti­at­ive. These proposed changes aim to:

  • simplify com­pli­ance for busi­nesses
  • modernise cookie and tracking rules
  • clarify defin­i­tions such as “personal data”
  • better align GDPR with AI reg­u­la­tion

It’s important to note that the GDPR-related changes are still proposals and have not yet been adopted. Until then, the current GDPR rules continue to apply in full. The Digital Omnibus is EU le­gis­la­tion and does not change the UK GDPR, but it will matter for UK busi­nesses that are subject to the EU GDPR.

4. Reforms in the UK

In the UK, the Data (Use and Access) Act 2025 has been the most sig­ni­fic­ant reform since Brexit. Its data pro­tec­tion pro­vi­sions are now largely in force, including the new com­plaints procedure and the relaxed cookie rules under PECR.

GDPR checklist and key steps for com­pli­ance

Use this GDPR checklist to quickly evaluate your current setup:

✓ Do you clearly document what personal data you collect?

✓ Do you have a lawful basis (e.g. consent or le­git­im­ate interest)?

✓ Is your privacy policy complete and easy to un­der­stand?

✓ Can users access, correct, or delete their data?

✓ Do you report data breaches to the ICO (and, where the EU GDPR applies, to the competent EU authority) within 72 hours?

✓ Have you im­ple­men­ted Privacy by Design and Privacy by Default?

✓ Are your pro­cessors (e.g. hosting providers) GDPR-compliant?

✓ Do you have a procedure for handling data pro­tec­tion com­plaints?

✓ Have you paid the ICO data pro­tec­tion fee (unless you are exempt)?

✓ If you serve EU customers: have you appointed an EU rep­res­ent­at­ive where required?

✓ Do you regularly review and update your data pro­tec­tion measures?

If you cannot answer all questions with “yes”, your GDPR com­pli­ance needs im­prove­ment.

How the GDPR affects website operators

For website operators, the GDPR has direct practical con­sequences:

Privacy policy

Every website must provide a clear and ac­cess­ible privacy policy that explains:

  • what data is collected
  • why it is collected
  • how long it is stored

Consent man­age­ment

Users must actively consent to:

  • cookies (where required)
  • tracking tech­no­lo­gies
  • marketing com­mu­nic­a­tions

Consent must be informed, specific, and revocable at any time.

In the UK, cookie rules are set out in PECR. Since 5 February 2026, certain low-risk cookies, such as first-party analytics cookies or cookies that remember a user’s display settings, no longer require consent, provided users are clearly informed and can object. Ad­vert­ising cookies still require consent. Fines for PECR breaches can now reach the same level as under the UK GDPR. If your website targets users in the EU, the stricter cookie rules of the EU member states continue to apply to them.

Data security

Companies must implement ap­pro­pri­ate technical and or­gan­isa­tion­al measures, such as:

  • en­cryp­tion
  • access controls
  • secure hosting

What are data pro­tec­tion officers and when are they required?

A data pro­tec­tion officer (DPO) is re­spons­ible for ensuring that an or­gan­isa­tion complies with the GDPR and handles personal data correctly. The role is primarily advisory and su­per­vis­ory, not op­er­a­tion­al.

In practice, a DPO:

  • informs and advises the company and its employees about their data pro­tec­tion ob­lig­a­tions
  • monitors com­pli­ance with the GDPR, including internal policies and processes
  • supports and reviews data pro­tec­tion impact as­sess­ments
  • trains staff and raises awareness about data pro­tec­tion
  • acts as a contact point for su­per­vis­ory au­thor­it­ies and data subjects

These re­spons­ib­il­it­ies are defined in Article 39 of the GDPR.

Under the GDPR, a data pro­tec­tion officer is required if:

  • you are a public authority or public body
  • your core activ­it­ies involve regular and sys­tem­at­ic mon­it­or­ing of in­di­vidu­als on a large scale
  • your core activ­it­ies involve large-scale pro­cessing of sensitive data (e.g. health data) or data relating to criminal con­vic­tions

The same criteria apply under the UK GDPR. There is no fixed employee threshold in the UK.

Note

Some EU countries (such as Germany) have ad­di­tion­al national re­quire­ments with fixed employee thresholds.

GDPR and other reg­u­la­tions

The GDPR does not exist in isolation. It interacts with other laws, including:

  • in the UK: the Data Pro­tec­tion Act 2018 and PECR, both amended by the Data (Use and Access) Act 2025
  • national data pro­tec­tion laws in EU member states (e.g. Germany’s TDDDG)
  • EU rules on cookies and elec­tron­ic com­mu­nic­a­tions under the ePrivacy Directive (the planned ePrivacy Reg­u­la­tion was withdrawn in 2025)
  • the EU AI Act, which also applies to UK providers whose AI systems are used in the EU

These frame­works in­creas­ingly overlap, es­pe­cially when it comes to tracking tech­no­lo­gies and AI.

Why GDPR com­pli­ance matters

GDPR com­pli­ance is essential for any or­gan­isa­tion that processes personal data of in­di­vidu­als in the EU or the UK. It helps busi­nesses avoid sig­ni­fic­ant legal and financial risks, including fines of up to €20 million under the EU GDPR or £17.5 million under the UK GDPR, or 4% of global annual turnover, whichever is higher. At the same time, com­pli­ance builds trust. Users expect trans­par­ency and control over their data, and companies that meet these ex­pect­a­tions are more likely to gain long-term customer con­fid­ence.

The GDPR also improves internal processes by requiring clear doc­u­ment­a­tion and struc­tured data handling. This leads to better data security, more efficient workflows, and greater ac­count­ab­il­ity. Ul­ti­mately, GDPR com­pli­ance is not just about avoiding penalties. It is about es­tab­lish­ing re­spons­ible data practices that support trust, reduce risk, and prepare busi­nesses for future reg­u­lat­ory de­vel­op­ments.

GDPR remains the standard for data pro­tec­tion

The General Data Pro­tec­tion Reg­u­la­tion continues to define how personal data is handled not only in the EU, but in­creas­ingly around the world. Its UK coun­ter­part, the UK GDPR, follows the same prin­ciples, even though the two regimes are gradually diverging in the details. While the core prin­ciples of the GDPR have remained stable since 2018, ex­pect­a­tions around trans­par­ency, ac­count­ab­il­ity, and data usage have become more precise and more strictly enforced.

For busi­nesses, this means that GDPR com­pli­ance is no longer a one-time project, but an ongoing re­spons­ib­il­ity. New tech­no­lo­gies such as AI, evolving reg­u­lat­ory ini­ti­at­ives like the Digital Omnibus, and stricter en­force­ment practices are con­tinu­ously shaping how the reg­u­la­tion is in­ter­preted in practice. Companies must therefore regularly review their processes, doc­u­ment­a­tion, and technical measures to ensure they remain compliant.

At the same time, the GDPR also offers clear ad­vant­ages. By es­tab­lish­ing con­sist­ent rules and high data pro­tec­tion standards, it creates trust among users and provides a reliable legal framework for operating across the EU market. Busi­nesses that take com­pli­ance seriously not only reduce legal risks, but also strengthen their cred­ib­il­ity and long-term com­pet­it­ive­ness.

Ul­ti­mately, the GDPR is not just about avoiding fines. It is about building re­spons­ible data practices that align with user ex­pect­a­tions and future reg­u­lat­ory de­vel­op­ments. Using a struc­tured GDPR summary and regularly reviewing your GDPR checklist can help ensure that your or­gan­isa­tion remains compliant, secure, and prepared for what comes next.

Reviewer

Go to Main Menu