Data Protection Monitor
Global Privacy & Data Protection Intelligence

Not every instrument is backed by its official text yet. At least one law or rulebook covered here has no official source (tier 1) retrieved for it yet. No finding on this page is shown with confidence above “Probable” until stronger sources are retrieved.

Saudi Arabia Data Protection & Privacy Regulation

SA schema gdpri-v2 trajectory: not yet assessed regulated (omnibus) overlaps: Sentinel (AML/CFT), World Payments, artificial-intelligence

Last updated · 10 categories · 137 claims · 100 sources in the cumulative register

Saudi Arabia's Personal Data Protection Law has entered its first sustained enforcement phase.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Regulator & Framework, Enforcement & Redress (2 open gaps).

Framework & posture10 of 10 modules active
10 active · 19 binding instruments
Next milestoneNo upcoming dated milestone on record
Record & confidence mix138 claims · 97 sources · machine-compiled
118 Probable18 Contested / unverified
Evidence re-verified: ·Position last changed: ·
Record history & provenance ▾

Methodology & record provenance: Module confidence is derived from the underlying claims (source tier and primary excerpt retention), while statutory legal force is tracked independently.

Review status: AI-synthesised · Tier-1/2 verified · As-of date: 2026-11-17

Jurisdiction brief

Latest update · 15 November 2026

Lead Signal

Saudi Arabia's data protection authority has opened a consultation on draft amendments to the Implementing Regulation of the Personal Data Protection Law, running from 6 October to 5 November 2026. The draft would broaden the trigger for breach notification, introduce an express data-localisation requirement in place of the current transfer-safeguards approach, and add controller-registration obligations. None of these changes is yet in force; if adopted, they would take effect 60 days after publication in the Official Gazette.

Key regulatory facts for Saudi Arabia
Key regulatory facts for Saudi Arabia
Regulatory DimensionSaudi Arabia Standing Position
JurisdictionSaudi Arabia (SA)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 137 sourced findings)
Regulator & FrameworkComprehensive omnibus statute in force with an operational regulator, implementing regulations, and an active registration platform.
Lawful Processing & Special DataLawful-basis regime is narrower than GDPR (fewer enumerated grounds; legitimate interest only added by 2023 amendment and excluded for sensitive data), creating residual compliance friction.
Data Subject RightsCore rights exist and are binding, but response-window specificity and portability provisions are thinner than GDPR, creating operational ambiguity flagged by practitioners.
Controller/Processor DutiesCore accountability infrastructure (DPIA, DPO, ROPA, breach notification) is binding and operative, but the immediate data-subject breach notification standard (rather than a risk-based threshold) is flagged by commentators as operationally stringent and under-specified.
Primary Instruments CitedNational Law Review, Saudi Privacy Law, CMS Law, Pinsent Masons (Out-Law), Saudi Privacy Law (private commentary site)
Last Confirmed / Updated (100 sources in cumulative register)

#

Comprehensive omnibus statute in force with an operational regulator, implementing regulations, and an active registration platform.

Primary frameworkPersonal Data Protection Law (PDPL), Royal Decree M/19 (17 Sept 2021), as amended 21 March 2023, with Implementing Regulations and Cross-Border Data Transfer Regulation (effective 14 Sept 2023, fully enforceable 14 Sept 2024)
Traffic-light rationale — GreenComprehensive omnibus statute in force with an operational regulator, implementing regulations, and an active registration platform.

Sub-modules (5)

Regulator and authorityGreen

SDAIA is the designated data protection regulator under the PDPL, exercising quasi-judicial enforcement powers through specialized committees.

Claims (7):

  • The Saudi Data and Artificial Intelligence Authority (SDAIA) is the designated regulator for the Personal Data Protection Law.
  • SDAIA is the competent authority responsible for supervising and enforcing the PDPL, with a mandate extending to national data governance and AI strategy.
  • Saudi Data and Artificial Intelligence Authority (SDAIA) — The PDPL and its regulations came into force on 14 September 2023, followed by a one-year grace period that ended on 14 September 2024, since which date the PDPL has been fully enforceable under SDAIA.
  • SDAIA is the competent authority for PDPL enforcement, combining data-protection and AI policy functions.
  • Saudi Data and Artificial Intelligence Authority (SDAIA) — Continuing competent authority for the PDPL; initial two-year Council of Ministers designation lapsed September 2025 with no transfer to NDMO
  • Proposed Amendments to the Implementing Regulation of the PDPL (2025 consultation round) — SDAIA's third public consultation round on PDPL Implementing Regulation amendments (privacy-policy language, direct marketing, record-keeping, complaint procedures, DPO role, controller registration) opened 27 April 2025 and closed 27 May 2025 via the Istitlaa Platform, followed by a further revised draft put to consultation in 2026.
  • SDAIA supervises implementation of the PDPL and separately leads national AI governance instruments

Act and instrumentsGreen

The PDPL, as amended, together with its Implementing Regulations and the Regulations on Personal Data Transfers, form the primary instrument set.

Claims (7):

  • The Personal Data Protection Law was implemented by Royal Decree M/19 of 17 September 2021 approving Resolution No. 98, and amended on 21 March 2023.
  • SDAIA — Draft amendments to the PDPL Implementing Regulations published 6 October 2026 for consultation closing 5 November 2026; if approved, effective 60 days from Gazette publication.
  • The PDPL Implementing Regulations were published 7 September 2023, one week before the PDPL's 14 September 2023 entry into force.
  • SDAIA — On amendments to the PDPL Implementing Regulation (announced 4 Aug 2026), comment period to 5 November 2026; no amendment finalised.
  • Personal Data Protection Law (PDPL) — In force since 14 September 2023
  • SDAIA — Public consultation on draft amendments to PDPL Implementing Regulations, 6 October-5 November 2026, covering localisation, breach-notification thresholds, DPIA, DPO and controller-registration obligations
  • Personal Data Protection Law (Royal Decree M/19, amended M/148) — In force since 14 September 2023; grace period expired 14 September 2024

Material scopeGreen

The PDPL covers personal data processing principles (purpose limitation, minimization), controller obligations, registration/ROPA, data subject rights, and penalties.

Claims (1):

  • The PDPL covers key principles such as purpose limitation and data minimization, controller obligations including registration and maintenance of data processing records, data subject rights, and penalties for breach of provisions.

Territorial scopeGreen

The PDPL has extraterritorial effect, applying to entities inside and outside the Kingdom that process personal data of Saudi citizens or residents.

Claims (4):

  • The PDPL applies to all entities, whether based inside or outside the Kingdom, that process the personal data of Saudi citizens or residents, and also extends to individuals who collect personal data of others.
  • Personal Data Protection Law (PDPL) — Any entity processing personal data of individuals located in Saudi Arabia, regardless of the entity's own location.
  • PDPL — Non-KSA processors handling KSA residents' data, per secondary commentary
  • PDPL Art 2(1)-(2) — PDPL applies to processing of personal data in the Kingdom and to processing of data of Kingdom residents by any party anywhere, excluding purely personal/family use not disclosed to others

Regulator registration and filingAmber

Controllers must register via an electronic portal (National Data Governance Platform) with an annual fee and maintain a Record of Processing Activities (ROPA) registered with SDAIA.

Claims (6):

  • Data controllers must register via an electronic portal which includes an annual registration fee.
  • Data controllers must create and maintain a record of how they process personal data, and it must be registered with the SDAIA.
  • SDAIA — On the National Data Governance Platform enabling overseas organisations (previously blocked by a commercial-registration requirement) to register as controllers.
  • SDAIA launched a public consultation (open through 27 May 2025) on proposed amendments to the PDPL Implementing Regulations, including changes to DPO appointment rules and controller registration/oversight obligations; final adoption status not independently confirmed.
  • National Data Governance Platform (NDGP) — Controller must register on the NDGP where it is a public entity, processes sensitive data, or processing personal data is its main activity in the Kingdom
  • National Data Governance Platform (NDGP) registration — No registration fee currently applies
Category narrative 57 words

Saudi Arabia's Personal Data Protection Law (PDPL), enacted by Royal Decree M/19 and amended in March 2023, is a GDPR-style omnibus statute administered by the Saudi Data and Artificial Intelligence Authority (SDAIA). The law and its Implementing Regulations/Cross-Border Data Transfer Regulation have been fully in force and enforceable since 14 September 2024, following a phased transition period.

Periodic update · new data 2026-11-15

The Saudi Data and Artificial Intelligence Authority (SDAIA) supervises implementation of the Personal Data Protection Law and separately leads national AI governance instruments. The Personal Data Protection Law, established by Royal Decree M/19 and amended by M/148, has been in force since 14 September 2023; its grace period expired on 14 September 2024, after which full enforcement became active.

The Saudi Data and Artificial Intelligence Authority opened a public consultation on draft amendments to the PDPL Implementing Regulations, running from 6 October to 5 November 2026, covering data localisation, breach-notification thresholds, data protection impact assessments, data protection officer requirements and controller-registration obligations. If the amendments are adopted as drafted, they would take effect 60 days after publication in the Official Gazette, which had not occurred as.

Outlook

The closing of the consultation window on 5 November 2026 sets up a decision point on adoption. Whether the draft amendments proceed to gazettal, and in what form, remained unresolved as; the existing 2023 law and its current Implementing Regulation remain the operative framework in the interim.

3 earlier distinct updates
Periodic update · new data 2026-11-04

The Saudi Data and Artificial Intelligence Authority has opened a public consultation on a substantial package of amendments to the Implementing Regulation of the Personal Data Protection Law, running from 6 October 2026 to 5 November 2026. The package is wide-ranging: it touches cross-border data handling, breach notification, the circumstances requiring a data protection officer and controller registration, and the scope of consent for direct marketing. None of these changes has been adopted; they remain proposals open for comment, and the authority has not itself confirmed a decision date or an Official Gazette publication date. Secondary legal commentary places a likely effective date 60 days after eventual publication, but this figure comes from third-party reporting rather than from the regulator directly, and should be read as indicative rather than confirmed.

Outlook

The consultation closes 5 November 2026. Whether and in what form the draft provisions are adopted will determine the shape of the Kingdom's data protection framework going into 2027; the authority's own confirmation of a Gazette publication date would be the next concrete marker to watch.

Periodic update · new data 2026-10-25

The Saudi Data and Artificial Intelligence Authority, which combines data-protection enforcement with artificial-intelligence policy functions, published draft amendments to the Personal Data Protection Law's Implementing Regulations on 6 October 2026. The consultation on these draft amendments closes 5 November 2026, and if the amendments are approved as proposed, they would take effect 60 days following publication in the official Gazette. This places the authority in an active rule-making posture this period, with a defined and relatively near-term timeline running from the consultation close through to a prospective commencement date.

The draft amendments described in available commentary are extensive, touching cross-border data transfer rules, breach-notification obligations, data protection officer administrative requirements, records-of-processing-activities obligations, and direct-marketing provisions. This breadth suggests the authority is using this consultation cycle to make a comprehensive update to the Implementing Regulations rather than a narrow, single-issue amendment, which is consistent with a data protection framework still maturing since the Personal Data Protection Law's own effective date in 2023.

No primary Saudi Data and Artificial Intelligence Authority website page was directly retrieved and quoted confirming the draft amendment text this period; the available findings rest on corroborating commentary from multiple independent legal and compliance publishers describing the same consultation, instrument, and dates consistently.

Outlook

The 5 November 2026 consultation close is the immediate date to track, as scheduled. Whether the authority publishes a final version of the amendments that matches the draft text described in current commentary, and the precise date from which the 60-day commencement period would run, are the two open questions most likely to be resolved in the near term following the consultation close.

Periodic update · new data 2026-10-18

SDAIA published draft amendments to the PDPL Implementing Regulations for public consultation on 6 October 2026, with the window closing 5 November 2026. This is corroborated by two independent law-firm summaries describing the same SDAIA consultation notice, giving the fact of the consultation itself a reasonably solid secondary-source basis, though the primary SDAIA notice has not been independently retrieved. If approved, the amendments are understood to take effect sixty days after publication in the official Gazette, which would place a plausible effective date in the first quarter of 2027, though this remains contingent on the outcome of the consultation and is not yet confirmed.

SDAIA is understood to be the competent authority responsible for administering the PDPL, with an allocation of authority stated as being without prejudice to the Saudi Central Bank's powers over the entities that the Saudi Central Bank regulates. This carve-out is reported via a Tier 4 industry guide rather than a pinpoint statutory citation, and the exact article establishing the division of regulatory responsibility between SDAIA and the Saudi Central Bank has not been independently retrieved this cycle. Entities operating in or adjacent to the financial sector in Saudi Arabia should therefore be aware that data-protection compliance questions may, in practice, engage both SDAIA and the Saudi Central Bank depending on the nature of the processing and the regulated status of the entity concerned, though the precise contours of this dual-authority arrangement remain to be clarified by primary source material.

