A municipal utility revises its privacy notice and asks the provider of its customer portal which countries data reaches. The answer: “All data is stored in Germany.” A later review shows a different picture. Email delivery runs through a provider in the United States, a monitoring service stores error messages with customer numbers in Ireland and Canada, and night-shift support sits in a third country. A.2.5.3 requires you to define and document the countries and international organizations that personal data can reach, and to make this information available to customers.
The list of destination countries is a simple piece of information with great effect. The customer needs it for the information given to data subjects, for their record of processing and for assessing whether a transfer is permitted.
What does the standard require?
A.2.5.3 matches A.1.5.3 for controllers and is closely tied to A.2.5.2.
- Define and document possible destinations. You determine to which countries and international organizations data can be transferred, and record this.
- Make it available to customers. The countries and organizations that come into question in normal operations are named to customers.
- Include subcontractors. The list also contains the countries that result from using subcontractors.
- Link to A.2.5.2. For every country on the list, the question of the basis for the transfer arises.
- Exception for requests from authorities. Outside normal operations, there can be transfers at the request of law enforcement authorities. The countries then cannot always be named in advance, or a jurisdiction prohibits naming them to protect an investigation. For this, the standard refers to A.1.5.2, A.2.5.5 and A.2.5.6.
In practice
Capture every place data can be. This includes storage locations in normal operation and for recovery, places of processing, access by support and administration, the seats of subcontractors and their own subcontractors.
Check international organizations. For most service providers they play no part. Whoever transfers data to bodies of the United Nations or other intergovernmental bodies, for example, includes them explicitly.
Keep the list per service. A provider with several products often uses different subcontractors. A country list per service is more precise and more useful to the customer than a combined list.
Provide it in a usable form. Customers carry the countries into their privacy notices and their record of processing. Give the list clearly and completely, with country names and the purpose for which data can get there.
Update before changes take effect. A new country usually arises from a new subcontractor or a new location. Link the list to these processes, so that it is updated and the customer is informed before the first data goes there.
Typical audit evidence
For A.2.5.3, auditors typically expect:
- Country list per service with countries, international organizations and the reason in each case
- Reconciliation with subcontractors and their locations (→ Supplier Register)
- Proof that customers received it, for example as a contract annex or a published list
- Change history of the list with the date customers were informed (→ Change Log)
- Procedure for requests from authorities governing the exception from normal operations
KPI
% of processor transfer destinations formally approved and documented
What counts are all countries and international organizations on the list. Formally approved means: the destination was released internally, the basis for the transfer is clear, and it is covered by the contract with the customer or by an announcement without objection. The target is 100%.
Supporting KPIs:
- Number of countries found in reviews that were missing from the list
- Share of list changes that customers were told about before the first transfer
- Time between onboarding a subcontractor and updating the list
Link to the GDPR
Under Article 30(2)(c) GDPR, transfers to third countries or international organizations, with the destination identified, belong in the processor’s record. Under Articles 13(1)(f) and 14(1)(f), the controller has to tell data subjects about an intended transfer to a third country, and needs your list to do so. Article 44 applies to every transfer, and under Article 28(3)(a) a transfer takes place only on documented instructions (→ GDPR General Data Protection Regulation).
Related controls
A.2.5.3 supplies the list other controls rely on:
- A.1.5.3 Countries and international organizations to which PII can be transferred: the same control for controllers.
- A.2.5.2 Basis for PII transfer between jurisdictions: the basis for every country on the list.
- A.2.5.7 Disclosure of subcontractors used to process PII: the subcontractors many of the countries come from.
- A.2.5.5 Notification of PII disclosure requests: handling requests from authorities outside normal operations.
- A.2.2.7 Records related to processing PII: the record in which the transfers are listed.
Sources
- ISO/IEC 27701:2025, Annex A, Table A.2, A.2.5.3, and Annex B, B.2.5.3: Countries and international organizations to which PII can be transferred
- Regulation (EU) 2016/679 (GDPR), Articles 13, 14, 28, 30 and 44
- ISO/IEC 27701: Privacy Information Management System: structure of the standard and roles