Skip to content
All articles
With cloud AI

GDPR and DORA do not ban cloud AI. The firm stays accountable.

No Romanian or EU rule forbids a regulated firm from using cloud AI. Using it does not transfer responsibility for the underlying processing either. Three regulators and one court showed between December 2024 and March 2026 how that duty is read.

BastionUpdated 5 min read

GDPR Article 28 permits the appointment of a processor. DORA Article 30 makes the location of processing a matter of disclosure, not prohibition. The vendor may operate the infrastructure, process the data and even face regulatory action. The organisation that uses the service still carries obligations of its own.

DateEventSource
December 2024The Italian data protection authority fines OpenAI EUR 15 millionThe Hacker News
2 May 2025The Irish Data Protection Commission fines TikTok EUR 530 millionData Protection Commission (Ireland)
18 December 2025BaFin publishes its guidance on ICT risks in the use of AIBaFin
19 March 2026Reuters reports that a Rome court cancelled the OpenAI fineReuters, via Yahoo Finance
The three events in date order; the OpenAI fine and its annulment count as one

TikTok: the statement about server locations proved wrong

On 2 May 2025 the Irish Data Protection Commission fined TikTok EUR 530 million over transfers of European user data to China. The decision found an infringement of Article 46(1) GDPR because TikTok “failed to verify, guarantee and demonstrate” that its safeguards gave the data an equivalent level of protection. CNBC reported the order to bring processing into compliance within six months, and TikTok’s intention to appeal.

The regulator records that TikTok had told the inquiry it did not store European data on servers in China, and then in April 2025 “informed the DPC of an issue that it had discovered in February 2025 where limited EEA User Data had in fact been stored on servers in China, contrary to TikTok’s evidence to the Inquiry”.

OpenAI: a EUR 15 million fine, annulled in court

In December 2024 the Italian data protection authority fined OpenAI EUR 15 million. The Hacker News listed the grounds: processing users’ personal data to train ChatGPT without an adequate legal basis, failing to notify a March 2023 breach, and lacking age verification. On 19 March 2026 Reuters reported that a Rome court had cancelled the fine.

The provider’s regulatory position is not the customer’s compliance position. The vendor has its own responsibilities and the customer has its own, and the split depends on the relationship, the processing and the applicable framework.

The vendor spent fifteen months in a legal process about how it handled the personal data of its users. Whether the fine stood or fell, a customer’s data protection officer could not answer one question about that processing from documents the customer controls.

DORA and BaFin: cloud AI is a third-party risk

For financial entities DORA adds a layer. It requires management of ICT third-party risk and appropriate contractual and operational arrangements around critical ICT services.

On 18 December 2025 Germany’s BaFin published guidance on ICT risks in the use of artificial intelligence; the English version is dated 23 January 2026. It states that “many AI systems cannot be operated without the use of cloud services”, which is why ICT third-party risk applies, and it tells financial entities that “when using cloud services, the financial entity should also consider the risks of unauthorised data leakage, including to the cloud service provider.”

BaFin supervises German banks, not Romanian ones. DORA is one regulation for the whole Union, so a national supervisor writing down how it reads DORA for AI is the closest thing to a preview a Romanian risk officer will get. On that reading an AI system is software like any other, and its provider is a third party.

Four duties that stay with the organisation

A cloud provider can supply contractual commitments, certifications, documentation and regional processing options. Four duties still land on the buyer:

  • DORA Article 28(8): the financial entity must hold an exit strategy for each ICT service supporting a critical or important function, and the exit plan must be “sufficiently tested”. The duty sits with the entity, not the vendor.
  • DORA Article 30(2)(f): the contract must provide assistance at “no additional cost, or at a cost that is determined ex-ante” when an ICT incident occurs. Check a per-token API contract for this clause.
  • GDPR Article 46, read with the TikTok decision: when data crosses a border, the controller carries the burden of demonstrating equivalent protection.
  • GDPR Article 9: a hospital’s prompts are health data by nature, the hardest category.

AWS, Azure and Google Cloud list no cloud region in Romania, checked 22 September 2026. AWS lists Bucharest as a point of presence of its CloudFront content delivery network, not as a region. Every answer from these three clouds is therefore a cross-border one today.

The organisation also has to answer what data is processed, on what legal basis, where, by which subprocessors, under which transfer mechanism and for how long, and what evidence exists for an audit.

Local processing changes the conversation, not the duty

An on-premise system does not make an organisation compliant with GDPR. It does remove one category of questions. If a prompt is processed entirely inside the organisation’s own premises, no cross-border transfer has to be established for that path. The processing environment can be documented directly, the infrastructure can be inspected, the logs stay internal, and access runs through existing network and identity controls.

A policy says that employees must not send sensitive data outside the organisation. An architectural control makes that rule much harder to break by accident. Not every workload should move on-premise: for low-risk information cloud AI is appropriate, and the law does not force the purchase of an appliance. The organisation has to be able to explain, document and defend the way its AI systems process information.

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.

Bastion keeps processing at one address that the contract names, the customer’s premises or a partner’s data centre, so the transfer question has a one-line answer and the register row names that address. The appliance ships with a contract annex written to DORA Article 30, an exit plan that can be tested on the appliance itself, and a boot log that shows what booted and when.

The appliance supplies evidence, and compliance stays with the organisation. A box in the building does not write the data protection impact assessment, and it does not decide which use cases fall under the AI Act.

Questions this article answers

Is ChatGPT GDPR compliant?
No regulator has settled that for every use: Italy fined OpenAI EUR 15 million in December 2024, and a Rome court cancelled the fine in March 2026. Either way, the organisation keeps its own GDPR duties.
Do GDPR or DORA ban cloud AI?
No. GDPR Article 28 permits a processor, and DORA Article 30 makes the location of processing a matter of disclosure.
Is there a cloud region in Romania?
AWS, Azure and Google Cloud list no cloud region in Romania, checked 22 September 2026. AWS lists Bucharest as a CloudFront point of presence, not as a region.

On the record

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8

    Amazon Web Services

    Amazon CloudFront key features: points of presence

    read 2026-11-17

  9. 9

    Microsoft

    Azure geographies

    read 2026-09-22

  10. 10