Zum Hauptinhalt springen
ISO/IEC 27701:2025 · Annex A, Table A.2 · Control for PII processors

A.2.5.2 Basis for PII transfer between jurisdictions

Updated on 5 min Reviewed by: Cenedril Editorial
ISO/IEC 27701:2025GDPR

A provider of ticketing software with a data centre in Frankfurt expands its support. A team in a third country takes over the night shift, and an AI service from the United States is added to summarize long tickets. Customers find out through a changed list on the website, two weeks after the switch. A hospital among the customers would have objected, and now it can only do so after the fact. A.2.5.2 requires you to tell the customer in good time on what basis you transfer personal data to other jurisdictions and which changes you are planning, so that they can object or end the contract.

Transfers to other jurisdictions are among the most sensitive points of processing on behalf of others. The customer remains responsible and can only judge a transfer if they know about it in time.

What does the standard require?

A.2.5.2 is the counterpart of A.1.5.2. The processor documents the basis of its transfers and keeps the customer informed about it.

  • Document the basis. Whether and how data may go to another jurisdiction depends on where it comes from and where it goes. You document how you meet the applicable requirements, and this is the basis of the transfer.
  • Disclose every transfer. The customer learns of every transfer, including those to suppliers, to other parties and to other countries or international organizations.
  • Announce changes in advance. You communicate planned changes beforehand, within an agreed period, so that the customer can object or end the contract.
  • Limits for changes without notice. If the contract allows certain changes without information, their limits have to be fixed. The standard’s example: changing suppliers yes, moving data to other countries no.
  • Name the instruments. For international transfers, you identify the agreements in use, together with the countries and the circumstances in which they apply. The standard mentions three examples: model contract clauses, binding corporate rules and the Cross Border Privacy Rules.

In practice

Capture every route. Transfers arise from storage locations, from subcontractors and their subcontractors, from support access abroad, from maintenance access and from services such as email delivery, monitoring or AI features. Remote access from a third country is also treated as a transfer in practice.

Determine the instrument per route. For transfers from the EU, the main options are adequacy decisions, standard data protection clauses and binding corporate rules. The derogations for specific situations in Article 49 GDPR rarely carry regular transfers on behalf of customers. For each instrument, record which supplementary measures it requires.

Agree a notice period and keep it. Set out in the contract how long before a change the customer is informed, and anchor the period where the change is decided: in procurement, in product planning, in operations. Otherwise it slips through when a new service is introduced quickly.

Use a fixed information channel. Customers should be able to subscribe to changes, for example through email notifications or a customer portal. A silent edit of a web page hardly meets the duty to inform in advance.

Write the limits of blanket permissions in checkable terms. State in the contract which kinds of change are possible without notice, which countries remain excluded and which safeguards apply unchanged.

Typical audit evidence

For A.2.5.2, auditors typically expect:

  • Overview of transfer routes with country, recipient, instrument and supplementary measures
  • Agreements concluded, such as standard data protection clauses with subcontractors (→ Supplier Register)
  • Contract clauses on the notice period and on the limits of changes without information
  • Customer notifications of changes with date and period (→ Stakeholder Communication Plan)
  • Assessment of the legal requirements for transfers per destination country (→ Legal Compliance Register)

KPI

% of processor cross-border transfers with documented legal basis

What counts are all transfer routes to other jurisdictions, including routes via subcontractors and remote access. Documented means: instrument, countries, conditions and supplementary measures are recorded, and the customer has been informed. The target is 100%.

Supporting KPIs:

  • Share of changes announced in advance within the agreed period
  • Number of objections from customers and how they were resolved
  • Share of transfer routes whose instrument was reviewed in the last year

Under Article 44 GDPR, the rules on transfers to third countries and international organizations apply explicitly to processors as well. The instruments are adequacy decisions under Article 45, appropriate safeguards under Article 46, including standard data protection clauses under paragraph 2(c) and binding corporate rules under Article 47, and the derogations under Article 49. Article 28(3)(a) requires that transfers, too, take place only on documented instructions. For new or replaced subcontractors, Article 28(2) gives the controller a right to object (→ GDPR General Data Protection Regulation).

A.2.5.2 opens the group of controls on sharing, transfer and disclosure:

Sources

Frequently asked questions

Is remote access from a third country already a transfer?

In practice, access from a third country to data stored in the EU is treated as a transfer. This concerns support teams or administrators outside the EU, for example. Such access therefore belongs in your overview, with country and basis.

How long should the notice period for changes be?

The standard requires an agreed period and does not set a length. Several weeks are common, so that the customer can review the change, carry out an assessment of their own if needed and object. What matters is that the period is in the contract and is kept.

May the contract allow me to make changes without notice?

Yes, as long as clear limits are drawn. The standard gives an example itself: changing suppliers without notice can be allowed, moving data to other countries cannot. Describe precisely in the contract which changes fall under the permission.

No Cookies!

This wiki collects nothing, bakes nothing and leaves nothing behind. There's nothing to consent to. Privacy doesn't get better than this.