Cookie settings

Necessary, always on: they keep the site working and remember your cookie choice.

Skip to content
Skip to content

Saudi PDPL. Transfers and records.

Saudi PDPL: where personal data sits, and when it may leave

For a Saudi bank, PDPL evidence and SAMA evidence are the same records, and the transfer register is where they meet. Each duty sits beside its bank control.

By Dipal Panchal, co-founder and CEO · Last reviewed: November 8, 2026

Overview

Who the Saudi PDPL covers

The Personal Data Protection Law, issued by Royal Decree M/19 in 2021 and amended by M/148 in 2023, has been in force since September 14, 2023. Its one-year grace period ended on September 14, 2024.

It covers processing in the Kingdom, and processing from abroad of data on people who live there (Article 2(1)). The Saudi Data and Artificial Intelligence Authority (SDAIA) supervises it, without prejudice to the Saudi Central Bank’s powers (Article 30(1)).

An Implementing Regulation (IR below) and a Transfer Regulation set the detail. Article numbers below follow SDAIA’s official English texts. This page is general information, not legal advice.

  • Processing in the Kingdom, and from abroad on its residents
  • Personal or family use sits outside it, unless published or disclosed
  • Banks also answer to SAMA’s Cyber Security Framework, mapped below
  • Government and critical infrastructure: NCA ECC-2:2024 applies too

Six values, sorted under Article 1(11)

How a reviewer labels values from one bank’s systems. Article 1(11) lists the sensitive categories; credit data has its own rules instead.

Records
ValueDetected typeLabelReasonKept or rejected
1023456789 in customers.national_idNational ID numberPersonal dataStarts with 1, a citizen’s number in SAMA’s Appendix C format; a placeholderKept
2234567890 in hr.iqama_noIqama (resident ID)Personal dataStarts with 2, a foreign resident’s number; a placeholderKept
J45 in clinic.visitsDiagnosis code (ICD-10)Sensitive: health data, Article 1(11)An asthma code beside an employee ID in the staff clinic systemKept
Christian in hr.profile.religionReligious beliefSensitive: Article 1(11)A belief field kept for a holiday rosterKept
parents_unknown = Y in onboarding.kycParentage indicatorSensitive: Article 1(11)Shows that a parent is unknown, a category the GDPR list lacksKept
Score 712 in loans.bureau_scoreCredit dataPersonal data; not sensitiveCredit data has its own rules (Article 24), outside the Article 1(11) listRejected
Requirements

Each duty beside the bank control it touches

The law and regulations fill the first three columns; the fourth links each duty to the SAMA or NCA control an examiner tests. The last is our recommendation.

Each duty beside the bank control it touches
ArticleWhat it requiresTime limit or amountBank control it touchesRecord that shows it
Articles 10–11, 18(1)Collect directly from the person, keep data to the minimum needed, and destroy it once its purpose ends.Destruction without undue delaySAMA CSF 3.3.11 secure disposalRetention rules, with a dated check against the oldest records in each system
Saudi PDPL Article 4; IR Article 3(1)(a)Act on requests to access, obtain, correct or destroy personal data.Thirty days from the request; thirty more for disproportionate effort or repeated requests, notified firstNone specificA search record per request: received and answered dates, systems searched, what each held
Article 19; IR Article 23Organizational, administrative and technical measures; IR Article 23 points to NCA controls where they apply.OngoingSAMA CSF 3.3.9 cryptography (key management is a separate test); NCA ECC 2-7-2 where in scopeA dated check of each store’s protection state, with its classification
Article 20; IR Article 24Notify SDAIA of a breach that may cause harm; tell affected people without undue delay where it may cause damage.Within seventy-two hours of becoming aware (IR Article 24(1))SAMA CSF 3.3.15: tell SAMA at once of medium or high incidents; IR Art. 24(4) keeps both reportsThe breach record with awareness and notice times, and a dated list of what the system held
Article 29; Transfer RegulationTransfer abroad only for a listed purpose, with adequate protection, minimum data and no harm to national security.A risk assessment before safeguard-based transfers (Transfer Regulation Article 7)SAMA CSF 3.4.3: cloud outside Saudi Arabia needs SAMA’s explicit approvalA transfer register kept by its owner: data, destination, purpose, safeguard, and the date each entry was last checked
Article 31; IR Article 33Keep a record of each processing activity: purpose, categories of people, recipients, transfers abroad, retention.For the processing period plus five years (IR Article 33(1))SAMA CSF 3.3.3 asset register; NCA ECC 2-1-5 classificationThe record, with each system matched to a dated search of it
Article 22; IR Article 25Assess the impact of processing for any product or service, given the nature of the activity.No deadline; required in the cases IR Article 25(1) lists, sensitive data among themNone specificThe assessment’s data section, built from a dated search
Article 30(2); IR Article 32Appoint a DPO if you are a large-scale public entity, observe people systematically, or mainly process sensitive data.On meeting a triggerNone specificThe dated appointment decision, naming the officer, their duties and who approved it
Articles 35–36Art. 36: a warning or up to SAR 5,000,000 per violation, which may double on repeat.Art. 35: up to two years’ prison, SAR 3,000,000 or both, for disclosing sensitive data to harm or gainNot applicableNot a record: penalties follow a committee or court decision
Questions

When data may leave the Kingdom

Is the purpose on the list?

Article 29(1) allows a treaty obligation, the Kingdom’s interests or a contract with the person. Transfer Regulation Article 2 adds central processing, a service to the person and research.

