Do US companies need a DPO?
Only if the GDPR applies to them (Art. 3(2): they offer goods or services to people in the EU or monitor their behavior) and they meet an Art. 37(1) trigger, or a member-state law such as Germany's requires one.[1] Many US companies that the GDPR covers need an EU representative under Art. 27 instead of, or as well as, a DPO.
Not legal advice. This page summarizes the GDPR and official guidance. Whether the GDPR applies to you, and whether you need a DPO or an EU representative, depends on facts that a qualified privacy lawyer should review.
For a quick first answer, use the GDPR self-check for DPO and EU representative duties. If you already know you need a DPO, see how outsourced DPO services work and what DPO providers publish as prices.
Does GDPR apply to a US company?
It can, even with no office in Europe. Article 3 sets out two routes.[1]
- Establishment (Art. 3(1)). If you have an establishment in the EU, such as a branch or subsidiary, the GDPR applies to processing in the context of its activities, wherever the processing takes place.
- Targeting or monitoring (Art. 3(2)). With no EU establishment, the GDPR still applies when your processing relates to (a) offering goods or services to people in the EU, paid or free, or (b) monitoring their behavior in the EU.
The EDPB's guidelines on territorial scope explain both tests.[2] A website that people in the EU can simply reach is not enough on its own. Signs of targeting include naming EU countries, using an EU language or currency that is not used in your home market, delivering to the EU, or running marketing aimed at EU audiences. Monitoring includes tracking people online, behavioral advertising and geolocation for marketing.
When is a DPO mandatory?
Under Article 37(1), a controller or processor must designate a DPO in three cases:[1]
- Public authorities and bodies, except courts acting in their judicial capacity.
- Large-scale monitoring as a core activity. Your core activities consist of processing that, by its nature, scope or purposes, requires regular and systematic monitoring of people on a large scale. The DPO guidelines give examples such as behavioral advertising, email retargeting, loyalty programs, location tracking by apps, and fitness or health tracking via wearables.[3]
- Large-scale sensitive data as a core activity. Your core activities consist of large-scale processing of special categories of data (Art. 9, such as health, genetic or biometric data) or data about criminal convictions and offenses (Art. 10).
If none of these apply, the GDPR does not require a DPO. The DPO guidelines recommend that you document the analysis behind that conclusion.[3]
What counts as "large scale" and "core activities"?
The GDPR defines neither term with a number. The EDPB-endorsed DPO guidelines (WP243) explain both.[3]
- Core activities are the key operations needed to achieve your goals. A hospital's processing of patient health data is core. Supporting functions, such as paying staff or standard IT support, are ancillary, not core.
- Large scale has no numeric threshold. The guidelines name four factors: the number of people concerned, as a number or a share of the relevant population; the volume of data and range of data items; how long or how permanently the processing runs; and its geographic reach.
- Examples from the guidelines. Large scale: a hospital processing patient data, a bank or insurer processing customer data in the regular course of business, or a search engine processing data for behavioral advertising. Not large scale: an individual physician's patient data, or an individual lawyer's data on criminal convictions.
- Regular and systematic monitoring means monitoring that is ongoing or recurs at intervals, and that follows a system or method. All forms of tracking and profiling on the internet count, including behavioral advertising.
Can EU national law require a DPO?
Yes. Article 37(4) lets EU or member-state law require a DPO in cases beyond Article 37(1).[1]
Germany is one example. Section 38 of its Federal Data Protection Act (BDSG) requires controllers and processors to designate a DPO if they constantly employ, as a rule, at least 20 persons dealing with automated processing of personal data. It also requires one regardless of headcount if their processing needs a data protection impact assessment under Article 35, or if they process personal data commercially for transfer or for market or opinion research.[5]
This applies to bodies subject to German law. Whether it reaches a particular US company, for example one with a German subsidiary, is a question for a German data protection lawyer.
What is an EU representative (Article 27)?
It is a person or company in the EU that you designate in writing to represent you on GDPR matters. Article 27 requires one when Article 3(2) applies, that is, when you have no EU establishment but offer goods or services to, or monitor, people in the EU.[1]
- Where. The representative must be established in one of the EU countries where the people whose data you process are (Art. 27(3)).
- What it does. Supervisory authorities and individuals can address the representative, in addition to or instead of you, on all issues about your processing (Art. 27(4)). Designating one does not shield you from legal action (Art. 27(5)).
- The Article 27(2) exemption. No representative is needed for (a) processing that is occasional, does not include large-scale processing of special category or criminal offense data, and is unlikely to result in a risk to people's rights and freedoms, or (b) a public authority or body.
An EU representative is a different role from a DPO. The representative acts on your instructions; a DPO must be independent. For that reason, the EDPB does not consider the representative role compatible with acting as the same company's external DPO.[2] Published EU representative prices start at ≈ $320*2 per year (REP27 Base, excl. VAT).[9] See the table of EU representative prices from all6 providers in the index, or read the full guide to the GDPR Article 27 representative.
What about US privacy laws?
US laws do not use the GDPR's DPO role. The DPO is a GDPR concept. A growing number of US states have comprehensive consumer privacy laws (see the IAPP tracker).[6] These laws use different duties, such as privacy notices, consumer rights requests, opt-outs and assessments. California's CCPA is one example; the California Attorney General publishes an overview.[7]
Health data is different. The HIPAA Privacy Rule says a covered entity "must designate a privacy official who is responsible for the development and implementation of the policies and procedures of the entity". It must also designate a contact person or office to receive complaints, and document both designations (45 CFR 164.530(a)).[8] The HIPAA privacy officer guide for health tech companies covers who needs one and how the role compares with a DPO.
What happens if you skip it?
You risk a fine. Under Article 83(4)(a), infringing the obligations in Articles 8, 11, 25 to 39, 42 and 43 (which include the EU representative rules in Art. 27 and the DPO rules in Arts. 37 to 39) is subject to fines of up to ≈ $11.0 million*1 or, for an undertaking, up to 2% of its total worldwide annual turnover of the preceding financial year, whichever is higher.[1]
Should you appoint a DPO voluntarily?
You may. Article 37(4) allows any controller or processor to designate a DPO.[1]But the DPO guidelines say that when you designate a DPO voluntarily, the same requirements on designation, position and tasks apply as if it were mandatory.[3] If you want privacy help without taking on those rules, the guidelines note you can use staff or outside consultants for data protection tasks without calling them a DPO. If you do, make clear in your communications that they are not a DPO, so there is no confusion about their title, status, position and tasks.[4] See what a DPO consultant does and costs.
Frequently asked questions
Do US companies need a DPO under GDPR?
Only if the GDPR applies to them and they meet an Article 37(1) trigger, or a member-state law requires one. Many US companies that the GDPR covers need an EU representative under Article 27 instead of, or as well as, a DPO.[1]
Does GDPR apply to a US company with no EU office?
It can. Under Article 3(2), the GDPR applies to a company outside the EU that offers goods or services to people in the EU, or monitors their behavior in the EU.[1]
What is the difference between a DPO and an EU representative?
A DPO (Article 37) informs, advises and monitors compliance, and must be independent. An EU representative (Article 27) is a contact point in the EU for authorities and individuals, and acts on the company’s behalf.[1][2]
Is there a headcount that makes a DPO mandatory under GDPR?
No. The GDPR uses "large scale" without a number. The DPO guidelines list factors such as the number of people concerned, the volume and range of data, how long the processing lasts and its geographic reach. Some national laws, such as Germany’s BDSG, add their own rules.[3][5]
What is the fine for not appointing a required DPO?
Breaches of the obligations in Articles 8, 11, 25 to 39, 42 and 43 (which include the DPO and EU representative rules) can lead to fines of up to about $11.0 million (converted) or, for an undertaking, up to 2% of total worldwide annual turnover of the preceding financial year, whichever is higher (Article 83(4)(a)). The GDPR sets the amount in euros.[1]
Next steps
- Run the DPO checker: seven yes/no questions based on Articles 3, 27 and 37.
- Learn what an outsourced DPO does and how to compare providers.
- See published DPO and EU representative prices, with sources.
- Guides by industry: health tech and HIPAA, SaaS and ed tech.
Currency notes
Amounts marked ≈ were published in another currency and are shown in US dollars, converted at 1 EUR = 1.0990 USD (ECB euro reference rate) from the ECB euro foreign exchange reference rates of , and rounded to the nearest $10. The amounts themselves (fees, fine limits, insurance cover) are set in the original currency, so the dollar figure is approximate and moves with exchange rates.
- ≈ $11.0 million: published as €10,000,000, converted at 1 EUR = 1.0990 USD (ECB euro reference rate, ).
- ≈ $320: published as €290, converted at 1 EUR = 1.0990 USD (ECB euro reference rate, ).
Sources
- Regulation (EU) 2016/679 (General Data Protection Regulation), official text on EUR-Lex (accessed )
- EDPB Guidelines 3/2018 on the territorial scope of the GDPR (Article 3) (accessed )
- Article 29 Working Party, Guidelines on Data Protection Officers (WP243 rev.01), endorsed by the EDPB (accessed )
- Article 29 Working Party, Guidelines on Data Protection Officers (WP243 rev.01), full text (PDF) (accessed )
- Federal Data Protection Act (BDSG), official English translation, Section 38 (accessed )
- IAPP, US State Privacy Legislation Tracker (accessed )
- California Attorney General, California Consumer Privacy Act (CCPA) (accessed )
- 45 CFR 164.530, HIPAA Privacy Rule administrative requirements (eCFR) (accessed )
- REP27, Pricing (accessed )
- European Central Bank, euro foreign exchange reference rates (rates of 20 November 2026, used to convert prices to US dollars) (accessed )