Saudi PDPL Draft Would Store Personal Data in the Kingdom

The window for comments closed on 5 November 2026, and the draft now sits with the regulator. Saudi Arabia’s Data and Artificial Intelligence Authority, which supervises the Kingdom’s Personal Data Protection Law, published proposed amendments to the law’s Implementing Regulations on 6 October 2026 and collected feedback through its public consultation platform until 5 November. Buried among the ten or so headline changes is the one with the largest architectural consequence: a new provision, drafted as Article 23(2), that would require data controllers to store personal data inside the Kingdom. If adopted, the amended regulations take effect sixty days after publication in the Official Gazette, and as of mid-November no approved text had appeared there. The current rules still govern today. The draft is the version to plan against.

What the draft would change

The storage clause is short, and its brevity is the problem. As drafted, controllers must store personal data within the Kingdom, while personal data may still be transferred or disclosed outside it in accordance with the law and its transfer regulations. Two readings compete. One treats the clause as a baseline storage duty with lawful transfer as the exception, which would push multinationals toward maintaining an in-Kingdom copy of Saudi personal data. The other reads it as a restatement of the status quo, where offshore hosting remains fine provided transfers rest on a lawful basis. Law firm analyses from Reed Smith and Pinsent Masons flag the ambiguity in almost identical terms, and both advise resolving it during consultation rather than after the text hardens. For a software vendor whose production database runs in another country, the distance between the two readings is a replica database on one side and a re-hosted architecture on the other.

The breach notification regime tightens in parallel. Today, a controller notifies the authority within 72 hours where an incident potentially harms data subjects or conflicts with their interests. The draft removes that threshold, so the 72-hour clock would apply to any breach, damage or unauthorised access, while the separate harm test for notifying affected individuals stays in place. Registration obligations also move directly into the regulations, with mandatory registration for public entities, controllers whose core activity requires processing, controllers handling sensitive data, and, notably, controllers that transfer personal data outside the Kingdom. That last trigger could pull a substantial population of internationally active companies onto the national register for the first time.

The remaining changes are shorter but not trivial. A new provision would require responses to authority requests within twenty business days, with extensions granted at the regulator’s discretion. Records of processing activities would need to be kept for the life of the processing plus five further years. Impact assessments would be restructured around clearer triggers, including sensitive data, large-scale or systematic monitoring, and the use of undefined “emerging technologies”, a phrase whose breadth concerns legal commentators, since reading it to cover artificial intelligence as a category would make assessments routine for ordinary deployments. Privacy information would need to be provided in clear, simplified language consistent with the language customarily used for the relevant products or services.

Individual-rights mechanics get tidied as well. The statutory 30-day window for answering a data subject request would stay, but an unanswered request could be deemed rejected, opening the path to a complaint with the authority. The current 90-day limit on filing such complaints would be removed in the draft, and consent requirements would be refined so that consent comes from a person with full legal capacity and is not obtained through misleading means. Marketing rules tighten too: the draft strengthens withdrawal and opt-out requirements for promotional messages, which lands on any business running consent-based campaigns into the Kingdom.

One further signal sits outside this consultation. In July 2026 the authority consulted separately on draft guidelines for licensing entities that audit and inspect personal data processing, a step compliance analysts read as preparation for independent audits to become a routine procurement question. Combined with the draft’s registration and response deadlines, the direction of travel is a framework that assumes evidence on demand rather than policies on file.

The state of play behind the draft

The framework this amends is young and already enforced. The law itself took force in September 2023 and became fully binding in September 2024 after a one-year grace period. Its maximum fine stands at 5 million Saudi riyals per violation, doubled for repeat offences. Enforcement is not hypothetical: the authority’s violation committees issued 48 penalty decisions in the year to mid-January 2026, covering unlawful collection, disclosure without justification and marketing messages sent without consent, figures the Saudi Press Agency reported in January. A regulator that has already built an enforcement record is drafting with confidence, and the draft’s tight sixty-day effective window after publication assumes organisations have been watching.