The PDPL's territorial reach is understood, per secondary legal commentary, to extend to non-Saudi Arabia processors handling the personal data of Saudi Arabia residents. This extraterritorial scope, if accurately characterised, places Saudi Arabia's data protection regime within a broader international pattern of residence-based rather than purely establishment-based jurisdictional reach. As with the competent-authority allocation, the specific statutory provision establishing this territorial scope has not been independently retrieved this cycle, and the characterisation rests on law-firm secondary commentary rather than a pinpoint citation to the PDPL text itself.

Taken together, these three elements, the draft amendment consultation, the SDAIA-Saudi Central Bank authority allocation, and the extraterritorial scope, describe a regulatory framework that is actively being refined through SDAIA's rulemaking process while resting, for several of its foundational features, on secondary rather than primary-source confirmation. This is a framework in active development rather than a settled, fully primary-sourced regime at this point in its maturity.

Outlook

The consultation on the draft PDPL Implementing Regulation amendments closes 5 November 2026. The period immediately following closure should be watched for SDAIA's response to consultation feedback and, eventually, for publication of the finalised amendments in the official Gazette, which would trigger the sixty-day countdown to effectiveness. Primary-source confirmation of both the competent-authority allocation between SDAIA and the Saudi Central Bank, and the PDPL's precise territorial-scope provision, would strengthen the evidentiary basis for assessments of Saudi Arabia's regulatory framework in future cycles.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (25)
  1. Probable OneTrust DataGuidance — The Saudi Data and Artificial Intelligence Authority (SDAIA) is the designated regulator for the Personal Data Protection Law. observed
  2. Probable OneTrust DataGuidance — The Personal Data Protection Law was implemented by Royal Decree M/19 of 17 September 2021 approving Resolution No. 98, and amended on 21 March 2023. observed
  3. Probable OneTrust DataGuidance — The PDPL covers key principles such as purpose limitation and data minimization, controller obligations including registration and maintenance of data processing records, data subject rights, and penalties for breach of provisions. observed
  4. Probable IAPP — The PDPL applies to all entities, whether based inside or outside the Kingdom, that process the personal data of Saudi citizens or residents, and also extends to individuals who collect personal data of others. observed
  5. Probable IAPP — Data controllers must register via an electronic portal which includes an annual registration fee. observed
  6. Probable IAPP — Data controllers must create and maintain a record of how they process personal data, and it must be registered with the SDAIA. observed
  7. Probable https://www.reedsmith.com/our-insights/blogs/viewpoints/102o5at/sdaia-consults-on-extensive-amendments-to-the-saudi-pdpl-implementing-regulation/ — SDAIA — Draft amendments to the PDPL Implementing Regulations published 6 October 2026 for consultation closing 5 November 2026; if approved, effective 60 days from Gazette publication.
  8. Probable Clyde & Co — SDAIA — On the National Data Governance Platform enabling overseas organisations (previously blocked by a commercial-registration requirement) to register as controllers. observed
  9. Probable SGC Consulting — SDAIA is the competent authority responsible for supervising and enforcing the PDPL, with a mandate extending to national data governance and AI strategy. observed
  10. Probable Clyde & Co — The PDPL Implementing Regulations were published 7 September 2023, one week before the PDPL's 14 September 2023 entry into force. observed
  11. Uncertain National Law Review — SDAIA launched a public consultation (open through 27 May 2025) on proposed amendments to the PDPL Implementing Regulations, including changes to DPO appointment rules and controller registration/oversight obligations; final adoption status not independently confirmed. observed
  12. Probable https://securiti.ai/saudi-arabia-personal-data-protection-law/ — Saudi Data and Artificial Intelligence Authority (SDAIA) — The PDPL and its regulations came into force on 14 September 2023, followed by a one-year grace period that ended on 14 September 2024, since which date the PDPL has been fully enforceable under SDAIA.
  13. Probable https://www.dataguidance.com/jurisdictions/saudi-arabia — SDAIA — On amendments to the PDPL Implementing Regulation (announced 4 Aug 2026), comment period to 5 November 2026; no amendment finalised.
  14. Probable Global Privacy Blog — Personal Data Protection Law (PDPL) — Any entity processing personal data of individuals located in Saudi Arabia, regardless of the entity's own location. observed
  15. Probable Saudi Privacy Law — SDAIA is the competent authority for PDPL enforcement, combining data-protection and AI policy functions. observed
  16. Uncertain Chambers and Partners — PDPL — Non-KSA processors handling KSA residents' data, per secondary commentary observed
  17. Probable Bureau of Experts at the Council of Ministers — Personal Data Protection Law (PDPL) — In force since 14 September 2023 observed
  18. Probable Securiti — Saudi Data and Artificial Intelligence Authority (SDAIA) — Continuing competent authority for the PDPL; initial two-year Council of Ministers designation lapsed September 2025 with no transfer to NDMO observed
  19. Probable Saudi Data and Artificial Intelligence Authority (SDAIA) — PDPL Art 2(1)-(2) — PDPL applies to processing of personal data in the Kingdom and to processing of data of Kingdom residents by any party anywhere, excluding purely personal/family use not disclosed to others observed
  20. Probable Morgan Lewis — National Data Governance Platform (NDGP) — Controller must register on the NDGP where it is a public entity, processes sensitive data, or processing personal data is its main activity in the Kingdom observed
  21. Probable Saudi Data and Artificial Intelligence Authority (SDAIA) — National Data Governance Platform (NDGP) registration — No registration fee currently applies observed
  22. Probable Bird & Bird — Proposed Amendments to the Implementing Regulation of the PDPL (2025 consultation round) — SDAIA's third public consultation round on PDPL Implementing Regulation amendments (privacy-policy language, direct marketing, record-keeping, complaint procedures, DPO role, controller registration) opened 27 April 2025 and closed 27 May 2025 via the Istitlaa Platform, followed by a further revised draft put to consultation in 2026. observed
  23. Probable Clyde & Co — SDAIA — Public consultation on draft amendments to PDPL Implementing Regulations, 6 October-5 November 2026, covering localisation, breach-notification thresholds, DPIA, DPO and controller-registration obligations observed
  24. Probable Vigilbase — SDAIA supervises implementation of the PDPL and separately leads national AI governance instruments observed
  25. Probable RecordingLaw — Personal Data Protection Law (Royal Decree M/19, amended M/148) — In force since 14 September 2023; grace period expired 14 September 2024 observed

#

Lawful-basis regime is narrower than GDPR (fewer enumerated grounds; legitimate interest only added by 2023 amendment and excluded for sensitive data), creating residual compliance friction.

Primary frameworkPDPL (as amended) Arts. 5-6 and Implementing Regulation Art. 16
Traffic-light rationale — AmberLawful-basis regime is narrower than GDPR (fewer enumerated grounds; legitimate interest only added by 2023 amendment and excluded for sensitive data), creating residual compliance friction.

Sub-modules (4)

Lawful basesAmber

Consent remains the primary basis; the 2023 amendment added a legitimate-interest ground (not applicable to sensitive data).

Claims (3):

  • The 2023 PDPL amendments permit processing on the basis of legitimate/lawful interest of the controller or another person where it does not prejudice the data subject's rights, but this basis does not apply to sensitive personal data.
  • Legitimate interest (Art.6(4) PDPL) — Legitimate interest is a lawful basis but restricted: unavailable to public entities, unavailable for sensitive data, requires a lawful purpose, a balance test, and a documented assessment
  • Lawful bases (Art.6 PDPL) — Six lawful bases recognised: consent, contractual necessity, legal obligation, vital interests, public task, legitimate interests; consent is the primary/default basis

Special categoriesAmber

Special categories include health, genetic, credit/financial data, and (uniquely versus GDPR) tribal origin, with Articles 26-27 imposing additional restrictive measures for health and credit data.

Claims (4):

  • The PDPL's special-category definitions differ from GDPR notably in referencing tribal origin and credit data as sensitive categories.
  • Implementing Regulation Articles 26-27 impose additional restrictive and specific measures for processing health and credit data, including a need-to-know access approach.
  • Sensitive data (Art.1(11) PDPL) — Sensitive data defined as data revealing racial/ethnic origin, religious/intellectual/political belief, criminal convictions and security data, biometric/genetic data for identification, health data, and data indicating one/both parents unknown
  • Sensitive data processing restrictions (Art.6(4)/IR Art.11) — No sensitive data processed without explicit documented consent (save limited exceptions); legitimate interest cannot be used for sensitive data; sensitive data cannot be used for marketing

Pseudonymisation and anonymisationGreen

SDAIA has issued guidelines assisting entities in determining when personal data should be destroyed or anonymized.

Claims (2):

  • SDAIA's guidance materials include guidelines to assist entities in determining when personal data should be destroyed or anonymized.
  • Anonymisation (Art.1(8) Implementing Regulation) — Anonymisation is the irreversible removal of identifying characteristics; once anonymised, data is outside PDPL scope and data subjects cannot exercise PDPL rights over it
Category narrative 40 words

The PDPL originally made consent the primary lawful basis, with the 2023 amendments introducing a legitimate-interest basis (excluded for sensitive data). Special categories include health, genetic, credit/financial, and tribal-origin data, subject to additional safeguards; SDAIA has also issued anonymization/destruction guidance.

Periodic update · new data 2026-10-25

The draft amendments to the Personal Data Protection Law's Implementing Regulations propose removing the standalone definition of direct marketing currently found in the regulatory text. Commentary describes this as a structural drafting change requiring edits to every affected cross-reference wherever the defined term currently appears, rather than a substantive narrowing of what counts as direct marketing activity. Despite this structural change, the underlying lawful-basis gateway for processing, the Article 11 consent requirement, is reported to persist unchanged, meaning that the core lawful-processing test applicable to marketing and other processing activities does not appear to be weakened by the removal of the standalone definition.

This combination, removing a standalone definition while preserving the underlying consent gateway, suggests a consolidation or simplification exercise in the structure of the regulations rather than a substantive policy shift in what lawful bases are available or required for marketing-related processing. For controllers currently relying on the existing direct-marketing definition to scope their marketing-consent compliance programmes, the practical implication is a need to track how marketing activity is defined and treated once the standalone definition is removed and cross-references are redrafted, to confirm that consent-gateway compliance remains correctly scoped under the revised structure.

Outlook

The practical effect of the direct-marketing definition's removal will depend on how the redrafted cross-references ultimately treat marketing activity within the broader lawful-processing framework once the amendments are finalised following the 5 November 2026 consultation close, as scheduled. Controllers with marketing programmes should watch for the final text to confirm continuity of their consent-based compliance approach.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (11)
  1. Probable OneTrust DataGuidance — The 2023 PDPL amendments permit processing on the basis of legitimate/lawful interest of the controller or another person where it does not prejudice the data subject's rights, but this basis does not apply to sensitive personal data. observed
  2. Probable IAPP — Implementing Regulation Article 28 requires controllers to obtain consent before processing data for promotional/awareness purposes, but includes an indirect exemption where there was a previous interaction between controller and data subject; Article 29 imposes consent for direct-marketing communications without that exemption. observed
  3. Probable OneTrust DataGuidance — The PDPL's special-category definitions differ from GDPR notably in referencing tribal origin and credit data as sensitive categories. observed
  4. Probable IAPP — Implementing Regulation Articles 26-27 impose additional restrictive and specific measures for processing health and credit data, including a need-to-know access approach. observed
  5. Probable IAPP — SDAIA's guidance materials include guidelines to assist entities in determining when personal data should be destroyed or anonymized. observed
  6. Probable GovernanceDocs — Legitimate interest (Art.6(4) PDPL) — Legitimate interest is a lawful basis but restricted: unavailable to public entities, unavailable for sensitive data, requires a lawful purpose, a balance test, and a documented assessment observed
  7. Probable Saudi Data and Artificial Intelligence Authority (SDAIA) — Consent (Art.11 Implementing Regulation) — Valid consent must be freely given, for a specific purpose, recorded with time/method of collection, kept separate per purpose; explicit consent required in defined cases including sensitive data; withdrawal must be as easy as giving consent observed
  8. Probable DLA Piper — Lawful bases (Art.6 PDPL) — Six lawful bases recognised: consent, contractual necessity, legal obligation, vital interests, public task, legitimate interests; consent is the primary/default basis observed
  9. Probable Saudi Data and Artificial Intelligence Authority (SDAIA) — Sensitive data (Art.1(11) PDPL) — Sensitive data defined as data revealing racial/ethnic origin, religious/intellectual/political belief, criminal convictions and security data, biometric/genetic data for identification, health data, and data indicating one/both parents unknown observed
  10. Probable Chambers and Partners — Sensitive data processing restrictions (Art.6(4)/IR Art.11) — No sensitive data processed without explicit documented consent (save limited exceptions); legitimate interest cannot be used for sensitive data; sensitive data cannot be used for marketing observed
  11. Probable Saudi Data and Artificial Intelligence Authority (SDAIA) — Anonymisation (Art.1(8) Implementing Regulation) — Anonymisation is the irreversible removal of identifying characteristics; once anonymised, data is outside PDPL scope and data subjects cannot exercise PDPL rights over it observed

