Every procurement officer in Saudi Arabia asks an AI vendor the same first question: does our data stay in the Kingdom? The answer that usually comes back is "we have a region in Dammam" or "we are PDPL-compliant", and both can be true without answering the question. A cloud region inside the country means the storage disks and general compute sit here. It does not mean the language model that reads your prompt runs on those servers, and it does not mean the vendor has signed a contract saying so. This guide separates the three layers that marketing tends to merge: where data is stored at rest, where the request is processed inside the model, and what Saudi law and regulators actually require. We read the region and documentation pages of ten platforms, the documents published on SDAIA's National Data Governance Platform, the National Cybersecurity Authority's published controls and the CST cloud regulations, all on 8 November 2026. We ran no hands-on tests, and nothing here is legal advice.
What the law actually requires: conditions on transfer, not mandatory localisation
The Personal Data Protection Law was issued by Royal Decree M/19 on 16 September 2021, amended by Royal Decree M/148 in March 2023, came into force on 14 September 2023 and gave organisations until 14 September 2024 to comply. The point most sales decks skip: the law as it stands today does not oblige a company to store personal data inside Saudi Arabia. It conditions transfers abroad, in Article 29 and in the Regulation on Personal Data Transfer outside the Kingdom, issued in September 2023 and amended on 1 September 2024. A transfer must serve one of the listed purposes, must not prejudice national security, must go to a country that SDAIA deems to offer adequate protection, and must involve the minimum data needed. As of this guide no adequacy list has been published, so in practice transfers rest on the alternative safeguards: SDAIA's Standard Contractual Clauses, which must be used without modification; Binding Common Rules inside a corporate group; or an accreditation certificate valid for two years, each accompanied by a documented risk assessment under SDAIA's transfer risk assessment guideline.
All of these documents sit in the knowledge centre of the National Data Governance Platform: the Law, the Implementing Regulations, the Transfer Regulation, the Standard Contractual Clauses, the Binding Common Rules guide, the rules on appointing a Data Protection Officer, the rules on accreditation certificates for controllers and processors, and the rules of the National Register of Controllers. The same platform hosts the register itself, breach notification, impact assessment, and an accreditation service for AI service providers that starts with registering the entity and appointing an AI officer, then a questionnaire reviewed by a committee. Fines reach five million riyals and can be doubled for repeat violations; law firms counted forty-eight published enforcement decisions in the year to January 2026.
The part that matters most to anyone signing now: on 6 October 2026 SDAIA published a draft of extensive amendments to the Implementing Regulations for public consultation on the Istitlaa platform until 5 November 2026. One draft clause reads, in effect, that the controller shall store personal data within the Kingdom, with transfers still permitted under the Law. If adopted as drafted, a Saudi at-rest copy becomes a baseline duty rather than a preference, and every contract signed this year should be asked whether it can deliver one. As of 8 November the outcome of the consultation had not been published.
Government, critical infrastructure and finance: here residency is mandatory
For government entities and critical national infrastructure the picture is different, and more interesting than the old summaries suggest. The second edition of the Essential Cybersecurity Controls, published in 2024, deleted the 2018 sub-control that read "entity's information hosting and storage must be inside the Kingdom of Saudi Arabia", moved data-localisation controls to the National Data Management Office at SDAIA, and kept the requirement that managed cybersecurity service centres be located entirely inside the Kingdom. The second edition of the Cloud Cybersecurity Controls did the same, telling entities to refer to the National Data Management Office on localisation before taking any action, and requiring that community clouds for government and critical infrastructure be isolated. The localisation rule itself now lives with the CST: version four of the Cloud Computing Services Provisioning Regulations, in force since October 2023, prohibits transferring content that contains Saudi government data outside the Kingdom for any purpose, backups included, requires notice and consent before any subscriber's content leaves the country, and sorts providers into registration classes, where only Class C may hold every level of government data up to top secret.
Banks need the central bank's non-objection before outsourcing; SAMA's official forms ask for the storage location and, when the provider sits abroad, for the reasons a provider inside the Kingdom was not used, and they bar subcontracting without the bank's approval and SAMA's non-objection. For AI specifically, SDAIA has published the AI Ethics Principles in September 2023, the Generative AI Guidelines for government in January 2024 and the AI Adoption Framework in September 2024. All three are guidance, not binding law, and we found no Saudi AI-specific statute in force. The October 2026 draft does add "emerging technologies" and fully automated decisions to the triggers for a data protection impact assessment.
The hyperscalers: what is in the Kingdom and what is only announced
Google Cloud has the longest presence on the ground. The Dammam region opened on 15 November 2023, CNTXT is the exclusive reseller for purchases through a Saudi entity, and Vertex AI has been available in Dammam since May 2024, with sovereign controls operated by CNTXT together with SITE. Google's model-locations page lists Dammam and Doha under "Middle East" with a single shared list of Gemini models. Its data-residency page, updated on 7 November 2026, then says the decisive thing: Google commits to in-region machine-learning processing in thirteen locations, from the United States and the EU to India, Singapore, Japan and South Korea, and neither Dammam nor Doha is among them. Storage at rest in Dammam is committed; processing inside Dammam is not. The ten-billion-dollar AI hub announced by PIF and Google Cloud in May 2025 remains, in everything we could find, announced rather than launched.
Oracle runs two commercial regions, Jeddah and Riyadh, the second hosted by center3 since August 2024. OCI Generative AI has been available in Riyadh since 18 August 2025 with what Oracle calls local model processing, covering Cohere's chat, embedding and rerank models, Meta's Llama models and OpenAI's open-weight models, most of them on dedicated clusters rather than on demand. Jeddah is not a Generative AI region, and xAI's Grok models are not offered in the Middle East regions; Oracle's own documentation says a Grok call goes to an xAI location. The stc sovereign cloud on Oracle Alloy, announced in April 2024, has no published launch date.
Microsoft confirmed its "Saudi Arabia East" region in the Eastern Province with three availability zones on 10 February 2026, and on 31 August 2026 set availability for November 2026. When we read Microsoft's official retail-price list on 8 November, the region carried about thirty core services, from virtual machines to storage and databases, and not a single AI meter. At the same hour we opened Microsoft's official product-availability-by-region table in a headless browser: Saudi Arabia is not among the thirty-three geographies the table lists, and "Azure OpenAI" no longer appears as a product row at all, having been renamed Foundry Models, which the table marks as generally available in UAE North, UAE Central and Qatar Central; anyone searching that table for the old name finds nothing. The table describes product availability per region, not where each model processes a request. UAE North, where Saudi customers are pointed today, is better documented than most buyers realise: the model-availability page dated September 2026 shows in-region processing only for regional provisioned deployments of eleven OpenAI models and for regional standard deployments of the embedding models and the transcription model. Everything else in UAE North, including the DeepSeek, Mistral, Cohere and Grok models, is a "Global" deployment whose prompts may be processed in any geography where the model is offered, and the Data Zone option that confines processing to one geography exists only for the United States and the EU. Add to this that Saudi Arabia is not a Microsoft 365 datacenter location, so a Saudi organisation's Copilot interactions are stored in another geography, the nearest being the UAE or Qatar.
AWS operates the Bahrain and UAE regions and said on 31 August 2026 that its Saudi region is on track to launch in December 2026, with an investment above 5.3 billion dollars and an AI zone with HUMAIN of up to fifty megawatts by 2028. Amazon Bedrock runs in the UAE and Bahrain today, but the model table distinguishes three patterns: Amazon's Nova models are available in-region in the UAE, while Anthropic's models in the UAE and Bahrain are offered through global cross-region inference only, which the documentation says may process data in any commercial region. There is no Middle East geography among the cross-region inference groups. What Bedrock will offer on the day the Saudi region opens is not yet documented.
Alibaba Cloud and the Saudi Cloud Computing Company say data stays in two Riyadh availability zones, yet Alibaba's Model Studio regions page, updated 6 November 2026, lists Beijing, Singapore, Virginia, Frankfurt, Tokyo and Hong Kong; Riyadh is absent, which leaves self-deploying the open Qwen models on Riyadh compute as the local option. We found no official documentation of AI services in Huawei Cloud's Riyadh region, and no confirmation that Tencent's announced Riyadh region has opened.
HUMAIN and the Saudi vendors: what works today
HUMAIN, the PIF company, appears in every announcement, so it pays to separate what exists from what is promised. Existing: the HUMAIN Chat app on the ALLaM model since August 2025; the HUMAIN Voice platform, whose documentation states data residency in the Kingdom; and HUMAIN ONE, the agent platform announced with Turing and then with AWS and Microsoft, without published prices. Promised: HUMAIN Cloud itself was reported as not yet operational in October 2026, with a first fourteen megawatts of Blackwell systems due in the last quarter of 2026, while the Cohere and Mistral partnerships for sovereign Arabic models speak of infrastructure that becomes operational in the last quarter of 2027. HUMAIN's own website could not be reached while we wrote this, so everything above comes from the HUMAIN Voice documentation and dated press releases.
Below HUMAIN sits a layer of vendors who write "Saudi Arabia" into their documentation rather than only their press releases. Hams.AI says audio and text stay in Saudi data centres and that processing runs there by default. Nabrah, in Riyadh, hosts its data locally with an ISO certification. Hamsa, with OmniOps, has run on infrastructure managed inside the Kingdom since July 2026, including air-gapped deployments. WriteX by Lisan deserves a correction to our own listing: the site offers self-hosted and on-premises deployment, but the company is registered in a UAE free zone with a Riyadh office, and its published AWS case study describes data residency within the UAE. In speech, Munsit from CNTXT has offered on-premises containers since May 2026 that send no audio to any external cloud, and Speechmatics documents on-premises containers with a licence that needs no internet connection, its cloud regions being Europe, the United States and Australia only.
The global model vendors: who offers nearby residency and who does not
OpenAI extended data residency on 25 November 2025 to Europe, the United Kingdom, the United States, Canada, Japan, South Korea, Singapore, India, Australia and the UAE; Saudi Arabia is not on the list, the option is for enterprise plans, and the Stargate campus in Abu Dhabi expects its first two hundred megawatts to go live in 2026. Anthropic documents two inference options, global or United States at a higher price, with no European or Gulf region, and its models reached through Bedrock in the UAE or through Microsoft Foundry are processed globally. Google, as shown above, makes no in-region processing commitment for Gemini in Dammam. Mistral documents self-deployment on open inference engines and signed a partnership with HUMAIN in August 2026 that may bring its compute to the Kingdom. Cohere documents private deployment inside the customer's own data centre or cloud, where the data never leaves the environment, and its Arabic transcription model is released under the Apache 2.0 licence.
That points to the route many government bodies are quietly taking: open-weight models on compute inside the Kingdom. The Apache 2.0 licence permits commercial self-hosting of the Jais family from the UAE, the Qwen models, OpenAI's open-weight models and the small preview release of ALLaM, while Llama comes under Meta's community licence with its own conditions, Gemma under Google's terms of use and Falcon under its own licence. This route gives complete residency at an operational price: a team that runs the clusters, updates the models and owns their security.
The questions to ask a vendor before signing
- Where is our data stored at rest, where is the request processed inside the model, and is the second commitment in the contract or on a marketing page? Ask for the region name and the deployment type, literally.
- If data leaves the Kingdom, what is the legal basis: SDAIA's Standard Contractual Clauses unmodified, Binding Common Rules, or an accreditation certificate? Who writes the transfer risk assessment?
- Does the contract carry what Article 17 of the Implementing Regulations requires: purpose, data types, duration, whether the processor is subject to other countries' laws and what that means, named sub-processors, and breach notification to the controller?
- Can a copy be stored inside the Kingdom today, ahead of the amendment proposed in October 2026?
- Are our prompts used for training, is a zero-retention option available, and how long are request logs kept?
- For government and critical infrastructure: what is the provider's CST registration class, is the environment isolated as the Cloud Cybersecurity Controls require, and are managed security and support delivered from inside the Kingdom?
- For financial institutions: has SAMA's non-objection been obtained, and does the contract allow subcontracting without your approval?
- Has your entity registered in the National Register of Controllers, appointed a Data Protection Officer where required, and run an impact assessment that treats AI as an emerging technology?
What we could not verify
We did not reach the official text of the Law and its regulations in quotable form on SDAIA's site or the Bureau of Experts' portal, so we relied on the document index of the National Data Governance Platform and on dated law-firm analyses, and we have left out article numbers we could not confirm, such as the imprisonment provision for disclosing sensitive data. We do not know whether Microsoft's Saudi region was live on 8 November, which AI models it will carry at opening, or the outcome of the regulatory consultation. We did not verify AI services in Huawei Cloud's Riyadh region, Tencent's launch, the status of the PIF and Google hub, any operating capacity of HUMAIN Cloud, or anything on HUMAIN's own website. We did not read the text of the Data Cybersecurity Controls, any SAMA cloud framework, or health-data localisation rules. Everything written here about contracts and regulations is an editor's reading, not a lawyer's.
What to choose
If you are a government entity or critical infrastructure, the question is not which model but which Class C provider and which isolated environment, and the practical options today are OCI Generative AI in Riyadh on dedicated clusters, open-weight models on local compute, or HUMAIN's products once their pricing and documentation are public. If you are a private company processing personal data, you can use OpenAI models in UAE North today on a regional provisioned deployment, Nova models in Bedrock's UAE region, or Google's services in Dammam with the understanding that processing is not committed, provided you have Standard Contractual Clauses and a documented risk assessment in place. If your data is sensitive Arabic speech or text, the vendors that write "Saudi" into their documentation, Hams, Nabrah, Hamsa and HUMAIN Voice, and the on-premises containers from Munsit, Speechmatics and Cohere, are the ones that answer procurement's question with a documented yes. In every case, ask the vendor for a single documentation page that names the region and the deployment type rather than a "sovereign" badge, and read it again in a month; in this subject above all, the facts move faster than the contracts.