Operational GRC for audit-ready organizations in Saudi ArabiaBook a Demo
Frameworks · GDPRSaudi Arabia

You did the PDPL. That is most of this.

The PDPL was amended in 2023 to align more closely with the GDPR, so a Saudi organisation that built a proper privacy programme has built most of the substance. What remains is scope, transfers, and a handful of specifics — and the transfer part is harder than it looks in both directions.

Frameworks · GDPRGovrly

This page reflects how we see the GDPR applied in practice by organisations based in the Kingdom. It is not an official reference and it is not legal advice. The authoritative sources are Regulation (EU) 2016/679 itself, the guidance of the relevant supervisory authorities, and the PDPL and its implementing regulations as published by SDAIA. Confirm what applies to your organisation with your own advisers.

§ 01Govrly
Frameworks · GDPR

Does the GDPR apply to a Saudi organisation?

From the compliance programmes we build and run in Saudi Arabia: often yes. The GDPR applies to organisations established outside the EU where they offer goods or services to individuals in the EU, or monitor the behaviour of individuals in the EU. Having no EU office, no EU entity and no euro-denominated revenue does not remove it.

This surprises people, so it is worth being concrete. A Saudi SaaS company with European users is in scope. A Saudi company running analytics that track visitors in the EU is in scope. A Saudi subsidiary processing employee data for a European parent is in scope. So is a Saudi processor handling EU personal data on a customer's instructions.

What is not in scope is as useful to know: serving EU customers who happen to be businesses, without processing personal data about individuals in the EU, generally is not. Neither is a website that is merely accessible from Europe without targeting anyone there. The test is targeting and monitoring, not reachability.

Applies outside the EU
Extraterritorial
Neither direction, KSA and EU
No adequacy
Breach notification, as in the PDPL
72 hours
One inventory serves both
Shared records
§ 02Govrly
Frameworks · GDPR

The part that catches Saudi organisations

Most teams handle records, bases and rights competently, then hit the transfer question halfway through a deal and discover it runs in both directions.

EU → Kingdom
Governed by the GDPR

Because there is no adequacy decision for Saudi Arabia, personal data moving from the EU to the Kingdom must rely on an Article 46 safeguard — most commonly Standard Contractual Clauses, or Binding Corporate Rules for intra-group transfers — supported by a transfer impact assessment. Your European customer will ask for this in their vendor review, and increasingly asks for it before signing rather than after.

Kingdom → anywhere
Governed by the PDPL

Transfers out of the Kingdom require the conditions in the PDPL and its transfer regulations to be met, with SDAIA-approved safeguards where no adequacy determination exists — and none has been published. SDAIA issued a risk assessment guideline for outbound transfers in February 2025 which, while not binding, sets out the methodology it expects controllers to follow.

The practical consequence is that a Saudi company hosting EU personal data, or an EU company hosting Saudi personal data, is running two transfer assessments over one dataset. Doing them from a single transfer register is considerably less work than doing them from two — and considerably more defensible, because the answers cannot drift apart.

Neither direction has adequacy
Two regimes, two sets of safeguards, no shortcut

The European Commission has not granted Saudi Arabia an adequacy decision. And SDAIA has not published a formal adequacy list of its own. Both regimes therefore require safeguards for the same data crossing the same border, in opposite directions, assessed under different rules.

§ 03Govrly
Frameworks · GDPR

GDPR and PDPL, side by side

Broadly familiar in shape, materially different in detail — and in some respects the PDPL asks for more.

Read the last row before assuming the overlap solves the problem. The shared architecture means the work compounds — one processing inventory, one set of lawful basis decisions, one rights workflow can serve both. But each regime applies on its own terms, and a supervisory authority in either jurisdiction will assess you against its own law rather than the other one.