#

Core rights exist and are binding, but response-window specificity and portability provisions are thinner than GDPR, creating operational ambiguity flagged by practitioners.

Primary frameworkPDPL (as amended), Implementing Regulation Arts. on data subject requests
Traffic-light rationale — AmberCore rights exist and are binding, but response-window specificity and portability provisions are thinner than GDPR, creating operational ambiguity flagged by practitioners.

Sub-modules (5)

Access rightAmber

Data subjects may submit requests, including verbal requests under an authentication mandate in the Implementing Regulation.

Claims (2):

  • The Implementing Regulation permits verbal data subject requests under an authentication mandate, which is regarded as an operational burden on controllers.
  • Right to access and portability (Art.4(2),(3) PDPL) — Data subjects have a right to access their personal data and a right to obtain it in a readable, clear format

Rectification and erasureAmber

Controllers may reject excessive/repetitive DSRs with justification but cannot charge fees for them.

Claims (2):

  • There is no allowance under the Implementing Regulation for data controllers to charge data subjects for DSRs deemed excessive or repetitive, though controllers can reject such requests with justification.
  • Right to erasure (Art.4 PDPL) — Data subjects may request destruction of their personal data once no longer needed, without prejudice to Art.18 retention duties

Restriction and objectionAmber

A right to object to profiling/direct marketing is provided via Implementing Regulation Art. 28, paralleling GDPR Art. 21.

Claims (1):

  • Implementing Regulation Article 28 allows data controllers to rely on legitimate interest, subject to the data subject's right to object, for profiling and direct-marketing purposes.

Data portabilityRed

No explicit data-portability right was identified in the PDPL or Implementing Regulation text reviewed.

Deadlines and response windowsRed

No fixed statutory response-window (e.g., a GDPR-style 30-day deadline) for DSR responses was located in the sources reviewed; the Implementing Regulation instead emphasizes justification for rejection rather than timing.

Claims (1):

  • Data-subject rights request (Art.3(1)(a) Implementing Regulation) — Controllers must act on a rights request within 30 days, extendable once by up to 30 further days with notice of reasons
Category narrative 44 words

The PDPL provides a GDPR-style suite of data subject rights (access, correction, deletion, restriction, objection), but the Implementing Regulation gives less granular guidance on scope and timelines than GDPR; no explicit data-portability provision or fixed statutory response deadline was identified in the materials reviewed.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (6)
  1. Probable IAPP — The Implementing Regulation permits verbal data subject requests under an authentication mandate, which is regarded as an operational burden on controllers. observed
  2. Probable IAPP — There is no allowance under the Implementing Regulation for data controllers to charge data subjects for DSRs deemed excessive or repetitive, though controllers can reject such requests with justification. observed
  3. Probable IAPP — Implementing Regulation Article 28 allows data controllers to rely on legitimate interest, subject to the data subject's right to object, for profiling and direct-marketing purposes. observed
  4. Probable DataSec — Data-subject rights request (Art.3(1)(a) Implementing Regulation) — Controllers must act on a rights request within 30 days, extendable once by up to 30 further days with notice of reasons observed
  5. Probable Saudi Data and Artificial Intelligence Authority (SDAIA) — Right to erasure (Art.4 PDPL) — Data subjects may request destruction of their personal data once no longer needed, without prejudice to Art.18 retention duties observed
  6. Probable Saudi Data and Artificial Intelligence Authority (SDAIA) — Right to access and portability (Art.4(2),(3) PDPL) — Data subjects have a right to access their personal data and a right to obtain it in a readable, clear format observed

#

Core accountability infrastructure (DPIA, DPO, ROPA, breach notification) is binding and operative, but the immediate data-subject breach notification standard (rather than a risk-based threshold) is flagged by commentators as operationally stringent and under-specified.

Primary frameworkPDPL (as amended) Arts. 20-23, Implementing Regulation (DPIA, breach, security provisions)
Traffic-light rationale — AmberCore accountability infrastructure (DPIA, DPO, ROPA, breach notification) is binding and operative, but the immediate data-subject breach notification standard (rather than a risk-based threshold) is flagged by commentators as operationally stringent and under-specified.

Sub-modules (7)

Accountability & DPIAGreen

DPIAs are mandated in nine defined processing scenarios, paralleling GDPR Art. 35.

Claims (3):

  • The Implementing Regulation mandates data controllers conduct documented privacy impact assessments in nine different scenarios of personal data processing, including anonymization, sensitive personal data, and use of new technologies.
  • Implementing Regulation to the PDPL Art 25 — Controller must carry out and document a written DPIA before processing relying on new technologies or automated decisions
  • Data Protection Impact Assessment (Art.25 Implementing Regulation) — A DPIA is required where processing meets one of the Art.25 triggers, including systematic/extensive evaluation and large-scale high-risk processing; a single assessment may cover similar operations

DPO requirementsAmber

SDAIA's DPO Rules require appointment of a data protection officer under specified conditions, including for public entities.

Claims (5):

  • SDAIA's Rules on Appointing a Personal Data Protection Officer define the DPO role and clarify that controllers must appoint a DPO where, among other conditions, the controller is a public entity.
  • DPO appointment trigger (Art.5 DPO Rules) — A DPO must be appointed where the controller is a public entity processing at scale, performs large-scale monitoring as a core activity, processes sensitive data at scale as a core activity, or is a marketing company processing data for marketing
  • DPO independence and registration (Art.4(1), Art.6(5) DPO Rules) — DPO must have appropriate qualifications/experience; appointment must be documented; DPO tasks must not conflict with other duties or affect independence; appointment must be registered promptly via NDGP
  • PDPL Implementing Regulation (draft) — Draft amendments revise DPO-appointment circumstances and introduce mandatory National Register of Controllers registration for public entities, core data-processing activities, sensitive-data processing, or cross-border transfer/disclosure.
  • Implementing Regulation of the Personal Data Protection Law — DPO rules — SDAIA requires certain data controllers meeting SDAIA-defined criteria to appoint one or more data protection officers.

Ropa requirementsAmber

Controllers must maintain and register a Record of Processing Activities with SDAIA; the PDPL does not explicitly extend this obligation to processors as GDPR does.

Claims (4):

  • The PDPL requires controllers, but does not explicitly require processors, to maintain data processing records, unlike the GDPR which imposes this duty on both.
  • PDPL Implementing Regulations — Controllers must keep a Record of Processing Activities during the relevant processing period and for a further five years after it ends.
  • PDPL controllers — Records of processing activities meeting eight minimum fields, in writing, available to SDAIA on request, retained for the processing period plus five years
  • Records of processing activities (Art.31/Art.33 Implementing Regulation) — Controlling entity must maintain a record of processing activities and make it available to the Competent Authority on request

Joint controller arrangementsAmber

No dedicated joint-controller regime distinct from general controller/processor duties was identified; controllers assume sole accountability for processor compliance.

Claims (2):

  • Data controllers are required to periodically conduct compliance assessments of selected data processors, assuming sole accountability for processor processing activities before SDAIA and data subjects.
  • Processor obligations (Art.17 Implementing Regulation) — Controllers must select processors with sufficient guarantees and conclude agreements covering breach notification; a processor acting outside instructions is treated as a controller and directly liable

Security measuresGreen

Article 23 requires controllers to implement necessary security/technical measures, referencing National Cybersecurity Authority (NCA) standards where applicable.

Claims (1):

  • Article 23 of the Implementing Regulation requires data controllers to implement necessary security and technical measures, referencing National Cybersecurity Authority standards where the NCA regulates the controller, or best international cybersecurity standards otherwise.

Breach notificationAmber

Breach notification requires reporting to SDAIA within 72 hours and immediate notification to affected data subjects.

Claims (12):

  • The Implementing Regulation requires organizations to notify SDAIA of a data breach within 72 hours and to notify affected data subjects immediately.
  • PDPL Implementing Regulations Article 20 — A personal-data breach posing risk to a data subject must be reported to SDAIA within 72 hours under Implementing Regulations Article 20, per secondary-source commentary not independently verified against primary text this cycle.
  • Saudi data controllers — 72 hours of becoming aware of a breach, via the National Data Governance Portal, where notification to SDAIA is required.
  • PDPL controllers — 72 hours to SDAIA
  • Implementing Regulations Art 24 requires controllers to notify SDAIA within 72 hours of becoming aware of a breach that may harm personal data or data subjects' rights, with no materiality self-assessment permitted.
  • Implementing Regulation to the PDPL — Controller must notify SDAIA via the National Data Governance Portal within 72 hours of becoming aware of a personal data breach
  • Breach notification to SDAIA (Art.24(1) Implementing Regulation) — Controllers must notify SDAIA within 72 hours of becoming aware of a qualifying personal-data breach via the National Data Governance Platform, with five specified content items
  • Breach notification to individuals (Art.24(3) Implementing Regulation) — Where a breach may harm data subjects or conflict with their rights, affected individuals must be notified without undue delay, in clear simple language, with four specified content items
  • PDPL Implementing Regulation (draft) — Draft amendment to Article 24 would remove the current harm-assessment threshold gating notification to SDAIA, broadening the breach-notification duty.
  • Implementing Regulation of the Personal Data Protection Law, Art. 24 — A data controller must notify SDAIA through the National Data Governance Portal within 72 hours of becoming aware of a personal-data breach that could harm the data or individuals concerned, and must notify affected data subjects without undue delay where applicable.
  • PDPL Implementing Regulation, Article 24 — Controllers must notify SDAIA within 72 hours of becoming aware of a breach that could harm the data or data subjects or conflict with their rights/interests
  • PDPL Implementing Regulation, Article 24 (draft amendment) — Draft amendment would delete the 'Personal Data Breach' harm threshold and require notification of any breach, damage or unauthorized access

Retention and disposalAmber

SDAIA guidance addresses when personal data should be destroyed or anonymized, though no fixed statutory retention period was located.

Claims (1):

  • SDAIA has published guidelines to assist entities in determining when personal data should be destroyed or anonymized.
Category narrative 41 words

Controllers face DPIA obligations across nine defined scenarios, DPO appointment rules for public entities and certain processing profiles, ROPA maintenance, periodic processor-compliance assessments, NCA-referenced security measures, and a dual-track breach notification regime (72 hours to SDAIA; immediate to affected data subjects).

Periodic update · new data 2026-11-15

Under Article 24 of the Implementing Regulation currently in force, a controller must notify SDAIA within 72 hours of becoming aware of a breach that could harm the personal data or could conflict with the data subject's rights or interests. A draft amendment to Article 24, out for comment until 5 November 2026, would delete the existing harm-assessment threshold entirely, requiring notification of any breach, damage or unauthorized access regardless of whether harm to the data subject can be shown. The same consultation also proposes new controller-registration obligations and changes to data protection impact assessment and data protection officer requirements.

None of these proposed changes to controller and processor duties is in force; the current 72-hour harm-based notification duty remains the operative standard pending any adoption of the amendments.

Outlook

A broadened, harm-agnostic breach-notification trigger would represent a materially lower threshold for controllers operating in Saudi Arabia than the standard currently in force. Adoption depends on the outcome of the consultation that closed on 5 November 2026 and on subsequent Gazette publication.

2 earlier distinct updates
Periodic update · new data 2026-11-04

Two controller-facing obligations are under active revision through the same Implementing Regulation consultation. The first concerns breach notification: the current regime gates the duty to notify the regulator of a personal-data breach behind a harm-assessment threshold, and the draft amendment would remove that threshold, broadening the circumstances in which notification to the authority becomes mandatory. The underlying harm-assessment text that the draft would replace was not itself retrieved verbatim for this review, so the precise before-and-after wording cannot yet be set out side by side; the direction of the change, however, is clear from the draft and from legal commentary on it.

