BroadRouter

Saudi and UAE PDPL and LLM APIs: a cross-border checklist

By the BroadNet Inference team · 8 min read · Published

Under Saudi Arabia's PDPL, sending personal data in a prompt to an LLM API hosted abroad is a transfer outside the Kingdom. Article 29 and SDAIA's transfer regulation set the conditions: an adequate destination or safeguards, the minimum data needed, and a risk assessment in some cases. The UAE law also regulates cross-border transfers. Minimise first, then check where the provider processes. Not legal advice.

If your prompt carries personal data about people in Saudi Arabia or the UAE, and the LLM provider processes it outside the country, you are making a cross-border transfer. Both countries regulate that. This post walks through what the Saudi PDPL and SDAIA’s transfer regulation say, what the UAE law covers, and the questions to ask an LLM API provider before you send the first request. It is a practical checklist, not legal advice; confirm your own case with counsel. Serving users in Egypt? See the companion post on Egypt’s data protection law (Law 151 of 2020) and LLM APIs.

Article references below are BroadRouter’s reading of SDAIA’s Arabic texts, fetched from SDAIA’s platform on 15 November 2026. English renderings are our translation, not an official one.

When does an LLM API call become a transfer?

Three definitions in the Saudi Personal Data Protection Law (PDPL) decide it:

  • Personal data is any data that can identify a person directly or indirectly: name, ID number, address, phone, account numbers, photos and similar (Article 1).
  • Processing is any operation on personal data, and the law’s list includes collection, storage, use, disclosure and transfer (Article 1).
  • Transfer means moving personal data from one place to another for processing (Article 1).

Article 2 then applies the law to processing in the Kingdom and to processing of residents’ personal data by any party outside the Kingdom. So a support chatbot that sends a customer’s name, phone number and complaint to a model hosted abroad is in scope. A prompt with no personal data in it is not a personal data transfer at all, which is why minimisation comes first in the checklist below.

What does Saudi PDPL Article 29 require?

Article 29 is the transfer rule. In our reading of the Arabic text:

Part What it says
29(1) Purposes A transfer outside the Kingdom is allowed to meet an agreement the Kingdom is party to, to serve the Kingdom’s interests, to perform an obligation to which the data subject is a party, or for other purposes set by the regulations
29(2)(a) The transfer must not harm national security or the Kingdom’s vital interests
29(2)(b) The destination must offer an adequate level of protection, not lower than the PDPL’s, based on SDAIA’s assessment
29(2)(c) The transfer must be limited to the minimum personal data needed
29(3) 29(2) does not apply in cases of extreme necessity to protect the data subject’s life or vital interests, or to prevent or treat infection
29(4) The regulations set the detail, including exemptions from 29(2)(b) and (c)

Two other articles matter for API buyers. Article 8 says a controller must choose a processor that provides the guarantees needed to comply, and must verify that it does. Article 19 requires organisational, administrative and technical measures to protect personal data, including when it is transferred.

What does SDAIA’s transfer regulation add?

SDAIA’s Regulation on the Transfer of Personal Data outside the Kingdom (issue 02, August 2024) fills in Article 29:

Article What it adds
2 “Other purposes” include central operational processing needed for the controller’s activities, providing a service or benefit to the data subject, and scientific research
3 SDAIA publishes the list of countries and organisations with adequate protection on its website, reviewed every four years or when needed
4 Where an exemption applies, the controller uses appropriate safeguards: standard contractual clauses, binding common rules, or an accreditation certificate. Several exemption cases exclude sensitive data
5 The PDPL keeps applying to onward transfers of the data
7 A risk assessment is required before a transfer that relies on Article 4, and before transferring sensitive data continuously or at wide scale

SDAIA’s knowledge center also publishes a guideline on assessing transfer risk, a guide to binding common rules and the standard contractual clauses themselves. Read those before you design a pipeline that sends Saudi personal data abroad.

Sensitive data under Article 1 includes health, genetic and biometric data, criminal and security data, religious or political belief, and ethnic origin. Voice recordings of patients or photos of ID cards in a prompt push you into the stricter cases.

What are the penalties in the Saudi PDPL?

Article 36 sets a warning or a fine of up to five million riyals for violations not covered by Article 35, and a fine can be doubled for repeat violations. Article 35 sets up to two years in prison, a fine of up to three million riyals, or both, for disclosing or publishing sensitive data in breach of the law with intent to harm the data subject or for personal gain. Article 20 requires the controller to notify SDAIA of a leak, damage or unlawful access, and to notify the data subject if it could harm them.

What does the UAE PDPL say about cross-border transfers?

The UAE’s federal law is Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data. The government portal u.ae says it came into force on 2 January 2022, applies to processing of personal data inside or outside the country, prohibits processing without consent except in listed cases, and sets the requirements for cross-border transfer and sharing. The official text on u.ae is in Arabic.

Pinsent Masons’ 2023 guide, a law-firm summary, says the law allows transfers to countries the UAE Data Office approves as adequate, or where a bilateral or multilateral agreement applies, and in limited other cases such as contracts with enforceable data protection terms. It also said the executive regulations had not been issued. Check their current status before you rely on any detail.

