Guide · Data sovereignty

GCC Health Data Sovereignty Compliance: Saudi PDPL, Oman PDPL, and UAE Health Data Residency Requirements

Across the Gulf, health data is treated as sensitive, national and, in several jurisdictions, resident by default. Health systems modernising their data estates need analytics and research capability without moving data across borders it should not cross. This guide summarises the principal frameworks and what they mean for infrastructure design.

Published by Consenta · 28 September 2026

Why sovereignty is the design constraint

GCC governments are investing heavily in digital health as part of national transformation programmes such as Saudi Vision 2030 and Oman Vision 2040. The same programmes place a premium on national control of sensitive data. For health data, the practical result is a combination of strict consent and permit requirements, restrictions on transfer outside the country, and sector rules that favour in-country hosting.

Any architecture that depends on copying patient records into an external platform, even an anonymised one, will encounter these constraints early. Architectures that leave data where it is and move only queries and aggregate results start from a stronger position.

Saudi Arabia: Personal Data Protection Law

The Saudi Personal Data Protection Law, issued by Royal Decree M/19 of 2021 and amended in 2023, came into force on 14 September 2023 with a one-year transition period. It is supervised by the Saudi Data and Artificial Intelligence Authority (SDAIA). Health data is classed as sensitive data and attracts additional obligations.

Transfers of personal data outside the Kingdom are governed by the Regulation on Personal Data Transfer outside the Kingdom, which permits transfer only on specified grounds such as an adequate level of protection, appropriate safeguards or defined exceptions, and generally requires a risk assessment. Health-sector and government cloud requirements frequently add an expectation that health data is hosted in-Kingdom.

Oman: Personal Data Protection Law

Oman’s Personal Data Protection Law, Royal Decree 6/2022, took effect in February 2023, and its Executive Regulations were issued in 2024 by the Ministry of Transport, Communications and Information Technology, followed by a transition period. The law is notable for requiring a permit from the Ministry before processing certain categories of data, including health, genetic and biometric data.

Controllers must also meet obligations on consent, security, breach notification and cross-border transfer. For health organisations, the permit requirement means that the purposes and safeguards of each processing activity must be defined clearly before processing begins.

United Arab Emirates: health data localisation

Health data in the UAE is governed principally by Federal Law No. 2 of 2019 on the Use of Information and Communications Technology in Health Fields and its implementing regulations. The law requires health data and information relating to health services provided in the State to be stored and processed inside the UAE, subject to exceptions set by ministerial decision.

The federal Personal Data Protection Law, Federal Decree-Law No. 45 of 2021, excludes health personal data that is governed by its own legislation. Emirate-level health authorities, including the Department of Health Abu Dhabi and the Dubai Health Authority, issue their own data and cybersecurity standards, and the DIFC and ADGM free zones operate separate data protection regimes.

Qatar and Bahrain

Qatar’s Law No. 13 of 2016 on Personal Data Privacy Protection treats health data as personal data of a special nature, which may only be processed with permission from the competent authority and subject to additional safeguards. Bahrain’s Law No. 30 of 2018 on Personal Data Protection likewise classes health data as sensitive and restricts its processing and transfer.

What compliant health data infrastructure looks like

The common thread is that health data should stay under national control, that each use should be tied to a defined, permitted purpose, and that the organisation should be able to prove both. Infrastructure that meets these expectations tends to share several properties.

  • In-country deployment: data remains in national infrastructure; analysis is brought to it.
  • Purpose-bound access: every query is checked against the patient’s consent and the organisation’s permit or legal basis before it runs.
  • Aggregate outputs: only de-identified, disclosure-controlled results leave the environment.
  • Evidence by default: a tamper-evident audit trail of consent events and access decisions, available to regulators on request.

How Consenta approaches sovereignty

Consenta is sovereign data infrastructure. Its federated model runs within the data holder’s environment, its programmable consent engine enforces permissions at the point of use, and its trust layer anchors only cryptographic hashes of consent events, never personal or health data. Consenta is in discussion with health organisations in the Gulf.

Frequently asked questions

Can health data leave Saudi Arabia?+

Only on the grounds set out in the PDPL and its transfer regulation, such as adequacy, appropriate safeguards or defined exceptions, usually following a risk assessment. Sector and government cloud rules often expect health data to remain in-Kingdom, so federated analysis is generally the lower-risk design.

Is a permit needed to process health data in Oman?+

Yes. Oman’s PDPL requires a permit from the competent ministry before processing health, genetic and biometric data, in addition to the law’s general obligations.

Does UAE law require health data to be stored in the UAE?+

Federal Law No. 2 of 2019 requires health data relating to health services provided in the UAE to be stored and processed in the country, except where ministerial decisions permit otherwise.

Programmable consent, enforced at the point of use

Consenta is sovereign data infrastructure for health data: consent that is recorded, enforced, revocable and auditable, with federated access so data stays where it is. Join the waitlist as a patient, organisation or data buyer, or contact the team at [email protected].

Further reading

This guide is general information about the regulatory landscape and is not legal advice. Regulatory requirements change; organisations should obtain their own legal and data protection advice before acting.