Saudi Arabia data residency for KYC data: PDPL, SAMA and what must stay in the Kingdom

Updated: 1 hour ago
A Saudi client asks where its customers' KYC data will live. The answer depends on who regulates the client.
As of November 2026, no single law requires all KYC data to stay in Saudi Arabia. Firms regulated by the Saudi Central Bank (SAMA) need SAMA's approval to use cloud services outside the Kingdom.
Every other business can transfer personal data abroad only under the conditions of the Personal Data Protection Law (PDPL). And the Saudi Data and AI Authority (SDAIA) has proposed a general duty to store personal data in the Kingdom, which is still a draft.
This guide to Saudi Arabia data residency for KYC data sets out each rule, labels it as in force or draft, and ends with a checklist for assessing a KYC vendor.
Saudi Arabia data residency Key Takeaways |
|
|
|
|
|
|
Does KYC data have to be stored in Saudi Arabia?
For SAMA-regulated institutions, in practice, yes, unless SAMA approves otherwise.
For capital market institutions, the regulator's cybersecurity guidelines point to cloud services located in the Kingdom.
For other businesses, the law in force restricts transfers abroad but does not require local storage. A draft amendment would change that for every controller.
KYC data is personal data. It includes:
National IDs, Iqamas and passports
Selfies and biometric checks
Source-of-funds documents
Screening results and risk scores
Which rule applies depends on who holds the data.
Who you are | Rule | Effect on where KYC data sits | Status |
SAMA Member Organization (bank, insurer, finance company and others in scope) | SAMA Cyber Security Framework, 3.4.3 Cloud Computing | In principle, only cloud services located in Saudi Arabia. Cloud outside the Kingdom needs explicit SAMA approval | In force |
SAMA Member Organization | SAMA Cyber Security Framework, 3.4.2 Outsourcing | SAMA approval before material outsourcing | In force |
CMA-licensed capital market institution | CMA Cybersecurity Guidelines for Capital Market Institutions | Cloud services expected to be located in Saudi Arabia | In force as guidelines |
Any controller of personal data of people in the Kingdom | PDPL, Article 29, and the Regulation on Personal Data Transfer outside the Kingdom | No local storage rule. Transfers abroad need a permitted purpose plus adequacy or safeguards | In force |
Any controller | Draft amendments to the PDPL Implementing Regulation, proposed Article 23(2) | Personal data to be stored in the Kingdom; compliant transfers still allowed | Draft |
Government entity or critical national infrastructure operator | NCA ECC-2:2024 and CCC-2:2024 | The 2024 versions no longer carry an explicit in-Kingdom hosting clause. Other rules may still require it | In force |
Cloud provider serving customers in the Kingdom | CST Cloud Computing Regulatory Framework | Provider registration and obligations; strict rules for government data | In force |
Every financial institution and DNFBP | Anti-Money Laundering Law, Article 12 | Says nothing on location. Records kept at least 10 years and readily available to authorities | In force |
This table is a starting point, not a legal opinion on your licence.
A firm can also sit in more than one row. A fintech serving a Saudi bank usually inherits the bank's SAMA obligations by contract.

What does the PDPL say about transferring personal data outside the Kingdom?
The PDPL allows transfers abroad, on conditions. The destination must offer an appropriate level of protection, or the controller must put safeguards in place: SDAIA's standard contractual clauses, binding common rules or a certificate of accreditation.
Status: in force. SDAIA has enforced the law since 14 September 2024.
The rules sit in Article 29 of the PDPL and in the Regulation on Personal Data Transfer outside the Kingdom. Three points matter for KYC data:
No adequacy list. SDAIA is meant to publish the countries it considers adequate. We found no published list as of November 2026, so safeguards are the working route.
A risk assessment comes with the safeguards. A controller relying on standard contractual clauses or another safeguard must assess the transfer risk first. The same applies to continuous or large-scale transfers of sensitive data, a category that covers the biometric data used in identity verification. SDAIA issued non-binding guidelines on these assessments in February 2025.
Minimum data only. The transfer must be limited to the data needed and must not prejudice national security or the Kingdom's vital interests.
SDAIA's standard contractual clauses in practice
SDAIA's clauses are its own text. EU clauses signed with a vendor do not satisfy the PDPL, and an existing data transfer agreement needs to be compared against the Saudi version and the gaps closed.
For a KYC vendor hosted abroad, the minimum file is the signed SDAIA clauses, the transfer risk assessment, and a map of every onward transfer to the vendor's own sub-processors.
What changes if the 2026 PDPL amendments are adopted?
Local storage would become the default for every controller. Status: draft. SDAIA published revised amendments to the PDPL Implementing Regulation on 6 October 2026 and the consultation closed on 5 November 2026.
We found no adopted text as of 19 November 2026.
The draft proposes:
Storage in the Kingdom (proposed Article 23(2)). Controllers would store personal data in Saudi Arabia. Transfers that comply with the PDPL would remain possible.
Registration. Controllers that transfer or disclose personal data outside the Kingdom would have to register with SDAIA.
Faster breach reporting. Notification to SDAIA within 72 hours, without the current condition that the breach may cause harm.
Short lead time. The amendments would take effect 60 days after publication in the Official Gazette.
The draft does not explain how "store in the Kingdom" and "transfers still allowed" fit together. The cautious reading is that a primary copy stays in Saudi Arabia and anything leaving follows the transfer rules. Until a final text is published, that is our interpretation.
Sixty days is too short to renegotiate a hosting arrangement. Ask vendors now whether they can offer in-Kingdom storage and how long a migration would take.