GDPRSaudi PDPL
Supervisory authorityNational authorities across the EU and EEASDAIA
Territorial reachEstablishment in the EU, or offering goods and services to, or monitoring, individuals in the EUPersonal data of individuals in the Kingdom, including where processed abroad
StructureLawful basis, data subject rights, accountability, transfer restrictionsThe same architecture — the 2023 amendments aligned it more closely
Rights responseOne month, extendable by two further months30 days, with a limited extension
Breach notification72 hours to the supervisory authority72 hours to SDAIA
Transfers outAdequacy, or Article 46 safeguards such as SCCs and BCRsConditions under the transfer regulations, with SDAIA-approved safeguards
Does one satisfy the other?No — GDPR compliance does not discharge the PDPLNo — PDPL compliance does not discharge the GDPR
§ 04Govrly
Frameworks · GDPR

What it asks for in practice

If you recognise all six of these from your PDPL programme, that is the point.

Article 30
Records of processing

What personal data you hold, why, on what basis, who it is shared with, where it goes and for how long. The same inventory your PDPL programme maintains, with EU-specific detail added rather than a second register built.

Article 6
A lawful basis per activity

Established per processing activity, not per organisation. Where consent is relied on, it must be freely given, specific, informed and demonstrable — and withdrawable as easily as it was given.

Chapter III
Data subject rights

Access, rectification, erasure, restriction, portability and objection, answered within a month. The workflow is the one you already run for PDPL requests, with a different clock and a wider set of rights.

Article 35
Impact assessments

A DPIA where processing is likely to result in high risk — new technologies, large-scale monitoring, systematic profiling. The trigger list is worth checking against your roadmap rather than your current state.

Articles 33–34
Breach notification

72 hours to the supervisory authority, and to affected individuals where the risk to them is high. The same clock as the PDPL, which means one incident process can serve both if it captures the reasoning.

Article 28
Processor obligations

If you process EU personal data for customers, your contract must contain specified terms and you must impose equivalent obligations on sub-processors. This is what your European customer's legal team will review first.

§ 05Govrly
Frameworks · GDPR

Running GDPR and PDPL together in Govrly

Two regimes over one dataset is only expensive if you maintain two sets of records.

One inventory
Processing records serving both

A single record of each processing activity carrying its PDPL position and its GDPR position — lawful basis, purpose, recipients, retention — rather than two registers that describe the same activity and slowly disagree.

Transfers
One register, two assessments

Each transfer recorded once with its direction, mechanism and assessment, satisfying the GDPR safeguard requirement and the PDPL transfer conditions from the same entry.

Rights
One workflow, two clocks

Requests logged from intake and tracked against whichever deadline applies, with a record of exactly what was provided — because the two regimes run to different timeframes over the same process.

Incidents
One assessment, two notifications

A breach assessed once against both thresholds within the 72-hour window, with the reasoning preserved rather than reconstructed months later when someone asks why you did or did not notify.

Shared controls
Security evidence reused

The access control, encryption and logging that Article 32 expects are the same controls carrying your NCA ECC or ISO 27001 requirements. One implementation, one evidence set, several obligations.

Vendors
Sub-processors in one place

Your processor chain recorded once, supporting Article 28 obligations to your EU customers and PDPL processor requirements at the same time.

§ 06Govrly
Frameworks · GDPR

A practical path, starting from a PDPL programme

This sequence assumes you already have privacy records. If you do not, start with the PDPL work — it is the same foundation and it is mandatory.

  1. 01
    /08
    Establish whether you are actually in scope

    Offering goods or services to individuals in the EU, or monitoring their behaviour. Answer this properly before building anything, because the answer is sometimes no and sometimes broader than expected.

  2. 02
    /08
    Determine your role for each activity

    Controller for your own data, processor for your customers'. Most organisations are both, and the obligations differ substantially — which is why this comes before the record-keeping rather than after.

  3. 03
    /08
    Extend your processing records rather than duplicating them

    Add the GDPR-specific fields to the inventory your PDPL programme maintains. Two registers describing the same activity will disagree within a quarter, and the disagreement is what an auditor finds.

  4. 04
    /08
    Map your transfers in both directions

    What comes in from the EU, what goes out of the Kingdom, and the mechanism for each. This is the step that most often reveals processors nobody had recorded.

  5. 05
    /08
    Put the Article 28 terms in place

    Where you process EU personal data for customers, the contract terms are specified and your customer's legal team will check them. Have them ready rather than negotiating under deal pressure.

  6. 06
    /08
    Widen the rights workflow

    The GDPR grants rights the PDPL does not, and runs to a different deadline. One intake, one workflow, two timeframes — not a second process.

  7. 07
    /08
    Check your DPIA triggers against the roadmap

    High-risk processing includes new technologies and systematic monitoring. Assessing what you are about to build is considerably cheaper than assessing what you have already shipped.

  8. 08
    /08
    Decide on representation

    Organisations in scope without an EU establishment may need a representative in the Union. Confirm your position with counsel — it is a specific requirement with specific exemptions, and it is easy to get wrong in both directions.

