Law · Privacy · Saudi Arabia
Saudi PDPL compliance: obligations, transfers and penalties
Saudi PDPL compliance means meeting Saudi Arabia's Personal Data Protection Law, enforced by SDAIA. It has applied since 14 September 2023 and became fully enforceable after the grace period ended on 14 September 2024, with breach notification within 72 hours and fines of up to SAR 5 million per violation.
What you need to know about Saudi PDPL
Who must comply with the Saudi PDPL?
Organisations processing personal data in Saudi Arabia, or about people residing there.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What does the Saudi PDPL require?
The Saudi PDPL requires a lawful basis, clear privacy notices, security measures, records of processing, 72-hour breach notification to SDAIA, impact assessments, controlled transfers abroad and respect for data subject rights.
Lawful processing
Consent or listed cases.
In QULDEX: Basis per purposePrivacy policy
Inform at collection.
In QULDEX: Notice versionsSecurity and breaches
72-hour notice to SDAIA.
In QULDEX: Breach timersImpact assessments
For products and services.
In QULDEX: Assessment workflowTransfers abroad
Transfer Regulation conditions.
In QULDEX: Transfer registerData subject rights
Access, copy, correct, destroy.
In QULDEX: Request logWhich Saudi PDPL articles matter most?
These 14 provisions carry the obligations most organisations work on. Select any one to see what it requires, typical evidence and the matching GDPR article.
Showing up to 6 per group. Search, filter, or open a group to see all 14.
Scope 2
Art. 2ScopeApplies to processing of personal data in the Kingdom, and to processing outside it of personal data of people residing in the Kingdom.
In QULDEXQULDEX gives this obligation an owner, evidence requests and a review date, and maps it to GDPR and ISO 27701.
- Maps to
- GDPR Art. 3
Art. 1Sensitive dataDiffers from GDPRSensitive data includes racial or ethnic origin, religious belief, criminal records, biometric, genetic, health, credit and location data.
In QULDEXSensitive data is tagged in the record of processing.
Lawful processing 3
Art. 5–6Consent and other basesProcess with consent, or under listed cases such as legitimate interest (except sensitive data), legal obligation or vital interest.
In QULDEXEach purpose records its basis.
- Typical evidence
- Purpose register
- Maps to
- GDPR Art. 6
Art. 11Purpose and minimisationCollect only what is needed for a specified, legitimate purpose.
In QULDEXQULDEX gives this obligation an owner, evidence requests and a review date, and maps it to GDPR and ISO 27701.
- Maps to
- GDPR Art. 5
Art. 12–13Privacy policy and noticePublish a privacy policy and inform data subjects when collecting their data.
In QULDEXQULDEX gives this obligation an owner, evidence requests and a review date, and maps it to GDPR and ISO 27701.
- Typical evidence
- Privacy policy
- Maps to
- GDPR Art. 13
Obligations 6
Art. 8ProcessorsChoose processors that give sufficient guarantees and check their compliance.
In QULDEXEach processor is linked to its contract and checks.
- Typical evidence
- Processor contracts
- Maps to
- GDPR Art. 28
Art. 19Security measuresApply organisational, administrative and technical measures to protect personal data.
In QULDEXSecurity controls are reused from ISO 27001 and NCA ECC.
- Typical evidence
- Security evidence
- Maps to
- GDPR Art. 32NCA ECC
Art. 20Breach notificationNotify SDAIA of a breach that may harm data subjects, within 72 hours under the Implementing Regulations, and inform data subjects where required.
In QULDEXBreaches start a 72-hour timer.
- Typical evidence
- Breach register
- Maps to
- GDPR Art. 33–34
Art. 22Impact assessmentAssess the impact of processing on data subjects for products and services.
In QULDEXImpact assessments run with sign-off.
- Typical evidence
- Impact assessments
- Maps to
- GDPR Art. 35
Art. 30Data protection officerAppoint a DPO in the cases set by the Implementing Regulations, such as public bodies, large-scale sensitive data or systematic monitoring.
In QULDEXQULDEX gives this obligation an owner, evidence requests and a review date, and maps it to GDPR and ISO 27701.
- Typical evidence
- DPO appointment
- Maps to
- GDPR Art. 37
Art. 31Records of processingKeep records of processing activities for the retention period.
In QULDEXThe record of processing is kept per activity.
- Typical evidence
- Record of processing
- Maps to
- GDPR Art. 30
Rights 1
Art. 4Data subject rightsRights to be informed, to access, to obtain a copy, to correct, and to destroy personal data.
In QULDEXRequests are logged with deadlines.
- Typical evidence
- Request log
- Maps to
- GDPR Art. 15–17
Transfers 1
Art. 29Transfers outside the KingdomTransfer only under the conditions in the law and the Personal Data Transfer Regulation, such as adequate protection or appropriate safeguards.
In QULDEXTransfers record destination and basis.
- Typical evidence
- Transfer register
- Maps to
- GDPR Art. 44–49
Enforcement 1
Art. 35–36PenaltiesAdministrative fines up to SAR 5 million per violation, doubled for repeat violations; disclosing sensitive data unlawfully can bring up to 2 years in prison or a SAR 3 million fine.
In QULDEXQULDEX gives this obligation an owner, evidence requests and a review date, and maps it to GDPR and ISO 27701.
Nothing matches that search.
Article numbers follow the PDPL as amended; details sit in the Implementing Regulations and the Transfer Regulation. Summaries are QULDEX paraphrases, not legal advice.
How do you comply with the Saudi PDPL?
Map processing, fix notices and bases, set up breach and rights processes, and document every transfer abroad. Most organisations need 3 to 6 months, less with a GDPR programme.
Map processing and sensitive data
Record purposes, data, bases, processors and transfers.
Notices and bases
Publish the privacy policy, capture consent, record other bases.
Breach and rights processes
72-hour notice to SDAIA and request handling.
Transfers abroad
Assess each transfer under the Transfer Regulation.
DPO and impact assessments
Appoint a DPO where required and assess high-impact processing.
Keep it current
Every breachNotify within 72 hoursOn changeRe-assess impactYearlyReview the programme
Durations are QULDEX planning ranges.
Which records does the Saudi PDPL need?
SDAIA expects these records.
| Record | Article | Where it lives in QULDEX |
|---|---|---|
| Record of processing | Art. 31 | Risk register |
| Privacy policy and notices | Art. 12–13 | Policy library |
| Consent logs | Art. 5–6 | Evidence vault |
| Processor contracts and checks | Art. 8 | Vendor register |
| Breach register and notifications | Art. 20 | CAPA automation |
| Impact assessments | Art. 22 | Audit workspace |
| DPO appointment | Art. 30 | Policy library |
| Transfer assessments | Art. 29 | Vendor register |
| Rights request log | Art. 4 | Evidence vault |
Record names are QULDEX recommendations based on the PDPL and its regulations.
How long does Saudi PDPL compliance take and what drives the effort?
Most organisations need 3 to 6 months. Sensitive data, transfers abroad and processor numbers drive the effort.
Where the time goes
Bars show the upper end of each range on one scale (6 months = full width).
What changes the effort
- Sensitive data: credit, health and location data need extra care
- Transfers abroad: cloud and group transfers need assessment
- Processors: every processor needs checks
- Existing GDPR programme: much carries over
- NCA ECC in place: covers security measures
How ready are you for the Saudi PDPL?
Check these eight things first. Nothing you enter leaves this page.
How the Saudi PDPL maps to GDPR, the UAE PDPL and NCA ECC
The Saudi PDPL shares GDPR's building blocks but treats more data as sensitive and regulates transfers through its own regulation. NCA ECC evidence covers the security measures.
Saudi PDPL vs GDPR at a glance
| Saudi PDPL | GDPR | |
|---|---|---|
| Regulator | SDAIA | National supervisory authorities |
| Breach notice | 72 hours to SDAIA | 72 hours to the authority |
| Sensitive data | Includes credit and location data | Special categories, no credit data |
| Transfers | Transfer Regulation conditions | Adequacy, SCCs, BCRs |
| Penalties | Up to SAR 5 million, doubled for repeats; prison for sensitive data disclosure | Up to €20m or 4% of turnover |
| In QULDEX | QULDEX maps each process to both laws, so one privacy programme serves Saudi Arabia and the EU. | |
Privacy crosswalk
| Saudi PDPL | GDPR | UAE PDPL | NCA ECC-2:2024 | Shared evidence |
|---|---|---|---|---|
| Art. 5–6 Basis | Art. 6 | Art. 4 | — | Purpose register |
| Art. 8 Processors | Art. 28 | Art. 8 | 4-1 | Contracts |
| Art. 19 Security | Art. 32 | Art. 20 | Domain 2 | Security evidence |
| Art. 20 Breach | Art. 33–34 | Art. 9 | 2-13 | Breach register |
| Art. 22 Impact | Art. 35 | Art. 21 | 1-5 | Assessments |
| Art. 29 Transfers | Art. 44–49 | Art. 22–23 | 4-2 | Transfer register |
| Art. 31 Records | Art. 30 | Art. 7 | — | Record of processing |
Indicative mapping for planning, not legal advice.
How QULDEX runs Saudi PDPL compliance from data map to SDAIA review
QULDEX is Saudi PDPL compliance and audit management software built from EGV Group's audit delivery, used by controllers, their DPOs and privacy auditors. Pick your role to see who does what.
For organisations processing personal data in Saudi Arabia.
- MapRecord processingRecord of processing
- NoticeFix noticesPolicy versions and consent logs
- BreachesNotify SDAIA in 72 hoursBreach timers
- TransfersAssess transfersTransfer register
- AssessRun impact assessmentsAssessment workflow
- AuditProve complianceControlled evidence sharing
For DPOs and privacy consultants.
- MapRun the gap assessmentA reusable PDPL gap template
- NoticeAdviseTemplates
- BreachesDecide and notifyDecision records
- TransfersCheck conditionsStatus per transfer
- AssessReviewSign-off
- AuditPrepare the packAn audit-ready pack
For independent privacy auditors.
- MapPlanScope in a standard format
- NoticeReviewView-only access
- BreachesReviewIncident history
- TransfersTestTransfer evidence
- AssessSampleView-only evidence with download control and an access log
- AuditAuditFindings into CAPA
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →Saudi PDPL questions people ask
When did the Saudi PDPL come into force?
It came into force on 14 September 2023, with a one-year grace period that ended on 14 September 2024. Since then it has been fully enforceable.
Who enforces the Saudi PDPL?
The Saudi Data and Artificial Intelligence Authority (SDAIA). Its violation review committees issued 48 decisions confirming violations by January 2026.
What are the Saudi PDPL penalties?
Administrative fines of up to SAR 5 million per violation, which can be doubled for repeat violations. Unlawfully disclosing sensitive data can bring up to 2 years in prison or a fine of up to SAR 3 million.
How fast must breaches be reported?
Within 72 hours of becoming aware of a breach that may harm data subjects, under the Implementing Regulations, with data subjects informed where required.
Can personal data be transferred outside Saudi Arabia?
Yes, under the conditions in the PDPL and the Personal Data Transfer Regulation, such as adequate protection in the destination or appropriate safeguards.
Go deeper on Saudi PDPL
GCC compliance topic hub
NCA ECC, SAMA CSF, UAE IAS and Gulf data protection laws.
blog.quldex.comData privacy topic hub
GDPR, ISO 27701 and privacy-law comparisons.
blog.quldex.comAudit evidence naming convention
A file-naming scheme auditors can follow.
blog.quldex.comAudit sampling size for compliance
How many samples auditors look at.
References
- Personal Data Protection Law, Royal Decree M/19 (2021), as amended by Royal Decree M/148 (2023). sdaia.gov.sa
- PDPL Implementing Regulations and Personal Data Transfer Regulation, SDAIA. sdaia.gov.sa
- Saudi Press Agency on SDAIA violation decisions, Jan 2026. spa.gov.sa
- EU GDPR, Regulation (EU) 2016/679. eur-lex.europa.eu
Reviewed by
Page history
- : Page first built: article explorer, transfers, penalties, readiness check and GDPR comparison
Be ready for an SDAIA review
Answer a short readiness check and get a gap summary by article. No sales call needed to see the result.