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.
Saudi PDPL. Transfers and records.
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
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.
How a reviewer labels values from one bank’s systems. Article 1(11) lists the sensitive categories; credit data has its own rules instead.
| Value | Detected type | Label | Reason | Kept or rejected |
|---|---|---|---|---|
| 1023456789 in customers.national_id | National ID number | Personal data | Starts with 1, a citizen’s number in SAMA’s Appendix C format; a placeholder | Kept |
| 2234567890 in hr.iqama_no | Iqama (resident ID) | Personal data | Starts with 2, a foreign resident’s number; a placeholder | Kept |
| J45 in clinic.visits | Diagnosis code (ICD-10) | Sensitive: health data, Article 1(11) | An asthma code beside an employee ID in the staff clinic system | Kept |
| Christian in hr.profile.religion | Religious belief | Sensitive: Article 1(11) | A belief field kept for a holiday roster | Kept |
| parents_unknown = Y in onboarding.kyc | Parentage indicator | Sensitive: Article 1(11) | Shows that a parent is unknown, a category the GDPR list lacks | Kept |
| Score 712 in loans.bureau_score | Credit data | Personal data; not sensitive | Credit data has its own rules (Article 24), outside the Article 1(11) list | Rejected |
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.
| Article | What it requires | Time limit or amount | Bank control it touches | Record 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 delay | SAMA CSF 3.3.11 secure disposal | Retention 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 first | None specific | A search record per request: received and answered dates, systems searched, what each held |
| Article 19; IR Article 23 | Organizational, administrative and technical measures; IR Article 23 points to NCA controls where they apply. | Ongoing | SAMA CSF 3.3.9 cryptography (key management is a separate test); NCA ECC 2-7-2 where in scope | A dated check of each store’s protection state, with its classification |
| Article 20; IR Article 24 | Notify 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 reports | The breach record with awareness and notice times, and a dated list of what the system held |
| Article 29; Transfer Regulation | Transfer 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 approval | A transfer register kept by its owner: data, destination, purpose, safeguard, and the date each entry was last checked |
| Article 31; IR Article 33 | Keep 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 classification | The record, with each system matched to a dated search of it |
| Article 22; IR Article 25 | Assess 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 them | None specific | The assessment’s data section, built from a dated search |
| Article 30(2); IR Article 32 | Appoint a DPO if you are a large-scale public entity, observe people systematically, or mainly process sensitive data. | On meeting a trigger | None specific | The dated appointment decision, naming the officer, their duties and who approved it |
| Articles 35–36 | Art. 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 gain | Not applicable | Not a record: penalties follow a committee or court decision |
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.
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).
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.
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.
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.
| Item | Status | Instrument |
|---|---|---|
| Law | In force since September 14, 2023; grace period ended September 14, 2024 | PDPL, Article 43 |
| Implementing Regulation | The 2023 text, in force with the Law and not yet amended | Implementing Regulation, Article 38 |
| Transfer Regulation | Version 2.0 of August 2024, in force | Transfer Regulation |
| Draft amendments to the Implementing Regulation | Consulted October 6 to November 5, 2026; closed, not adopted. Draft Art. 23(2) would require storage in the Kingdom | Istitlaa project 75590 |
| If adopted | In force sixty days after publication in the Official Gazette (draft Article 38); no date announced | Istitlaa project 75590 |
| Regulator | SDAIA, with the Saudi Central Bank’s powers over banks preserved | PDPL Article 30(1) |
| Bank frameworks | SAMA CSF version 1.0 (2017) in force; NCA ECC-2:2024 replaced ECC-1:2018 | SAMA Rulebook; NCA ECC-2:2024 |
| Review | Editorial review by Sylox; not reviewed by a lawyer | Last reviewed November 8, 2026 |
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 evidenceOur recommended order; neither the law nor SAMA prescribes it. The source coverage register guide shows how to record each system you checked.
Record every system you checked, what you found and what you couldn’t reach.
The options for where IRIS runs, and the outbound connections each one needs.
Evidence for an examiner’s data request, traced to the source, table and scan date.
IRIS maps its evidence to Saudi PDPL controls through its unified compliance framework. Your assessment decides what it shows. A scored Saudi PDPL readiness view isn’t in v1; ask us if you need one.
No, they aren’t built-in patterns today. Add the ten-digit formats as custom patterns; IRIS already recognizes payment-card numbers and IBANs.
No. Draft Article 23(2) would require storing personal data in the Kingdom, but the amendments were only consulted on, from October 6 to November 5, 2026, and are not adopted.
Yes. IRIS logs access, correction and erasure requests and searches connected databases; your team makes the change in the source system. Capabilities vary by edition.
Start the transfer register with one system: a free assessment scans one database with a read-only login you create.