Two carve-outs matter in practice:

  • Free zones. The DIFC has its own law (DIFC Law No. 5 of 2020, listed on u.ae), and the ADGM has its own Data Protection Regulations 2021. If you operate from either, their transfer rules apply instead.
  • Health data. u.ae lists Federal Law No. 2 of 2019 on the use of ICT in health fields, and Pinsent Masons notes that the federal health data law restricts transfer of health data. Clinical transcripts and patient chats need their own review.

Which questions should you ask an LLM API provider?

# Question Why it matters
1 Where do the GPUs that process my requests sit, for each model? Location decides whether it is a transfer
2 Are any models served by partners, and where? Partner hosting can change the country
3 Can I pin processing to one region, in writing? Self-serve region choice is rare
4 Are prompts, files, audio and outputs retained? For how long? Retention abroad widens exposure
5 Is my data used to train or evaluate models? Changes the purpose of processing
6 What metadata is kept, and does it include personal data? Logs are processing too
7 Who are the subprocessors? Article 8 asks you to verify your processors
8 Will you sign contractual clauses that match SDAIA’s standard clauses or the UAE requirements? Safeguards under the transfer rules
9 How fast do you tell me about a breach? You must notify the regulator
10 Can I restrict keys to my servers? Limits who can send data at all

For the GDPR version of these questions see GDPR and LLM APIs: 15 questions; for retention terms across the big providers see LLM API data retention compared.

How do you minimise what leaves the country?

Article 29(2)(c) asks for the minimum data needed, and that is also the cheapest control to build:

  1. Strip identifiers before the call. Replace names, phone numbers, national IDs and IBANs with placeholders, and map them back after the answer. Sending sensitive data to an LLM API has patterns for this.
  2. Send only the fields the task needs. A ticket classifier needs the complaint text, not the customer record.
  3. Keep transcripts and images in-country. Send the text the model needs, not the whole recording or ID photo, where the task allows.
  4. Log less. Store token counts and cost, not prompts. See usage logging with PII redacted.
  5. Lock keys to your servers with an IP allow-list.

When do you need in-country inference?

If a regulator, a sector rule or a contract says the data must be processed in the country, minimisation is not enough. You need a provider that runs inference there, or your own hardware.

One verified example: OpenAI announced inference residency in the UAE for eligible API, ChatGPT Enterprise and ChatGPT Edu customers, so GPU inference for eligible workspaces can be kept on UAE-based engines. Check its current eligibility and model list with OpenAI. We did not verify an equivalent public offering for Saudi Arabia while writing this post. Self-hosting an open-weight model on your own GPUs in the Kingdom is the other route; the self-hosting vs API cost post covers the break-even.

Where BroadNet Inference fits

BroadNet is the company behind BroadRouter, so weigh this accordingly. Its inference privacy statement says its own models and the open-weight models it hosts run on BroadNet-owned or leased hardware in the United States, with partner capacity as backup, and that partner-served models run under zero-data-retention terms with US inference partners. There is no self-serve region selector. The statement asks you to contact BroadNet (info@broadnet.ai) to agree processing locations before you send data with residency requirements.

So a call from Riyadh or Dubai to BroadNet Inference is a transfer to the US, and you need a lawful basis for it under Article 29 or the UAE rules. If you need in-Kingdom or in-country processing, BroadNet is not the default fit; agree a location with BroadNet in writing first, or choose an in-country option.

What BroadNet does offer is retention you can describe simply. Its API reference says it does not retain prompts, audio, images, answers or transcripts, and keeps content-free traffic and usage records for billing, tax, security and legal needs. That helps minimisation and keeps less personal data stored abroad. See zero data retention for the detail and the ZDR checklist for the questions to put to any provider.

Questions

Is calling a foreign LLM API a cross-border transfer under the Saudi PDPL?

If the prompt contains personal data and the provider processes it outside the Kingdom, treat it as one. The law defines processing to include transfer, defines transfer as moving personal data from one place to another for processing, and Article 2 covers residents' data processed by any party outside the Kingdom. Confirm your case with counsel.

Does the Saudi PDPL require data to stay in the Kingdom?

The law text does not ban transfers. Article 29 allows them for listed purposes if they do not harm national security or the Kingdom's vital interests, the destination offers adequate protection (or the regulation's safeguards apply), and only the minimum data needed is sent. Sector rules can be stricter, so check your regulator.

Which countries does SDAIA consider adequate?

Article 3 of SDAIA's transfer regulation says SDAIA publishes the list on its official website and reviews it every four years or when needed. Check the current list on SDAIA's platform before you rely on a destination.

Does the UAE PDPL apply to an LLM API call?

The UAE government portal says the federal law applies to processing of personal data inside or outside the country and sets requirements for cross-border transfer. DIFC and ADGM have their own data protection laws, and health data has its own federal rules. Check which regime applies to you.

Can I keep LLM inference inside the UAE?

Some providers offer it. OpenAI announced inference residency in the UAE for eligible API, ChatGPT Enterprise and ChatGPT Edu customers. BroadNet Inference does not offer self-serve regional processing; its privacy statement asks you to agree processing locations with BroadNet before sending data with residency requirements.

Does zero data retention solve the transfer question?

No. Retention and location are separate. A provider that keeps no prompts still processes them where its GPUs are. Zero retention reduces what is stored abroad and helps minimisation, but the transfer rules still apply to the request itself.

Read as MarkdownAsk ChatGPTAsk ClaudeAsk Perplexity