The second concerns organisational duties: the draft revises the circumstances in which a controller must appoint a data protection officer, and introduces a mandatory National Register of Controllers obligation applying to public entities, to organisations whose core activity consists of data processing, to processing of sensitive data, and to any processing involving cross-border transfer or disclosure. Both elements remain proposals; neither is in force.

Outlook

If adopted as drafted, these changes would require affected controllers to review both their breach-response procedures and their registration and DPO-appointment status ahead of any effective date the authority eventually sets. The consultation closes 5 November 2026, and no adoption decision has been recorded as at the date of this note.

Periodic update · new data 2026-10-25

The Implementing Regulations' Article 24 currently requires controllers to notify the Saudi Data and Artificial Intelligence Authority within 72 hours of becoming aware of a breach that may harm personal data or data subjects' rights, with no materiality self-assessment permitted under the current, in-force text. The draft amendments under consultation would preserve this no-threshold structure while being part of a broader package that also touches data protection officer administrative requirements and records-of-processing-activities obligations.

On the administrative side, commentary describes a proposed requirement for organisations to input their data protection officer's contact details into the National Data Governance Platform, centralising what may currently be a more fragmented administrative process. Separately, simplified records-of-processing-activities requirements are proposed, clarifying that records must be retained for a defined period, which would give controllers clearer guidance on retention duration than may currently exist. Taken together, these two administrative changes point toward streamlining certain compliance-process burdens even as the substantive breach-notification duty remains strict and threshold-free.

The absence of a materiality threshold for breach notification is a significant operational point for controllers and processors: any breach that may cause harm to personal data or to data subjects' rights triggers the 72-hour clock, regardless of the controller's own assessment of the breach's severity or likely impact. This places a premium on robust internal breach-detection and escalation processes capable of meeting a 72-hour notification window without the benefit of a materiality filter to exclude lower-risk incidents.

Outlook

Controllers and processors operating in Saudi Arabia should treat the no-threshold 72-hour breach-notification duty as a standing operational requirement that is not expected to loosen under the draft amendments. The proposed centralisation of data protection officer contact details into the National Data Governance Platform and the clarified records-of-processing-activities retention-period guidance are the two administrative changes to track for implementation once the amendments are finalised following the 5 November 2026 consultation close, as scheduled.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (28)
  1. Probable IAPP — The Implementing Regulation mandates data controllers conduct documented privacy impact assessments in nine different scenarios of personal data processing, including anonymization, sensitive personal data, and use of new technologies. observed
  2. Probable OneTrust DataGuidance — SDAIA's Rules on Appointing a Personal Data Protection Officer define the DPO role and clarify that controllers must appoint a DPO where, among other conditions, the controller is a public entity. observed
  3. Probable OneTrust DataGuidance — The PDPL requires controllers, but does not explicitly require processors, to maintain data processing records, unlike the GDPR which imposes this duty on both. observed
  4. Probable IAPP — Data controllers are required to periodically conduct compliance assessments of selected data processors, assuming sole accountability for processor processing activities before SDAIA and data subjects. observed
  5. Probable IAPP — Article 23 of the Implementing Regulation requires data controllers to implement necessary security and technical measures, referencing National Cybersecurity Authority standards where the NCA regulates the controller, or best international cybersecurity standards otherwise. observed
  6. Probable IAPP — The Implementing Regulation requires organizations to notify SDAIA of a data breach within 72 hours and to notify affected data subjects immediately. observed
  7. Probable IAPP — SDAIA has published guidelines to assist entities in determining when personal data should be destroyed or anonymized. observed
  8. Probable Clyde & Co — PDPL Implementing Regulations — Controllers must keep a Record of Processing Activities during the relevant processing period and for a further five years after it ends. observed
  9. Uncertain SGC Consulting — PDPL Implementing Regulations Article 20 — A personal-data breach posing risk to a data subject must be reported to SDAIA within 72 hours under Implementing Regulations Article 20, per secondary-source commentary not independently verified against primary text this cycle. observed
  10. Probable https://www.dlapiperdataprotection.com/?c=SA — Saudi data controllers — 72 hours of becoming aware of a breach, via the National Data Governance Portal, where notification to SDAIA is required.
  11. Uncertain GovernanceDocs — PDPL controllers — Records of processing activities meeting eight minimum fields, in writing, available to SDAIA on request, retained for the processing period plus five years observed
  12. Uncertain RecordingLaw — PDPL controllers — 72 hours to SDAIA observed
  13. Probable RecordingLaw — Implementing Regulations Art 24 requires controllers to notify SDAIA within 72 hours of becoming aware of a breach that may harm personal data or data subjects' rights, with no materiality self-assessment permitted. observed
  14. Probable https://sdaia.gov.sa/en/SDAIA/about/Documents/ImplementingRegulation.pdf — Implementing Regulation to the PDPL — Controller must notify SDAIA via the National Data Governance Portal within 72 hours of becoming aware of a personal data breach
  15. Probable Arelion — Implementing Regulation to the PDPL Art 25 — Controller must carry out and document a written DPIA before processing relying on new technologies or automated decisions observed
  16. Probable GovernanceDocs — Breach notification to SDAIA (Art.24(1) Implementing Regulation) — Controllers must notify SDAIA within 72 hours of becoming aware of a qualifying personal-data breach via the National Data Governance Platform, with five specified content items observed
  17. Probable Securiti — Breach notification to individuals (Art.24(3) Implementing Regulation) — Where a breach may harm data subjects or conflict with their rights, affected individuals must be notified without undue delay, in clear simple language, with four specified content items observed
  18. Probable GovernanceDocs — Data Protection Impact Assessment (Art.25 Implementing Regulation) — A DPIA is required where processing meets one of the Art.25 triggers, including systematic/extensive evaluation and large-scale high-risk processing; a single assessment may cover similar operations observed
  19. Probable Saudi Data and Artificial Intelligence Authority (SDAIA) — DPO appointment trigger (Art.5 DPO Rules) — A DPO must be appointed where the controller is a public entity processing at scale, performs large-scale monitoring as a core activity, processes sensitive data at scale as a core activity, or is a marketing company processing data for marketing observed
  20. Probable Saudi Data and Artificial Intelligence Authority (SDAIA) — DPO independence and registration (Art.4(1), Art.6(5) DPO Rules) — DPO must have appropriate qualifications/experience; appointment must be documented; DPO tasks must not conflict with other duties or affect independence; appointment must be registered promptly via NDGP observed
  21. Probable Saudi Data and Artificial Intelligence Authority (SDAIA) — Processor obligations (Art.17 Implementing Regulation) — Controllers must select processors with sufficient guarantees and conclude agreements covering breach notification; a processor acting outside instructions is treated as a controller and directly liable observed
  22. Probable OneTrust DataGuidance — Records of processing activities (Art.31/Art.33 Implementing Regulation) — Controlling entity must maintain a record of processing activities and make it available to the Competent Authority on request observed
  23. Probable Reed Smith — PDPL Implementing Regulation (draft) — Draft amendment to Article 24 would remove the current harm-assessment threshold gating notification to SDAIA, broadening the breach-notification duty. observed
  24. Probable Reed Smith — PDPL Implementing Regulation (draft) — Draft amendments revise DPO-appointment circumstances and introduce mandatory National Register of Controllers registration for public entities, core data-processing activities, sensitive-data processing, or cross-border transfer/disclosure. observed
  25. Probable DLA Piper — Implementing Regulation of the Personal Data Protection Law, Art. 24 — A data controller must notify SDAIA through the National Data Governance Portal within 72 hours of becoming aware of a personal-data breach that could harm the data or individuals concerned, and must notify affected data subjects without undue delay where applicable. observed
  26. Probable DLA Piper — Implementing Regulation of the Personal Data Protection Law — DPO rules — SDAIA requires certain data controllers meeting SDAIA-defined criteria to appoint one or more data protection officers. observed
  27. Probable Vigilbase — PDPL Implementing Regulation, Article 24 — Controllers must notify SDAIA within 72 hours of becoming aware of a breach that could harm the data or data subjects or conflict with their rights/interests observed
  28. Probable National Law Review — PDPL Implementing Regulation, Article 24 (draft amendment) — Draft amendment would delete the 'Personal Data Breach' harm threshold and require notification of any breach, damage or unauthorized access observed

#

Transfer mechanisms are now GDPR-aligned in structure, but no specific adequacy decisions (received or granted) were identified in the reviewed sources, leaving practical cross-border flows dependent on SCCs/BCRs and TIAs.

Primary frameworkRegulations on Personal Data Transfers 2023 (Cross-Border Data Transfer Regulation), PDPL Art. 28 (as amended)
Traffic-light rationale — AmberTransfer mechanisms are now GDPR-aligned in structure, but no specific adequacy decisions (received or granted) were identified in the reviewed sources, leaving practical cross-border flows dependent on SCCs/BCRs and TIAs.

Sub-modules (6)

Transfer mechanismsGreen

Transfers are permitted on three grounds: adequacy decision, appropriate safeguards, or derogations, per the Cross-Border Data Transfer Regulation.

Claims (5):

  • The Cross-Border Data Transfer Regulation allows transfer of personal data on three grounds, organized in a manner broadly in line with the GDPR.
  • SDAIA Risk Assessment Guideline — In February 2025 SDAIA introduced a Risk Assessment Guideline providing a structured, non-binding methodology for assessing cross-border transfer risk under the PDPL, its Implementing Regulations, and the Transfer Regulations.
  • Definition of Transfer of Personal Data (Art.1(2) Transfer Regulation) — Transfer of personal data is defined as transfer outside the Kingdom for processing purposes; disclosure outside the Kingdom is treated/regulated separately
  • Suspension of cross-border transfer (Art.7 Transfer Regulation) — Where foreign regulatory conflict, national-security/vital-interest risk, or a high-risk assessment outcome arises, the controller must immediately stop the transfer and re-assess risks before resuming
  • Transfer exemption cases (Art.4(2) Transfer Regulation) — Where no adequacy list applies, transfer may proceed under narrow Art.4(2) exemption cases (e.g. international-agreement compliance, vital-interest/public-health necessity), each tied to its own safeguard

Adequacy receivedRed

No inbound adequacy decisions (i.e., other regimes recognizing Saudi Arabia as adequate) were identified in the sources reviewed.

Claims (1):

  • SDAIA adequacy/white-list determination — SDAIA must publish an adequacy list of countries/organisations providing adequate protection, reviewed periodically; no adequacy list has yet been published

Adequacy grantedAmber

SDAIA/the competent authority is empowered to issue adequacy decisions for destination countries, sectors, and international organizations, but no published list of adequate jurisdictions was located.

Claims (1):

  • Adequacy decisions for destination countries, other sectors, and international organizations are to be determined and issued by the competent authority, with defined assessment criteria and revision frequency.

SCCs and BCRsGreen

SDAIA has issued Standard Contractual Clauses (SCCs) and Binding Common Rules (BCRs) guidance for data transfers.

Claims (2):

  • SDAIA's Standard Contractual Clauses (SCCs) and Binding Common Rules (BCRs) guide data transfers, requiring adherence to the PDPL and Implementing Regulations.
  • Appropriate-safeguards mechanisms (Art.5 Transfer Regulation) — Absent an adequacy finding, controllers must rely on SDAIA's Standard Contractual Clauses (issued September 2024), binding common rules for a corporate group, or SDAIA-licensed accreditation/certification

Transfer impact assessmentGreen

A Transfer Impact Assessment is mandated for transfers to countries lacking an adequacy decision, incorporating post-Schrems II style risk assessment.

Claims (2):

  • The transfer regulation mandates a Transfer Impact Assessment to transfer data to countries without adequacy decisions, incorporating mechanisms introduced after the Schrems II decision.
  • Transfer risk assessment (Art.8 Transfer Regulation) — A documented transfer risk assessment is mandatory when relying on Art.5 or Art.6 mechanisms, and whenever continuous/large-scale sensitive-data transfer occurs regardless of mechanism

Data localisationAmber

The PDPL's original default was a prohibition on transfers outside Saudi Arabia; the 2023 amendment rewrote the transfer article to be permissive, reducing localisation stringency but retaining stop/prohibition triggers including national security.