Is the destination adequate?

SDAIA’s portal shows no adequacy list today. Without one, contractual clauses, binding common rules or a certificate work only in the five cases of Transfer Regulation Article 4(2).

Does a bank need more?

Yes. SAMA CSF 3.4.3 says to use cloud services located in Saudi Arabia, or get SAMA’s explicit approval for cloud outside it. Outsourcing abroad needs a written no objection.

Who decides if data should be there?

The owner. A scan can show me where data sits, but there is no way for it to know whether that place should hold it. A transfer register needs the owner’s decision.

Timeline

Status on November 8, 2026

Checked on dgp.sdaia.gov.sa, Istitlaa, SAMA Rulebook and nca.gov.sa on November 8, 2026. Next review by February 6, 2027, or when SDAIA publishes amendments.

Status on November 8, 2026
ItemStatusInstrument
LawIn force since September 14, 2023; grace period ended September 14, 2024PDPL, Article 43
Implementing RegulationThe 2023 text, in force with the Law and not yet amendedImplementing Regulation, Article 38
Transfer RegulationVersion 2.0 of August 2024, in forceTransfer Regulation
Draft amendments to the Implementing RegulationConsulted October 6 to November 5, 2026; closed, not adopted. Draft Art. 23(2) would require storage in the KingdomIstitlaa project 75590
If adoptedIn force sixty days after publication in the Official Gazette (draft Article 38); no date announcedIstitlaa project 75590
RegulatorSDAIA, with the Saudi Central Bank’s powers over banks preservedPDPL Article 30(1)
Bank frameworksSAMA CSF version 1.0 (2017) in force; NCA ECC-2:2024 replaced ECC-1:2018SAMA Rulebook; NCA ECC-2:2024
ReviewEditorial review by Sylox; not reviewed by a lawyerLast reviewed November 8, 2026
With IRIS

IRIS doesn’t certify compliance. IRIS maps its evidence to Saudi PDPL controls through its unified compliance framework. A scored readiness view for Saudi PDPL isn’t in v1; ask us if you need one.

Article 31: the systems in your record, checked against what they hold: IRIS produces part of this, for the sources you connect, by source, table, column or file.

Article 1(11): where sensitive data sits: IRIS produces part of this, for the data types IRIS detects, such as diagnosis codes.

Article 19 and SAMA CSF 3.3.5: who can reach each dataset: IRIS produces part of this, where the source exposes permission data.

Article 19 and SAMA CSF 3.3.9: how stored values are protected: IRIS produces part of this, checks sampled values for encryption, masking or hashing, once activated on your install.

Article 4: the search behind a request: IRIS produces part of this, connected databases only, not files or mailboxes; the change happens in the source system.

SAMA CSF 3.3.3: which systems a scan covered and couldn’t read: IRIS produces this.

Explore evidence

Build the transfer register a bank needs

Our recommended order; neither the law nor SAMA prescribes it. The source coverage register guide shows how to record each system you checked.

1. List every system that holds personal data

Owner
Data protection officer
Tool or path
Your Article 31 record and the hosting inventory
Expected output
Each system with its owner, its purpose and the country where it is hosted.
How to verify
Every system in the asset register (SAMA CSF 3.3.3) appears on the list, or is marked out of scope.

2. Find personal and sensitive data in each one

Owner
Data platform lead
Tool or path
A discovery scan, or queries each system owner runs
Expected output
Tables and files holding personal data, the Article 1(11) categories flagged, and the date found.
How to verify
Each listed system shows a search date, or a recorded reason for none.

3. Record each copy held outside the Kingdom

Owner
Data protection officer, with legal counsel
Tool or path
The transfer register
Expected output
For each copy abroad: the Article 29 purpose, the safeguard and any transfer risk assessment.
How to verify
Every cloud account and the outsourcing register (SAMA Outsourcing Rules) were checked for copies abroad, not just the record.

4. Search again after each change

Owner
Data platform lead
Tool or path
The step 2 method, repeated
Expected output
A dated search showing each copy moved, deleted or covered by a safeguard.
How to verify
The register’s dates follow the changes, and open items have owners.

The official texts behind each cell

  1. Personal Data Protection Law, official English text, Saudi Data and AI Authority. Opened November 8, 2026.
  2. Implementing Regulation of the Personal Data Protection Law, Saudi Data and AI Authority. Opened November 8, 2026.
  3. Regulation on Personal Data Transfer Outside the Kingdom, version 2.0 (August 2024), Saudi Data and AI Authority. Opened November 8, 2026.
  4. Amendments to the Implementing Regulation of the PDPL, consultation project 75590, Istitlaa public consultation platform. Opened November 8, 2026.
  5. Cyber Security Framework, version 1.0 (May 2017), Saudi Central Bank Rulebook. Opened November 8, 2026.
  6. Essential Cybersecurity Controls, ECC-2:2024, National Cybersecurity Authority. Opened November 8, 2026.
  7. Rules on Outsourcing (banking sector), 2019, Saudi Central Bank Rulebook. Opened November 8, 2026.
  8. Account Opening Rules, Appendix (C): national ID and Iqama number structure, Saudi Central Bank Rulebook. Opened November 8, 2026.
  9. Guide to the Saudi PDPL for Controllers and Processors, version 1.0 (December 2023), Saudi Data and AI Authority. Opened November 8, 2026.
FAQ

IRIS and the Saudi rules, briefly

Protect your brand. Start with your data.

Start the transfer register with one system: a free assessment scans one database with a read-only login you create.