Does using a widely used AI tool involve one?

Frequently yes, because processing happens wherever the vendor operates rather than where you are. That makes it a property of the purchase rather than a later infrastructure question, which is why it is usually discovered afterwards rather than planned for.

What should we ask a vendor?

Where processing happens, whether it can be confined to a region, who else is involved in delivering the service and where they operate. The third question is the one that most often produces new information, because onward arrangements are rarely volunteered.

Does keeping everything local solve it?

It removes the question rather than answering it, and it costs something real. Regional processing and self-hosting both narrow the field of available tools and add operational work, so it is a deliberate trade rather than the obviously safe choice.

Glossary

Cross-border transfer

Moving personal data between countries, which generally needs a specific legal mechanism rather than being permitted by default.

In plain terms

Personal data going somewhere else in the world. It is not forbidden and it is not automatic: there is a short list of ways to make it lawful, and using an ordinary AI tool frequently does it without anybody having noticed a transfer took place.

Why it matters

Because this is the requirement AI adoption runs into most often and recognises least. The tool is chosen for what it does, the processing happens wherever the vendor operates, and the transfer is a consequence of the purchase rather than a decision anybody made, so it tends to be discovered rather than planned.

How it works

Access counts, not just copying. Somebody in another country being able to view material is generally treated as a transfer even if nothing is stored there, which catches support arrangements and vendor operations teams that a buyer thinking about servers would not have considered.

The mechanisms are a defined set rather than a general justification. There are recognised ways of making a transfer lawful, they carry conditions, and the practical work is establishing that one genuinely applies rather than assembling an argument that the transfer is reasonable.

Onward transfers are the part that gets missed. A vendor may process where they say and rely on somebody else who does not, so the question is not only where your vendor operates but where everybody they depend on does, which is answerable and rarely volunteered.

Which arrangements are available shifts over time, so an assessment carries a date. A basis relied on today may be revisited, and an organisation with a written record of what it relied on and when is in a much better position than one that concluded the matter was settled.

Keeping processing in one place is the direct answer and it costs something. Regional options and self-hosting remove the question rather than answering it, and they narrow the field of tools and add operational work, which is a real trade rather than a free one.

The direction of travel matters as much as the destination, because obligations attach to the organisation sending rather than to the one receiving. A vendor operating lawfully in their own country is not thereby making your transfer lawful, which is why a vendor's compliance statement is evidence about them and never a substitute for your own basis.

What a buyer checks, and what decides it

The gap between the columns exists because the left is designed to be found and the right is not concealed but simply not published. A vendor's country of incorporation is on every page; where their support team sits, and which other companies process on their behalf, appear in a sub-processor list that a buyer has to go and read. That asymmetry produces a familiar sequence: a tool is selected on capability, a regional option is chosen to be safe, and somebody later discovers that a support arrangement or an onward provider sits somewhere the assessment never contemplated. None of that requires a vendor to have been evasive. The practical response is three questions rather than a project, and they are answerable in a sales conversation: where does processing happen, who can see it and from where, and who else is involved. The third is the one worth pressing on, because it is the only one whose answer a buyer cannot infer from anything they can see.

Seen in the wild

An assistant processing material outside the country where the staff using it sit.
ChatGPT
Asking a search vendor which regions processing can be confined to, and who else is involved.
Glean
Running a model locally so material never leaves at all.
LM Studio

Common misconceptions

People assume

It only applies when data is stored abroad.

In fact

Access is generally treated as a transfer too. Somebody in another country able to view material counts even where nothing is stored there, which catches support teams and vendor operations that a buyer thinking about servers would miss.

People assume

Choosing a regional option settles it.

In fact

It settles where your vendor processes and not where their own suppliers do. Onward transfers are the part most often missed, and the question of who else is involved is answerable and rarely offered unprompted.

Questions

Does using a widely used AI tool involve one?: Frequently yes, because processing happens wherever the vendor operates rather than where you are. That makes it a property of the purchase rather than a later infrastructure question, which is why it is usually discovered afterwards rather than planned for.
What should we ask a vendor?: Where processing happens, whether it can be confined to a region, who else is involved in delivering the service and where they operate. The third question is the one that most often produces new information, because onward arrangements are rarely volunteered.
Does keeping everything local solve it?: It removes the question rather than answering it, and it costs something real. Regional processing and self-hosting both narrow the field of available tools and add operational work, so it is a deliberate trade rather than the obviously safe choice.