Skip to content
All articles
Data, privacy and GDPR

AI data residency: the law asks where, and the answer is a setting

DORA requires a financial entity's contracts to name the regions or countries where data is processed and stored. For a cloud AI service, that answer can depend on a deployment type somebody selected.

BastionUpdated 3 min read

Residency asks where data is processed and stored. Privacy asks what happens to it. An organisation can satisfy one and fail the other: keeping data in the European Union does not make a processing activity lawful under the GDPR, and keeping it in Romania does not make a system secure.

What DORA Article 30 asks for, in its own words

Article 30(2) of DORA lists what the contractual arrangements on the use of ICT services must include, and point (b) requires:

the locations, namely the regions or countries, where the contracted or subcontracted functions and ICT services are to be provided and where data is to be processed, including the storage location, and the requirement for the ICT third-party service provider to notify the financial entity in advance if it envisages changing such locations

Regulation (EU) 2022/2554, Article 30(2)(b)

The point does not ask for European hosting. It asks the contract to name the locations and to oblige the provider to give advance notice before it changes them.

The obligation stays with the customer. Recital 64 states that “A financial entity should at all times remain fully responsible for complying with its obligations set out in this Regulation.”

Why a cloud service’s answer depends on the deployment type

CaseWhat the documentation states
A deployment type labeled Global“For any deployment type labeled 'Global,' prompts and responses may be processed in any geography where the relevant model sold by Azure is deployed”
A DataZone deployment created in an EU member stateProcessing may occur “in that or any other European Union Member Nation”
Stored dataIt “Is stored at rest in the Foundry resource in the customer's Azure tenant, within the same geography as the resource”
Where a model sold by Azure processes and stores data, from Microsoft's documentation

So the Article 30(2)(b) answer for that service is one line per deployment type, and it changes when an engineer changes the deployment type.

What local inference changes in the contract answer

With inference inside the organisation's own network, the Article 30(2)(b) answer does not depend on a console setting. The contract names one location, the customer's own site, and there is no subcontracted processing location to track.

With Bastion

What Bastion changes

Bastion is a private AI system delivered as one sealed box that runs inside your building. One monthly fee covers the hardware, the model, the hardened operating system and support, and nothing your team types leaves the building.

A Bastion node answers inside the customer's network without an outbound connection, so the processing location stays one fixed address: the customer's own site, or a partner's data centre that the contract names. That does not discharge the rest of DORA. It makes one row of the register short, stable and easy to evidence.

Questions this article answers

What does DORA require a contract to say about where data is processed?
Article 30(2)(b) requires the contract to name the regions or countries where the functions and ICT services are provided and where data is processed, including the storage location. It also requires the provider to notify the financial entity in advance if it envisages changing those locations.
Does keeping AI data in the EU make the processing compliant?
No. Residency answers where the data sits; compliance is answered by the whole processing activity. DORA Recital 64 states that a financial entity should at all times remain fully responsible for complying with its own obligations.
Where does a cloud AI service process prompts?
It depends on the deployment type somebody selected. Microsoft's documentation for models sold by Azure states that for any deployment type labeled Global, prompts and responses may be processed in any geography where the model is deployed, while a DataZone deployment created in an EU member state may process in that or any other European Union Member Nation.

On the record

  1. 1
  2. 2