Article 27 GDPR for UK Companies Do You Need an EU Representative

Article 27 GDPR for UK Companies: Do You Need an EU Representative?

Summary

A UK company needs an EU representative under Article 27 of the GDPR when it offers goods or services to people in the EU, or monitors their behaviour there, and has no EU establishment. Two exemptions apply: occasional, low-risk processing and processing for public authorities. You must appoint the representative in writing, and they must be based in an EU country where those people are.

This guide covers when Article 27 applies, the exemptions, who can act as your representative, where they must be based and what the role does and does not do. It covers the EU GDPR only. UK law is outside its scope.

Key Takeaways

•  Article 27 follows Article 3(2). It applies to a company outside the EU that offers goods or services to people in the EU, or monitors their behaviour there.

•  The law looks at where the individuals are. Nationality doesn’t matter, and a UK citizen living in France counts.

•  Appointing a representative does not move your legal responsibility to them. You remain answerable for your processing.

When Article 27 Applies to a UK Company

Article 27(1) says that where Article 3(2) applies, the controller or processor must designate a representative in the Union in writing. So the first question is whether Article 3(2) covers you.

Article 3(2) applies to a controller or processor not established in the Union when its processing relates to one of two things:

•  offering goods or services to people in the Union, whether or not they pay; or

•  monitoring the behaviour of people in the Union, as far as that behaviour takes place there.

The test focuses on people in the Union. It says nothing about citizenship. A UK company that sells to a British expatriate living in Spain is covered by the same rule as one that sells to a Spanish national.

Offering Goods or Services to People in the EU

The European Data Protection Board (EDPB) says processing personal data of someone in the EU is not enough on its own. The company must be targeting, meaning it has shown it plans to offer goods or services to people in one or more EU countries. Our guide to Article 27 GDPR for US companies looks at how this targeting test is judged for American businesses.

Recital 23 says that a website being reachable from the EU, an email address, or a language used in the company’s own country does not settle the question. The EDPB’s guidelines on territorial scope list factors that point towards targeting, and they work best in combination:

•  an EU country is named in connection with the product or service;

•  the company pays for search advertising or runs campaigns aimed at an EU country audience;

•  the site uses an EU country domain such as “.de”, or a neutral one such as “.eu”;

•  the site uses a language or currency of an EU country that the company’s home country does not generally use, especially with the option to order in it;

•  the company delivers goods to EU countries; and

•  the site mentions customers based in various EU countries.

A UK online shop with prices in euros, a German-language version,n and delivery to Germany is a clear case. A UK plumber whose website happens to be readable in Berlin is not.

Monitoring Behaviour in the EU

The second trigger covers monitoring. The EDPB gives examples that include behavioural advertising, location tracking for marketing, online tracking through cookies or fingerprinting, and health analytics services.

Monitoring does not need the same intention to target. The EDPB still says that not every online collection of data about people in the EU counts. It looks at why the company collects the data and whether it analyses or profiles behaviour afterwards.

A UK company with no EU customers can still fall inside Article 3(2) if it tracks visitors in the EU for behavioural advertising or profiling.

The Two Exemptions

Article 27(2) removes the duty in two cases.

The first is processing that meets every one of these conditions:

•  it is occasional;

•  it does not include large-scale processing of special category data or criminal offence data; and

•  it is unlikely to result in a risk to the rights and freedoms of individuals, taking into account its nature, context, scope and purposes.

The second is a public authority or body.

The EDPB reads “occasional” narrowly. Processing is occasional only if it is not carried out regularly and falls outside the company’s normal course of business. It also notes that the risk test refers to any risk, not only high risk. A company that serves EU customers as part of its normal trade is unlikely to qualify.

Who Can Act as Your Representative

The EDPB says a representative can be an individual or an organisation established in the Union. In practice, this includes law firms, consultancies, and other companies appointed through a service contract. One representative can act for several non-EU controllers and processors.

