FAQEU GDPR

GDPR Article 3 Territorial Scope

Use GDPR Article 3 as a processing-activity test, not as a blanket label for every non-EU business that touches EU data.

The tests cover processing in the context of an EU establishment, offering goods or services to people in the Union, monitoring behavior in the Union, the public-international-law rule, and the linked Article 27 representative requirement.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 25, 2026
Questions
4

Structured answer sets in this page tree.

Primary sources
2

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated Jul 25, 2026
Overview

applies to particular processing activities through an , non-EU targeting or monitoring, or the narrower public-international-law rule. This FAQ separates those tests and the related Article 27 representative decision.

Search this module

Find a question or answer quickly

4 of 4 questions
Question 1

Does GDPR Article 3 apply to a non-EU organization?

It can, but only through the Article 3 triggers. First, GDPR applies to processing carried out in the context of the activities of an establishment of a controller or processor in the Union, even if the processing itself takes place outside the Union.

Second, for a controller or processor not established in the Union, GDPR applies only where the processing relates to offering goods or services to data subjects in the Union or monitoring their behavior as far as that behavior takes place in the Union. The EDPB stresses that the Article 3 assessment is made for the particular processing activity, not by labeling the entire legal entity as globally in scope.

Article 3(3) is a separate rule: GDPR also applies where Member State law applies by virtue of public international law. The EDPB gives EU Member State diplomatic missions and consular posts as the relevant type of setting; this is not a general fallback for ordinary overseas business activity.

  • Start with Article 3(1): identify any and explain how the processing is carried out in the context of that establishment's activities.
  • If there is no trigger, test Article 3(2)(a): whether the processing relates to offering goods or services to data subjects who are in the Union.
  • Separately test Article 3(2)(b): whether the processing relates to that takes place within the Union.
  • Check Article 3(3) only where Member State law may apply by virtue of public international law, and record the instrument or status that creates that link.
  • Avoid unsupported conclusions such as "EU user equals GDPR" or "non-EU company equals out of scope"; document the actual processing activity and the trigger that applies.

Does the GDPR automatically apply to every non-EU company with EU customers?

No. Article 3 requires an context, an offer of goods or services to data subjects in the Union, monitoring of behavior in the Union, or the separate public-international-law rule in Article 3(3). For Article 3(2), merely processing personal data about someone in the Union is not enough without the targeting or monitoring element.

Citations
Question 2

What facts show offering goods or services to people in the Union?

For Article 3(2)(a), the key question is whether the controller or processor appears to envisage offering goods or services to data subjects in one or more EU Member States. Payment is not required.

A website being reachable from the Union, listing an email address, or using a language generally used in the organization's own country is not enough by itself. Stronger evidence can include naming EU Member States in the offer, EU-directed advertising, EU delivery, EU customer references, EU languages or currencies tied to ordering, EU contact details, or an EU top-level domain.

  • Keep screenshots or product records showing EU countries, delivery areas, booking availability, account creation, or checkout paths.
  • Record language, currency, domain, ad-campaign, search-marketing, and customer-reference signals together; one weak signal may not be enough on its own.
  • Distinguish intentional EU offering from incidental use by a person who happens to travel into the Union.
  • Map the evidence to the processing activity, such as account registration, payment, shipping, customer support, personalization, or marketing.
Citations
Question 3

What counts as monitoring behavior in the Union?

Article 3(2)(b) applies where the processing relates to monitoring data subjects' behavior and that behavior takes place within the Union. The EDPB says monitoring requires attention to the controller's purpose, especially later behavioral analysis or profiling; not every collection or analysis of data from people in the Union is automatically monitoring.

Official source examples of monitoring indicators include behavioral advertising, geolocation for marketing, online tracking through cookies or fingerprinting, personalized health or diet analytics, CCTV, individual-profile market studies, and monitoring or regular reporting on a person's health status.

  • Identify the behavior observed, where it takes place, and the personal data used to observe it.
  • Record whether tracking, profiling, prediction, segmentation, targeted advertising, or individualized reporting is part of the purpose.
  • Separate ordinary service logging from behavior monitoring when there is no later behavioral analysis or profiling purpose.
  • For processors, document whether their processing is related to the controller's EU-targeting or EU-monitoring activity.
Citations
EDPB Guidelines 3/2018 on territorial scope

Explains that monitoring depends on purpose and behavioral analysis or profiling, and gives examples such as cookies, fingerprinting, geolocation, CCTV, and health-status monitoring.

Question 4

When is an EU representative needed?

Where Article 3(2) applies, a non-EU controller or processor must designate a unless an Article 27(2) exemption applies. The GDPR exemptions are narrow: processing that is occasional, does not include large-scale processing of special-category or criminal-offence data, and is unlikely to result in a risk to natural persons' rights and freedoms, or processing by a public authority or body.

