Saudi PDPL Amendments 2026: Data Localisation Explained

ApexlyTech Team 8 min read
Saudi PDPL Amendments 2026: Data Localisation Explained

In short: The Saudi PDPL amendments that the Saudi Data and Artificial Intelligence Authority (SDAIA) published for consultation on 6 October 2026 would, for the first time, require controllers to store personal data inside Saudi Arabia, while still allowing lawful transfers abroad. The draft would also make breach reports to SDAIA mandatory whether or not harm is likely, and make registration on the National Register of Controllers compulsory for more organisations. The consultation closes on 5 November 2026; nothing is in force yet, but any SaaS, ERP, CRM or app that holds Saudi residents' data should map where that data sits now.

Key takeaways

  • As of 3 November 2026 the amendments are a draft. If approved, they take effect 60 days after publication in the Official Gazette, according to Clyde & Co and Reed Smith.
  • Draft Article 23(2) would require controllers to store personal data within the Kingdom. Transfers and disclosures outside Saudi Arabia would remain possible under the existing transfer rules.
  • Draft Article 24 would remove the "likely harm" test for notifying SDAIA of a breach; the 72-hour reporting deadline stays.
  • Registration with the National Register of Controllers would become mandatory for, among others, any controller that transfers personal data outside Saudi Arabia.
  • A new 20-business-day deadline would apply to answering SDAIA's requests.

What is the Saudi PDPL?

The Personal Data Protection Law (PDPL) is Saudi Arabia's general data protection law, issued by Royal Decree No. M/19 of 16 September 2021 and in force since 14 September 2023, with a one-year grace period that ended on 14 September 2024. SDAIA is the regulator. The PDPL is applied through an Implementing Regulation, which is the text the October 2026 draft amends. A controller is the organisation that decides why and how personal data is processed; a processor acts on the controller's behalf.

This guide is written by the ApexlyTech team at Apexly Technologies (Pvt) Ltd, which builds custom software, SaaS platforms, ERP and CRM systems and cloud deployments for clients in Pakistan, the Gulf and elsewhere. It summarises the proposals; it is not legal advice.

What do the Saudi PDPL amendments propose?

The Saudi PDPL amendments change about a dozen articles of the Implementing Regulation. The table summarises the ones with the most effect on software and data teams, as described by Clyde & Co, Reed Smith and Pinsent Masons in October 2026.

AreaTodayProposed
Where data is stored (Art. 23)No general in-Kingdom storage ruleControllers must store personal data within the Kingdom; transfers abroad still permitted under the PDPL
Security (Art. 23(1))Security measures requiredEntities under National Cybersecurity Authority (NCA) standards follow them; others follow "recognized cybersecurity standards" and best practices
Breach notice to SDAIA (Art. 24)Within 72 hours where harm is likelyWithin 72 hours regardless of whether harm is likely
Impact assessments (Art. 25)Narrower triggersAlso required for minors' data, large-scale or systematic monitoring, "emerging technologies" and automated decisions affecting people
Register of Controllers (Art. 34)Separate SDAIA rulesMandatory for public entities, data-centred businesses, sensitive-data processors and anyone transferring data abroad
SDAIA requests (new Art. 36)New articleAnswer within 20 business days; extensions at SDAIA's discretion
Marketing (Arts. 28 and 29)Prior-relationship exceptionConsent verified and evidenced; on withdrawal, stop processing and destroy data derived from it

Does personal data have to be stored in Saudi Arabia?

Not under the current rules, but it would under the draft. Clyde & Co notes that today's framework has no general requirement to store personal data in the Kingdom. Draft Article 23(2) would require controllers to "store Personal Data within the Kingdom" while keeping transfers and disclosures abroad lawful. Reed Smith and Pinsent Masons both point out that the draft does not say whether a local copy is enough when data is also processed abroad, or how backups and replicas are treated. Expect that question in the final text or in SDAIA guidance.

What changes for PDPL breach notification?

The 72-hour clock stays, but the threshold would fall away. Under the draft, a controller would notify SDAIA within 72 hours of becoming aware of a personal data breach "regardless of whether harm is likely to result", according to Clyde & Co. Notifying the affected individuals would still depend on an assessment of damage. Pinsent Masons expects this to increase the number of reportable incidents significantly.

Who must register with the National Register of Controllers?

Under draft Article 34, registration through SDAIA's platform would be mandatory for public entities, controllers whose core activities require processing personal data, controllers processing sensitive data or data of people lacking legal capacity, and controllers that transfer or disclose personal data outside Saudi Arabia. Reed Smith reads this as reaching non-Saudi controllers too.