Claims (8):

  • The PDPL as originally published adopted a restrictive starting point, prohibiting transfers of personal data outside Saudi Arabia except where the executive regulations provided otherwise.
  • A transfer must be stopped or prohibited if it impacts national security or the Kingdom's interests, among other listed scenarios such as high risk shown by a TIA.
  • PDPL Implementing Regulation (draft) — Draft Article 23(2) introduces an express requirement for controllers to store personal data within the Kingdom of Saudi Arabia, while permitting transfer or disclosure outside the Kingdom in accordance with the PDPL and Implementing Regulation.
  • Draft amendments to the Implementing Regulation of the PDPL — SDAIA consultation open 6 October-5 November 2026 proposing a new Art 23(2) data-localisation requirement, broadened Art 25 DPIA triggers, removal of the 'potential harm' threshold gating the 72-hour breach notice, and a registration trigger for controllers transferring data abroad
  • SDAIA draft PDPL amendments — Data localisation as the first listed Key Change, open for consultation until 5 November 2026; substantive rule text not retrieved
  • SDAIA — Draft Art 23(2) would require controllers to store personal data within the Kingdom by default, while permitting cross-border transfer under the Law and its Implementing Regulations; open for consultation to 5 November 2026.
  • Data localisation — PDPL and Implementing Regulation impose no general requirement that personal data be stored or processed inside Saudi Arabia; sector rules (NCA, SAMA) may separately require local hosting for specific regulated entities
  • PDPL Implementing Regulation (draft amendment) — Draft amendments would introduce express data localisation requirements, a change from the current transfer-safeguards approach
Category narrative 55 words

The PDPL's original restrictive, prohibition-first stance on cross-border transfers was substantially liberalized in the 2023 amendments and the September 2023 Cross-Border Data Transfer Regulation, which permits transfer on three grounds (adequacy decision, appropriate safeguards including SCCs/BCRs, or derogations), and mandates a Transfer Impact Assessment (TIA) for transfers to non-adequate jurisdictions, modeled on post-Schrems II practice.

Periodic update · new data 2026-11-15

The current cross-border transfer regime under the Personal Data Protection Law and its Implementing Regulation operates on a safeguards and risk-assessment basis rather than a blanket localisation requirement. Draft amendments out for consultation until 5 November 2026 would introduce an express data-localisation requirement, departing from that safeguards-based approach. This proposal is understood on a statutory-interface reading of the draft text rather than on a retrieved primary Gazette publication, and has not been adopted as.

Outlook

If adopted, a general localisation requirement would be a structural shift for organisations that currently rely on transfer safeguards rather than in-Kingdom storage. The practical scope and any sectoral carve-outs had not been confirmed as, pending the consultation outcome and any subsequent gazettal.

3 earlier distinct updates
Periodic update · new data 2026-11-04

The draft Implementing Regulation amendments under consultation would introduce, for the first time, an express requirement that personal data be stored within the Kingdom of Saudi Arabia. The same draft provision permits transfer or disclosure of data outside the Kingdom where the conditions set out in the Law and the Regulation are satisfied, so the proposal is framed as a localisation default paired with a conditional export permission rather than an outright prohibition on cross-border movement. This is a notable departure from the position reported previously, under which the Law did not require personal data to be stored or processed inside the Kingdom. The provision remains in draft; the consultation on it closes 5 November 2026 and the authority has not confirmed whether or in what form it will be adopted.

Outlook

Adoption of the localisation requirement, even subject to a transfer exception, would be the most significant change to the Kingdom's cross-border data regime since the Implementing Regulation first took effect. Organisations relying on offshore storage or processing arrangements involving data relating to the Kingdom have reason to watch the consultation outcome closely; the effective date, if the provision is adopted, is reported by secondary sources as 60 days after Gazette publication, though the regulator has not confirmed this timeline itself.

Periodic update · new data 2026-10-25

The most significant proposed change in Saudi Arabia's current data protection reform package is a new draft Article 23(2), which would introduce a default requirement for controllers to store personal data within the Kingdom. Importantly, this default localisation requirement is paired with a continued permission for cross-border transfer or disclosure where the Personal Data Protection Law and its Implementing Regulations so provide, meaning the proposal does not amount to an absolute prohibition on cross-border data flows but rather shifts the default starting position from transfer-permitted to localisation-by-default, with transfer available as a provided-for exception rather than a general rule.

This development sits within a jurisdiction whose data protection framework is not part of the European Union's regulatory architecture, and whose cross-border transfer rules are instead a matter of the Kingdom's own Personal Data Protection Law and its separate Transfer Regulation. The direction of this proposed change, toward a default localisation posture, is consistent with a broader regional and global pattern of jurisdictions tightening default expectations around where personal data is stored, even as specific mechanisms for permitted cross-border transfer are preserved alongside that default.

For controllers and processors currently relying on cross-border data architecture, whether for group-level data processing, cloud infrastructure located outside the Kingdom, or cross-border service delivery, the practical significance of draft Article 23(2) is that any such architecture may need to be reassessed against a default localisation requirement once the amendments are finalised, with continued reliance on cross-border transfer dependent on qualifying under the Law and its Implementing Regulations. The consultation on this and the other draft amendments closes 5 November 2026, with the amendments, if approved, expected to take effect 60 days following publication in the official Gazette.

Outlook

Organisations with cross-border data architecture touching Saudi Arabia should treat the proposed default localisation requirement under draft Article 23(2) as the single most consequential item in this consultation cycle to monitor through to finalisation. Confirmation of which specific transfer mechanisms will qualify as provided-for exceptions under the finalised Law and Implementing Regulations will be the key detail to watch once the draft text moves toward adoption following the 5 November 2026 consultation close, as scheduled.

Periodic update · new data 2026-10-18

SDAIA's draft amendments to the PDPL Implementing Regulations, published for consultation on 6 October 2026, list data localisation as the first Key Change among the proposed amendments, according to law-firm commentary on the consultation notice. The substantive operative text of the data-localisation provision, including its scope, the categories of data or processing activity it would apply to, and any thresholds or exemptions, has not yet been retrieved; the finding currently rests on the fact that data localisation appears first in SDAIA's own listing of Key Changes, as relayed by secondary commentary, rather than on the provision's actual drafted language.

This is nonetheless a significant signal in its own right. The prominence given to data localisation within SDAIA's consultation framing suggests that cross-border data transfer arrangements, currently governed by whatever baseline cross-border transfer mechanism exists under the PDPL's current Implementing Regulations, may be materially tightened once the amendments are finalised. Entities that currently process Saudi Arabia residents' personal data outside the Kingdom, whether through cloud infrastructure, group-wide data processing arrangements, or outsourced processing relationships, would be the natural constituency affected by any data-localisation requirement, though until the operative text is available, the precise compliance burden cannot be assessed with confidence.

The consultation period runs until 5 November 2026. If the amendments, including the data-localisation provision, are approved following that consultation, they would take effect sixty days after publication in the official Gazette, which would place a plausible effective date in the first quarter of 2027. This timeline gives affected entities a window, albeit currently an uncertain one given the unresolved substantive scope, to begin assessing their cross-border data architecture ahead of a possible early-2027 effective date.

No other cross-border or adequacy-related development for Saudi Arabia was evidenced this cycle. The data-localisation Key Change stands as the sole, though materially significant, finding in this module, and its ultimate impact will depend heavily on the operative text that has not yet been published or retrieved.

Outlook

The most consequential open question for this module is the substantive content of the data-localisation provision itself, which is expected to become clearer either during the consultation period, which closes 5 November 2026, or upon publication of the finalised amendments in the Gazette. Entities with cross-border data architecture touching Saudi Arabia residents' personal data should monitor for the release of the operative text, which will determine the actual scope and compliance implications of the data-localisation Key Change. Until that text is available, any assessment of impact remains necessarily provisional.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (19)
  1. Probable IAPP — The Cross-Border Data Transfer Regulation allows transfer of personal data on three grounds, organized in a manner broadly in line with the GDPR. observed
  2. Probable IAPP — Adequacy decisions for destination countries, other sectors, and international organizations are to be determined and issued by the competent authority, with defined assessment criteria and revision frequency. observed
  3. Probable OneTrust DataGuidance — SDAIA's Standard Contractual Clauses (SCCs) and Binding Common Rules (BCRs) guide data transfers, requiring adherence to the PDPL and Implementing Regulations. observed
  4. Probable IAPP — The transfer regulation mandates a Transfer Impact Assessment to transfer data to countries without adequacy decisions, incorporating mechanisms introduced after the Schrems II decision. observed
  5. Probable OneTrust DataGuidance — The PDPL as originally published adopted a restrictive starting point, prohibiting transfers of personal data outside Saudi Arabia except where the executive regulations provided otherwise. observed
  6. Probable IAPP — A transfer must be stopped or prohibited if it impacts national security or the Kingdom's interests, among other listed scenarios such as high risk shown by a TIA. observed
  7. Probable Clyde & Co — PDPL Implementing Regulation (draft) — Draft Article 23(2) introduces an express requirement for controllers to store personal data within the Kingdom of Saudi Arabia, while permitting transfer or disclosure outside the Kingdom in accordance with the PDPL and Implementing Regulation. observed
  8. Probable https://www.clydeco.com/en/insights/2026/10/sdaia-publishes-draft-amendments-to-the-pdpl — Draft amendments to the Implementing Regulation of the PDPL — SDAIA consultation open 6 October-5 November 2026 proposing a new Art 23(2) data-localisation requirement, broadened Art 25 DPIA triggers, removal of the 'potential harm' threshold gating the 72-hour breach notice, and a registration trigger for controllers transferring data abroad
  9. Probable https://www.reedsmith.com/our-insights/blogs/viewpoints/102o5at/sdaia-consults-on-extensive-amendments-to-the-saudi-pdpl-implementing-regulation/ — SDAIA draft PDPL amendments — Data localisation as the first listed Key Change, open for consultation until 5 November 2026; substantive rule text not retrieved
  10. Probable Clyde & Co — SDAIA Risk Assessment Guideline — In February 2025 SDAIA introduced a Risk Assessment Guideline providing a structured, non-binding methodology for assessing cross-border transfer risk under the PDPL, its Implementing Regulations, and the Transfer Regulations. observed
  11. Probable https://www.reedsmith.com/our-insights/blogs/viewpoints/102o5at/sdaia-consults-on-extensive-amendments-to-the-saudi-pdpl-implementing-regulation/ — SDAIA — Draft Art 23(2) would require controllers to store personal data within the Kingdom by default, while permitting cross-border transfer under the Law and its Implementing Regulations; open for consultation to 5 November 2026.
  12. Probable Global Privacy Blog — SDAIA adequacy/white-list determination — SDAIA must publish an adequacy list of countries/organisations providing adequate protection, reviewed periodically; no adequacy list has yet been published observed
  13. Probable Saudi Data and Artificial Intelligence Authority (SDAIA) — Definition of Transfer of Personal Data (Art.1(2) Transfer Regulation) — Transfer of personal data is defined as transfer outside the Kingdom for processing purposes; disclosure outside the Kingdom is treated/regulated separately observed
  14. Probable Saudi Data and Artificial Intelligence Authority (SDAIA) — Suspension of cross-border transfer (Art.7 Transfer Regulation) — Where foreign regulatory conflict, national-security/vital-interest risk, or a high-risk assessment outcome arises, the controller must immediately stop the transfer and re-assess risks before resuming observed
  15. Probable RecordingLaw — Appropriate-safeguards mechanisms (Art.5 Transfer Regulation) — Absent an adequacy finding, controllers must rely on SDAIA's Standard Contractual Clauses (issued September 2024), binding common rules for a corporate group, or SDAIA-licensed accreditation/certification observed
  16. Probable Arelion — Transfer exemption cases (Art.4(2) Transfer Regulation) — Where no adequacy list applies, transfer may proceed under narrow Art.4(2) exemption cases (e.g. international-agreement compliance, vital-interest/public-health necessity), each tied to its own safeguard observed
  17. Probable RecordingLaw — Transfer risk assessment (Art.8 Transfer Regulation) — A documented transfer risk assessment is mandatory when relying on Art.5 or Art.6 mechanisms, and whenever continuous/large-scale sensitive-data transfer occurs regardless of mechanism observed
  18. Probable RecordingLaw — Data localisation — PDPL and Implementing Regulation impose no general requirement that personal data be stored or processed inside Saudi Arabia; sector rules (NCA, SAMA) may separately require local hosting for specific regulated entities observed
  19. Probable Clyde & Co — PDPL Implementing Regulation (draft amendment) — Draft amendments would introduce express data localisation requirements, a change from the current transfer-safeguards approach observed

#

Financial and health/credit sector overlays are well-documented and binding; employment, education, and insurance sector-specific DP rules were not located and are flagged as gaps.

Primary frameworkPDPL Implementing Regulation Arts. 26-27; SAMA IT Governance/Cybersecurity Framework; NCA Essential Cybersecurity Controls
Supervisory authoritySaudi Central Bank (SAMA)
Traffic-light rationale — AmberFinancial and health/credit sector overlays are well-documented and binding; employment, education, and insurance sector-specific DP rules were not located and are flagged as gaps.