Sector overlays do not wait for the amendment

Parts of the economy already operate under stricter location rules than the draft would impose on everyone else. Government data must sit with a registered provider and may not leave the Kingdom for any purpose, including temporary caching or backup, unless another law expressly allows it. Banks and other financial institutions face central bank guidance that says public and hybrid cloud should in principle use only services located in the Kingdom, with explicit approval required to use a service abroad. Cybersecurity controls for data centres add a staffing layer, with roles at provider facilities reserved for qualified Saudi nationals at the three higher data classification levels. A cloud vendor reading only the draft storage clause would underestimate what its regulated customers already require, and the gap between the general regime and these sector regimes is where scoping mistakes happen.

What cloud and software teams should re-plan

The practical work divides into architecture and contracts. On architecture, the options in order of cost are an in-Kingdom hosting region for Saudi personal data, a split design that keeps the authoritative store inside the Kingdom with controlled replication for processing elsewhere, and hybrid models that pair local primary storage with offshore analytics under documented transfer bases. Keeping encryption keys in the Kingdom strengthens the residency argument regardless of which model wins. On contracts, residency commitments need to flow down to subprocessors, breach support timelines need to fit the tightened notification clock, and acquisition teams should add hosting footprint to diligence checklists, since remediation after closing is slower and pricier than a pre-signing warranty.

Timing is the other variable. If the final text follows the draft, the interval between Official Gazette publication and effect is sixty days, which is enough to switch a region selector and not enough to rebuild a platform. Organisations that map their Saudi data flows now, inventory which systems hold personal data of residents, and pre-negotiate local hosting capacity will treat the publication date as a switch they flip. Those that wait for the Gazette to start planning will be reading the final text while their deadline runs.

The grey areas worth watching

Three questions will shape the real compliance load. Whether an in-Kingdom copy satisfies the storage duty or the authoritative store itself must move. What “storage” means where processing spans distributed stacks, content delivery caches and vendor-managed backups. And how far “emerging technologies” reaches, since an expansive reading would fold routine software into impact-assessment obligations. None of these is settled in the draft. All of them were open for comment until 5 November, which is the constructive part of the story: the authority published its thinking early, collected structured feedback, and the organisations that engaged now hold a documented position. The final text, whenever it lands, will reward the teams that spent November on data-flow maps rather than on speculation.

Sources

  • Sumrite 🔗, “Saudi PDPL Compliance Guide 2026: Enforcement Is Now Live” (accessed 2026-11-19).
  • Akin Gump 🔗, “Saudi Data and AI Authority Proposes Amendments to Implementing Regulations of the PDPL – 10 Key Proposed Changes” (accessed 2026-11-19).
  • Reed Smith 🔗, “SDAIA Consults on Extensive Amendments to the Saudi PDPL Implementing Regulation” (accessed 2026-11-19).
  • Pinsent Masons 🔗, “Saudi consultation proposes data protection reform” (accessed 2026-11-19).
  • Legal 500 🔗, “Saudi Arabia’s Proposed PDPL Implementing Regulation Amendments: What Businesses Deploying AI, Cloud And Data-driven Technologies Need To Know” (accessed 2026-11-19).
  • Zamakhchary Legal Services 🔗, “Saudi Arabia’s cloud computing zone: two decisions for technology and data groups run from abroad” (accessed 2026-11-19).
  • Global Law Experts 🔗, “Saudi Arabia’s PDPL Implementing Regulations, What M&A, Cloud and SaaS Teams Must Do Now” (accessed 2026-11-19).

This article was prepared by the expert team at Global Infinity Labs, drawing on insights and data provided through its MCP data services.

About Global Infinity Labs

Global Infinity Labs is an AI innovation company specializing in MCP data services.

Email: support@globalinfinitylabs.com

To share industry insights, report corrections, or submit story tips: editors@globalinfinitylabs.com or https://www.globalinfinitylabs.com/submit.