Some roles do not fit. The EDPB does not consider the representative role compatible with that of an external data protection officer because a DPO must act independently, while a representative acts on the company’s instructions. It also does not consider the role compatible with acting as the company’s processor.

A single company does not need a separate representative for each processing activity.

Where the Representative Must Be Based

Article 27(3) says the representative must be established in one of the Member States where the people whose data you process are. If most of them are in one country, the EDPB recommends choosing a representative in that country, while staying easy to reach for people in the others.

The location of your data processing does not decide this. The location of the individuals does.

What the Representative Does

Under Article 27(4), the representative must be addressed by supervisory authorities and individuals, in addition to or instead of you, on all issues related to processing. In practice, they:

•  act as the contact point for EU supervisory authorities and for individuals;

•  keep a copy of your record of processing activities under Article 30, which you must keep accurate and supply to them; and

•  pass on communications to you so that you can respond.

You must also name the representative in your privacy notice. Articles 13(1)(a) and 14(1)(a) require the identity and contact details of the controller’s representative, where applicable. The EDPB adds that failing to tell people who your representative is breaches your transparency duties. The GDPR does not require you to notify the supervisory authority of the appointment.

The representative should be able to communicate in the languages of the authorities and individuals they deal with.

Responsibility Stays With You

Article 27(5) states that the appointment is without prejudice to legal action against the controller or processor. Recital 80 says it does not affect their responsibility or liability.

The EDPB confirms that the GDPR does not make the representative liable in your place. It also says the role was created so that authorities can start enforcement through the representative, and that the representative can be held directly liable only for its own duties under Articles 30 and 58(1)(a).

The EDPB calls a representative essential so authorities and individuals can contact them easily. Choose one that is easy to reach.

Conclusion

Article 27 turns on where your customers and the people you track are. Nationality does not change the answer, and the exemptions are narrow. Check whether you offer goods or services to people in the EU or track their behaviour; if so, appoint a suitable representative in writing and name them in your privacy notice.

We are updating this guide because the original quoted a fine figure, referred to EU citizens where the law covers people in the Union, described UK legislation as still passing through Parliament, and treated the UK GDPR as the Data Protection Act 2018. If you need an EU-based point of contact, see our Article 27 EU Representative service, read why a representative matters for EU sales and marketing, or speak to our GDPR consultants.

Frequently Asked Questions

Does a UK Company Always Need an EU Representative?

No. Article 27 applies only where Article 3(2) does, meaning the company is not established in the EU and offers goods or services to people in the EU or monitors their behaviour there. A company with an EU establishment, or one that only has incidental EU contact, falls outside it. The exemptions in Article 27(2) also apply in narrow cases.

Can Our Data Protection Officer Be Our EU Representative?

The EDPB does not consider an external DPO able to act as the company’s representative because the DPO must work independently, while a representative acts on the company’s instructions. Choose a separate representative.

Does Appointing a representative make us compliant?

No. The appointment covers one obligation. The company remains responsible for all its GDPR duties, and the representative is not liable in its place.

Disclaimer: This blog post is intended solely for informational purposes. It does not offer legal advice or opinions. This article is not a guide for resolving legal issues or managing litigation on your own. It should not be considered a replacement for professional legal counsel and does not provide legal advice for any specific situation or employer.

About the Author

Ana Mishova

Sales & Business Development Consultant

Ana Mishova is a Sales & Business Development Consultant at GDPRLocal, the UK’s fastest-growing B2B compliance partner. With four years at the company, she has experience across operations, from creating processes and shaping compliance services to driving growth through sales, marketing, and strategic partnerships.

Her prior experience includes working closely with current and prospective clients and coordinating with stakeholders to design and plan compliance products. She has led internal change initiatives, driven sales, and guided organisations in selecting the most appropriate compliance strategies.

She holds a degree in psychology, which enhances her ability to connect with people and understand their needs. At GDPRLocal, she works with colleagues to strengthen the sales function and plays an active role in developing the sales strategy.