Saudi PDPL compliance, run as an operating discipline
SDAIA supervises enforcement, and the records it asks for are the ones most programmes lack. Govrly connects your data inventory, processing activities, lawful bases, transfer records, and rights requests to the same governance platform that runs your cybersecurity program — so privacy is evidenced continuously, not reconstructed under investigation.
This page reflects how we see these requirements applied in practice. It is not an official reference. The authoritative source is the current document published by SDAIA, which may be revised — confirm what applies to your organisation against it and with your own advisers.
What is the Saudi PDPL?
From the compliance programmes we build and run in Saudi Arabia: the Saudi PDPL is the Kingdom's Personal Data Protection Law, issued under Royal Decree M/19 in September 2021 and amended by Royal Decree M/148 in March 2023. It governs how any organisation collects, processes, stores, and transfers the personal data of individuals in Saudi Arabia, and is enforced by SDAIA.
Two sets of regulations sit beneath the law: the Implementing Regulations and the Personal Data Transfer Regulations, both published by SDAIA on 7 September 2023. Together they set out what compliance actually requires in practice — the lawful bases, the registration obligation, the transfer conditions, and the records a controller must be able to produce.
The Saudi PDPL applies extraterritorially. Any organisation processing the personal data of individuals residing in the Kingdom falls within scope, whether or not it has a presence in Saudi Arabia. For international companies, that makes it a market-access requirement rather than a local formality.
The Saudi PDPL is now actively enforced
This is the material difference between the PDPL and a framework you self-assess against. There is a regulator, there are committees, and there are decisions on record.
The Saudi Data and Artificial Intelligence Authority supervises and enforces the PDPL through the National Data Governance Platform. It can request compliance documentation, conduct inspections, and act on data subject complaints.
Violations are reviewed by the Committees for Reviewing Violations of the PDPL and its Implementing Regulations, which operate under published rules of procedure covering complaints, hearings, and the issuance of decisions.
SDAIA announced in early 2026 that dozens of enforcement decisions had been issued over the preceding year, across multiple sectors. The common findings were basic: processing without a valid lawful basis, unauthorised disclosure, and inadequate security measures.
SDAIA can order corrective measures and suspend processing activities. For an organisation whose service depends on processing personal data, a suspension is the more serious outcome.
What Saudi PDPL compliance requires
Eight obligations account for most enforcement findings. Each one produces records a controller must be able to retrieve on request.
Consent is the default basis under the Saudi PDPL. Where you rely on something else, the basis must be identified, documented, and defensible per processing activity — not assumed across the organisation.
A maintained inventory of what data you hold, why, on what basis, who it is shared with, and how long it is retained. This is the single artefact most often missing when an investigation opens.
Controllers are required to register on the National Data Governance Platform and keep those particulars current.
Rights of access, correction, deletion, and portability, alongside the right to be informed. Requests must be answered within 30 days, and both the request and the response need logging.
SDAIA must be notified within 72 hours of becoming aware of a breach. That window is unforgiving without a rehearsed process and a maintained contact path.
Transfers outside the Kingdom are subject to conditions under the Personal Data Transfer Regulations, including risk assessment where required. Transfer decisions must be recorded and justifiable.
Sensitive categories attract heightened obligations and the criminal exposure above. They need to be identified in the inventory before they can be protected differently.
Certain controllers are required to appoint a DPO. Where the obligation applies, the appointment and the officer's independence need to be evidenced.
Running PDPL obligations in Govrly

