You are about to hand a vendor access to every conversation your customers will have with your business. Before that contract is signed, you need written answers to a specific set of questions.
This chatbot data security checklist is not a build guide. It is a procurement document you send to the vendor, and the answers tell you whether you should sign at all.
Most UAE businesses do not discover the gaps until after deployment, when a customer complains, a regulator asks a question, or a subprocessor changes its terms. By then the leverage is gone. Ask now.
Key Takeaways
- Developer checklists don't protect chatbot buyers — Standard chatbot security guides cover OWASP Top 10 mappings, intent classifier hardening and platform configuration lists — useful for engineers, useless for the operations lead about to sign the SOW. This one is a vendor questionnaire to send before signature.
- DIFC and ADGM layer on top of PDPL — Federal Decree-Law No. 45 of 2021 has applied since 2 January 2022 as the mainland baseline. Entities registered in DIFC or ADGM sit under those free zones' own data protection regimes as well, so ask the vendor which specific regime governs your engagement.
- Ownership and deletion rights need a written clause — Many vendor MSAs default conversation data ownership to the vendor, with the customer holding only a licence. Insist on an explicit clause confirming your business owns all conversation data, plus a written retention schedule and deletion process.
- Unauthorized outbound WhatsApp risks a AED 150,000 fine — Cabinet Resolutions 56 and 57 of 2024, in force since 27 August 2024, require TDRA approval and Do Not Call Registry checks before outbound messages. DNCR breaches escalate from AED 50,000 to AED 75,000 to AED 150,000 by the third offence.
- No written answers means no real controls — A vendor who cannot produce a DPA, a data retention policy and an access control document on request has not built those controls. Watch too for clauses reserving the right to use anonymised conversation data for model improvement without an explicit opt-out.
What Every Other Chatbot Security Checklist Gets Wrong
Search for chatbot security and you get developer documents. OWASP Top 10 mappings, intent classifier hardening, dialog management notes, platform configuration lists.
Useful if you are writing the code. Useless if you are the operations lead about to sign the SOW.
The buyer's exposure begins the moment the vendor receives access to a single customer message, before a line of production code runs. That is why this checklist has to arrive before the contract does, not after go-live.
Every question below expects a written answer on the vendor's letterhead. If the answer is verbal, it does not exist.
This document sits downstream of a broader framework. If you have not yet defined what your agent is and is not allowed to promise, start with our guide to AI guardrails and come back when the boundaries are drafted.
Data Ownership, Residency and Deletion Rights
Photo: panumas nikhomkhai on Pexels
Who legally owns the conversation logs? Read the vendor's standard MSA carefully.
Many default ownership of conversation data to the vendor, with the customer holding a licence to use it. Ask for an explicit clause that says the business retains full ownership of all customer conversation data, in every format, on every system.
Then ask for the retention schedule in writing. How long are logs kept, on which servers, in which country, under whose legal jurisdiction? A vendor that cannot answer the country question in one sentence is not going to answer it better later.
Deletion rights are the third piece. If a customer asks you to erase their conversation history, what is the vendor's documented process, and how long does it take?
Include subprocessors in the same question: does the vendor pass conversation data to a third-party LLM or NLP provider, and does that data feed model training? Under PDPL, both matter, and both belong in the DPA before you sign.
UAE Law: What PDPL, DIFC and ADGM Require Your Vendor to Prove
Federal Decree-Law No. 45 of 2021, the PDPL, has been in force since 2 January 2022 and sets the mainland baseline. Ask the vendor to confirm PDPL compliance in writing and to name the individual responsible for your account as data controller contact.
If your entity is registered in DIFC or ADGM, the mainland answer is not enough. Both free zones run their own data protection regimes that layer on top of PDPL for entities operating inside them.
A vendor who responds with a generic "GDPR-equivalent" line has not read your registration. Push back and ask which specific regime governs your engagement, and what the vendor has done to comply with it.
Request a signed Data Processing Agreement before the MSA is executed, not after. Under PDPL the DPA is the mechanism through which you transfer processing obligations to the vendor and establish where liability sits when something goes wrong. No DPA, no signature.
If the chatbot will send outbound or marketing messages, Cabinet Resolutions 56 and 57 of 2024 apply too. They took effect on 27 August 2024 and require TDRA prior approval and Do Not Call Registry checks before outbound campaigns run.
First DNCR breach is AED 50,000. Second is AED 75,000. Third is AED 150,000.
Ask the vendor how their platform enforces DNCR screening at the message level, not the campaign level.
DNCR penalties escalate with each repeat breach under Cabinet Resolutions 56 and 57 of 2024.
| Breach Number | Fine |
|---|---|
| First DNCR breach | AED 50,000 |
| Second DNCR breach | AED 75,000 |
| Third DNCR breach | AED 150,000 |
Access Control: Who at the Vendor Can Read Your Customers' Conversations
Every vendor has an internal team, and someone on that team has read access to your data. The question is who, how many, and under what conditions.
Ask for the role-based access control policy. How many vendor staff can view conversation logs? Does read access require manager approval?
Are those approvals logged? A vendor that says "only engineers who need it" without a policy document is describing an ad-hoc process, not a control.
Data isolation is separate from access control and equally important. Your customer conversations must not be reachable from another vendor client's admin account. Ask for evidence of tenant isolation, not a marketing claim about it.
Confirm multi-factor authentication on the admin dashboard. Password-only login for the dashboard that reads your customers' messages is not acceptable in 2026.
Then ask about audit logs: can you view a timestamped record of every internal access to your data, and how long are those logs retained? If the vendor cannot show you the log format, the log does not exist.
WhatsApp and Multi-Channel Data Security in the UAE
WhatsApp is the primary customer channel in the UAE. A customer will message on WhatsApp and expect a reply in minutes, which means most of your conversation volume, and most of your exposure, lives there.
Ask whether the vendor's WhatsApp Business API integration encrypts message payloads in transit and at rest, independently of the platform-level encryption Meta provides. Where are those payloads logged, and for how long? "Encrypted by WhatsApp" is not an answer about what happens inside the vendor's own systems.
Channel authorization is next. The chatbot must only send messages to numbers that have explicitly opted in, and the platform must have controls preventing unauthorized bulk outbound sends.
This is where the Cabinet Resolutions 56 and 57 obligations bite hardest, because a rogue outbound campaign triggers TDRA scrutiny in hours, not weeks. This is why defining which channels and tools your agent can initiate on its own belongs in the contract, not in a config file someone can edit later.
Then there is bilingual data handling, which is a UAE-specific exposure point. Your customers write in Arabic, English, and a mix of both, sometimes in Arabizi.
Ask explicitly: is Arabic text sent to a third-party NLP or LLM processor, and under which data agreement is that transfer covered? A vendor that has thought about English but not Arabic has not thought about your market.
Output Guardrails: What Your Chatbot Must Never Be Allowed to Say or Do
Photo: Tobias Scheuer on Pexels
Uncontrolled output is a security problem, not just a quality one. A chatbot that invents a price, fabricates a return policy or promises a service you do not offer creates contractual and regulatory exposure the moment a customer relies on it. The Chevy Tahoe incident, where a dealership bot agreed to sell a truck for one dollar, is what unbounded output looks like.
Ask the vendor how output guardrails are enforced. Hard-coded rules, a separate validation layer, or model-level fine-tuning?
Can you, the business, define and update those limits without the vendor's involvement, or does every rule change require a support ticket? Wrong prices, fake policies and invented promises need to be blocked at the output layer before the customer sees them.
The financial arithmetic is straightforward. Proper guardrails cost a fraction of a single output incident, and the incident is one you cannot budget for because you do not know when it lands.
Book the Review Before You Sign
Once you have the vendor's written answers, bring the responses to a consultation and we will give you an honest read on the setup before you commit. Start a conversation with our team before the contract goes back.
Red Flag Answers, and What to Do Before You Sign
A vendor who cannot produce a written DPA, a data retention policy, and an access control document on request has not built those controls. The checklist did not create the gap. It surfaced one that was already there.
Watch for this contract clause in particular: "we reserve the right to use anonymised conversation data for model improvement" without an explicit opt-out. This is a data ownership red flag, it conflicts with PDPL obligations, and it must be negotiated out before signature.
Anonymisation is not a get-out from consent.
If the vendor is hosted outside the UAE and cannot confirm exactly where data is processed, that is a cross-border data transfer trigger under PDPL. It is not a technicality to accept on verbal assurance. Ask for the country, the data centre, and the legal basis in one written answer.
The last step is not more paperwork. It is a conversation with someone who can read the vendor's responses and tell you honestly whether the setup holds up under UAE law. That is the review our team offers.
FAQ
Does the UAE's PDPL require a chatbot vendor to sign a data processing agreement before deployment?
Yes. Under Federal Decree-Law No. 45 of 2021 the DPA transfers processing obligations from controller to processor and sets liability boundaries. Sign it before the MSA is executed.
What is the difference between DIFC data protection rules and the mainland UAE PDPL for chatbot deployments?
DIFC and ADGM run their own data protection regimes that apply to entities registered or operating in those free zones, layered on top of the mainland PDPL baseline. Which regime governs your engagement depends on where your entity is registered.
Who legally owns the conversation logs, my business or my chatbot vendor?
That depends entirely on what the contract says. Many vendor MSAs default ownership to the vendor with the customer holding a licence. Insist on an explicit clause confirming the business retains full ownership.
If my vendor suffers a data breach, what are my obligations under UAE law?
The business remains the data controller under PDPL and carries the primary notification obligation. Your DPA should require the vendor to notify you of any incident within a defined window, in enough detail to meet your own regulatory disclosure duties.
Do UAE regulations require businesses to disclose to users that they are speaking with a chatbot rather than a human?
Transparency in automated processing is a core PDPL principle, and best practice is to tell users clearly at the start of the conversation. Ask your vendor to show you the default disclosure copy.
Can a vendor hosted outside the UAE legally store and process my customers' conversation data?
It is possible, but it triggers cross-border data transfer requirements under PDPL that must be documented in the DPA. If the vendor cannot tell you which country the data lives in and on what legal basis it left the UAE, that is not a workable answer.
What fines can a UAE business face under Cabinet Resolutions 56 and 57 of 2024 if a chatbot sends unsolicited outbound messages?
Do Not Call Registry breaches carry fines of AED 50,000 for a first offence, AED 75,000 for a second, and AED 150,000 for a third, under the Cabinet Resolutions that took effect on 27 August 2024. The chatbot's outbound controls must screen against DNCR at the message level.