Other changes worth knowing

  • Data subject requests: the 30-day response period stays, extendable by up to 30 days; an unanswered request is deemed rejected and the person can complain to SDAIA.
  • Privacy policies: must be in clear, simplified language suited to the audience, which Clyde & Co expects will mean Arabic versions in practice.
  • Data Protection Officers: SDAIA's separate DPO rules would be folded into the Regulation; appointments must be documented and the DPO's contact details filed on SDAIA's platform.
  • Records of processing: Pinsent Masons reports they would be kept for five years after the activity ends, with SDAIA's templates removed.
  • Complaints: the 90-day limit for filing a complaint would be removed.

Who is affected?

The proposals matter to any organisation that processes personal data of people in Saudi Arabia, and Reed Smith reads the registration rule as reaching controllers outside the Kingdom too. The storage and registration proposals matter most to:

  • SaaS vendors whose Saudi customers' data sits in a cloud region outside the Kingdom.
  • Groups that run one ERP or CRM instance for the whole Gulf from the UAE, Bahrain or Europe.
  • Apps that send Saudi users' data to analytics, support desks, email platforms or AI model APIs hosted abroad, each of which may count as a transfer.
  • Outsourced development and support teams, including in Pakistan, that access production data remotely.

What should you do now? A preparation checklist

  1. Map where Saudi personal data lives. List every database, file store, backup, log pipeline, data warehouse and third-party service that holds it, with the hosting country for each.
  2. Separate storage from transfer in your map. Mark which systems store the primary copy and which only receive data, because the draft treats the two differently.
  3. Check in-Kingdom hosting options. Find out whether your cloud provider, database service and backup target offer a Saudi region, and what moving costs in effort and latency.
  4. Review your breach runbook. Assume every personal data breach will need a 72-hour notice to SDAIA and make sure detection, triage and reporting can meet that.
  5. Prepare for registration. If you transfer data abroad or your core business is data processing, collect what a registration would need: entity details, processing purposes, DPO contact and transfer destinations.
  6. Fix marketing consent records. Store when and how consent was given, and make withdrawal stop the processing and delete derived data, such as segments and scores.
  7. Add DPIA triggers to your change process. New AI features, automated decisions and monitoring should prompt an impact assessment before release.
  8. Watch for the final text. The rules would apply 60 days after Gazette publication, which is a short window for a hosting move.

Technical notes for engineering teams

If in-Kingdom storage is adopted, the cleanest design is usually tenant-level data residency: each customer's primary database and object storage live in a region chosen per tenant, with shared services (authentication, billing, monitoring) carrying as little personal data as possible. Keep logs and traces free of personal data where you can, because log pipelines often replicate to a central region. Check the defaults of managed backups and disaster recovery, which may copy data to a paired region in another country. For AI features, keep a record of which prompts contain personal data and where the model endpoint runs. For a wider view of hosting choices, see our guide to cloud migration.

How ApexlyTech can help

We design and build multi-region SaaS, ERP and CRM systems, and we can help you map where Saudi personal data flows, plan tenant-level residency, move workloads to an in-Kingdom region and add consent and breach-reporting features to your product. We are a software company, not a law firm, so we work alongside your legal adviser. See our cloud solutions and SaaS development services, or contact us.

Frequently asked questions

Are the Saudi PDPL amendments in force?

No. As of 3 November 2026 they are a draft published by SDAIA for public consultation, which runs from 6 October to 5 November 2026. If SDAIA approves them, the amended Implementing Regulation would take effect 60 days after its publication in the Official Gazette. The final text may differ from the draft.

Will the PDPL ban transferring data outside Saudi Arabia?

No. The draft keeps transfers and disclosures outside the Kingdom lawful where they meet the PDPL and its transfer rules. What it adds is a requirement to store personal data within the Kingdom. Commentators say it is not yet clear whether a local copy alongside processing abroad would satisfy that requirement.

How long do you have to report a data breach under the Saudi PDPL?

Seventy-two hours from becoming aware of it, both now and under the draft. The change is the threshold: the draft would require notifying SDAIA of every personal data breach regardless of whether harm is likely. Telling affected individuals would still depend on an assessment of the likely damage to them.

Do the Saudi PDPL amendments affect companies outside Saudi Arabia?

They can. Reed Smith's reading of the draft is that the mandatory registration rules would also reach controllers based outside Saudi Arabia, for example any controller that transfers or discloses personal data outside the Kingdom. Foreign SaaS vendors with Saudi users should therefore check the final text with Saudi-qualified counsel.

What should a SaaS company do before the final rules arrive?

Map every system that stores Saudi personal data and its hosting country, price an in-Kingdom region for primary storage and backups, update the breach runbook for a 72-hour notice to SDAIA, and tidy marketing consent records. These steps are useful whatever the final text says, and they shorten any later move.

Sources

All sources checked 3 November 2026. The draft text is published on SDAIA's consultation platform (Istitlaa), which could not be opened when checked, so the summary above relies on the three law firm analyses below.