Skip to main content

Marketing

Saudi Arabia's draft PDPL amendments: what changes for WhatsApp marketing, and how to prepare now

On 6 October 2026 Saudi Arabia's data authority, SDAIA, published draft amendments to the PDPL Implementing Regulations. If adopted, a past purchase would no longer be enough to send someone a promotional message: you would need their consent, proof of it and a clear way to withdraw it. The draft also asks controllers to store personal data in the Kingdom. This guide explains what the draft says, what it does not settle yet, and how to set up consent, stop handling and data storage for WhatsApp in MonoChat.

MonoChat Team Updated: 7 min read

On this page
  1. What the draft says
  2. What it means for WhatsApp marketing in Saudi Arabia
  3. How to prepare in MonoChat
  4. A note for banks and financial institutions
  5. Checklist
  6. Payments and the rest of the Saudi stack
  7. Sources

Saudi customers live on WhatsApp. The Communications, Space and Technology Commission’s Saudi Internet 2025 report found that 94.4% of men and 90.4% of women use it, more than any other app, according to Minute Mirror’s coverage of the report (28 August 2026). So when the Saudi Data and AI Authority (SDAIA) proposes new rules on marketing consent and data storage, every business that messages Saudi customers on WhatsApp should read them.

On 6 October 2026 SDAIA published draft amendments to the Implementing Regulations of the Personal Data Protection Law (PDPL) and opened them to public consultation until 5 November 2026. They are not in force yet. This guide explains what the draft says about marketing messages and data storage, what it leaves open, and what you can set up in MonoChat now so the final text does not catch you unprepared.

It is a summary of a draft and of two law firms’ readings of it, not legal advice.

What the draft says

Consent for every promotional message (Article 28)

Under the current Implementing Regulations, Reed Smith notes, a prior interaction between a business and a customer implies consent for direct marketing. A customer who bought once could receive offers.

The draft removes that shortcut. It would require consent for messages sent for “promotional or awareness purposes” in all circumstances. Clyde & Co adds two duties that come with it: controllers must keep evidence of consent, and provide clear and accessible mechanisms to withdraw it.

Marketing processing, not only messages (Article 29)

The draft widens the scope from sending direct marketing messages to all processing of personal data for marketing purposes. When a customer withdraws consent, the business must stop the marketing, stop the processing behind it, and destroy the personal data generated by that processing without undue delay, according to Clyde & Co.

Store personal data in the Kingdom (Article 23)

The most discussed change: an express requirement for controllers to store personal data within the Kingdom, while personal data “may be transferred or disclosed outside the Kingdom in accordance with the provisions of the Law”. Reed Smith reads two possible meanings:

  • a local copy is always required, and lawful transfers abroad are allowed on top of it, which would be a major policy shift; or
  • storage in the Kingdom is the baseline, and a lawful transfer removes the need for a local copy.

The final text will have to settle which one applies.

Register when data leaves the Kingdom (Article 34)

Controllers that transfer or disclose personal data outside Saudi Arabia would have to register in the National Register of Controllers, and Reed Smith reads the rule as reaching controllers outside the Kingdom too.

Privacy notices people can read (new Article 18)

Privacy notices would need clear, simplified language, in the language customarily used with the people concerned, which Clyde & Co says would in practice mean Arabic for most organisations.

When it would apply

If SDAIA adopts the amendments, they enter into force 60 days after publication in the Official Gazette. No adoption date had been announced when we checked on 13 November 2026.

What it means for WhatsApp marketing in Saudi Arabia

Meta already requires an opt-in before a business starts a WhatsApp conversation with someone. The draft goes further in three ways that matter for daily work:

  1. “They bought from us” is no longer consent. Your offer list has to be built from people who said yes to offers, not from your order history.
  2. You must be able to show the yes. When, where and how each customer agreed.
  3. “Stop” must work everywhere at once. A customer who withdraws should drop out of every campaign, flow and automated offer, not only the next broadcast.

Service messages, such as order confirmations, delivery updates and appointment reminders, are a different category. The draft’s consent rule targets promotional and awareness messages; Meta classes order and account updates as utility templates, and a utility template that carries an offer is reclassified as marketing. Keeping the two apart is now worth more than ever.

How to prepare in MonoChat

The Opt-in node in MonoChat’s flow designer asks the customer for consent and stores the answer in their Opt-in profile field, Yes or No. Put it where it is natural to ask: after a first order is confirmed, at the end of a support conversation, or in the welcome flow of a click-to-WhatsApp ad.

A message that says what people are agreeing to works better than a generic one:

Would you like to hear about our new arrivals and Ramadan offers on WhatsApp? We send at most one offer a week, and you can stop any time by replying STOP. [Yes, send offers] [No, thanks]

MonoChat stores Yes or No; the conversation itself keeps the request and the customer’s reply in the session history. Keep your own record of the wording, the date and where the consent was given, for example in a profile field your flow fills in or in your CRM, because the draft asks for evidence.

2. Send offers only to people who said yes

Bulk messages in MonoChat can be filtered to customers whose Opt-in is Yes. Build your offer audiences from that filter instead of from a purchase list, and keep separate templates for service updates and for offers.