Govrly
What this looks like in Govrly

One processing record carries its PDPL position and its GDPR position together, one transfer register serves both sets of assessments, and one incident assessment feeds both notification decisions — while the security controls behind Article 32 are the same records already carrying your NCA ECC or ISO 27001 requirements.

See it in a demo →

§ 07Govrly
Frameworks · GDPR

GDPR — FAQs

Often yes. The GDPR applies to organisations established outside the EU where they offer goods or services to individuals in the EU, or monitor the behaviour of individuals in the EU. Having no EU office, no EU entity and no euro revenue does not remove it. The test is targeting and monitoring, not where you are incorporated.

No. The PDPL was amended in 2023 to align more closely with the GDPR, so the architecture is shared and most of the substantive work carries across. But each regime applies on its own terms, and neither discharges the other. A supervisory authority in either jurisdiction assesses you against its own law.

Yes, with appropriate safeguards. There is no European Commission adequacy decision for Saudi Arabia, so transfers rely on an Article 46 mechanism — most commonly Standard Contractual Clauses, or Binding Corporate Rules for intra-group transfers — supported by a transfer impact assessment. Your European customer will ask to see this during vendor review.

Those are governed by the PDPL and its transfer regulations rather than the GDPR. SDAIA has not published a formal adequacy list, so transfers generally rely on approved safeguards. SDAIA issued a risk assessment guideline for outbound transfers in February 2025 which, while not legally binding, sets out the methodology it expects controllers to follow.

Possibly. Organisations in scope of the GDPR without an establishment in the Union may be required to designate a representative there, subject to specific exemptions. This is worth confirming with counsel rather than assuming, because it is a discrete requirement that organisations get wrong in both directions — appointing unnecessarily, or not appointing when required.

Breach notification is 72 hours under both regimes, to the relevant supervisory authority. Rights requests differ: the GDPR allows one month with an extension of two further months in defined circumstances, while the PDPL runs to 30 days with a more limited extension. One workflow can serve both, provided it tracks which clock applies to which request.

A data protection impact assessment, required under Article 35 where processing is likely to result in a high risk to individuals — typically new technologies, large-scale systematic monitoring, or extensive profiling. The practical advice is to check the triggers against your product roadmap rather than your current state, because assessing something before you build it is far cheaper.

A great deal. Article 28 specifies terms your contract must contain, requires you to impose equivalent obligations on any sub-processor, and constrains you to acting on the controller's documented instructions. If you process EU personal data for customers, this is the part their legal team reviews first and negotiates hardest.

It evidences privacy governance against a recognised standard, which is persuasive with European buyers and covers much of the same operational ground. It does not discharge the GDPR — no certification does — but for an organisation running both PDPL and GDPR obligations, a certified privacy management system is a single credible answer to a question both audiences ask.

Yes, and that is the efficient way to run it. One processing record carries both positions, one transfer register serves both sets of assessments, one rights workflow tracks both clocks, and the security controls behind Article 32 are the same records already carrying your NCA ECC or ISO 27001 requirements.

§ Frameworks · GDPRNCA · SAMA · CST · PDPL

One dataset should not need two privacy programmes

See what your existing PDPL records already cover against the GDPR, and where the two genuinely diverge.

Govrly's risk register: inherent and residual risk heat maps, scored by likelihood and impact№ 04B&W
Risks · inherent → residualPlate IV