Sub-modules (7)

Financial sector overlayGreen

SAMA's IT Governance Framework and Cybersecurity Framework apply to banks, insurance/reinsurance companies, financing companies and credit bureaus regulated by SAMA.

Claims (3):

  • SAMA's Cybersecurity Framework applies to institutions including banks, insurance and reinsurance companies, financing companies, and credit bureaus.
  • SAMA's IT Governance Framework, issued 12 December 2021, requires SAMA-regulated Member Organisations to identify and address IT risks and periodically self-assess compliance.
  • SAMA Open Banking Policy — Third-party access to bank customer financial data requires explicit and informed consent

Health sector overlayAmber

Implementing Regulation Article 26 imposes need-to-know-basis and documentation requirements specific to health data processing.

Claims (1):

  • Implementing Regulation Article 26 requires a restrictive, need-to-know-basis approach and documentation of all processing stages, with a specified owner for each stage, when processing health data.

Telecoms and eprivacyAmber

The NCA's Essential Cybersecurity Controls (2018) apply to government entities and private-sector organizations operating Critical National Infrastructure, with CITC having separately drafted an ICT-sector cybersecurity framework.

Claims (2):

  • The National Cybersecurity Authority's Essential Cybersecurity Controls, in force since 2018, apply to government organizations and private-sector organizations owning, operating, or hosting Critical National Infrastructure.
  • CST/CITC Telecom Data Processing Principles — Telecom providers must process customer data within the Kingdom and notify CITC/CST immediately of a breach of customer personal data

Employment dataRed

No dedicated employment-data DP overlay distinct from general PDPL obligations was identified in the sources reviewed.

Credit and scoringAmber

Credit data is treated as a special category under the PDPL, with Implementing Regulation Article 27 imposing restrictive measures on credit-data processing.

Claims (1):

  • Implementing Regulation Article 27 imposes restrictive and specific measures for processing credit data, similar to those for health data.

educationRed

No education-sector-specific DP overlay was identified in the sources reviewed.

insuranceAmber

Insurance companies fall within SAMA's regulated financial-sector cybersecurity/IT governance perimeter but no insurance-specific DP overlay beyond this was identified.

Claims (1):

  • SAMA's Cybersecurity Framework applies to institutions including banks, insurance and reinsurance companies, financing companies, and credit bureaus.
Category narrative 65 words

Financial-sector data processing is overlaid by SAMA's IT Governance and Cybersecurity Frameworks applying to banks, insurers, financing companies and credit bureaus; health and credit data receive additional PDPL Implementing Regulation restrictions (Arts. 26-27); telecoms/CNI-linked processing intersects with the National Cybersecurity Authority's Essential Cybersecurity Controls and a CITC draft ICT cybersecurity framework. No dedicated employment-data, education-sector, or insurance-specific DP overlay beyond general PDPL/NCA rules was identified.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (8)
  1. Probable OneTrust DataGuidance — SAMA's Cybersecurity Framework applies to institutions including banks, insurance and reinsurance companies, financing companies, and credit bureaus. observed
  2. Probable OneTrust DataGuidance — SAMA's IT Governance Framework, issued 12 December 2021, requires SAMA-regulated Member Organisations to identify and address IT risks and periodically self-assess compliance. observed
  3. Probable IAPP — Implementing Regulation Article 26 requires a restrictive, need-to-know-basis approach and documentation of all processing stages, with a specified owner for each stage, when processing health data. observed
  4. Probable OneTrust DataGuidance — The National Cybersecurity Authority's Essential Cybersecurity Controls, in force since 2018, apply to government organizations and private-sector organizations owning, operating, or hosting Critical National Infrastructure. observed
  5. Probable IAPP — Implementing Regulation Article 27 imposes restrictive and specific measures for processing credit data, similar to those for health data. observed
  6. Probable Saudi Central Bank (SAMA) — SAMA Open Banking Policy — Third-party access to bank customer financial data requires explicit and informed consent observed
  7. Probable CMS Law — CST/CITC Telecom Data Processing Principles — Telecom providers must process customer data within the Kingdom and notify CITC/CST immediately of a breach of customer personal data observed
  8. Probable Pinsent Masons (Out-Law) — SAMA Open Banking Framework — SAMA commenced permanent licensing of the first fintech companies to provide open banking services, moving open banking from the regulatory sandbox into a fully licensed regime observed

#

Direct-marketing consent rules are binding and actively enforced; cookie/tracker, dark-pattern, opt-out-signal, and clean-room coverage are gaps in the current PDPL framework as researched.

Primary frameworkPDPL Implementing Regulation Arts. 28-29 (direct marketing)
Traffic-light rationale — AmberDirect-marketing consent rules are binding and actively enforced; cookie/tracker, dark-pattern, opt-out-signal, and clean-room coverage are gaps in the current PDPL framework as researched.

Sub-modules (6)

Cookies and trackersRed

No PDPL-specific cookie/tracker consent regime distinct from general lawful-basis rules was identified.

Claims (1):

  • Personal Data Protection Law — Non-essential cookies/trackers require opt-in consent in practice, as the PDPL has no cookie-specific provision and consent is the general lawful-basis default under Art 5, with limited exceptions under Art 6

Dark patternsRed

No PDPL dark-pattern prohibition provision was identified in sources reviewed.

Claims (1):

  • Personal Data Protection Law — Methods and means of personal data collection must be direct, clear, secure, appropriate to the data subject's circumstances, and must not involve deception, misleading or extortion

Opt out signalsRed

No PDPL recognition of technical opt-out signals (e.g., Global Privacy Control) was identified.

Clean rooms and dcrRed

No clean-room/data-collaboration-room specific rule was identified under the PDPL.

Cross context advertisingRed

No CPRA-style 'sale'/'share' cross-context advertising concept was identified under the PDPL.

Direct marketingAmber

Implementing Regulation Arts. 28-29 require consent for promotional/marketing communications, and marketing-without-consent violations are the most frequently cited SDAIA enforcement finding.

Claims (7):

  • Implementing Regulation Article 29 mandates data controllers collect consent from data subjects before processing data for direct marketing communications, without the prior-interaction exemption found in Article 28.
  • A notable share of SDAIA's 2025 enforcement decisions involved sending marketing and promotional messages without obtaining prior consent, a violation remaining widespread across retail, telecommunications, and financial services.
  • Personal Data Protection Law — A controller must obtain the targeted recipient's prior consent before sending direct marketing or awareness-raising material via post, email, phone-based or electronic channels
  • Implementing Regulation to the PDPL — Before processing personal data for direct marketing, the controller must obtain consent under IR Art 11, provide an opt-out at least as easy as the opt-in, clearly state its identity, and stop sending marketing immediately on withdrawal of consent
  • Marketing without consent is the most cited violation category among SDAIA's 2025 enforcement decisions, with 2026 enforcement actions heavily penalising mass SMS/WhatsApp/email marketing campaigns lacking documented consent.
  • Direct marketing (Art.29 Implementing Regulation) — Direct marketing requires Art.11 consent, an opt-out mechanism as easy as giving consent, clear sender identification, and stopping without undue delay on withdrawal
  • PDPL Implementing Regulation (draft) — Draft amendment would require consent before sending promotional/awareness materials to any recipient, and would require verification of consent where a prior relationship is relied upon.
Category narrative 44 words

The PDPL Implementing Regulation regulates direct marketing consent (Arts. 28-29), and marketing/promotional messaging without prior consent is among the most commonly cited SDAIA enforcement violations. No PDPL-specific cookie/tracker consent regime, dark-pattern prohibition, opt-out-signal (e.g., GPC) recognition, clean-room framework, or CPRA-style cross-context-advertising rule was identified.

Periodic update · new data 2026-11-04

A further element of the same Implementing Regulation consultation would require consent before sending promotional or awareness-raising materials to any recipient, and would additionally require verification of consent where a controller instead relies on having an existing relationship with the recipient as its basis for sending such materials. This would extend the consent requirement beyond the narrower circumstances addressed under the current marketing provisions. The change is, again, a draft proposal open for comment until 5 November 2026 and is not yet in force.

Outlook

If adopted, the amendment would narrow the room controllers currently have to rely on an existing-relationship basis for sending marketing or awareness communications without separately verifying consent. Organisations running direct-marketing or customer-communication programmes touching the Kingdom should treat the consultation outcome as the next relevant marker, rather than the current text, which remains unchanged pending the authority's decision.

1 earlier distinct update
Periodic update · new data 2026-10-25

Marketing conducted without documented consent is reported as the most frequently cited violation category among the Saudi Data and Artificial Intelligence Authority's confirmed 2025 enforcement decisions, with continuing 2026 enforcement actions penalising mass messaging campaigns across SMS, WhatsApp, and email channels that lack documented consent from recipients. This sustained enforcement focus indicates that commercial marketing practices remain a leading area of active supervisory attention under the Personal Data Protection Law.

Against this enforcement backdrop, the draft amendments to the Implementing Regulations under consultation would make two changes relevant to commercial marketing practice. First, the standalone definition of direct marketing currently in the regulatory text would be removed, a structural drafting change requiring edits to all affected cross-references, while the underlying Article 11 consent requirement is reported to persist unchanged as the operative lawful basis for marketing activity. Second, a new requirement would be introduced obliging marketers to disclose the sender's identity when sending direct marketing material, adding a transparency obligation that sits alongside, rather than replacing, the existing consent requirement.

Read together, the enforcement pattern and the proposed amendments describe a consistent regulatory posture: documented consent remains the central lawful basis for marketing activity, and the authority continues to actively penalise its absence, while the proposed sender-identification requirement would add a further, distinct transparency obligation on top of the consent requirement rather than substituting for it. Organisations conducting direct marketing into the Saudi market, whether by SMS, WhatsApp, email, or other channels, should treat documented consent and, pending finalisation of the proposed changes, sender identification as the two central compliance points in this area.

Outlook

Continued active enforcement against marketing conducted without documented consent is the clearest pattern to expect going forward, consistent with the volume and categories seen in the confirmed 2025 enforcement decisions. The proposed sender-identification requirement for direct marketing material is a new obligation to track through to finalisation following the 5 November 2026 consultation close, as scheduled, alongside the broader fate of the direct-marketing definition's removal from the regulatory text.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (9)
  1. Probable IAPP — Implementing Regulation Article 29 mandates data controllers collect consent from data subjects before processing data for direct marketing communications, without the prior-interaction exemption found in Article 28. observed
  2. Probable IAPP — A notable share of SDAIA's 2025 enforcement decisions involved sending marketing and promotional messages without obtaining prior consent, a violation remaining widespread across retail, telecommunications, and financial services. observed
  3. Probable ConsentX — Personal Data Protection Law — Non-essential cookies/trackers require opt-in consent in practice, as the PDPL has no cookie-specific provision and consent is the general lawful-basis default under Art 5, with limited exceptions under Art 6 observed
  4. Probable KSAPDPL.com — Personal Data Protection Law — A controller must obtain the targeted recipient's prior consent before sending direct marketing or awareness-raising material via post, email, phone-based or electronic channels observed
  5. Probable Saudi Data and Artificial Intelligence Authority (SDAIA) — Implementing Regulation to the PDPL — Before processing personal data for direct marketing, the controller must obtain consent under IR Art 11, provide an opt-out at least as easy as the opt-in, clearly state its identity, and stop sending marketing immediately on withdrawal of consent observed
  6. Probable Saudi Data and Artificial Intelligence Authority (SDAIA) — Personal Data Protection Law — Methods and means of personal data collection must be direct, clear, secure, appropriate to the data subject's circumstances, and must not involve deception, misleading or extortion observed
  7. Probable Waqi — Marketing without consent is the most cited violation category among SDAIA's 2025 enforcement decisions, with 2026 enforcement actions heavily penalising mass SMS/WhatsApp/email marketing campaigns lacking documented consent. observed
  8. Probable Saudi Data and Artificial Intelligence Authority (SDAIA) — Direct marketing (Art.29 Implementing Regulation) — Direct marketing requires Art.11 consent, an opt-out mechanism as easy as giving consent, clear sender identification, and stopping without undue delay on withdrawal observed
  9. Probable National Law Review — PDPL Implementing Regulation (draft) — Draft amendment would require consent before sending promotional/awareness materials to any recipient, and would require verification of consent where a prior relationship is relied upon. observed

#

Profiling-objection and genetic-data coverage are binding; AI risk-assessment instruments remain largely non-binding policy/guidance; biometric-specific rules and ADM transparency rights are gaps.