What do Saudi financial regulators require?
Sector regulators set the strictest rules in force today. SAMA expects Member Organisations to use cloud services located in Saudi Arabia and to seek approval for anything else.
The CMA's cybersecurity guidelines take the same position for capital market institutions.
SAMA: cloud approval and outsourcing
The SAMA Cyber Security Framework has been in force since May 2017. Section 3.4.3 covers hybrid and public cloud services, which is how most KYC platforms are delivered. Private, internal cloud is outside this section.
It asks a Member Organisation to:
Obtain SAMA approval before using cloud services or signing with a cloud provider.
Use, in principle, only cloud services located in Saudi Arabia, or obtain explicit SAMA approval for services outside the Kingdom.
Ensure the provider does not use the institution's data for secondary purposes.
Agree exit terms, including the return and deletion of data.
Section 3.4.2 adds SAMA approval before material outsourcing and compliance with SAMA's outsourcing rules.
Standard contractual clauses do not replace any of this. They answer SDAIA's question about personal data. SAMA's question is about operational and cyber risk, and it needs its own answer.
Payment firms and fintechs licensed by SAMA should confirm which SAMA frameworks apply to their licence category.
Read also: Best AML software for banks
Capital Market Authority firms
The CMA's Cybersecurity Guidelines for Capital Market Institutions expect cloud services to be located in Saudi Arabia, according to legal analysis of the guidelines.
Brokers, asset managers and fund managers should check the current text and whether the CMA treats it as binding for their licence.
NCA controls for government and critical infrastructure: what changed in 2024
Many vendor pages still say the NCA's Essential Cybersecurity Controls require in-Kingdom hosting. That was true of the 2018 version.
ECC-2:2024 removed the explicit requirement for government entities and critical national infrastructure operators to host and store data in the Kingdom. The NCA says CCC-2:2024 was updated to reflect the changes to data localisation.
Localisation has not disappeared for these entities. It now comes from other instruments: sector rules such as SAMA's, the cloud rules of the Communications, Space and Technology Commission (CST), which treat government data strictly, and national data classification policies.
A bank designated as critical infrastructure is still bound by SAMA.

Fully Compliant Everywhere
Learn how azakaw makes MLRO life easier with an AI-powered AML solution that uses regulator-specific templates or allows you to create your own rules and workflows.