The representative must be established in one of the Member States where the relevant data subjects are located. The EDPB also says designation of a representative does not itself create an under Article 3(1), and it does not remove the controller's or processor's own responsibility or liability.

  • Keep the written representative mandate and the Member State rationale tied to where affected data subjects are located.
  • Keep representative contact details aligned with privacy notices and other Article 13 or 14 information given to data subjects.
  • Keep enough processing-record information available for the representative to produce records when addressed under Article 27 and Article 30.
  • Do not rely on the representative as a substitute controller, processor, or DPO without checking the EDPB conflict guidance.
Citations
Regulation (EU) 2016/679 (GDPR)

Article 27 requires a written representative for Article 3(2) controllers or processors and states the exemptions, location rule, mandate, and liability reservation.

Primary sources

References and citations

edpb.europa.eu
Referenced sections
  • Explains representative designation, accessibility, privacy-notice disclosure, record availability, and the distinction from an Article 3(1) establishment.
"representative in the Union"
eur-lex.europa.eu
Referenced sections
  • Article 27 requires a written representative for Article 3(2) controllers or processors and states the exemptions, location rule, mandate, and liability reservation.
"Representatives of controllers or processors"
Related guides

Explore more topics

EU GDPR Applicability Test for Products, Vendors, and Data Flows
A concrete GDPR scope test for personal data, controller and processor roles, EU establishment, EU targeting or monitoring, special-category and child data, transfers, vendors, and evidence.
EU GDPR Article 30 RoPA Intake Workflow
This GDPR Article 30 RoPA intake workflow helps capture controller and processor fields, owners, transfers, retention, security measures, and evidence before a processing activity goes live.
EU GDPR Article 6 Legal Bases FAQ
FAQ on the six Article 6 GDPR lawful bases, consent caveats, legitimate interests, public-task and legal-obligation limits, and Article 9 special-category data.
EU GDPR Automated Decision-Making and Profiling: Article 22 Scope, Safeguards, and Evidence
GDPR guide to profiling and Article 22 decisions: scope, transparency, lawful basis, DPIA triggers, safeguards, human intervention, challenge rights, and evidence.
EU GDPR Breach Notification 72 Hours: Article 33 and 34 workflow
Official source EU GDPR breach notification workflow covering awareness, 72-hour supervisory authority notices, processor escalation, high-risk data-subject communication, delay reasons, and evidence logs.
EU GDPR Breach Notification Workflow: 72-hour clock, risk assessment, and records
A concrete EU GDPR breach notification workflow for detecting and triaging incidents, starting the awareness clock, assessing risk, notifying authorities or data subjects, and keeping Article 33 records.
EU GDPR Checklist: scope, lawful basis, DSARs, DPIA, RoPA, transfers
This GDPR checklist helps review scope, lawful basis, notices, DSAR handling, DPIAs, RoPA, processor contracts, SCC transfers, breach notification, retention, security, and evidence.
EU GDPR Children and Special-Category Data Guide
GDPR guide to children's consent and special-category data: Article 8 national age variation, Article 9 conditions, transparency, DPIA triggers, safeguards, and evidence.
EU GDPR Compliance Checklist: scope, rights, DPIA, RoPA, transfers
Practical EU GDPR compliance guide for mapping scope, lawful basis, notices, data-subject rights, DPIAs, RoPA, processor terms, breaches, transfers, retention, security, and penalties.
EU GDPR Controller, Processor, and Joint Controller Roles
Classify GDPR controllers, processors, and joint controllers from actual decision-making, then document Article 26 allocation, Article 28 terms, instructions, and vendor evidence.
EU GDPR Data Subject Rights and DSAR Workflow
GDPR rights-request workflow for intake, identity checks, request scope, the one-month response clock, extensions, refusals, processor coordination, and evidence.
EU GDPR deadlines and compliance calendar
EU GDPR calendar for calculating rights-request deadlines, breach notification, DPIA and prior-consultation gates, transfer reviews, and retention checks.
EU GDPR DPIA and Prior Consultation Workflow
Screen high-risk processing, run a GDPR Article 35 DPIA, record mitigation, and identify when Article 36 prior consultation is required.
EU GDPR DPIA and risk management under Articles 35 and 36
EU GDPR DPIA guide covering Article 35 triggers and contents, CNIL and DPC PIA methods, residual risk, mitigation records, and prior consultation limits.
EU GDPR DSAR Exceptions: refusal, extensions, identity checks
FAQ on when EU GDPR controllers may extend, charge for, narrow, redact, or refuse a data subject access request under Articles 12 and 15.
EU GDPR DSAR Workflow: Intake, Clock, Rights, and Evidence
Run a GDPR DSAR workflow for intake, identity checks, rights scoping, one-month response timing, extensions, refusals, processor handoffs, and evidence records.
EU GDPR FAQ: scope, lawful basis, rights, DPIA, breaches, transfers
Direct EU GDPR FAQ answers on scope, controller and processor roles, lawful basis, data subject rights, DPIAs, breach notification, international transfers, and Article 83 fine tiers.
EU GDPR International Transfers and SCCs: Chapter V evidence guide
GDPR Chapter V guide to adequacy decisions, SCCs, transfer assessments, supplementary measures, Article 49 derogations, and EU-US DPF checks.
EU GDPR Lawful Basis and Consent Guide
Focused GDPR guide to Article 6 lawful bases, consent conditions, legitimate interests, special category data, withdrawal, and evidence records.
EU GDPR Lawful Basis and LIA Workflow for Article 6(1)(f)
Assess GDPR legitimate interests with a purpose, necessity, balancing, Article 21 objection, and evidence-record workflow based on Article 6(1)(f).
EU GDPR Lead Supervisory Authority and One-Stop-Shop
How GDPR main establishment, cross-border processing, Article 56 lead authority competence, and Article 60 cooperation fit together.
EU GDPR LIA Template for Article 6(1)(f)
This EU GDPR legitimate interests assessment template helps document Article 6(1)(f) purpose, necessity, balancing, safeguards, objection rights, and evidence.
EU GDPR penalties and fines: Article 83 tiers and evidence
EU GDPR penalties guide covering Article 83 fine ceilings, the EDPB calculation method, CJEU conditions, Article 58 powers, and evidence.
EU GDPR Processor Contracts and Vendor Management | Article 28 Evidence Guide
EU GDPR Article 28 guide for processor contracts, sub-processor controls, controller-processor role boundaries, vendor evidence, and SCC transfer clauses where applicable.
EU GDPR Record of Processing Activities Template: Article 30 RoPA Fields
Build a GDPR Article 30 record of processing activities with separate controller and processor fields for purposes, data categories, recipients, transfers, erasure time limits, and security measures.
EU GDPR Requirements: scope, rights, security, DPIA, RoPA, and transfers
Overview of core EU GDPR requirements covering scope, principles, lawful basis, notices, data-subject rights, processors, RoPA, security, breaches, DPIAs, and international transfers.
EU GDPR Retention and Erasure Schedule
Build an EU GDPR retention and erasure schedule with purpose-based periods, expiry actions, Article 17 decisions, recipient notices, and deletion evidence.
EU GDPR SCC Transfer Impact Assessment FAQ
FAQ on when SCC transfer impact assessments are needed, what Clause 14 records, and when supplementary safeguards or transfer suspension are required.
EU GDPR Transfer TIA and SCC Workflow
A GDPR workflow for checking adequacy, selecting SCC modules, documenting transfer impact assessments, and recording supplementary measures for third-country transfers.
EU GDPR Transparency Notices: Articles 12, 13 and 14
GDPR privacy-notice guide for Articles 12, 13, and 14: direct collection, other data sources, purposes, lawful bases, recipients, transfers, retention, rights, and timing.
EU GDPR vs Brazil LGPD: scope, legal bases, rights, incidents, and transfers
Compare EU GDPR and Brazil LGPD scope, actors, legal bases, rights timing, security incidents, international transfers, evidence, regulators, and penalties.
EU GDPR vs California CCPA: scope, rights, opt-outs, and evidence
Compare EU GDPR and California CCPA scope, roles, consumer rights, response times, sale and sharing opt-outs, risk assessments, contracts, transfers, and enforcement.
EU GDPR vs ePrivacy Directive: personal data, cookies, consent, and communications
Compare the EU GDPR and ePrivacy Directive for personal data processing, consent and lawful basis, cookies and terminal access, electronic communications, and parallel compliance.
EU GDPR vs UK GDPR: Scope, Rights, Transfers, and Evidence
Compare the EU GDPR and amended UK GDPR across scope, rights, automated decisions, accountability, breaches, regulators, and international transfers.
GDPR processor vs controller: role boundaries and evidence
Decide whether a party is a GDPR controller, processor, or joint controller using purpose-and-means tests, Article 28 terms, Article 26 arrangements, and Article 30 records.
GDPR vs EU AI Act: privacy controls for AI systems
Map the GDPR work that remains necessary when an AI system processes personal data, including lawful basis, notices, DPIAs, Article 22, rights, security, records, and transfers.
GDPR vs EU Data Act: personal data, connected products, and access rights
Compare GDPR privacy duties with EU Data Act rights and duties for connected-product data, third-party access, data holders, users, contracts, cloud switching, and enforcement.
When does the EU GDPR require a DPIA?
Answer the EU GDPR DPIA threshold question with Article 35 triggers, high-risk criteria, supervisory-authority list checks, and DPIA content requirements.
When does the GDPR 72-hour breach notification clock start?
GDPR breach-awareness FAQ covering the Article 33 clock, processor escalation, delayed or phased notifications, risk assessment, and records to keep.