A recruitment platform writes in its privacy notice: “Your data is processed exclusively in Germany.” An applicant submits an access request and asks for all recipients. The answer reveals that the email service stores data in the USA and the video interview tool uses a subcontractor in Canada. The privacy notice is wrong, and nobody had a complete list. A.1.5.3 requires the organization to specify, document and make available the countries and international organizations that personal data can reach in normal operations, including the countries added through subcontractors.
The control is the map of your own data flows. Without it, you can neither check the basis of each transfer nor inform people truthfully about it.
What does the standard require?
The control asks for a list and states who should see it and what belongs in it.
- Specify and document. The organization determines to which countries and international organizations personal data may possibly be transferred, and records this.
- Available to customers. The countries and organizations that come into question in normal operations are made available to customers.
- Include subcontractors. Countries added through the use of subcontractors also belong on the list.
- Connect with A.1.5.2. Each country on the list is considered together with the basis for the transfer.
- Requests from authorities. Outside normal operations, there may be transfers at the request of law enforcement authorities. Their destination country cannot always be named in advance, or naming it is prohibited to keep investigations confidential. For this, the standard refers to A.1.5.2 and to controls A.2.5.5 and A.2.5.6 for PII processors.
In practice
Build the list from existing sources. The starting points are the record of processing activities, the Supplier Register and the subcontractor lists that processors maintain under their contracts. Each entry shows country, recipient, its role, the data categories concerned and the basis under A.1.5.2.
Take a close look at cloud services. With cloud providers, the region can often be chosen, while support and operations run through further locations. Record which region is booked and from where the provider can access the data (→ A.5.23 Information Security for Use of Cloud Services).
Publish the list. An overview in the privacy notice or on a dedicated page that contracts and notices refer to has proven useful. The same list feeds answers to data subjects and to customer questionnaires.
Steer changes. New service providers or subcontractors go on the list first and into use afterwards. When a processor announces a new subcontractor, you check the destination country before the objection period runs out.
Govern requests from authorities. Define who receives requests from foreign authorities, who carries out the legal review and how the outcome is documented.
Typical audit evidence
For A.1.5.3, auditors typically expect:
- List of possible destination countries and international organizations with recipient, role and data categories
- Published version in privacy notices or contract annexes, consistent with the internal list
- Subcontractor lists of service providers with locations (→ Supplier Register)
- Match of each country with its transfer basis under A.1.5.2 Identify basis for PII transfer between jurisdictions
- Procedure for requests from foreign authorities with responsibilities
KPI
% of transfer destinations formally approved and documented
Formally approved means: the destination country was checked and released before the first data flow, and the release is documented with date and basis. The target is 100%. Countries that only come to light during a review show that the approval step was bypassed.
Supporting KPIs:
- Share of service providers with a fully known subcontractor list
- Number of discrepancies between the published and the internal list
- Average time from the announcement of a subcontractor to its review
Link to the GDPR
Articles 13(1)(f) and 14(1)(f) GDPR require data subjects to be informed of an intended transfer to a third country or an international organization, together with details of the adequacy decision or safeguards. Article 15(1)(c) and 15(2) give a right of access to information on recipients in third countries and on the safeguards. Article 30(1)(e) requires transfers in the record of processing. Article 28(2) and (4) make the engagement of sub-processors subject to the controller’s authorization. For requests from courts and authorities in third countries, Article 48 provides that they are only recognized on the basis of an international agreement, such as a mutual legal assistance treaty (→ GDPR General Data Protection Regulation).
Related controls
A.1.5.3 provides the overview on which the other transfer controls build:
- A.1.5.2 Identify basis for PII transfer between jurisdictions: checks the supporting basis for each country.
- A.1.5.4 Records of transfer of PII: records the actual transfers.
- A.2.5.3 Countries and international organizations to which PII can be transferred: obliges processors to the same openness.
- A.2.5.7 Disclosure of subcontractors used to process PII: makes sure you know the subcontractors in the first place.
- A.5.23 Information Security for Use of Cloud Services: governs the selection and management of cloud services.
Sources
- ISO/IEC 27701:2025, Annex A, Table A.1, A.1.5.3, and Annex B, B.1.5.3: Countries and international organizations to which PII can be transferred
- Regulation (EU) 2016/679 (GDPR), Articles 13, 14, 15, 28, 30 and 48
- ISO/IEC 27701: Privacy Information Management System: structure of the standard and roles