Saudi Arabia's Personal Data Protection Law (PDPL) applies to any AI customer service tool that processes data about people in the Kingdom, including vendors based abroad. For support teams, four rules matter most: limits on transferring data outside the Kingdom, consent as the default legal basis, a data protection officer in some cases, and breach notice to SDAIA within 72 hours. Your AI vendor is your processor, and the law makes you responsible for choosing one that can meet these rules.
This article is general information, not legal advice. Check the current SDAIA texts and speak to qualified Saudi counsel before making compliance decisions.
TL;DR
- The PDPL has been in force since 14 September 2023, with a one-year grace period that ended on 14 September 2024. SDAIA (the Saudi Data and AI Authority) is the regulator.
- It covers processing of personal data about people in the Kingdom by any party, including parties outside Saudi Arabia (Article 2).
- Sending customer conversations to an AI vendor or model hosted abroad is a transfer outside the Kingdom. Article 29 and SDAIA's Transfer Regulation set the conditions.
- Controllers must pick processors that give "the necessary guarantees" and keep monitoring them (Article 8). That is why vendor due diligence matters.
- SDAIA consulted on draft amendments from 6 October to 5 November 2026. They would add an in-Kingdom storage requirement and make 72-hour breach notice unconditional. We found no final version published as of 18 November 2026, so treat them as proposals, not law.
- Fines run up to SAR 5 million per violation, and can be doubled for repeat violations (Article 36).
Does the PDPL apply to AI customer service?
Yes, in almost every case. A support conversation carries personal data by default: names, phone numbers, order numbers, account details, voice recordings, and sometimes health or financial information. Under Article 2, the law applies to any processing of personal data about individuals in the Kingdom, "by any means," including processing by a party outside the Kingdom.
In PDPL terms, your company is the controller (you decide why the data is processed). Your AI customer service vendor is a processor (it processes data on your behalf). Any model provider or cloud host the vendor uses is a further sub-processor.
Three things make AI support different from a classic helpdesk:
- More data moves. Every message, call transcript and screenshot goes to the AI for processing, often to a large language model hosted in another country.
- Voice adds new data types. Call recordings and transcripts can reveal far more than a ticket form.
- Context gets reused. Knowledge bases, conversation logs and training data can keep personal data longer than the original purpose needs.
The same questions come up when you choose an Arabic AI chatbot for Gulf customers, because the vendor's hosting and model choices decide where your data goes.
What the PDPL requires
Transfers outside the Kingdom
Article 29 of the PDPL lets a controller transfer personal data outside the Kingdom for set purposes, including performing an obligation to which the data subject is a party, and other purposes in the regulations. The conditions are:
- The transfer must not harm national security or the Kingdom's vital interests.
- The destination must offer an adequate level of protection, at least equivalent to the PDPL, based on SDAIA's assessment.
- The transfer must be limited to the minimum personal data needed.
SDAIA's Regulation on Personal Data Transfer outside the Kingdom, amended in 2024, adds the practical routes where no adequacy decision exists. These are standard contractual clauses (SDAIA published four versions covering controller and processor combinations), binding common rules for transfers within a corporate group, and certificates of accreditation. The amended regulation also sets out when a transfer risk assessment is required.
What this means for AI support: if your vendor, its cloud host or its model provider processes conversations outside Saudi Arabia, you need a lawful transfer route and a documented record of it. Article 31 requires your records of processing to state whether personal data is transferred outside the Kingdom.
Watch this space: SDAIA's October 2026 draft amendments to the Implementing Regulations propose a new Article 23 requiring controllers to store personal data within the Kingdom, while still allowing transfers under the law. If adopted, they take effect 60 days after publication in the Official Gazette. Today there is no general in-Kingdom storage requirement in the PDPL itself, though sector regulators (banking, for example) can impose their own.
Consent and other legal bases
Consent is the default. Article 5 says personal data may not be processed, nor its purpose changed, without the data subject's consent, except where the law says otherwise. The data subject can withdraw consent at any time. Article 7 adds that consent cannot be a condition of providing a service unless the service is directly related to the processing.
Article 6 lists cases where consent is not needed. Two matter most for customer service:
- Processing in performance of an agreement to which the data subject is a party. Answering a customer's question about their own order is the obvious example.
- Processing for the controller's legitimate interest, without prejudice to the data subject's rights, and only if no sensitive data is involved.
For marketing messages sent through support channels such as WhatsApp, the law requires the recipient's prior consent and a way to opt out (Article 25 in the version published by SDAIA). If you plan WhatsApp campaigns, the consent rules sit alongside Meta's own per-message charges, covered in our WhatsApp Business API pricing guide.
What this means for AI support: answering a support request usually rests on the customer relationship. Reusing those conversations for something else, such as training a model or sending offers, is a change of purpose and needs its own basis.
Data protection officer (DPO)
Article 30 leaves it to the Implementing Regulations to say when a controller must appoint a personal data protection officer. Under the current regulations, as summarised by DLA Piper, you need a DPO if:
- you are a public entity processing personal data on a large scale,
- your primary activities involve regular and continuous large-scale monitoring of individuals, or
- your core activities involve processing sensitive data.
A high-volume contact center handling health or financial data can fall into the third category. The October 2026 draft would drop the large-scale qualifier for public entities and require DPO contact details to be filed with SDAIA.
Breach notification
Article 20 requires the controller to notify SDAIA on learning of any breach of, damage to or illegal access to personal data, and to notify affected individuals where the breach could harm them or their rights. Under the current Implementing Regulations, notice to SDAIA is due within 72 hours of becoming aware of a breach that is likely to cause harm, filed through the National Data Governance Platform. Individuals must be told without undue delay.
The October 2026 draft would remove the harm test for SDAIA notice, so every breach would need reporting within 72 hours.
What this means for AI support: your 72-hour clock depends on how fast your vendor tells you. If its contract allows it to notify you "within a reasonable time," you may miss your deadline.
Other duties that touch AI support
- Choosing processors (Article 8): select only processors that provide the necessary guarantees, and monitor their compliance. This also covers the processor's own subcontracts.
- Impact assessments (Article 22): assess the impact of processing for products or services, based on the nature of your activity. A new AI agent is a natural trigger.
- Security (Article 19): take organisational, administrative and technical measures to protect personal data, including during transfers.
- Records (Article 31): keep records of processing, including purposes, recipients, retention periods and transfers abroad.
- Registration: SDAIA operates a national register of controllers. Check whether you must register.
Penalties under the PDPL
| Violation | Maximum penalty | Article |
|---|---|---|
| Disclosing or publishing sensitive data unlawfully, with intent to harm or for personal benefit | Up to 2 years' imprisonment and/or a SAR 3 million fine | 35 |
| Any other violation of the law or regulations | Warning or a fine up to SAR 5 million | 36 |
| Repeat violations | Fine can be doubled, up to twice the maximum | 35, 36 |
Data subjects can also claim compensation for material or moral damage.
20 questions to ask your AI customer service vendor about the PDPL
Use this list in your RFP or security review. Ask for answers in writing, with documents attached. Our enterprise chatbot platform checklist covers the wider evaluation (SSO, audit logs, handoff, pricing).
Data location and transfers
- In which countries are conversation data, call recordings, transcripts and attachments stored?
- In which countries are they processed, including by the AI model?
- Which sub-processors (cloud, model providers, transcription, voice) touch Saudi customer data, and where are they?
- What transfer route do you rely on for each transfer outside the Kingdom: adequacy, SDAIA standard contractual clauses, binding common rules, or certification?
- Can you offer in-Kingdom hosting or processing if the draft storage requirement is adopted, or if our sector regulator requires it?
Model use and retention
- Is our customer data used to train or improve any model, yours or a third party's? Can we opt out in the contract?
- How long are conversations, recordings and logs kept by default, and can we set our own retention?
- Can you delete a specific customer's data on request, including from backups and sub-processors, and how long does it take?
- Can personal data be redacted from transcripts and logs before storage?
Contract and roles
- Will you sign a data processing agreement that reflects the PDPL, not only the GDPR?
- Do you notify us before adding or changing sub-processors?
- Will you support our transfer risk assessment and impact assessment with documentation?
- What audit or assessment rights do we have?
Breaches and incidents
- How quickly will you notify us of a personal data breach? Is it a fixed number of hours in the contract?
- What information will the notice contain, so we can file with SDAIA within 72 hours?
- Who is your named security or privacy contact?
Customer rights and channels
- How do we find and export everything you hold about one customer, across chat, email, WhatsApp and voice?
- How does the AI handle a customer who withdraws consent or asks for a human?
- Can we stop the AI from collecting sensitive data (health, financial, ID numbers) it doesn't need?
- Which independent security reports can you share, and what are their dates and scope?
Question 20 is the one most often answered with a logo instead of a document. Ask for the report itself, its date and its scope.
Applying this to Open
Open sells AI customer service across WhatsApp, voice, chat and email, with an Arabic version of Agent 5 for Gulf customers. Run the questions above against Open the same way you would against any vendor.
Here is what Open publishes today. Its GDPR page says primary infrastructure and data storage are in Frankfurt, Germany; some sub-processors, support staff and third-party AI models process data outside the EEA under Standard Contractual Clauses and UK transfer terms. For a Saudi deployment, that means conversations leave the Kingdom, so you need an Article 29 transfer route. Open's security documentation is at trust.open.cx. For anything specific to your deployment in Saudi Arabia, ask for it in writing during evaluation.
On cost, Open charges $0.75–$0.90 per resolution, and handoffs to a human are not billed. See pricing.
Sources
- Personal Data Protection Law (English, reviewed version, April 2023), SDAIA, https://sdaia.gov.sa/en/SDAIA/about/Documents/Personal%20Data%20English%20V2-23April2023-%20Reviewed-.pdf, checked 2026-11-12
- Data Protection in Saudi Arabia, DLA Piper Data Protection Laws of the World, https://www.dlapiperdataprotection.com/index.html?c=SA&t=law, checked 2026-11-12
- The SDAIA publishes draft amendments to the Implementing Regulations of the PDPL (consultation 6 October to 5 November 2026), Clyde & Co, https://www.clydeco.com/en/insights/2026/10/sdaia-publishes-draft-amendments-to-the-pdpl, checked 2026-11-18
- SDAIA Consults on Extensive Amendments to the Saudi PDPL Implementing Regulation, Reed Smith, https://www.reedsmith.com/our-insights/blogs/viewpoints/102o5at/sdaia-consults-on-extensive-amendments-to-the-saudi-pdpl-implementing-regulation/, checked 2026-11-18
- Saudi Data and AI Authority Proposes Amendments to Implementing Regulations of the PDPL, Akin Gump, https://www.akingump.com/en/insights/alerts/saudi-data-and-ai-authority-proposes-amendments-to-implementing-regulations-of-the-pdpl-10-key-proposed-changes, checked 2026-11-12
- Updates to Saudi Arabia's Personal Data Protection Regulations: SCCs, Guidelines and More (October 2024), Mayer Brown, https://www.mayerbrown.com/en/insights/publications/2024/10/updates-to-saudi-arabias-personal-data-protection-regulations-sccs-guidelines-and-more, checked 2026-11-12
- Saudi Arabia updates Data Transfer Regulations and introduces the first set of Standard Contractual Clauses, Baker McKenzie, https://insightplus.bakermckenzie.com/bm/data-technology/saudi-arabia-updates-data-transfer-regulations-and-introduces-the-first-set-of-standard-contractual-clauses, checked 2026-11-12
- Open, GDPR, https://www.open.cx/gdpr, checked 2026-11-18
- Open, Pricing, https://www.open.cx/pricing, checked 2026-11-18
- Open Trust Center, https://trust.open.cx, checked 2026-11-18