3. Make “stop” stop everything

When a customer stops your marketing messages in WhatsApp itself, MonoChat sets their WhatsApp marketing stopped profile field to Yes, adds a whisper to their latest conversation for your team, and skips them in bulk messages and in the Send Template Message flow node for Marketing templates. When they resume, the field goes back to No.

A customer who writes “stop” or «إيقاف» in the chat instead should get the same result. A flow can watch for those words, set Opt-in to No and confirm in Arabic and English. MonoChat’s industry apps, such as Shop Assistant, Real Estate Assistant and Clinic Assistant, never send their campaigns to people who opted out.

4. Decide where your conversations live

When you connect a WhatsApp number on Meta’s Cloud API, MonoChat’s form lets you choose the storage region for the message data Meta keeps at rest. The regions on offer are Australia, Indonesia, India, Japan, Singapore, South Korea, Germany, Switzerland, the United Kingdom, Brazil, Bahrain, South Africa, the UAE and Canada; there is no Saudi region. If the final Article 23 asks for a copy in the Kingdom, the place to keep it is your own infrastructure: MonoChat can run on-premises, on your own servers or a cloud region of your choice. Talk to us about MonoChat Enterprise.

Link your privacy notice from the opt-in message or the welcome flow, in Arabic first and in English for your non-Arabic-speaking customers. MonoChat’s AI agents answer each customer in the language they write in, so the same flow can serve both.

A note for banks and financial institutions

The PDPL is not the only rule that matters here. SAMA’s circular 000046025849 of 29 October 2024, “Using Instant Chat Applications to Communicate with Customers”, tells the institutions SAMA supervises not to use instant chat applications such as WhatsApp to communicate with customers, and to consider secure alternatives such as live chat or a chatbot in their own app or website. If you are such an institution, WhatsApp is out for customer messaging, whatever the PDPL’s final text says.

Checklist

  • Opt-in node in your welcome, post-purchase or ad flows, with wording that names what people will receive
  • Your own record of the consent wording, date and source for each customer
  • Offer audiences built from Opt-in = Yes, not from order history
  • Separate utility templates (service) and marketing templates (offers)
  • A “stop” flow that sets Opt-in to No and confirms, next to WhatsApp’s own stop
  • A decision on where conversations are stored, and whether you need on-premises
  • A privacy notice in Arabic, linked where you ask for consent

Payments and the rest of the Saudi stack

Consent is one part of selling on WhatsApp in Saudi Arabia. For payments, MonoChat sends links in the chat through Tabby, Tamara, HyperPay, Tap, PayTabs and MyFatoorah (with the payment methods enabled on your MyFatoorah account, mada among them, since MonoChat 3.8.48); see buy now, pay later on WhatsApp. Meta bills its message fees directly, and MonoChat adds no markup. MonoChat’s Basic plan is free and Growth is $120 a month. Start at app.monochat.ai, or read more on MonoChat in Saudi Arabia.

Sources

FAQ

Frequently asked questions

Are the PDPL amendments in force?

Not yet. SDAIA published them as a draft for public consultation on 6 October 2026, and comments closed on 5 November 2026. According to Clyde & Co, if they are adopted they enter into force 60 days after publication in the Official Gazette. No adoption date had been announced when we checked on 13 November 2026.

What changes for promotional WhatsApp messages?

Today's Implementing Regulations imply that a prior interaction with a customer can stand in for consent, according to Reed Smith. The draft would require consent for promotional or awareness messages in all circumstances, evidence of that consent, and clear and accessible ways to withdraw it. On withdrawal, the marketing and the processing behind it stop, and data generated by that processing is destroyed without undue delay.

Does the draft require WhatsApp data to stay in Saudi Arabia?

Draft Article 23 adds a requirement for controllers to store personal data within the Kingdom, while still allowing lawful transfers abroad. Reed Smith calls the wording ambiguous: it may mean a local copy is always needed, or that in-Kingdom storage is the baseline unless a transfer is lawful. Meta's WhatsApp Cloud API offers no Saudi storage region today; the nearest are Bahrain and the UAE. Businesses that need their conversations on infrastructure they control can run MonoChat on their own servers.

Do service messages such as order updates need marketing consent?

The draft's consent rule is about promotional and awareness messages. Order confirmations, delivery updates and appointment reminders are service messages in Meta's terms (utility templates). Meta's own rules still require an opt-in before any business-initiated WhatsApp message, and a utility template must not carry an offer.

Can Saudi banks use MonoChat on WhatsApp?

Not for customer messaging over WhatsApp. SAMA's circular 000046025849 of 29 October 2024 tells the institutions it supervises not to use instant chat applications such as WhatsApp to communicate with customers, and to look at live chat or a chatbot inside their own app or website instead.

Is this legal advice?

No. It is a summary of a draft and of the commentary we cite, to plan with. Ask your counsel how the final text applies to you once SDAIA publishes it.

First month of Growth on us

Run WhatsApp, Instagram and Messenger from one inbox

Start free with MonoChat: shared team inbox, AI assistants, templates and campaigns on official Meta APIs.

One code per business • 30 days to redeem • No card needed

$150 to get started.

Claim