Regulatory Compliance in Saudi Arabia
Saudi Arabia's framework rests on the PDPL, its Implementing Regulations, and the separate Data Transfer Regulations, supervised by the Saudi Data and AI Authority. National cloud computing and cybersecurity frameworks apply alongside, and sectoral requirements in financial services and health add further obligations.
The requirements applicable to an organisation depend on its activities, sector, processing operations, and regulatory status.
Key compliance areas include
- Lawful basis and consent: Establish a basis for processing under the Law, including the bases added by the 2023 amendments.
- Privacy notice and transparency: Make a privacy notice available before collecting personal data, setting out the legal basis and purposes.
- Records and impact assessments: Maintain records of processing activities and carry out impact assessments where required.
- Data protection officer: Assess whether a data protection officer must be appointed under the criteria in the Implementing Regulations.
- Breach notification: Establish procedures for notifying SDAIA within seventy-two hours of becoming aware of a personal data breach.
- Transfers outside the Kingdom: Assess adequacy, appropriate safeguards, or an enumerated exception under the Data Transfer Regulations.
- Registration, marketing and credit data: Review national data controller registration, marketing rules and credit data requirements.
- Cloud, cybersecurity and sectoral compliance: Identify additional obligations under the national cloud and cybersecurity frameworks and sectoral rules.
One compliance partner. Saudi Arabia regulatory awareness. A connected global compliance strategy.
Key Regulatory Frameworks in Saudi Arabia
Personal Data Protection Law (PDPL)
The PDPL was issued by Royal Decree M/19 in 2021, amended by Royal Decree in 2023, and became enforceable following a grace period that ran to September 2024. It applies to any processing of personal data relating to individuals that takes place in the Kingdom, and to processing outside the Kingdom of personal data relating to individuals resident in the Kingdom.
The Law also covers the personal data of deceased persons where it would identify them or a family member, which is unusual and distinguishes it from most comparable regimes.
Depending on applicability, organisations may need to address:
- A lawful basis for processing, including consent and legitimate interests.
- Stricter conditions for sensitive data.
- A privacy notice given before collection.
- Records of processing activities.
- Appointment of a data protection officer where required.
- Registration on the national data controller register.
- Breach notification to SDAIA and affected data subjects.
- Conditions for transferring personal data outside the Kingdom.
The extension to the personal data of deceased persons where family members could be identified is a distinctive feature and should be reflected in retention and disclosure practices.
The 2023 Amendments
As originally issued, the PDPL took a restrictive approach, requiring personal data to be processed within the Kingdom in most cases and permitting transfers abroad only narrowly with authority approval. The 2023 amendments removed the general localisation default and reframed transfers around adequacy and safeguards.
The amendments also introduced legitimate interests as a lawful basis, which the original text lacked, significantly widening the options for routine commercial processing.
Changes introduced may include:
- Removal of the general requirement to process personal data inside the Kingdom.
- Introduction of legitimate interests as a lawful basis.
- A transfer regime based on adequacy determinations and appropriate safeguards.
- Revised provisions on marketing and on credit data.
- Changes to the penalty structure for certain violations.
Compliance programmes built against the 2021 text will be materially out of date; the amended Law and the 2023 Regulations are the operative framework.
Implementing Regulations
The Implementing Regulations issued in September 2023 provide most of the operational detail, covering privacy notices, records of processing, the conditions for relying on legitimate interests, data protection officer requirements, impact assessments, breach notification, and data subject request handling.
Areas addressed in the Regulations may include:
- Content required in a privacy notice.
- The record of processing activities and its particulars.
- The assessment required before relying on legitimate interests.
- Criteria for appointing a data protection officer.
- Impact assessment triggers and methodology.
- Timeframes for responding to data subject requests.
Because the Regulations carry the operational detail, compliance is assessed against them as much as against the Law itself.
Data Transfer Regulations
Transfers of personal data outside the Kingdom are governed by separate Data Transfer Regulations. Transfers are permitted where the destination has been assessed as providing an adequate level of protection, or where appropriate safeguards are in place such as binding common rules within a group, standard contractual clauses, or certification.
Where neither adequacy nor a safeguard is available, transfers may proceed only in limited enumerated situations, and a risk assessment is required in defined cases.
Organisations transferring data out of the Kingdom may need to consider:
- Whether an adequacy determination covers the destination.
- Which safeguard mechanism is available and appropriate.
- Whether a transfer impact or risk assessment is required.
- The limited exceptions where no safeguard exists.
- Restrictions applying to sensitive data and to onward transfers.
- That the transfer must not prejudice national security or the Kingdom's interests.
The requirement that a transfer not prejudice national security or the Kingdom's vital interests is an overriding condition with no equivalent in European transfer analysis.
Cloud, Cybersecurity and Sectoral Frameworks
National frameworks apply in addition to the PDPL. The National Cybersecurity Authority issues controls that regulated and government-linked entities are expected to implement, and cloud computing regulatory frameworks classify data and set hosting expectations. Financial institutions are subject to Saudi Central Bank requirements, and health data to Ministry of Health rules.
Sectoral considerations may include:
- National cybersecurity controls applicable to the entity.
- Cloud computing data classification and hosting expectations.
- Saudi Central Bank outsourcing and cloud requirements.
- Health data handling and hosting rules.
- Government and public sector data classification policies.
Even though the PDPL's general localisation default was removed, sectoral and cloud frameworks may still constrain where particular data can be hosted.
Marketing, Credit Data and Registration
The PDPL restricts the use of personal data for marketing, generally requiring consent and a means of opting out, and contains specific provisions on credit data including a requirement to notify the data subject before disclosing credit information.
SDAIA operates a national register of data controllers, and controllers are expected to register and keep their particulars current.
Organisations may need to consider:
- Consent and opt-out mechanics for direct marketing.
- Notification requirements before disclosing credit data.
- Registration on the national data controller register.
- Restrictions on using personal data for marketing obtained for another purpose.
- Record-keeping to evidence consent.
Confirm the current registration requirements and timetable with SDAIA, as the register and associated obligations have been rolled out progressively.
Data Subject Rights Under the PDPL
The PDPL gives data subjects a number of rights over their personal data. Depending on the circumstances, these may include.
Depending on the circumstances, these may include:
- Right to Be Informed: data subjects have the right to be informed of the legal basis and purpose for collecting their personal data.
- Right of Access: data subjects may request access to their personal data held by the controller, in accordance with the Regulations.
- Right to Obtain a Copy: data subjects may request a copy of their personal data in a readable and clear format.
- Correction: data subjects may request correction, completion, or updating of their personal data.
- Destruction: data subjects may request destruction of personal data no longer needed, subject to statutory retention requirements.
- Withdrawal of Consent: where processing is based on consent, data subjects may withdraw it at any time.
The Implementing Regulations set out the periods for responding to requests and the grounds on which a request may be refused.
Penalties for Non-Compliance
The PDPL distinguishes between violations. Disclosing or publishing sensitive data in breach of the Law can attract imprisonment of up to two years and a fine of up to SAR 3 million, and unlawfully transferring personal data outside the Kingdom can attract imprisonment and a fine. Other violations of the Law and its regulations attract a warning or a fine of up to SAR 5 million, which may be doubled for repeat offences.
A competent court determines criminal penalties, while a committee formed by SDAIA considers other violations and imposes administrative penalties. Courts may also order confiscation of proceeds and publication of the judgment at the offender's expense. Data subjects may separately claim compensation for damage through the courts, so exposure is not limited to regulatory penalties.
Saudi Arabia's Regulatory Timeline
Saudi Arabia issued, amended, and then enforced the PDPL over three years.
Key developments include:
- September 2021 - PDPL Issued: royal Decree M/19 issued the Personal Data Protection Law, originally including a general requirement to process personal data inside the Kingdom.
- March 2023 - PDPL Amended: amendments removed the general localisation default, introduced legitimate interests as a lawful basis, and reframed the transfer regime.
- September 2023 - Regulations Issued: the Implementing Regulations and separate Data Transfer Regulations were issued, providing the operational detail.
- September 2024 - Grace Period Ends: the compliance grace period expired, from which point the PDPL became enforceable against controllers and processors.
Important: SDAIA continues to issue guidance, adequacy determinations, and registration requirements. Confirm the current position from official sources before changing your compliance programme.
Regulatory Authorities in Saudi Arabia
Regulatory responsibilities are split between the competent authority for the PDPL and sectoral regulators. The relevant authority depends on the organisation's sector and activities.
Saudi Data and AI Authority (SDAIA)
The Saudi Data and AI Authority (SDAIA) is the competent authority for the PDPL. It issues regulations, rules, and guidance, operates the national data controller register, makes adequacy determinations for transfers, receives breach notifications and complaints, and supervises compliance. Supervision was contemplated to transfer to a dedicated data protection body in due course.
National Cybersecurity Authority (NCA)
Relevant to cybersecurity controls applicable to organisations in the Kingdom.
Saudi Central Bank (SAMA)
Relevant to financial institutions, which face additional requirements alongside the PDPL.
Communications, Space and Technology Commission (CST)
Relevant to communications, space and technology sector requirements.
Ministry of Health
Relevant to health data and the organisations that handle it.
Confirm whether supervisory responsibility still sits with SDAIA or has transferred, as the Law envisaged a future transfer to a dedicated body.
How RegulatoryBridge Supports Compliance in Saudi Arabia
RegulatoryBridge helps organisations assess Saudi Arabia's regulatory requirements and coordinate their compliance activities with wider international programmes. The scope of support is tailored to the organisation's activities, risk profile, and applicable legal requirements.
PDPL Compliance Assessment
Review your processing activities, legal bases, notices, policies, governance arrangements, and operational controls to identify potential gaps.
Data Protection Officer and Registration Assessment
Review whether your processing requires a data protection officer, and the registration and record-of-processing obligations SDAIA operates.
Data Subject Rights
Review request-handling processes, response timelines, privacy notices, and related documentation against the requirements applicable to you.
Breach Response and SDAIA Notification
Evaluate breach assessment procedures, escalation responsibilities, SDAIA notification readiness, and coordination between privacy, security, and legal teams.
International Data Transfers
Assess transfers out of the Kingdom against the Data Transfer Regulations, including adequacy determinations, appropriate safeguards, and risk assessment requirements.
Sectoral Compliance Coordination
Help organise requirements across the PDPL, cloud computing and cybersecurity frameworks, financial sector rules, and health data requirements.
Regulatory Monitoring
Monitor relevant developments and review compliance plans when legislation, SDAIA guidance, or enforcement decisions change.
Who Needs Regulatory Compliance Support in Saudi Arabia?
RegulatoryBridge supports organisations that need to understand and manage regulatory obligations in Saudi Arabia, including:
Organisations in the Kingdom
Public and private entities processing personal data of individuals where the processing takes place in Saudi Arabia.
International companies
Organisations outside the Kingdom processing personal data relating to individuals resident in Saudi Arabia.
Processors
Service providers processing on a controller's behalf, which must follow instructions and meet the security requirements.
Organisations needing a DPO
Controllers meeting the criteria in the Implementing Regulations, which must appoint a data protection officer.
Employers
Organisations handling employee and candidate data, including health information treated as sensitive data.
Entities under sectoral frameworks
Financial institutions, healthcare providers, and government-linked entities subject to cybersecurity and cloud frameworks in addition to the PDPL.
The precise obligations depend on the organisation's role, processing activities, size, risk profile, and territorial scope.
Our Saudi Arabia Compliance Approach
- 01
Identify Applicable Requirements
Assess your organisation's activities, role in processing personal data, industry, and connections to Saudi Arabia.
- 02
Map Regulatory Obligations
Identify applicable provisions, relevant authorities, effective dates, and sector-specific requirements.
- 03
Conduct a Gap Assessment
Review existing policies, notices, consent mechanisms, contracts, security controls, and operational processes.
- 04
Develop a Compliance Roadmap
Prioritise remediation activities and establish owners, milestones, documentation requirements, and implementation plans.
- 05
Maintain Ongoing Readiness
Review regulatory developments, reassess relevant obligations, and update compliance processes when required.
Why Choose RegulatoryBridge for Saudi Arabia?
45+ Jurisdictions
Coordinate Saudi Arabia compliance with requirements across other markets through a connected approach.
Centralised Visibility
Improve oversight of obligations, compliance gaps, responsibilities and implementation progress.
Practical Implementation
Turn complex regulatory requirements into prioritised actions and clear workflows.
Cross-Border Coordination
Support organisations managing international data flows, suppliers and multiple regulatory regimes.
Scalable Compliance
Adapt your compliance programme as your business, technology and regulatory exposure change.
Integrated Governance
Connect privacy, data protection governance, cybersecurity and wider digital compliance activities.
Frequently Asked Questions
Simplify Regulatory Compliance in Saudi Arabia
We support your data protection officer arrangements, SDAIA registration and interactions, and transfer documentation - so your global product team doesn't have to.