Two Gulf laws share one acronym. If your prompts carry personal data about people in Saudi Arabia or the UAE, both can apply to the API call.
How it works
Saudi Arabia. The Personal Data Protection Law (نظام حماية البيانات الشخصية) was issued by Royal Decree M/19 dated 9/2/1443H and amended by Royal Decree M/148 dated 5/9/1444H, according to SDAIA’s Arabic text. Article 43 says the law takes effect 720 days after its publication in the Official Gazette.
The provisions that matter for an LLM API, in BroadRouter’s reading of the Arabic text (English renderings are ours, not official):
| Article | What it says |
|---|---|
| 1 | Personal data is any data that can identify a person directly or indirectly; processing includes transfer |
| 2 | The law covers processing of residents’ personal data by any party outside the Kingdom |
| 8 | A controller must choose a processor that gives the guarantees needed to comply, and verify it |
| 29 | Transfers abroad: listed purposes, no harm to national security, adequate protection, minimum data needed |
| 36 | A warning or a fine of up to five million riyals for violations not covered by Article 35 |
SDAIA’s Regulation on the Transfer of Personal Data outside the Kingdom (issue 02, August 2024) adds an adequacy list that SDAIA publishes, safeguards such as standard contractual clauses and binding common rules, and risk assessments for some transfers.
UAE. The federal law is Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data. The u.ae portal says it came into force on 2 January 2022, applies to processing “inside or outside the country”, prohibits processing without consent except in listed cases, and sets requirements for cross-border transfer. Federal Decree-Law No. 44 of 2021 sets up the UAE Data Office as regulator. Free zones differ: the DIFC has DIFC Law No. 5 of 2020.
Why it matters
- Most prompts with names or phone numbers are in scope. Strip PII first; Article 29 asks for the minimum data needed anyway.
- Location decides the transfer. Where the GPUs sit is a data residency question for each model and each subprocessor.
The Saudi and UAE PDPL checklist has the full transfer analysis and ten questions for providers. Egypt’s law has its own name and number: see Egypt’s data protection law (Law 151 of 2020) and LLM APIs. For the EU equivalent, see GDPR.
On BroadNet Inference
BroadNet’s privacy statement says its own and hosted open-weight models run on BroadNet-owned or leased US hardware, with partner capacity as backup, and partner-served models run with US inference partners. So a call from Riyadh or Dubai to BroadNet Inference is a transfer to the US, and you need a lawful basis for it.
There is no self-serve region choice. The statement asks customers to contact BroadNet to agree processing locations before sending data with residency requirements; use the contact page. Inference content is not retained, which supports minimisation but is not in-country processing. This page is not legal advice.