How long must KYC and AML records be kept in Saudi Arabia?
At least 10 years. Status: in force. Article 12 of the Anti-Money Laundering Law (Royal Decree M/20) requires transaction records to be kept for 10 years from the transaction or account closure, and due diligence records for 10 years after the relationship ends.
The due diligence category covers CDD documents, account files, business correspondence, copies of identification and the results of any analysis. The Public Prosecution can extend the period in a specific case.
Two further requirements shape a vendor decision more than the number does:
Records must be sufficient to reconstruct a transaction.
Records must be readily available to the competent authorities.
The law does not say where AML records must be stored. It says they must exist for a decade and be produced on request.
That is twice the UAE's five-year minimum, and longer than most software contracts last. The retention plan has to cover what happens to the records when you change vendor.
Read also: Transaction monitoring in Saudi Arabia
What are the consequences of non-compliance?
The consequences depend on which rule applies to the business and what it has failed to do. There is no general storage-in-the-Kingdom rule in force for every business. Hosting data outside Saudi Arabia does not, by itself, mean that a company has breached the law.
The exposure arises when a company transfers personal data without meeting the PDPL’s requirements, uses cloud services without the required sector approval, or fails to keep and provide required records.
PDPL violations
A violation of the PDPL or its Regulations may result in a warning or a fine of up to SAR 5 million. The fine may be doubled for a repeated violation.
The final decision may also be published at the violator’s expense, and an individual who suffers harm may seek compensation through the courts.
The Law provides a separate criminal penalty for an individual who unlawfully discloses or publishes sensitive data with the intention of harming the data subject or obtaining a personal benefit: up to two years’ imprisonment, a fine of up to SAR 3 million, or both. This is a specific offence; it is not the automatic penalty for every non-compliant data transfer.
SAMA and other sector rules
For a SAMA Member Organisation, using cloud services without prior SAMA approval or using services outside the Kingdom without explicit approval can create a separate regulatory breach.
Depending on the circumstances, consequences may include financial penalties, censure or restrictions on banking activities. SAMA’s Rulebook describes loss of banking privileges as a possible outcome in extreme cases; it does not set one fixed penalty for every data-location breach.
Capital market institutions should assess their CMA requirements separately. The applicable consequences depend on the institution, the rule breached and the regulator’s response.
AML record-keeping failures
Failing to retain required records for at least 10 years, or being unable to produce them when requested, creates a separate compliance risk. It can also leave the business unable to reconstruct a transaction or evidence its decisions.
The specific consequences depend on the applicable supervisory framework and the facts; they should not be confused with the criminal penalties for committing money laundering.
Beyond regulatory action, a breach may require audits, remediation or a vendor migration, and may disrupt onboarding or affect client and contractual relationships. These are possible business consequences, not automatic statutory penalties.

Avoid Legal Sanctions & Penalties
Streamline compliance from identity and business verification to corporate compliance and AML transaction monitoring, reducing costs and complexity so you can scale with confidence.
Saudi Arabia vs UAE: quick comparison
The two countries answer the same question differently.
Saudi Arabia has an operational transfer regime, a central bank that expects in-Kingdom cloud and a 10-year AML retention period.
The UAE has a central bank localisation rule, free-zone transfer regimes and a five-year retention period.
Topic | Saudi Arabia | UAE |
Data protection law | PDPL, enforced by SDAIA since September 2024 | Federal PDPL on the mainland; separate laws in the DIFC and ADGM |
General local storage rule | None in force. Proposed in the October 2026 draft | None |
Transfer mechanisms | Operational: SDAIA clauses, binding common rules, accreditation. No adequacy list found | Operational in the DIFC and ADGM. Federal detail pending |
Central bank position | Cloud in the Kingdom in principle; SAMA approval for cloud abroad | Master System of Record stored in the UAE |
AML record retention | 10 years | 5 years |
A group onboarding customers in both countries cannot copy one setup to the other.
Read also: UAE data residency for KYC data

Choosing a KYC vendor for Saudi operations: what to check
Ask where the data is stored, where it is processed and who can reach it. A hosting region answers only the first.
Use this checklist in vendor due diligence:
Hosting region and backups. Where do production data, backups and disaster recovery copies sit? Is the region fixed in the contract?
Sub-processors. Which third parties handle document checks, biometrics, OCR and screening data, and where?
Support access. From which countries can vendor staff view customer records? Is access logged and time-limited?
Encryption keys. Who holds them, and where are they stored?
AI and model processing. Where do the models run? Is your customers' data used for training? SAMA's framework bars secondary use of the institution's data.
Logs and telemetry. Do monitoring tools export personal data to another region?
SAMA approval documentation. Can the vendor supply the architecture, security and contract evidence your approval request needs?
PDPL transfer safeguards. If anything leaves the Kingdom: SDAIA standard contractual clauses, a transfer risk assessment and a map of onward transfers.
Exit, return and deletion. Can you export every record in a usable format, and how is deletion evidenced?
Ten-year retrieval. How fast can a complete customer file be produced for a regulator, and who holds the records after the contract ends?
Readiness for the draft. Can the vendor move storage into the Kingdom, and how quickly?
Read also: Best identity verification software

