Saudi PDPL Compliance Checklist for IT Teams: What to Do First
In this article
- What the Saudi PDPL requires, in IT terms
- The PDPL checklist for IT teams
- A data inventory template you can copy
- HR data: the highest-risk set in most companies
- Breach response that fits inside 72 hours
- Mistakes that undermine PDPL compliance
- Key takeaways
- Frequently asked questions
- When did the Saudi PDPL come into force?
- What is the breach notification deadline under the PDPL?
- Does the PDPL require a data protection officer?
- Can we store personal data outside Saudi Arabia?
- What are the penalties for non-compliance with the PDPL?
Saudi PDPL compliance is the work of bringing every system that stores personal data under the Personal Data Protection Law, which took effect on 14 September 2023 and became fully enforceable by the Saudi Data and Artificial Intelligence Authority (SDAIA) when the one-year grace period ended on 14 September 2024. The law is written for controllers and processors, but most of its obligations land on the IT team: knowing where personal data lives, controlling who can reach it, deleting it on time, moving it across borders lawfully and reporting breaches to SDAIA within 72 hours. This checklist covers that IT side; the legal reading of your specific processing still needs a lawyer.
My own starting point was an integration, not a policy. At NAF Company I connected Jisr HR to SAP Business One so that employee master data, cost centers and payroll flowed between the two systems without manual re-entry. The moment that integration worked, personal data about every employee existed in two systems, a middleware log and several reports, and the data protection policy I later wrote had to describe all of them honestly. That is the PDPL in miniature: the law is about data flows, and the IT team is the only function that can see them end to end.
What the Saudi PDPL requires, in IT terms
The law and its Implementing Regulations (published by SDAIA on 7 September 2023, together with the Personal Data Transfer Regulations) set obligations that read as legal duties but translate into concrete system behavior. The table below pairs each obligation with what the IT team has to be able to show. Note that SDAIA opened a consultation on amendments to the Implementing Regulations in October 2026, so some details may change; verify the current text before you finalize procedures.
| Obligation under the PDPL | What it means in practice | What IT must be able to show |
|---|---|---|
| Lawful basis and consent | Personal data is processed for a defined purpose on a recognized legal basis; consent, where used, must be demonstrable and withdrawable | Where consent is recorded, how it is linked to the record, how withdrawal propagates to downstream systems |
| Privacy notice | Individuals are told, at or before collection, what is collected, why, on what basis and where it is used | Notices on web forms, HR onboarding, customer portals and apps match the real data flows |
| Records of processing activities | A written register of purposes, data categories, recipients, retention periods and security measures, kept for five years after processing ends and available to SDAIA on request | A data inventory by system, kept current when systems change |
| Data protection officer | Required where core activities involve regular, large-scale monitoring of individuals or sensitive data, and for public entities processing at scale | Named DPO with contact details, or a documented decision that the trigger does not apply |
| Security of personal data | Organizational, administrative and technical measures appropriate to the risk | Access control, encryption, logging, backup and vendor controls mapped to each system holding personal data |
| Breach notification | Notify SDAIA within 72 hours of becoming aware of a breach that meets the notification criteria; notify affected individuals without undue delay where required | An incident procedure with detection, assessment, decision and reporting steps that fit inside 72 hours |
| Data subject rights | Access, correction, deletion and other rights, generally answered within 30 days, extendable in defined cases with notice to the individual | A way to find, export, correct and delete one person’s data across all systems and backups |
| Cross-border transfer | Transfer outside the Kingdom only to countries with adequate protection, or with safeguards such as standard contractual clauses, binding corporate rules, certification or binding codes, with a transfer risk assessment in defined cases | A list of every cloud service, SaaS tool and vendor that stores or accesses personal data outside Saudi Arabia, with its legal mechanism |
| Destruction | Data is destroyed when the purpose ends, on request or on withdrawal of consent, including copies held by recipients and in backups | Retention schedules enforced in systems, and a backup retention policy that is consistent with them |
| Registration | Certain controllers (for example public entities and those whose main activity is processing, or who process high-risk sensitive data) must register on SDAIA’s national platform | A documented decision on whether registration applies, and the registration record if it does |
Penalties are significant: administrative fines for violations can reach SAR 5 million, doubled for repeat violations, and unlawful disclosure of sensitive data with intent to harm or gain carries criminal penalties of up to two years’ imprisonment and a fine of up to SAR 3 million. Those are the headline figures reported in law-firm summaries; the law text is the authority.
The PDPL checklist for IT teams
- Inventory every system that holds personal data. ERP, HR and payroll, CRM, e-commerce, email, file shares, CCTV, access control, visitor logs, WhatsApp groups used for business, spreadsheets on shared drives, and the backups of all of these. For each one, record the data categories, the business owner, the purpose, who has access and where it is hosted.
- Classify sensitive data separately. Health records, religious and ethnic data, biometric data, criminal records and similar categories carry stricter rules. Mark the fields and the systems that hold them.
- Map the flows between systems. Integrations are where personal data silently multiplies. The HR-to-ERP integration I mentioned above moves employee data on a schedule; so do bank payment files, insurance uploads, government portal submissions and reporting extracts. Document each flow with its direction, frequency, transport and the fields carried.
- Map the flows outside the Kingdom. Cloud email, backup services, support desks, analytics tools and parent-group systems abroad all count. Record the country, the vendor and the transfer mechanism, and flag the ones with no documented basis for legal review.
- Fix access control. Role-based permissions in the ERP and HR systems, named accounts only, MFA for remote and privileged access, quarterly access reviews signed by the data owner, and same-day deprovisioning. Most PDPL exposure in mid-sized companies is an ex-employee or a shared login, not a hacker.
- Set and enforce retention. Agree retention periods with HR, finance and legal (statutory requirements for accounting and employment records usually set the floor), configure them where the system allows, and schedule manual purges where it does not. Align backup retention so you are not keeping deleted records for years in tape.
- Build the data subject request procedure. One intake point, identity verification, a search list of systems per request type, a 30-day clock with an owner, and a log of every request and response.
- Write and rehearse the breach procedure. Who declares an incident, who assesses whether it involves personal data, who decides on notification, who drafts the SDAIA notification and who informs individuals. Run a tabletop exercise with a lost laptop and a compromised mailbox as scenarios and time it against 72 hours.
- Put data protection into vendor contracts. Processing instructions, confidentiality, security measures, sub-processor approval, breach notification to you within a short window, assistance with data subject requests, return or deletion at termination, and audit rights.
- Appoint the DPO or document why not. If the appointment triggers apply, the DPO needs a written appointment, published contact details and independence. If they do not, keep the reasoning in the compliance file and assign data protection responsibility to a named manager anyway.
- Secure what you keep. Encryption of laptops and backups, logging of access to HR and customer records, endpoint protection and patching. The PDPL does not prescribe technologies, but “appropriate measures” will be judged against common practice, and the NCA Essential Cybersecurity Controls are the most defensible reference for what that means in Saudi Arabia.
- Review annually and after every system change. A new module, a new integration or a migration changes the inventory. Treat the data protection register as a living document owned by IT and reviewed by legal.
A data inventory template you can copy
Keep the inventory in a spreadsheet or a GRC tool, one row per system and purpose. These are the columns that have proven sufficient for both an internal review and a legal review:
System | Owner (business) | Purpose | Data categories | Sensitive data? (Y/N)
Data subjects (employees / customers / visitors) | Source of data
Legal basis | Privacy notice reference | Retention period | Deletion method
Hosting location | Vendor | Transfer outside KSA? (Y/N) | Transfer mechanism
Access roles | Last access review | Integrations in / out | Backup retention
Fill the inventory from the systems, not from memory: export user lists, read integration logs and check cloud consoles for the hosting region. During ERP projects, build it alongside the data migration mapping, since the same people are already listing every field that moves; the approach is described in my ERP data migration checklist.
HR data: the highest-risk set in most companies
Employee records contain identity documents, bank details, insurance data, family information and often biometrics from attendance devices, and they move between HR, payroll, the ERP, the bank, the insurer and government portals. Four controls matter most:
- Restrict the HR system and the HR tables in the ERP to HR and finance roles; managers see only their own teams; IT administrators have audited, not routine, access.
- Keep integrations field-minimal. The ERP needs employee ID, name, cost center and salary posting data; it does not need passport scans. Design the integration to carry the minimum, as I did when connecting Jisr HR to SAP Business One in the project described in my SAP Business One manufacturing case study.
- Control attendance and CCTV data as sensitive, with its own retention period and a named owner.
- Handle leavers deliberately: what is retained for statutory reasons, for how long, and what is deleted.
Breach response that fits inside 72 hours
The clock starts when the controller becomes aware of the breach, so detection and escalation speed decide whether the deadline is achievable. A workable sequence: contain and preserve logs in the first hours; establish what data, whose and how much, and brief management and legal within the first day; decide on notification with legal and draft the SDAIA submission by hour 48; submit, record and start the post-incident review before hour 72. Keep a one-page notification template and the SDAIA channel details in the incident folder so nobody is searching for them during an incident.
Mistakes that undermine PDPL compliance
- Publishing a privacy policy and stopping there. A notice without an inventory, retention and access control is a promise the company cannot keep.
- Ignoring the backups. Deletion obligations extend to copies; if backups keep everything forever, the retention policy is fiction.
- Not knowing where SaaS data is hosted. Many tools default to regions outside the Kingdom; the transfer must be identified and given a lawful mechanism.
- Treating the ERP vendor’s access as harmless. Support engineers with standing administrator access to production are processors with no contract.
- Reading law-firm summaries as the law. Figures, thresholds and triggers in this article are drawn from published summaries of the PDPL and its regulations; the official Arabic text and SDAIA’s guidance govern, and the regulations are being amended.
Key takeaways
- The PDPL has been fully enforceable since 14 September 2024, and SDAIA is the regulator; the regulations are under revision, so verify details before finalizing procedures.
- Most obligations become IT controls: inventory, access, retention, deletion, transfer mapping and breach response.
- Integrations and backups are where personal data accumulates unnoticed; document both.
- The 72-hour breach notification and 30-day data subject response windows need rehearsed procedures, not just policies.
- HR data is usually the highest-risk set; restrict it, minimize what integrations carry and define leaver retention.
- Pair the IT checklist with legal review of lawful bases, notices, transfer mechanisms, DPO and registration triggers.
Frequently asked questions
When did the Saudi PDPL come into force?
The Personal Data Protection Law took effect on 14 September 2023, with Implementing Regulations and Personal Data Transfer Regulations published by SDAIA shortly before. Controllers had a one-year grace period, which ended on 14 September 2024; since then the law has been fully enforceable, and SDAIA has been acting on complaints from individuals.
What is the breach notification deadline under the PDPL?
Where notification to SDAIA is required, the controller must notify within 72 hours of becoming aware of the breach, and affected individuals must be informed without undue delay in the cases the regulations define. The practical consequence is that detection, assessment and decision-making have to be rehearsed in advance.
Does the PDPL require a data protection officer?
A DPO is required when the controller is a public entity processing personal data on a large scale, when core activities involve regular and continuous large-scale monitoring of individuals, or when core activities involve sensitive data. Other companies are not obliged to appoint one, but should still name a responsible manager and document the decision.
Can we store personal data outside Saudi Arabia?
Transfers outside the Kingdom are permitted to countries SDAIA assesses as providing adequate protection, or with appropriate safeguards such as standard contractual clauses, binding corporate rules, certification or binding codes of conduct, plus a transfer risk assessment in defined cases. Every cloud service hosting personal data abroad needs one of these mechanisms, so list them first.
What are the penalties for non-compliance with the PDPL?
Published summaries of the law cite administrative fines of up to SAR 5 million per violation, which can be doubled for repeat offenses, and criminal penalties of up to two years’ imprisonment and a SAR 3 million fine for disclosing sensitive data with intent to harm or benefit. Penalties are applied by SDAIA and the competent courts under the law’s procedures.
If you need the IT side of PDPL compliance built properly, from the data inventory and access model to retention in the ERP and a breach procedure your team can run, I can help you scope it alongside your legal advisers as part of a digital transformation and governance program. Contact me to discuss where your systems stand today.