Both roles appear in the same law, both involve talking to regulators, and the same privacy notice often names both. As a result, many businesses get the GDPR representative vs DPO question wrong. In practice, a GDPR representative and a data protection officer (DPO) do very different jobs, fall under different rules, and different things trigger them.

This post compares the GDPR representative vs DPO roles side by side, explains who needs which, and answers whether one provider can fill both.

Contents

  1. What Does a GDPR Representative Do?
  2. What Does a DPO Do?
  3. How Do Article 27 and Article 37 Compare?
  4. Do You Need One, Both or Neither?
  5. Can One Provider Do Both?
  6. FAQs

What Does a GDPR Representative Do?

Your representative gives an overseas business a local contact point. Under Article 27 of UK GDPR and its EU equivalent, businesses with no UK or EU establishment that target people there must appoint one, unless an exemption applies. KEWDATA’s GDPR representative service covers both regions.

In practice, the role is mainly administrative. Your representative receives messages from regulators and individuals, passes them to you, and holds a copy of your records of processing. They act on your written mandate, so they follow your instructions within the limits of that agreement.

Where Your Representative Must Be Based

Moreover, the law fixes the location. For UK GDPR, your representative must be in the UK. For the EU GDPR, they must be established in a member state where the people whose data you process are located.

What Does a DPO Do?

Your DPO is an internal adviser and watchdog, whether employed directly or provided under a service contract. Under Article 39, the DPO informs and advises your organisation, monitors compliance, advises on impact assessments, and acts as the contact point for the ICO. Our guide to when a DPO is mandatory covers the Article 37 tests in detail.

Above all, independence defines the role. Article 38 says your DPO can’t take instructions on how to carry out their tasks, can’t be dismissed or penalised for doing them, and reports to your highest level of management. The DPO advises and monitors, while your organisation stays responsible for compliance.

Who Can Be Your DPO

Your DPO can be a member of staff or an external provider working under a service contract. Either way, they need expert knowledge of data protection law and practice, and their other duties can’t create a conflict of interest.

How Do Article 27 and Article 37 Compare?

The table below sets the two roles side by side.

GDPR representative Data protection officer
Legal basis Article 27 Articles 37 to 39
Who needs one Businesses outside the UK or EU that offer goods or services to, or monitor, people there Public bodies, and organisations whose core activities involve large-scale monitoring or large-scale special category or criminal offence data
Where they’re based In the UK, or in an EU member state where your customers are No fixed location, but they must be easily accessible
Relationship to you Acts on your written mandate Independent, and can’t take instructions on their tasks
Main job Contact point and record holder Adviser, monitor and contact point
Who they deal with Regulators and individuals Regulators, individuals and your own staff and leadership
Telling the ICO UK representative details don’t need to be sent to the ICO Contact details must be published and given to the ICO
Liability Doesn’t take on your liability Doesn’t take on your liability

In short, the triggers have nothing in common. Article 27 depends on where you’re established and who you target. Article 37 depends on what you do with personal data, and how much of it.

Do You Need One, Both or Neither?

In other words, your answer depends on two separate questions: where you’re based, and what your core activities involve.

Representative Only

US online stores selling to UK customers, with no large-scale monitoring or sensitive data, need a UK representative but not a DPO. UK firms selling into Europe face the mirror image, covered in our EU representative for UK companies checklist.

DPO Only

By contrast, UK healthtech firms processing patient records at scale, with no EU customers, need a DPO but not an EU representative.

Both

For example, US health apps with large numbers of EU users need an EU representative because of where they’re established, and a DPO because of the health data they process as a core activity.

Neither

Finally, UK consultancies serving UK clients, with no large-scale sensitive processing, need neither. They can still appoint a DPO voluntarily, but the same statutory requirements then apply.

Can One Provider Do Both?

One firm can offer representative cover and DPO services, but it shouldn’t fill both roles for the same business in the EU. The EDPB’s guidelines on the territorial scope of the GDPR, adopted in November 2019, say the representative role isn’t compatible with the role of an external DPO established in the EU.

Again, the reasoning comes down to independence. Your representative acts under your instructions, while your DPO must be free of them. One person or organisation can’t do both without one role undermining the other.

GDPR Representative vs DPO in Practice

The ICO’s guidance on UK representatives doesn’t address the question directly, but the same conflict applies under UK GDPR. If you need both roles, ask any provider how it keeps them separate before you sign, and check what a GDPR representative fee should cover.

Questions to Ask Before You Sign

First, find out who exactly will hold each role, whether they work for the same organisation, and how the provider handles a regulator contacting both. Also ask what happens if your representative’s instructions ever clash with your DPO’s advice.

GDPR Representative vs DPO: FAQs

A GDPR representative is a local contact point for businesses outside the UK or EU, appointed under Article 27 and acting on your written mandate. A DPO is an independent adviser and monitor under Articles 37 to 39, required because of what you do with personal data, not where you are based.
One firm can offer both services, but it should not fill both roles for the same business in the EU. The EDPB says the representative role is not compatible with the role of an external DPO established in the EU, because the representative follows your instructions while the DPO must be independent.
No. A DPO is mandatory for public bodies and for organisations whose core activities involve large-scale regular and systematic monitoring, or large-scale processing of special category or criminal offence data. Others can appoint one voluntarily.
Your DPO’s contact details must be published and given to the ICO. UK representative details do not need to be sent to the ICO, but they should appear in your privacy notice.
Neither takes on your liability. Your organisation stays responsible for complying with UK GDPR or the EU GDPR, whichever roles you appoint.

Which Role Does Your Business Need?

First, make two checks: where you’re established, and what your core activities involve. Our team helps you work out which roles apply, then sets up the right cover. You can appoint a GDPR representative for the EU or the UK.

For independent DPO support, explore our outsourced DPO service.

Leave A Comment

Receive the latest news in your email
Table of content
Related articles