Yes, if your app processes personal data about people in Saudi Arabia, you need to comply with the PDPL in Saudi Arabia. This applies whether your company is based in the Kingdom or abroad, and whether the app is free or paid. Full enforcement began on 14 September 2024, and in January 2026, SDAIA announced that its violation committees issued 48 decisions during 2025.
This guide explains who PDPL covers, what it requires from app owners, how it affects your build, and what the penalties look like. It is not legal advice. Confirm your exact duties with qualified Saudi counsel.
PDPL is Saudi Arabia’s Personal Data Protection Law. It was issued by Royal Decree M/19 and amended by Royal Decree M/148. The Saudi Data and AI Authority (SDAIA) supervises it. Implementing Regulations and Transfer Regulations add the detailed rules.
The law entered into force on 14 September 2023. A one-year grace period ended on 14 September 2024, so it is now fully enforceable.
The test is simple. Does your app process personal data related to individuals in Saudi Arabia? If yes, PDPL applies. The law also reaches foreign organizations that process the data of people in the Kingdom.
| Your situation | Does PDPL apply? |
| Saudi startup app that collects names, emails, or phone numbers | Yes |
| Foreign app with users in Saudi Arabia | Yes |
| B2B app that stores employee logins and profiles | Yes, staff data is personal data |
| App with an analytics or advertising SDK that collects device identifiers | Likely yes; review each SDK |
| App that collects no personal data and sends nothing off the device | Probably not |
When in doubt, treat the app as in scope. Reviewing a small app costs far less than a violation.
If you build in the Kingdom, your mobile app development company in Saudi Arabia should raise PDPL during discovery, before design starts.
Personal data is any information that identifies a person, directly or indirectly. In apps, that includes:
PDPL gives stronger protection to sensitive data, such as health, biometric, genetic, and credit information. Sensitive data needs tighter controls and cannot rely on the “legitimate interest” basis.
PDPL separates two roles. The controller decides why and how data is processed. The processor handles data on the controller’s behalf.
The app owner is usually the controller. A development agency, cloud host, or SMS provider is often a processor. The Implementing Regulations require a written agreement with each processor that sets out its obligations, including notifying you of a breach without delay.
| Requirement | What it means for your app |
| Legal basis | Consent is the main basis. Other bases exist, such as contract, legal obligation, and legitimate interest |
| Privacy notice | Tell users what you collect and why, in clear language, at the point of collection |
| Purpose and minimization | Collect only what you need, and use it only for the stated purpose |
| Data subject rights | Let users access, correct, delete, and request a copy of their data, and withdraw consent |
| Response time | Answer data subject requests within 30 days |
| Security | Protect data with encryption, access control, and logging |
| Breach notification | Notify SDAIA within 72 hours of becoming aware of a breach that may cause harm |
| Records of processing | Keep a record of what you process, why, and who receives it |
| Controller registration | Register on SDAIA’s National Data Governance Platform where required |
| Data Protection Officer | Appoint one where the regulations’ criteria apply |
| Processor contracts | Use written agreements with every vendor that handles personal data |
| Cross-border transfers | Meet the Transfer Regulations before data leaves the Kingdom |
Consent can take any appropriate form, including electronic consent, as long as it is valid. Make it specific, easy to give, and easy to withdraw.
PDPL is not only a legal document. It shapes screens, code, and vendors. Our mobile app development team turns each requirement into a build task.
Backend and hosting choices often involve enterprise systems. Our software development company in Saudi Arabia team plans these alongside the app.
Under Article 24 of the Implementing Regulations, you must notify SDAIA within 72 hours of becoming aware of a personal data breach that may harm the data or the individuals, or conflict with their rights or interests. The clock starts when you become aware, not when the breach occurred. You submit the notice through SDAIA’s National Data Governance Platform and follow its breach procedural guide.
Prepare before an incident:
If a breach is likely to harm individuals, you may also need to inform them without undue delay.
Many apps send data abroad without noticing. A foreign cloud region, an overseas analytics tool, or a chatbot API can all move personal data out of the Kingdom.
PDPL allows transfers only under the Transfer Regulations. Transfers are permitted where the destination offers adequate protection, or where you apply appropriate safeguards. Some cases also require a documented transfer risk assessment, including continuous or large-scale transfers of sensitive data.
For app teams, the rule is practical: map every data flow before launch. Choose hosting and vendors with transfers in mind, because moving a live system later is expensive.
SDAIA is enforcing the law. Administrative fines can reach SAR 5 million, and the law carries criminal sanctions for intentional disclosure of sensitive data. SDAIA can also issue warnings and order corrective measures. Individuals can file complaints with SDAIA.
Cost depends on your data, vendors, and architecture. A simple app with few SDKs needs far less work than a platform with many integrations and sensitive data. No source gives one reliable price, so ask any vendor for an itemized estimate.
Compliance also affects project budgets. See how localization and compliance shape pricing in our guide to mobile app development cost in Saudi Arabia. If your app uses national identity sign-in, read our guide on how to add Nafath login to a mobile app, which covers identity data handling in detail.
If your app touches personal data about people in Saudi Arabia, plan to comply with PDPL in Saudi Arabia from the first sprint. Map your data. Choose a legal basis for each use. Write the privacy notice. Audit your SDKs. Decide where data lives. And rehearse your 72-hour breach plan.
Teams that treat PDPL as a design input build faster and avoid rework. Teams that treat it as a final checklist often rebuild consent screens, change hosting, and rewrite vendor contracts late in the project.
Yes. PDPL applies to organizations that process the personal data of individuals in Saudi Arabia, including foreign organizations.
Yes. Price does not matter. If the app processes personal data related to people in the Kingdom, PDPL applies.
The law entered into force on 14 September 2023, and the grace period ended on 14 September 2024. SDAIA announced 48 violation decisions for 2025.
Notify SDAIA within 72 hours of becoming aware of a breach that may cause harm to the data or the individuals, or conflict with their rights or interests.
You need one where the Implementing Regulations’ criteria apply, such as certain public entities and organizations that process sensitive data at scale. Check your case with counsel.
Possibly, but only within the Transfer Regulations. You need adequate protection or appropriate safeguards, and sometimes a transfer risk assessment. Plan hosting early.
Administrative fines can reach SAR 5 million. The law also provides criminal sanctions for intentional disclosure of sensitive data.
This article is general information, not legal advice. Facts come from public sources, including SDAIA announcements and legal analyses of the PDPL, its Implementing Regulations, and the Transfer Regulations. Rules and guidance change, so confirm current requirements with SDAIA and qualified Saudi counsel.
We design consent flows, data maps, and secure backends with Saudi requirements in mind. Talk to our team and we will scope the compliance work before you commit to a build.