Primary frameworkPDPL Implementing Regulation Art. 28; SDAIA AI Ethics Principles / draft Responsible AI Policy (non-binding guidance)
Traffic-light rationale — AmberProfiling-objection and genetic-data coverage are binding; AI risk-assessment instruments remain largely non-binding policy/guidance; biometric-specific rules and ADM transparency rights are gaps.

Sub-modules (6)

Profiling restrictionsAmber

Implementing Regulation Art. 28 provides a right to object to profiling and direct marketing, paralleling GDPR Art. 21.

Claims (1):

  • Implementing Regulation Article 28 allows reliance on legitimate interest for profiling and direct marketing purposes, subject to the data subject's right to object, similar to GDPR Article 21.

Automated decision making transparencyRed

No standalone ADM-transparency or explanation right distinct from the profiling-objection provision was identified.

AI risk assessmentsAmber

SDAIA opened public consultation on a draft Responsible AI Policy aimed at balancing AI adoption with risk mitigation, and has separately joined the OECD AI Recommendation.

Claims (3):

  • SDAIA opened a public consultation on a draft Responsible AI Policy aiming to balance AI adoption and responsible use while mitigating risks.
  • Prospective dedicated Saudi AI law — Commentary indicates Saudi Arabia is expected to pass its first dedicated AI law within two years, potentially incorporating mandatory ISO 42001 compliance
  • SDAIA AI Ethics Principles — Non-binding national AI governance framework (first issued September 2023, updated 2025); no dedicated binding AI statute exists

Biometric regimeRed

No PDPL-specific biometric-data regime (facial recognition, fingerprint, gait) distinct from general special-category rules was identified.

Claims (1):

  • PDPL Art 1(11) definition of Sensitive Data — Biometric and genetic data used for identification purposes is classified as Sensitive Data, triggering enhanced safeguards including explicit-consent requirement

Genetic dataGreen

Genetic data is explicitly included among special/sensitive categories falling under PDPL scope.

Claims (1):

  • Information such as genetic, health, credit, and financial data falls within the scope of the PDPL and is subject to additional regulation.

State surveillance carveoutsAmber

Cross-border transfers must be stopped where they impact national security or the Kingdom's interests, functioning as a state-security carve-out.

Claims (1):

  • A transfer must be stopped or prohibited if it impacts national security or the Kingdom's interests, among other listed scenarios such as high risk shown by a TIA.
Category narrative 69 words

The PDPL provides a right to object to profiling (Implementing Regulation Art. 28), and SDAIA has separately advanced AI governance instruments (draft Responsible AI Policy, AI Ethics Principles v2.0, generative-AI guidance) that interface with, but sit outside, the core PDPL. Genetic data is a recognized special category. National-security-linked carve-outs exist for cross-border transfer stoppage. No dedicated PDPL biometric-specific regime (facial recognition, gait, fingerprint) or standalone ADM-transparency/explanation right was identified.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (6)
  1. Probable IAPP — Implementing Regulation Article 28 allows reliance on legitimate interest for profiling and direct marketing purposes, subject to the data subject's right to object, similar to GDPR Article 21. observed
  2. Probable OneTrust DataGuidance — SDAIA opened a public consultation on a draft Responsible AI Policy aiming to balance AI adoption and responsible use while mitigating risks. observed
  3. Probable IAPP — Information such as genetic, health, credit, and financial data falls within the scope of the PDPL and is subject to additional regulation. observed
  4. Uncertain Modulos — Prospective dedicated Saudi AI law — Commentary indicates Saudi Arabia is expected to pass its first dedicated AI law within two years, potentially incorporating mandatory ISO 42001 compliance observed
  5. Probable arXiv preprint — SDAIA AI Ethics Principles — Non-binding national AI governance framework (first issued September 2023, updated 2025); no dedicated binding AI statute exists observed
  6. Probable Saudi Privacy Law (private commentary site) — PDPL Art 1(11) definition of Sensitive Data — Biometric and genetic data used for identification purposes is classified as Sensitive Data, triggering enhanced safeguards including explicit-consent requirement observed

#

Only a general guardian/representative concept was located; no PDPL-specific child/vulnerable-group sub-regime (age thresholds, parental consent mechanics, minor profiling bans) was found despite targeted searches.

Primary frameworkPDPL definitional provisions (data subject includes representative/legal guardian)
Traffic-light rationale — RedOnly a general guardian/representative concept was located; no PDPL-specific child/vulnerable-group sub-regime (age thresholds, parental consent mechanics, minor profiling bans) was found despite targeted searches.

Sub-modules (5)

Age verificationRed

No specific statutory age-of-consent threshold for data processing was identified.

Minor profiling bansRed

No minor-specific profiling ban was identified in the sources reviewed.

Education settingsRed

No education-settings-specific data protection rule was identified.

Dependent adultsRed

No dependent-adults (elderly/incapacitated) specific provision beyond the general guardian/representative concept was identified.

Category narrative 41 words

The PDPL's data-subject definition extends to a representative or legal guardian, implying protection for minors and incapacitated persons, but no specific statutory age of consent, dedicated parental-consent mechanism, minor-profiling ban, education-settings rule, or dependent-adults provision was identified in the sources reviewed.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (3)
  1. Probable OneTrust DataGuidance — The definition of 'data subject' in the PDPL extends to the representative or legal guardian of the individual to whom personal data relates. observed
  2. Probable Baker McKenzie — PDPL Implementing Regulation Art 13 — Where a data subject lacks legal capacity, consent for processing must be obtained from a verified legal guardian acting in the data subject's best interests observed
  3. Probable Usercentrics — Consent for children/incapacitated persons (Art.13 Implementing Regulation) — Consent for a child's, legally incompetent, or deceased person's data must be obtained from a parent or legal guardian; no specific numerical age threshold stated observed

#

Regulator powers and penalties are well-evidenced and enforcement activity is demonstrably rising, but private rights of action and collective redress mechanisms are not evidenced in the sources reviewed, and regulator funding/capacity data is absent.

Primary frameworkPDPL Arts. on penalties; SDAIA committee enforcement structure; Licensing and Accreditation Rules (Feb 2026)
Traffic-light rationale — AmberRegulator powers and penalties are well-evidenced and enforcement activity is demonstrably rising, but private rights of action and collective redress mechanisms are not evidenced in the sources reviewed, and regulator funding/capacity data is absent.

Sub-modules (6)

Regulator powers and penaltiesAmber

SDAIA's specialized committees hold quasi-judicial powers to investigate, review evidence, and impose sanctions; the PDPL provides for fines up to SAR 5 million and/or imprisonment up to two years.

