Saudi and UAE data protection law and an AI shopping assistant.

Updated
Saudi Arabia's Personal Data Protection Law (PDPL), enforced by SDAIA since 14 September 2024, and the UAE's Federal Decree-Law No.
Read moreShow less
Saudi Arabia's Personal Data Protection Law (PDPL), enforced by SDAIA since 14 September 2024, and the UAE's Federal Decree-Law No. 45 of 2021 both apply to the personal data an AI shopping assistant handles: messages, voice, basket, identity and delivery details.
bisky never uses conversations to train AI models, runs on servers in the European Union today, and lets each retailer set retention and delete a shopper's data on request. We follow the principles of both laws and we do not claim a certification. We go through each retailer's requirements with its team. This page is not legal advice.
What do the Saudi and UAE data protection laws say?
Both laws cover shoppers' data wherever it is processed and set rules for sending it abroad. Saudi Arabia's PDPL is enforced by SDAIA; the UAE law still waits on its Executive Regulations.
Read moreShow less
Sources checked on 5 November 2026; the Saudi consultation dates and the Clyde & Co citation re-checked on 19 November 2026. Laws and regulations change. Ask your lawyer for the current position.
| Saudi Arabia | UAE | |
|---|---|---|
| The law | Personal Data Protection Law (PDPL), with Implementing Regulations and Transfer Regulations | Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data |
| Regulator | Saudi Data and AI Authority (SDAIA) | UAE Data Office |
| In force | 14 September 2023, fully enforceable from 14 September 2024 | In force since 2 January 2022. Full implementation waits on the Executive Regulations |
| Reach | Processing in the Kingdom, and organisations abroad processing data of people in Saudi Arabia | Processing in the UAE, and controllers abroad processing data of people in the UAE. Not the DIFC or ADGM |
| Transfers abroad | Adequacy, or safeguards such as SDAIA's standard contractual clauses, with a risk assessment | Adequate protection, or routes such as a contract or the person's explicit consent |
| Open questions on 5 November 2026 | Draft amendments, consulted on until 5 November 2026, would add a storage-in-Kingdom requirement | We could not confirm that the Executive Regulations have been published |
Saudi Arabia
The PDPL took effect on 14 September 2023, a week after SDAIA published its Implementing Regulations and the Regulations on Personal Data Transfer outside the Kingdom (Clyde & Co, September 2023). A one-year grace period followed, and the law became fully enforceable by SDAIA on 14 September 2024 (Clyde & Co, 10 September 2024). It reaches organisations outside Saudi Arabia that handle the personal data of Saudi residents. People have rights to be informed, to access their data, to have it corrected and to have it destroyed, and controllers must keep records of processing. Transfers abroad need an adequacy decision or safeguards such as SDAIA's standard contractual clauses.
Two changes are in draft. Today a controller must notify SDAIA of a breach within 72 hours where it is likely to cause harm. Draft amendments to the Implementing Regulations would require notice to SDAIA of any breach within 72 hours, whether or not harm is likely, add an express requirement to store personal data within the Kingdom, and make registration mandatory for controllers that transfer data abroad. The public consultation ran from 6 October to 5 November 2026 (Clyde & Co, 8 October 2026). If the storage requirement is adopted, it matters for any provider hosting outside Saudi Arabia, including us.
The UAE
Federal Decree-Law No. 45 of 2021 was issued on 20 September 2021 (Simmons & Simmons, 6 December 2021) and came into force on 2 January 2022 (Chambers and Partners, Doing Business in the UAE 2025). It applies to controllers and processors in the UAE and to those abroad processing the data of people in the UAE. It does not apply to free zones with their own data protection laws, such as the DIFC and ADGM, or to health and banking data governed by their own laws. Consent is the main legal basis and must be specific, clear and unambiguous, and people can withdraw it. They can ask to access, correct and erase their data and to restrict its processing. The UAE Data Office oversees the law.
Full implementation waits on the Executive Regulations, which Chambers and Partners described as not yet formally released. As of 5 November 2026 we could not confirm from an official source that they have been published, and secondary sources disagree.
What personal data does an AI shopping assistant handle?
For bisky, these are the kinds of personal data in a shopper's conversation.
Read moreShow less
| Kind | What it is | How it is used |
|---|---|---|
| Messages | What the shopper types, voice notes (transcribed), and calls with their transcripts | Shown in your inbox, deleted with the conversation |
| Basket and orders | Products, quantities, checkout, order status | Sent to your platform or team when the shopper confirms |
| Identity | Your shopper id, or a WhatsApp number and profile name, and a name and phone where given | Used to keep one basket and to deliver |
| Delivery details | Address or location pin, to choose the branch and deliver | Address consent is recorded with a date |
| Photos and voice notes | Media a shopper sends on WhatsApp | Served only to your signed-in team |
| Remembered preferences | Usual products, preferences, dietary needs | Only if you turn memory on and the shopper says yes |
Shoppers do not create accounts with us. They talk to your store, and you are the controller of their data. bisky processes it to run the assistant for you. Each retailer's data is kept apart from every other retailer's. Phone numbers and emails are masked in the traces we use to debug replies.
How do consent, retention and deletion work?
- ConsentThe legal basis for each kind of processing is the retailer's to decide with its lawyers.
- RetentionEach retailer sets how long conversations are kept.
- DeletionYour team can request deletion of a shopper's data from the dashboard or through the API.
Read moreShow less
Consent
The legal basis for each kind of processing is the retailer's to decide with its lawyers. The product records the consents it collects, each with a date and a version: that the privacy notice was shown, that a delivery address may be kept, and a shopper's marketing opt-in or opt-out. Memory is off unless you turn it on. When it is on, the assistant asks a shopper you have identified, once, whether it may remember things such as usual products. It saves nothing without a yes and clears it when the shopper says forget. Call recording is off by default.
Retention
Each retailer sets how long conversations are kept. The default is 365 days after a conversation's last message, and a daily job deletes conversations past the retailer's period, with their messages, basket and reports.
Deletion
Your team can request deletion of a shopper's data from the dashboard or through the API, for example when the shopper asks you. Conversations, the shopper's profile and sessions, saved addresses, photos and voice notes, and debugging traces are deleted. Orders are kept for your accounts with the shopper's identifier removed. Your team can follow each request's status in the dashboard.
Where is the data processed, and by whom?
Our application and database servers are in Gravelines, France, in the European Union.
- AI model providersReplies are written by a language model whose hosts may be in the United States or other countries.
- Search and relevanceThe words of a search are turned into a form the catalogue search can compare.
- Speech providersVoice notes and calls are turned into text, and replies into speech, by speech providers for each language.
- Hosting, files and operationsServers in France, file storage, site delivery, email, WhatsApp delivery through Meta, and alerts to our own staff.
Read moreShow less
Our application and database servers are in Gravelines, France, in the European Union. We do not host in Saudi Arabia or the UAE today. Some of the companies that process data for us are outside the EU, so parts of a conversation leave it while a reply is being made:
- AI model providers. Replies are written by a language model whose hosts may be in the United States or other countries. Every request that can carry conversation data is sent with data collection denied, and we never train models on conversations.
- Search and relevance. The words of a search are turned into a form the catalogue search can compare, and a fast check compares results with the shopper's message.
- Speech providers. Voice notes and calls are turned into text, and replies into speech, by speech providers for each language, some of them in the United States.
- Hosting, files and operations. Servers in France, file storage, site delivery, email, WhatsApp delivery through Meta, and alerts to our own staff.
We give your team the full list, with each company and region, together with a data processing agreement, before launch. Platform credentials you give us are encrypted. Your team signs in to the dashboard in two steps, and an audit log records what staff do. More on security and data handling.
What do we not claim?
- No certificationbisky holds no ISO 27001 or SOC 2 certification, and no certification under either data protection law.
- No compliance badgeWe follow the principles of both laws, and we do not state that using bisky makes a retailer compliant.
- No local hosting todayData is not stored in Saudi Arabia or the UAE.
- Not legal adviceThis page summarises public sources with dates.
Read moreShow less
- No certification. bisky holds no ISO 27001 or SOC 2 certification, and no certification under either data protection law.
- No compliance badge. We follow the principles of both laws, and we do not state that using bisky makes a retailer compliant. That depends on the whole processing, including yours.
- No local hosting today. Data is not stored in Saudi Arabia or the UAE. Tell us your residency requirements and we will go through them with your team.
- Not legal advice. This page summarises public sources with dates. Your lawyer decides how the laws apply to you.
What should a retailer check before going live?
A checklist for an AI shopping assistant that will talk to shoppers in Saudi Arabia or the UAE.
- 01
Map the data
List what the assistant collects on each channel, using the table on this page, and add it to your records of processing. - 02
Update your notice
Tell shoppers in your privacy notice that an AI assistant answers them, what it keeps, for how long and who processes it. - 03
Decide transfers
Our servers are in the EU and AI model providers may be elsewhere. Choose the transfer route your lawyer is comfortable with. - 04
Set retention and memory
Pick a retention period shorter than the default if you need one, and decide whether the assistant may remember anything.
Read moreShow less
- Confirm whether your entity is in a free zone with its own law, such as the DIFC or ADGM.
- Check whether you need a data protection officer under the Saudi PDPL, for example if you process sensitive data or monitor people regularly.
- Agree a data processing agreement with every vendor that touches shopper data, including us, and review the list of companies that process data for them.
- Decide who answers access, correction and deletion requests, and test a deletion end to end before launch.
- Agree how a breach is reported to you, so you can meet SDAIA's 72-hour window.
- Turn on only the channels and memory you have covered in your notice, and keep call recording off unless you need it.
Data protection and AI shopping, answered.
Something we did not cover? Write to us; a person replies.
Write to hello@bisky.aiIs bisky certified under the Saudi or UAE data protection law?
No. We follow the principles of both laws, and we do not claim a certification. This page explains how bisky handles shopper data, and we go through your requirements with your legal and data protection team before launch. Meeting the law also depends on how you, the retailer, collect and use the data.
Where is shopper data stored?
Our application and database servers are in Gravelines, France, in the European Union. Requests to AI models go through providers that may be in the United States or other countries. We do not host in Saudi Arabia or the UAE today.
Are conversations used to train AI models?
No. We never train AI models on conversations, and every request to a language model that can carry conversation data is sent with data collection denied, on every channel.
Can a shopper's data be deleted?
Yes. Your team can request deletion of a shopper's data from the dashboard or through the API. Conversations, the shopper's profile and sessions, saved addresses, media and debugging traces are deleted. Orders are kept for your accounts with the shopper's identifier removed. Your team can follow each request.
How long are conversations kept?
Each retailer sets its own retention period. The default is 365 days after a conversation's last message, and a daily job deletes conversations past it.
Does the UAE law apply in the DIFC and ADGM?
No. Federal Decree-Law No. 45 of 2021 does not apply to free zones with their own data protection laws, such as the DIFC and ADGM. Retailers there follow those zones' own laws.
Is this page legal advice?
No. It is a plain summary of the laws as public sources describe them, with dates, and of how our product handles data. Ask your own lawyer how the laws apply to you.
Go through your requirements with us.
Bring your data protection questions to the demo. We walk your team through how the assistant handles shopper data.