- A.
- Records of processingWhat personal data you hold, where, why, on what lawful basis, shared with whom, and for how long — maintained as a live record rather than an annual spreadsheet exercise.
- B.
- A clock that is actually trackedRequests logged from intake, routed to an owner, tracked against the 30-day deadline, and closed with a record of exactly what was provided.
- C.
- 72 hours, with the reasoning keptIncidents assessed against the notification threshold within the window, and the decision reasoning preserved rather than reconstructed months later when someone asks why you did or did not notify.
- D.
- A register, not a memoryDestination, data categories, mechanism and the assessment behind each decision — including transfers made by processors acting on your behalf.
- E.
- Privacy and security, onceThe access control, encryption and logging your PDPL obligations depend on are the same records carrying your ECC or CSF requirements. One implementation, one evidence set, two obligations.
- F.
- Enforced, not just definedPeriods set per processing activity, with the evidence that data was actually deleted when they expired.
Why Saudi PDPL programs fail an investigation
Enforcement findings so far have not turned on sophisticated legal argument. They have turned on missing records.
- 01/06The privacy notice exists but the inventory doesn't
A published notice describes what the organisation intends to do. Without a records-of-processing inventory, nothing proves what it actually does.
- 02/06Consent was collected but not evidenced
Marketing consent in particular needs to be demonstrable — who consented, to what, and when. An unlogged consent is functionally the same as no consent.
- 03/06The 72-hour clock starts before anyone realises
Awareness of a breach begins at the operational level, not when it reaches the privacy team. Without an escalation path, the window closes during internal triage.
- 04/06Rights requests arrive through unmonitored channels
A request sent to a general inbox still starts the 30-day clock. Missed requests generate complaints, and complaints are how many investigations begin.
- 05/06Transfers happen through vendors nobody mapped
A processor moving data outside the Kingdom is still your transfer. Without a vendor inventory linked to data categories, this is invisible until it is discovered externally.
- 06/06Privacy sits apart from the security program
The technical and organisational measures the PDPL requires are the same controls your cybersecurity framework already governs. Running them as separate programs produces two incomplete evidence sets instead of one complete one.
How Govrly runs Saudi PDPL compliance
Privacy records live alongside your controls, risks, vendors, and evidence, because the PDPL asks you to prove the same safeguards your security framework already governs.
What you hold, where it sits, why you process it, the lawful basis, retention, and recipients — maintained as a live record rather than an annual spreadsheet exercise.
Requests logged from intake, routed to an owner, tracked against the 30-day deadline, and closed with a record of what was provided.
Incidents raised, assessed against the notification threshold, and tracked against the 72-hour window with the decision reasoning preserved.
Transfers recorded against destination, mechanism, data categories, and the assessment behind the decision — retrievable when SDAIA asks.
Vendor inventory with agreements, assessments, and the data categories each processor touches, linked to the controls their access affects.
The technical and organisational measures behind PDPL Article obligations are the same controls carrying your NCA ECC or SAMA CSF requirements. Implement once, evidence once, satisfy both.
Saudi PDPL vs GDPR
Organisations with an established GDPR program have a genuine head start — but the differences are not cosmetic, and assuming equivalence is how gaps get missed.
| Feature | Saudi PDPL | GDPR |
|---|---|---|
| Regulator | SDAIA | National supervisory authorities |
| Default lawful basis | Consent | Six bases of equal standing |
| Registration | Controllers register with the regulator | No general registration requirement |
| Breach notification | 72 hours to SDAIA | 72 hours to the supervisory authority |
| Rights response time | 30 days | One month, extendable |
| Administrative fines | Administrative fines, escalating on repeat | Administrative fines with a higher ceiling |
| Criminal liability | Yes, for sensitive data disclosure with intent | Member-state dependent |
| Managed in Govrly | Yes | Yes |
A practical path to Saudi PDPL compliance
Because enforcement is already active, sequence matters. Start with the records that an investigation would ask for first.
- 01/07Map what you actually hold
Build the data inventory before anything else. Every other obligation depends on knowing what personal data exists, where, and why.
- 02/07Establish and document lawful bases
Per processing activity, not per department. Where consent is the basis, confirm it is captured in a form you could evidence.
- 03/07Register and appoint
Complete controller registration, and appoint a DPO where the obligation applies.
- 04/07Stand up the rights workflow
A monitored intake channel, an owner, and a tracked 30-day clock. Test it with an internal request before a real one arrives.
- 05/07Rehearse the 72-hour path
Define what triggers assessment, who decides, and how SDAIA is notified. A tabletop exercise here is worth more than a written procedure alone.
- 06/07Bring transfers and vendors into scope
Record every cross-border transfer with its mechanism and assessment, and map which processors touch which data categories.
- 07/07Connect privacy to the security program
Link the technical and organisational measures to the controls already governed under your cybersecurity framework, so one evidence set serves both.
Processing records, lawful bases, rights requests and breach decisions sit alongside the access control, encryption and logging that protect them — because the safeguards the law expects are the controls your cybersecurity framework already governs.
Saudi PDPL FAQs
The Saudi PDPL is the Kingdom's Personal Data Protection Law, issued under Royal Decree M/19 in September 2021 and amended by Royal Decree M/148 in March 2023. It came into force on 14 September 2023 and governs how organisations collect, process, store, and transfer the personal data of individuals in Saudi Arabia. It is enforced by SDAIA.
SDAIA supervises enforcement of the law. Confirm the current enforcement position and any obligations specific to your organisation with SDAIA and your own advisers. SDAIA announced in early 2026 that dozens of decisions had been issued against organisations found in violation over the preceding year, across multiple sectors.
The law separates administrative violations from criminal conduct, and the consequences differ sharply — administrative fines that escalate on repeat violations, and materially heavier penalties where sensitive personal data is disclosed or transferred unlawfully with intent to cause harm or obtain benefit. Courts may also confiscate unlawful gains, and affected individuals may seek civil compensation separately. The specific figures are set out in the law and its implementing regulations and may be revised, so confirm what applies to your situation with your legal adviser.
Any organisation, public or private, that processes the personal data of individuals residing in Saudi Arabia. It applies extraterritorially, so organisations without a presence in the Kingdom are in scope if they process the data of people located there.
SDAIA must be notified within 72 hours of the organisation becoming aware of the breach. Where the breach may cause harm to the data subject, the individual must also be notified.
Thirty days. Both the request and the response is best logged, so the organisation can demonstrate that requests were received, handled, and answered within the period.
Consent is the default lawful basis under the Saudi PDPL, which differs from GDPR where six bases sit on equal footing. Alternative bases exist, but where an organisation relies on one it should identify and document that basis for the specific processing activity rather than assuming it applies broadly.
Yes. Cross-border transfers are governed by the Personal Data Transfer Regulations, which set conditions on when and how personal data may leave the Kingdom, including assessment requirements in defined circumstances. Transfer decisions and their justification is best recorded.
Certain controllers are required to appoint a DPO. Where the obligation applies, the appointment should be documented along with the officer's role and independence.
Yes. Controls, measures, and evidence are shared objects in Govrly, so the technical and organisational safeguards behind PDPL obligations can carry the corresponding NCA ECC, SAMA CSF, and ISO 27001:2022 requirements at the same time, with privacy records held alongside the wider governance program.
Have the records ready before SDAIA asks
Data inventory, lawful bases, transfers, rights requests, and breach decisions — connected to the controls that back them.
