GUIDE
Is an AI chatbot GDPR compliant in the UK? What a business owner must check
Last updated: · By Muhammad Abdul Ahad
Short answer
No chatbot is compliant by itself: compliance depends on how your business uses it. If a chatbot handles personal data such as names, emails or phone numbers, you need a lawful basis, clear privacy information, a contract with the vendor and a view on international transfers and risk. This guide is not legal advice.
Is an AI chatbot GDPR compliant in the UK?
A chatbot is not compliant or non-compliant on its own. The UK GDPR applies to what your business does with personal data, so compliance comes from how you set the chatbot up, what you tell people and what contract you have with the vendor. If your chatbot collects names, email addresses, phone numbers or free-text messages, the rules apply.
This guide is a practical checklist, not legal advice. The ICO notes that several of its pages are under review following the Data (Use and Access) Act, so check the linked pages for current wording and take professional advice for anything high-risk.
What personal data does a chatbot usually handle?
Think about what customers type, not only the forms you add. Typical examples are:
- Names, email addresses and phone numbers given for a booking or callback.
- Free-text messages, which can contain anything: health details, addresses, order problems.
- Booking details such as dates, times and services requested.
- Conversation history stored so your team can read it later.
Free text is the part owners overlook. A customer can volunteer sensitive information you never asked for, so decide what the assistant should do about it, for example by inviting them to contact the team directly for anything private.
What is your lawful basis?
You need a lawful basis for processing personal data and should document it before you start. The ICO lists seven: consent, contract, legal obligation, vital interests, public task, recognised legitimate interest and legitimate interests. The ICO also says no single basis is better than another. Pick the one that fits the purpose.
For a chatbot that answers a customer's question or books the appointment they asked for, that is often a question of whether the processing is needed to deliver what they requested, but that is for you to decide and record. If you also use chat data for marketing, treat that as a separate purpose with its own basis.
What must you tell people?
You must provide privacy information, and the ICO says it must cover who you are, why you use the data, your lawful basis, who you share it with (including anyone processing it on your behalf), how long you keep it, and people's rights including the right to complain to the ICO. Where data goes outside the UK, you must say so and describe the safeguards.
Practical steps:
- Add a short line in the chat window that this is an AI assistant, with a link to your privacy notice.
- Update the privacy notice to name chat, bookings and lead capture as purposes, and the vendor or category of vendor as a recipient.
- State a retention period, or the criteria you use, for chat records and leads.
Do you need a contract with the vendor?
Yes. The ICO says a processor must enter into a binding contract with the controller, containing specific compulsory provisions. A processor must act only on your instructions, keep data secure, tell you about a breach without undue delay, and get your written authorisation before using a sub-processor.
Ask the vendor for its data processing terms, a list of sub-processors, and what happens to your data when you cancel. If a vendor cannot show you these, treat that as a warning.
Where does the data go?
A restricted transfer is a transfer of personal data to a separate organisation outside the UK, including making it accessible. Each one needs a mechanism: UK adequacy regulations, appropriate safeguards such as the IDTA or the UK Addendum, together with a transfer risk assessment, or a narrow exception. AI tools often use model providers and hosting in several countries, so ask the vendor:
- Where is conversation data stored and processed?
- Which sub-processors, including AI model providers, see the content?
- Which transfer mechanism covers each one?
- Is my data used to train models? Get the answer in writing.
We do not give a general answer for any vendor, including ARIMEX. Ask the specific questions and keep the replies.
Do you need a DPIA?
A data protection impact assessment is required where processing is likely to result in high risk to people. The ICO lists artificial intelligence, machine learning and deep learning as examples of innovative technology, and says it requires a DPIA when combined with another risk criterion such as evaluation or scoring, or sensitive data. If you are unsure, the ICO recommends doing one.
A chatbot that only answers opening-hours questions is a different risk from one that scores leads or collects health information. Write down your reasoning either way, and keep it short.
What about automated decisions?
Article 22 of the UK GDPR is headed "Automated individual decision-making, including profiling". The ICO's AI guidance links solely automated decision-making to fairness. The point for a small business is simple: do not let a chatbot make decisions with legal or similarly significant effects on a person, such as refusing a service, without human involvement. Lead scoring that only helps your team prioritise follow-up is different from an automatic refusal, but check Article 22 as currently in force on legislation.gov.uk, which has been amended by the Data (Use and Access) Act 2025.
What is the owner's checklist?
- Decide what personal data the chatbot collects and why.
- Record a lawful basis for each purpose.
- Add an AI disclosure and a privacy notice link in the chat.
- Update the privacy notice, including recipients, retention and transfers.
- Sign or accept the vendor's data processing terms and review sub-processors.
- Ask where data is stored and which transfer mechanism applies.
- Decide whether a DPIA is needed and record why.
- Restrict the widget to your own domains where the product allows it.
- Set who in your team reads chats and how to delete a person's data on request.
- Review it again after any change in features, such as adding WhatsApp.
ARIMEX can answer these questions for your setup in a call. Book a demo and bring this list.
Related pages
Frequently asked questions
Is an AI chatbot automatically UK GDPR compliant?
No. The UK GDPR applies to how you use the tool and the personal data it handles, not to the product label. A vendor can help with security and contract terms, but you remain responsible for your own use.
Do I need to tell website visitors they are talking to an AI?
The ICO's guidance on explaining AI-assisted services is about being transparent with the people affected. As good practice, say clearly in the chat that it is an AI assistant, and link your privacy notice. Check ICO guidance or take advice for your case.
Do I need a data protection impact assessment (DPIA) for a chatbot?
Not always. The ICO says a DPIA is required where processing is likely to result in high risk, and it lists artificial intelligence as innovative technology that needs a DPIA when combined with another risk factor. If unsure, the ICO recommends doing one.
Is the chatbot vendor a data controller or a processor?
Usually your business decides why and how personal data is used, which makes you the controller, while the vendor acts on your instructions as a processor. The ICO says a processor must have a binding written contract with the controller.
Can a chatbot send customer data outside the UK?
It can, but a transfer to a separate organisation outside the UK needs a valid transfer mechanism, such as UK adequacy regulations or appropriate safeguards. Ask your vendor where data is processed and which mechanism applies.
Sources
- ICO - Guidance on AI and data protection (accessed )
- ICO - Explaining decisions made with artificial intelligence (accessed )
- ICO - When do we need to do a DPIA? (accessed )
- ICO - What does it mean if you are a processor? (accessed )
- ICO - What privacy information should we provide? (accessed )
- ICO - International transfers, a guide (accessed )
- ICO - A guide to lawful basis (accessed )
- UK GDPR Article 22 on legislation.gov.uk (accessed )