GDPR territorial scope · Articles 3 and 27 · Chapter V

Check GDPR scope across borders.

Choose where the organisation is based, where affected people are located, and the facts that change the test. The result keeps territorial scope, representation, and international transfers separate.

Build a scenario

Start with the two countries, then the actual activity.

750country routes
Check these facts

Country routes are fixed and indexable. The activity controls refine the live analysis without manufacturing a separate search page for every minor combination.

Why these questions

Three legal decisions, not one country label.

Article 3

Territorial scope

An establishment, deliberate offering, or behavioural monitoring can bring particular processing into GDPR scope. Mere accessibility is not enough.

Article 27

Representation

An organisation outside the EEA may need a representative where affected people are located. The occasional low-risk exception is narrow.

Chapter V

International transfer

A separate disclosure to a recipient outside the EEA may require adequacy, SCCs, BCRs, or another transfer route. Article 3 does not answer that question.

Business location

Compare common non-EEA markets.

The organisation’s home country changes the separate transfer analysis. Adequacy may be available, conditional, or absent.

Affected people

All 30 EU and EEA states.

The territorial test is European, while targeting evidence, representative placement, language, and supervisory context can be country-specific.

03/V

A boundary worth preserving

Applicability and data transfer are different questions.

An organisation outside the EEA can fall under GDPR through Article 3. That does not, by itself, answer whether a separate disclosure engages Chapter V, an adequacy decision, SCCs, or another transfer mechanism.

Build a governed workflow