Skip to content

Insight

AI

Most AI procurement questions in the GCC come down to a single sentence that nobody can produce: which model saw what, and where did it run?

10 June 2026 · 1 min read

Where your data goes, in one page

Most AI procurement questions in the GCC come down to a single sentence that nobody can produce: which model saw what, and where did it run?

Where your data goes, in one page

Three questions your contract should answer

  1. Which models are used, by name and version, for which parts of the workflow.
  2. Where each one runs, and which jurisdiction that puts the processing in.
  3. What a human reviews before anything is published, sent or posted.

The in-region options

For UAE data-residency requirements, open-weight models on Azure UAE or AWS in the UAE and Bahrain will do most jobs well enough. The quality gap against frontier models has narrowed enough that residency is rarely the binding constraint any more.

A common and workable pattern is a split: retrieval and any personal data stay in region, while a frontier model handles reasoning over already-redacted content. That has to be written down, not assumed.

The paragraph to insist on

Every contract should name the models, name the regions, and name the human who reviews the output. If your supplier cannot write that paragraph, they do not know the answer.


Written by the OneRee team. If any of this is wrong for your situation, tell us — we would rather update the page than be right on the internet.

One Thing — weekly

One practical idea a week, with the numbers behind it.

Subscribe

Keep reading

More from the team.

Next step

Tell us what you are trying to move.

Thirty minutes, no deck. We will tell you what we would do first, what it costs, and whether we are the right people for it.

back top