Claims (10):

  • The PDPL provides for stringent penalties for breaches, including imprisonment of up to two years and/or fines of up to SAR 5 million (approximately EUR 1.1 million).
  • SDAIA's specialized committees are vested with quasi-judicial powers to investigate suspected infringements, review evidence, and impose administrative sanctions including warnings, fines, and remedial orders.
  • PDPL penalties reach up to SAR 5 million per breach, doubling for repeat offences, with criminal liability of up to two years' imprisonment for egregious sensitive-data disclosures, and SDAIA holds power to suspend a controller's processing activities.
  • PDPL (Royal Decree M/19, as amended) — Administrative fines up to SAR 5,000,000 per violation, with criminal liability (up to two years' imprisonment and individual fines) for unauthorised disclosure/transmission of sensitive data with intent to cause harm or gain.
  • Under PDPL Art 36, SDAIA's review committees may issue warnings or administrative fines up to SAR 5,000,000 per violation, doubled for repeat violations.
  • PDPL Art 36 — Warning or fine up to SAR 5,000,000, doubled for repeat violations (not exceeding double the ceiling)
  • PDPL Art 35 — Up to 2 years imprisonment and/or fine up to SAR 3,000,000 for unlawful disclosure of sensitive data with intent to harm or for personal benefit, doubled for repeat offence
  • Criminal offence for unlawful sensitive-data disclosure (Art.35 PDPL) — Up to 2 years imprisonment and/or fine up to SAR 3,000,000, prosecuted by the Public Prosecution
  • Administrative fine for general violations (Art.36 PDPL) — Warning or administrative fine up to SAR 5,000,000, doubled for repeat violations by court order
  • SDAIA — PDPL fines reportedly up to SAR 5 million per breach

Enforcement activity indexAmber

SDAIA's specialized committees issued 48 decisions in the year preceding a February 2026 report, marking the first substantive enforcement wave since the PDPL became enforceable.

Claims (9):

  • SDAIA's specialized committees issued 48 decisions over the past year against organizations found in violation of the PDPL and its implementing regulations, representing the first substantive wave of adjudications since the PDPL became enforceable.
  • Common enforcement violations identified by SDAIA include processing without a lawful basis, unlawful collection and processing of personal data, and insufficient technical and organizational security controls.
  • SDAIA Committees for Reviewing Violations — Issued 48 enforcement decisions during 2025 confirming PDPL violations and imposing Art 36 penalties
  • SDAIA — 48 enforcement decisions issued under PDPL Article 36 over the preceding year, per a statement carried by the Saudi Press Agency on 16 January 2026
  • SDAIA announced in early 2026 that it had issued 48 formal decisions over the preceding year against organisations found in violation of the PDPL, confirming the regime's transition into active enforcement following the 14 September 2024 grace-period expiry.
  • SDAIA Committees for Reviewing Violations — 48 decisions during 2025, announced January 2026, covering unlawful processing, insufficient security controls and consent-less marketing.
  • SDAIA's Committees for Reviewing Violations of the PDPL issued 48 decisions confirming violations during 2025, announced 16 January 2026, covering processing without legal basis, unauthorised disclosure, inadequate safeguards and marketing without consent.
  • Information Regulator (South Africa) v WhatsApp LLC — Enforcement notice (served Sept 2024, published April 2025) for POPIA breaches of ss.8,9,11,13,15,17,19; settled 13 Nov 2025 with transparency and consent undertakings
  • SDAIA violation committees have moved into active enforcement, with secondary reporting of approximately 48 decisions across 2025-2026

Regulator funding and capacityRed

No specific data on SDAIA's data-protection enforcement budget or headcount was identified in the sources reviewed.

Collective redress and class actionsRed

No collective-redress or class-action mechanism for PDPL data subjects was identified in the sources reviewed.

Private right of actionRed

No explicit private right of direct court action for data subjects distinct from SDAIA's administrative committee process was identified.

Claims (2):

  • A person who suffers harm from a PDPL violation may claim compensation before the competent court for material or moral damage.
  • Data subject complaint mechanism, PDPL Art 34/Implementing Regulation Art 37 — Data subject may complain to SDAIA within 90 days of the incident or discovery of it, with discretionary late acceptance for reasonable cause

Recent developments 180dGreen

Within the last 180 days, SDAIA published (16 February 2026) the Rules Governing the Issuance of Accreditation Certificates for Controllers and Processors and related licensing/auditing rules; SDAIA also reported a stepped-up enforcement posture (48 decisions) in a 25 February 2026 announcement.

Claims (2):

  • On 16 February 2026, SDAIA published the 'Rules Governing the Issuance of Accreditation Certificates for Controllers and Processors' and related rules governing licensing to issue such certificates and auditing.
  • SDAIA's specialized committees issued 48 decisions over the past year against organizations found in violation of the PDPL and its implementing regulations, representing the first substantive wave of adjudications since the PDPL became enforceable.
Category narrative 79 words

SDAIA enforcement matured markedly in 2025-2026: specialized quasi-judicial committees issued 48 decisions in the year preceding a February 2026 report, covering unlawful processing, insufficient security controls, and consent-less marketing. Original PDPL penalties include fines up to SAR 5 million and/or up to two years' imprisonment. In February 2026, SDAIA published new Licensing/Accreditation Rules for controllers and processors. No explicit private right of action or collective-redress/class-action mechanism for data subjects was identified; redress currently flows through SDAIA's administrative committee process.

Periodic update · new data 2026-11-04

No enforcement action, penalty decision or redress matter has been identified in the current window. The principal development bearing on this module is procedural rather than adjudicative: the Implementing Regulation consultation described elsewhere in this note would, if adopted, alter the breach-notification threshold that in turn affects when the regulator's enforcement machinery is engaged in the first place. No primary enforcement activity accompanies the consultation itself.

Outlook

Enforcement posture is likely to be shaped indirectly by the outcome of the Implementing Regulation consultation rather than by any pending case; a broadened breach-notification trigger, if adopted, would be expected to increase the volume of matters reaching the regulator's attention over time, though no such effect can yet be observed.

2 earlier distinct updates
Periodic update · new data 2026-10-25

The Saudi Data and Artificial Intelligence Authority's Committees for Reviewing Violations of the Personal Data Protection Law confirmed 48 decisions finding violations during 2025, an outcome announced 16 January 2026. The violation categories cited across these decisions include processing without a legal basis, unauthorised disclosure, inadequate safeguards, and marketing without consent, with marketing without consent reported as the most frequently cited category overall. This enforcement-volume figure provides a concrete benchmark for the scale of the authority's active supervisory activity during what is a relatively early period in the Personal Data Protection Law's operative life, the Law itself having taken effect in September 2023.

The underlying penalty framework available to the authority's review committees, under Article 36 of the Personal Data Protection Law, allows for warnings or administrative fines of up to 5,000,000 Saudi riyals per violation, with that ceiling doubled for repeat violations. Separately, criminal liability under the Law can extend to imprisonment of up to two years alongside individual fines of up to 3,000,000 Saudi riyals for certain conduct, indicating that the Saudi enforcement regime carries both administrative and criminal dimensions depending on the nature and severity of the violation. The scale of these penalty ceilings, combined with the confirmed 2025 enforcement volume of 48 decisions, signals an active and consequential enforcement posture rather than a largely dormant penalty framework.

The pattern of cited violation categories, processing without a legal basis, unauthorised disclosure, inadequate safeguards, and marketing without consent, maps closely onto the core substantive obligations of the Personal Data Protection Law and its Implementing Regulations, suggesting that the authority's enforcement activity to date has concentrated on foundational compliance failures rather than more novel or technical areas of the Law.

Outlook

Continued enforcement activity at a comparable or increased volume to the 48 decisions confirmed for 2025 is the expected pattern for 2026, particularly given the authority's stated active focus on marketing-without-consent violations. Whether the draft amendments currently under consultation, if finalised, introduce any new enforcement priorities or penalty adjustments tied to the proposed localisation, breach-notification, or marketing provisions is a further point to watch once the amendments are finalised following the 5 November 2026 consultation close, as scheduled.

Periodic update · new data 2026-10-18

SDAIA confirmed, in a statement carried by the Saudi Press Agency on 16 January 2026, that its Committees for Reviewing Violations had issued 48 enforcement decisions under PDPL Article 36 over the preceding year. The amounts of individual decisions were not disclosed by SDAIA, limiting the ability to assess the scale or typical severity of penalties actually imposed, though the confirmed decision count itself indicates that the PDPL's enforcement machinery is operating with meaningful activity volume rather than remaining dormant following the law's implementation.

The available penalty framework, per Tier 3 commentary on PDPL Article 36, permits SDAIA's Committees for Reviewing Violations to issue warnings or administrative fines of up to SAR 5,000,000 per violation, doubled for repeat violations. Separately, unauthorised disclosure of sensitive data intended to cause harm carries a criminal penalty of up to two years' imprisonment and/or a fine of up to SAR 3,000,000. This combination of administrative and criminal exposure under a single statutory article gives Saudi Arabia's data protection enforcement regime a notably broader penalty range than a purely administrative-fine model, extending potential consequences for the most serious conduct, intentional harmful disclosure of sensitive data, into the criminal sphere.

Data subjects are understood to hold a right to claim compensation before the competent court for material or moral damage suffered as a result of a PDPL violation, according to secondary legal commentary; the pinpoint statutory article establishing this private right of action has not been independently retrieved this cycle. This private right of action exists alongside, rather than instead of, SDAIA's own administrative enforcement powers, giving affected data subjects a parallel avenue for redress distinct from any regulatory penalty SDAIA itself might impose on a controller or processor.

The confirmation of 48 decisions in the preceding year, read together with the available penalty ceiling of SAR 5,000,000 per violation, suggests an enforcement posture of active and recurring application rather than occasional or symbolic use of SDAIA's powers. However, because individual decision amounts remain undisclosed, it is not possible from the material available this cycle to assess what proportion of the 48 decisions approached the statutory maximum, nor to characterise the typical profile of a PDPL enforcement action under Article 36.

Outlook

The confirmed enforcement volume of 48 decisions over the preceding year establishes a baseline against which future enforcement-activity disclosures from SDAIA can be compared. Should SDAIA begin publishing individual decision amounts or further detail on the nature of violations underlying these decisions, future assessments of the PDPL enforcement regime's practical severity and targeting would be considerably strengthened. The interaction between this active enforcement posture and the pending PDPL Implementing Regulation amendments, including the data-localisation Key Change under consultation until 5 November 2026, is also worth monitoring, as any newly created obligations under the amended regulations would become a fresh basis for future Article 36 enforcement activity once in force.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (22)
  1. Probable OneTrust DataGuidance — The PDPL provides for stringent penalties for breaches, including imprisonment of up to two years and/or fines of up to SAR 5 million (approximately EUR 1.1 million). observed
  2. Probable IAPP — SDAIA's specialized committees are vested with quasi-judicial powers to investigate suspected infringements, review evidence, and impose administrative sanctions including warnings, fines, and remedial orders. observed
  3. Probable IAPP — SDAIA's specialized committees issued 48 decisions over the past year against organizations found in violation of the PDPL and its implementing regulations, representing the first substantive wave of adjudications since the PDPL became enforceable. observed
  4. Probable IAPP — Common enforcement violations identified by SDAIA include processing without a lawful basis, unlawful collection and processing of personal data, and insufficient technical and organizational security controls. observed
  5. Probable OneTrust DataGuidance — On 16 February 2026, SDAIA published the 'Rules Governing the Issuance of Accreditation Certificates for Controllers and Processors' and related rules governing licensing to issue such certificates and auditing. observed
  6. Probable Profectus — SDAIA Committees for Reviewing Violations — Issued 48 enforcement decisions during 2025 confirming PDPL violations and imposing Art 36 penalties observed
  7. Probable Saudi Compliance Institute — SDAIA — 48 enforcement decisions issued under PDPL Article 36 over the preceding year, per a statement carried by the Saudi Press Agency on 16 January 2026 observed
  8. Probable GovernanceDocs — SDAIA announced in early 2026 that it had issued 48 formal decisions over the preceding year against organisations found in violation of the PDPL, confirming the regime's transition into active enforcement following the 14 September 2024 grace-period expiry. observed
  9. Probable SGC Consulting — PDPL penalties reach up to SAR 5 million per breach, doubling for repeat offences, with criminal liability of up to two years' imprisonment for egregious sensitive-data disclosures, and SDAIA holds power to suspend a controller's processing activities. observed
  10. Probable Ampcus Cyber — PDPL (Royal Decree M/19, as amended) — Administrative fines up to SAR 5,000,000 per violation, with criminal liability (up to two years' imprisonment and individual fines) for unauthorised disclosure/transmission of sensitive data with intent to cause harm or gain. observed
  11. Probable https://securiti.ai/saudi-arabia-personal-data-protection-law/ — SDAIA Committees for Reviewing Violations — 48 decisions during 2025, announced January 2026, covering unlawful processing, insufficient security controls and consent-less marketing.
  12. Probable https://www.dlapiperdataprotection.com/?c=SA — A person who suffers harm from a PDPL violation may claim compensation before the competent court for material or moral damage.
  13. Probable Saudi Compliance Institute — Under PDPL Art 36, SDAIA's review committees may issue warnings or administrative fines up to SAR 5,000,000 per violation, doubled for repeat violations. observed
  14. Probable Securiti — SDAIA's Committees for Reviewing Violations of the PDPL issued 48 decisions confirming violations during 2025, announced 16 January 2026, covering processing without legal basis, unauthorised disclosure, inadequate safeguards and marketing without consent. observed
  15. Probable Saudi Privacy Law (private commentary site) — PDPL Art 36 — Warning or fine up to SAR 5,000,000, doubled for repeat violations (not exceeding double the ceiling) observed
  16. Probable https://www.smartsuite.com/frameworks/saudi-arabia-personal-data-protection-law-pdpl-2021 — PDPL Art 35 — Up to 2 years imprisonment and/or fine up to SAR 3,000,000 for unlawful disclosure of sensitive data with intent to harm or for personal benefit, doubled for repeat offence
  17. Probable Michalsons — Information Regulator (South Africa) v WhatsApp LLC — Enforcement notice (served Sept 2024, published April 2025) for POPIA breaches of ss.8,9,11,13,15,17,19; settled 13 Nov 2025 with transparency and consent undertakings observed
  18. Probable https://sdaia.gov.sa/en/SDAIA/about/Documents/ImplementingRegulation.pdf — Data subject complaint mechanism, PDPL Art 34/Implementing Regulation Art 37 — Data subject may complain to SDAIA within 90 days of the incident or discovery of it, with discretionary late acceptance for reasonable cause
  19. Probable SmartSuite — Criminal offence for unlawful sensitive-data disclosure (Art.35 PDPL) — Up to 2 years imprisonment and/or fine up to SAR 3,000,000, prosecuted by the Public Prosecution observed
  20. Probable OneClickComply — Administrative fine for general violations (Art.36 PDPL) — Warning or administrative fine up to SAR 5,000,000, doubled for repeat violations by court order observed
  21. Uncertain RecordingLaw — SDAIA — PDPL fines reportedly up to SAR 5 million per breach observed
  22. Uncertain The Leveraged Years — SDAIA violation committees have moved into active enforcement, with secondary reporting of approximately 48 decisions across 2025-2026 observed
No categories match.

No categories match your current search or filter selection.

Provenance and declared absence

Disclosure model: category cards load OPEN; narratives render in full; standing narratives load as a clamped teaser with an explicit “read full” control carrying the true word count. No text is hidden without disclosing how much of it there is.

Sub-modules are DP-specific nested subsections with their own real per-sub-module traffic light, rendered under each category across all regulatory modules.

Traffic-light dots are REAL data (baseline.<category>.traffic_light), not renderer-invented taxonomy, and are never suppressed -- unlike WPM, where a RAG dot would be forbidden as invented severity.

Family/accent taxonomy is renderer-level presentation config, not a JID field; it decorates the RAG dot, it does not replace it. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-17. A year-precision row is never promoted into a tighter band.

Envelope: baseline resolved at jurisdiction_json.baseline; 10 categories, 57 sub-module(s), 137 claim(s) (137 category placement(s)), 100 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 25 Oct 2026: upheld (20 confirmed against the cited source; 3 could not be checked). An automated, adversarial test run by a second model; no person has assessed the result.

Think something on this page is wrong? Report an error.

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (38 mapped).

Show article map
GDPR article to category mapping
ArticleCategorySub-module
Art. 5Controller/Processor Dutiesaccountability and dpia
Art. 6Lawful Processing & Special Datalawful bases
Art. 7Lawful Processing & Special Dataconsent thresholds
Art. 9Lawful Processing & Special Dataspecial categories
Art. 13Data Subject Rightsaccess right
Art. 14Data Subject Rightsaccess right
Art. 15Data Subject Rightsaccess right
Art. 16Data Subject Rightsrectification and erasure
Art. 17Data Subject Rightsrectification and erasure
Art. 18Data Subject Rightsrestriction and objection
Art. 19Data Subject Rightsrectification and erasure
Art. 20Data Subject Rightsdata portability
Art. 21Data Subject Rightsrestriction and objection
Art. 22Algorithmic, Biometric & Surveillance Governanceautomated decision making transparency
Art. 25Controller/Processor Dutiesaccountability and dpia
Art. 28Controller/Processor Dutiesjoint controller arrangements
Art. 30Controller/Processor Dutiesropa requirements
Art. 32Controller/Processor Dutiessecurity measures
Art. 33Controller/Processor Dutiessecurity measures
Art. 34Controller/Processor Dutiesbreach notification
Art. 35Controller/Processor Dutiesaccountability and dpia
Art. 37Controller/Processor Dutiesdpo requirements
Art. 38Controller/Processor Dutiesdpo requirements
Art. 39Controller/Processor Dutiesdpo requirements
Art. 44Cross-Border & Adequacytransfer mechanisms
Art. 45Cross-Border & Adequacyadequacy received
Art. 46Cross-Border & Adequacysccs and bcrs
Art. 47Cross-Border & Adequacysccs and bcrs
Art. 48Cross-Border & Adequacytransfer impact assessment
Art. 49Cross-Border & Adequacytransfer mechanisms
Art. 77Enforcement & Redressregulator powers and penalties
Art. 78Enforcement & Redressregulator powers and penalties
Art. 79Enforcement & Redressprivate right of action
Art. 80Enforcement & Redresscollective redress and class actions
Art. 81Enforcement & Redresscollective redress and class actions
Art. 82Enforcement & Redressprivate right of action
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties