GDPR can apply without EU office
A U.S. company sells a meal-planning app. It accepts users in France, shows euro prices, and links each user’s clicks to that user’s account.
It has no office in the European Union.
The common answer is that GDPR does not apply because the company is outside the Union.
That answer is wrong because Article 3(2) covers offering services or monitoring behavior in the Union.
A non-Union office is only one possible territorial link. The rule separates the material scope test from the territorial test before applying the six principles.
Material and territorial scope
The rule first identifies the processing and checks material scope. It then checks for at least one territorial connection. Once both scope stages are satisfied, all six principles apply together.
🔑 RULE: GDPR applies when processing is within material scope and at least one Article 3 territorial connection exists.
-
Material scope. Article 2(1) applies to the processing of personal data wholly or partly by automated means.
It also applies to non-automated processing of personal data that form part of a filing system or are intended to form part of a filing system.
Article 2(2) excludes, among other things, purely personal or household activity, activities outside the scope of Union law, certain competent-authority activities, and common foreign and security policy activities.
-
Territorial scope. Under Article 3(1), GDPR applies to processing in the context of the activities of an establishment of a controller or processor in the Union.
This applies regardless of whether the processing takes place in the Union or not.
Under Article 3(2), GDPR also applies when a controller or processor not established in the Union processes personal data of data subjects who are in the Union.
The processing must relate to offering goods or services, irrespective of whether payment is required, or monitoring behavior as far as behavior takes place within the Union.
-
The six principles. Article 5(1) requires personal data to be:
- Processed lawfully, fairly, and transparently.
- Collected for specified, explicit and legitimate purposes and not further processed incompatibly with those purposes.
- Adequate, relevant, and limited to what is necessary.
- Accurate and, where necessary, kept up to date.
- Kept in a form that permits identification for no longer than is necessary.
- Processed with appropriate security, including protection against unauthorized or unlawful processing and accidental loss, destruction, or damage.
-
Accountability. Article 5(2) states that the controller is responsible for, and must be able to demonstrate, compliance with paragraph 1.
Accountability is not a seventh principle.
-
Key concepts. Personal data means any information relating to an identified or identifiable natural person.
Processing means any operation performed on personal data. It includes collection, recording, storage, use, disclosure, alteration, restriction, erasure, or destruction.
A controller determines the purposes and means of processing.
A processor processes personal data on behalf of the controller.
Pseudonymized data remains personal data when additional information can still attribute it to a person.
Special categories include racial or ethnic origin, political opinions, religious or philosophical beliefs, trade-union membership, genetic data, biometric data used for unique identification, health data, and data concerning sex life or sexual orientation.
Article 9(2) exceptions are required for processing special-category data.
The order matters. First identify personal-data processing. Then check the territorial link. If either scope stage fails, GDPR does not apply to that processing. If both stages pass, all six principles apply together.
Testing material and territorial scope
This flowchart stops at the first failed material or territorial condition. It keeps Article 2(2) exclusions together before testing the territorial routes.
Loading diagram…
The chart handles scope before principles because a principle cannot bring excluded processing into GDPR. The worked case follows the same path.
Personal data and territorial scope
Each fact below is matched to the scope condition or personal-data definition it affects. The verdict appears only after every relevant condition is tested.
| Fact | Criterion it touches | Met or not met |
|---|---|---|
| The app links each user’s clicks to that user’s account. | Article 4(1) personal data and Article 4(2) processing | Met: linked clicks relate to an identifiable natural person and are collected, recorded, and used. |
| The app accepts users in France and shows euro prices. | Article 3(2)(a), offering goods or services to data subjects in the Union | Met. |
| The company sells a meal-planning app. | Article 2(1), automated processing of personal data | Met: the app processes the linked click data by automated means. |
| The company has no office in the European Union. | Article 3(1), processing in the context of an EU establishment | Not met, but this does not end the analysis. |
| Verdict | Article 2(1) material scope plus Article 3(2)(a) territorial scope | GDPR applies. The wrong answer stopped after checking for an EU establishment and skipped Article 3(2). |
The linked account makes the clicks personal data, while the French offer supplies the territorial connection.
Monitoring behavior and pseudonymized data
The facts below test the monitoring route and whether pseudonymized information remains personal data. The verdict is left open for the complete case.
| Fact | Criterion it touches | Verdict |
|---|---|---|
| A Canadian company runs a language-learning app for Canadian subscribers. | No stated EU establishment and no stated offer directed to people in the Union | ? |
| The company has no establishment in the Union. | Article 3(1) | ? |
| A Canadian subscriber uses the app while in Italy. | Article 3(2), data subject in the Union | ? |
| The app records the subscriber’s location and search history to assess behavior and send targeted prompts. | Article 3(2)(b), monitoring behavior as far as behavior takes place within the Union | ? |
| The records use a pseudonymous account ID, with the account information held separately. | Article 4(1) and 4(5), personal data and pseudonymization | ? |
Practice
Does GDPR apply to the processing described?
The offering route is absent or unclear, but the monitoring route is enough. The separate account information means pseudonymization has not removed personal-data status.
Territorial scope, principles, and roles
These items isolate territorial scope, purpose limitation, pseudonymization, and controller-versus-processor roles. Each wrong choice misapplies a named criterion.
Practice
A U.S. nonprofit uses an automated form to collect names and email addresses for a newsletter. It has no establishment in the Union, sends the newsletter only to U.S. residents, and does not monitor behavior in the Union. Does GDPR apply based on these facts?
An online store collects an email address to send a shipping notice for a completed order. It later uses the address to build unrelated advertising profiles without explaining that new use. Which principle is most directly at issue?
A clinic replaces patient names with codes and stores the code key in a separate secured file. Which statement is correct?
A retailer decides why customer data will be used and how the system will operate. A cloud host stores the data and acts only on the retailer’s documented instructions. Which role assignment is correct?
Each item changes one part of the rule. The scope test, principles, pseudonymization, and roles must remain distinct.
Anonymous data falls outside GDPR
Was: A U.S. company sells a meal-planning app, accepts French users at euro prices, links their clicks to accounts for recommendations, and has no EU office.
Now: The company permanently removes the account link and every other identifier before it stores or uses the clicks; does the verdict for those click records change?
Answer: Yes, for those click records. The material-scope criterion of processing personal data is no longer met because the records are anonymous, so the French offer does not bring those non-personal records into GDPR.
The territorial fact did not move. The result changes because the material-scope input moved from identifiable personal data to anonymous information.
The six principles and GDPR scope
Lawfulness, fairness, and transparency require a valid and open basis for processing.
Purpose limitation keeps later use tied to specified, explicit and legitimate purposes.
Data minimization limits collection to what is adequate, relevant, and necessary.
Accuracy requires correct and, where necessary, up-to-date data.
Storage limitation ends identifiable storage when it is no longer than is necessary.
Integrity and confidentiality require appropriate security against unauthorized or unlawful processing and accidental loss, destruction, or damage.
Scope combines material scope with at least one territorial connection, and all six principles apply once the processing is in scope.
The criterion people skip is Article 3(2)(b), monitoring behavior as far as that behavior takes place in the Union.
This method differs from HIPAA covered entities and disclosures, which starts with entity status and permitted disclosure, and from PCI DSS requirements, which starts with payment-card security requirements.
Unlock the full lesson and continue reading
Signup to continue reading this lesson and unlimited access questions, flashcards, AI notes, and more