Know Who Is Your Customer
Screen transactions and entities against over 1,400 global sanctions, Politically Exposed Persons (PEPs), and adverse media watchlists. Safeguard your business.
Example: a Saudi finance company choosing a KYC vendor
This scenario is illustrative.
A SAMA-licensed finance company shortlists two vendors. Vendor A hosts in a cloud region in Saudi Arabia. Vendor B hosts in the EU and has signed SDAIA's standard contractual clauses.
Vendor B has dealt with the PDPL. It has not dealt with SAMA: the company would need explicit approval for cloud outside the Kingdom, with no guarantee of getting it.
Vendor A still needs SAMA approval, because cloud use requires it wherever the servers are.
Follow-up questions also show that its biometric check runs through a sub-processor abroad. That transfer needs PDPL safeguards and belongs in the approval file.
The lesson: "hosted in Saudi Arabia" is the first question, not the last.
How azakaw handles data security
azakaw is an AI-powered compliance platform covering KYC, KYB, screening, risk scoring, transaction monitoring and case management.
Customer data on the platform is protected with encryption, secure authentication and role-based access controls. The platform also supports jurisdiction-specific configuration. For Saudi clients, hosting is in Saudi Arabia.
Data location is a question we expect in every Saudi evaluation, and the right answer depends on your licence and regulator.

Scale with Confidence
Ensure you comply with all data AML requirements to scale your business with confidence. Ask us about hosting, security and data handling for your jurisdiction.
Frequently asked questions
Is there a data localisation law in Saudi Arabia?
Not a general one in force. The PDPL regulates transfers and does not mandate local storage.
Localisation comes from sector rules, mainly SAMA's for financial institutions, the CMA's guidelines and the rules for government data. SDAIA's October 2026 draft would add a general storage duty for all controllers.
Can a Saudi bank use AWS, Azure or Google Cloud regions outside the Kingdom?
Only with explicit SAMA approval. The Cyber Security Framework says that, in principle, only cloud services located in Saudi Arabia should be used.
Choosing an in-Kingdom region does not remove the approval step: SAMA approval is required before using cloud services at all.
Does the PDPL apply to companies outside Saudi Arabia?
Yes. It covers the processing of personal data of individuals residing in the Kingdom by parties outside it.
A UAE or European firm onboarding Saudi residents is in scope, and SDAIA opened its registration platform to foreign controllers in 2026.
Who regulates data protection in Saudi Arabia?
SDAIA supervises and enforces the PDPL. SAMA and the CMA regulate how their licensees use cloud and outsourcing.
The NCA sets cybersecurity controls for government and critical infrastructure, and the CST regulates cloud providers. A bank answers to several of them at once.
Does encrypting data make an offshore copy acceptable?
No. Encryption reduces risk. It does not change where the data is.
An encrypted backup outside the Kingdom is still a transfer under the PDPL and, for a SAMA Member Organisation, still cloud use outside Saudi Arabia.
Conclusion
Where KYC data must be stored in Saudi Arabia depends on who regulates you. SAMA-regulated institutions should plan for in-Kingdom cloud or explicit approval, capital market institutions should read the CMA guidelines, and everyone else follows the PDPL transfer rules.
A general storage-in-Kingdom duty is proposed but not yet in force, and AML law expects records to be kept for at least 10 years and produced on request.
Start by mapping which rules apply to your entity. Then ask every vendor where the data is stored, where it is processed, who can reach it and how quickly storage could move into the Kingdom.

Enterprise Compliance, Simplified
Detect, prevent, and resolve suspicious activities in real-time with azakaw’s AI-powered AML solution. Adopt a smarter and faster monitoring system that reduces false positives.
Related articles
Sources
Saudi Central Bank (SAMA), Cyber Security Framework, sections 3.4.2 Outsourcing and 3.4.3 Cloud Computing (SAMA Rulebook)
Personal Data Protection Law (Royal Decree M/19 of 1443H, as amended) and its Implementing Regulation
SDAIA, Regulation on Personal Data Transfer outside the Kingdom, Standard Contractual Clauses and Risk Assessment Guideline (February 2025)
SDAIA, draft amendments to the PDPL Implementing Regulation (consultation 6 October to 5 November 2026)
Anti-Money Laundering Law (Royal Decree M/20 of 1439H), Article 12
National Cybersecurity Authority, ECC-2:2024 and CCC-2:2024
Communications, Space and Technology Commission, Cloud Computing Regulatory Framework
Capital Market Authority, Cybersecurity Guidelines for Capital Market Institutions
Legal analysis: Akin, Al Tamimi, Clyde & Co, Clifford Chance, CMS, HFW, Hunton, King & Spalding, Morgan Lewis, Pinsent Masons
This content is provided for general informational purposes and does not constitute legal or regulatory advice. Data protection, data localisation and AML record-keeping requirements in Saudi Arabia vary by sector, licence and regulator, and some of the rules described here are in draft and may change. Organisations should consult the applicable legislation, regulator guidance and qualified legal or compliance professionals before making hosting or outsourcing decisions.






