UK GDPR and live chat meet the moment a visitor types a name, an e-mail address or an order number into your website widget. That message is personal data, and the rules that apply to it in the United Kingdom are the UK GDPR, the Data Protection Act 2018 and, for cookies and similar technologies, the Privacy and Electronic Communications Regulations, usually shortened to PECR.
This guide explains in plain language what a UK business should decide before it adds a chat widget and an AI assistant. It is general information, not legal advice, and the rules have been amended since 2021, so confirm the points that matter with your data protection lead or a qualified adviser and with current guidance from the regulator.
How UK GDPR Applies to a Chat Widget
After Brexit, the UK kept the European GDPR as domestic law, with changes, and it is now called the UK GDPR. It sits beside the Data Protection Act 2018, which covers areas such as exemptions and the regulator’s powers. The regulator is the Information Commissioner’s Office, whose UK GDPR guidance and resources are the best primary source.
The UK GDPR applies to organisations established in the UK and to organisations elsewhere that offer goods or services to people in the UK or monitor their behaviour. A shop in Dublin that sells to British customers should treat the rules as relevant. Our broader guide to GDPR and live chat covers the EU version, and most of it carries over, with the UK differences described below.
Who is who
- Controller: your business, which decides why and how chat data is used.
- Processor: the chat vendor, which handles data on your instructions. Talkmio plays this role for the conversations on your account.
- Data subject: the visitor who writes to you.
What Personal Data a Chat Collects
Start with an inventory, because you cannot describe or protect what you have not listed. A typical chat system records:
- the text of every message the visitor and your team write;
- anything volunteered in a chat: name, e-mail, phone number, address, order number, complaint details;
- technical context such as country, page, device and browser, which Talkmio uses to show context in the Inbox;
- contact records and conversation history, so returning visitors are recognised;
- attachments and screenshots.
Visitors sometimes share special category data, such as health information, without being asked. Your chat cannot prevent that, so decide in advance how your team responds: do not request it, tell visitors not to send it in chat and move such cases to a secure channel.
Choose a Lawful Basis for Each Use
Under the UK GDPR every use of personal data needs a lawful basis. Chat usually involves more than one.
| Use of chat data | Likely lawful basis | Note |
|---|---|---|
| Answering a customer’s question | Contract or legitimate interests | Use contract when the visitor is a customer or about to become one |
| Handling complaints and orders | Contract or legal obligation | Keep a record you can show a regulator or a court |
| Improving answers and staff training | Legitimate interests | Record your balancing test and minimise personal details |
| Sending marketing after a chat | Consent, or soft opt-in where PECR allows it | Never bundle marketing consent into a support chat |
| Setting non-essential cookies for the widget | Consent under PECR | Check which cookies the widget actually sets |
The point is to decide and write it down. A short record of the basis for each use is what a regulator, or a customer who asks, will want to see.
Cookies, Storage and PECR
PECR covers storing or reading information on a visitor’s device. If a chat widget sets cookies or uses local storage that is not strictly necessary for the service the visitor asked for, you need consent before it runs. Some chat functions may count as essential, but do not assume. Check what your widget stores, list it in your cookie notice and make sure your consent tool controls it correctly.
The UK has reformed parts of this area recently, including exceptions for some low-risk technologies, so read the ICO’s current cookie guidance rather than relying on older advice. Our article on chat widget cookies and consent explains how to map what a widget stores to your banner categories.
Transparency: Tell Visitors What Happens
People should know, in plain language, who you are, why you collect chat data, which lawful basis you rely on, who receives it, how long you keep it and how to exercise their rights. Put this in your privacy notice, and add a short pointer near the widget, for example in the welcome text: “Chat messages are stored to help us answer you. See our privacy notice.”
If an AI assistant answers the first message, say so. A visitor should not believe a person is writing when software is. Talkmio’s own approach is that Mio answers only from your website, FAQ and uploaded files, and hands the chat to a person when it cannot answer. For help with the notice itself, see our guide to a live chat privacy policy.
International Transfers and Data Location
The UK restricts transfers of personal data to other countries unless a safeguard applies, such as an adequacy decision or approved contract terms. UK rules currently treat the European Economic Area as adequate, which matters because Talkmio stores data on servers in the EU, in Germany. Only conversation text and relevant knowledge base excerpts go to the AI model provider.
Do not stop there. Ask any vendor for its list of sub-processors, the countries involved and the transfer mechanism for each, and file the answer with your records. Our guide to EU data residency for live chat gives a checklist of questions.
Rights Requests: Access, Deletion and More
Visitors can ask what you hold about them, ask for corrections, object to certain processing and, in some cases, ask for deletion. You normally have one month to respond, which can be extended for complex requests. A chat makes this practical if you plan for it.
- Verify the requester’s identity before you disclose anything.
- Search the Inbox by name, e-mail or text, and check the Contacts record.
- Export or delete the data. Talkmio lets you export or delete data at any time, and [email protected] can help with platform-side removal.
- Reply in writing and keep a short log of the request, the date and what you did.
Our guide to data subject access requests in live chat contains a reply template.
Retention, Security and Records
Keep chats only as long as you need them. A customer-service history that helps with repeat contacts may justify months or a few years, depending on your business. Marketing leads and anonymous questions do not need the same period. Write down a rule and apply it. Plan limits on history, such as 30 days on Free, 365 days on Pro and unlimited on Ultimate, are product limits, not a legal recommendation, so set your own retention policy independently.
- Access: give agents the lowest role that lets them work. In Talkmio, Agents handle conversations while Admins also manage websites, Mio and settings.
- Records: keep a record of processing that lists chat as an activity.
- Assessment: for AI features or large-scale monitoring, consider a data protection impact assessment.
- Incidents: know who decides whether a breach must be reported to the ICO within 72 hours.
- Fee: most UK controllers must pay the ICO data protection fee. Check whether it applies to you.
AI Assistants and UK GDPR Live Chat
Adding an AI assistant to a chat does not change who is responsible, but it adds questions you should answer in advance.
- What goes to the model? In Talkmio, only the conversation text and relevant knowledge base excerpts go to the AI model provider. Your visitors’ IP, country and device data are used to show context in the Inbox.
- Is there automated decision-making? Answering product questions is not the same as a decision with legal or similarly significant effects, which the UK GDPR restricts. Keep decisions about refunds, credit or eligibility with a person, and tell Mio never to promise them.
- Can people reach a human? Mio hands the conversation to your team when it cannot answer from your content, when the visitor asks for a person, complains or asks about an order. Keep that route visible.
- Is the content accurate? Because Mio answers only from your own pages and files, inaccurate answers usually trace back to outdated content. Accuracy is a data protection principle too, so keep the knowledge base current.
If your use is large scale, or you add features that profile visitors, consider a data protection impact assessment before launch, and record the result.
Special Cases: Children, Employees and B2B
Children
If your site is aimed at children, or likely to be used by them, the ICO’s children’s code applies and the bar for transparency and data minimisation is higher. Use simple language, avoid collecting more than you need and do not rely on a child’s consent for marketing.
Employees and intranets
If you run chat on an internal portal for staff questions, remember that employees are data subjects too. Tell them what is stored, who can read chats and how long they are kept, and do not use chat transcripts for monitoring unless you have a clear, documented reason.
Business customers
Business-to-business chats still contain personal data, such as the name and work e-mail of the person writing. The same rules apply, although the lawful basis is more often legitimate interests or contract than consent.
A UK GDPR Live Chat Checklist
| Area | Question | Done when |
|---|---|---|
| Inventory | What does the chat collect? | A written list exists |
| Lawful basis | Which basis covers each use? | Recorded for support, training and marketing |
| Notice | Does the privacy notice mention chat and AI? | Published and linked from the widget |
| Cookies | What does the widget store? | Listed and controlled by your consent tool |
| Vendor terms | Do you have the processing terms and sub-processor list? | Requested and filed |
| Rights | Who answers requests, and how fast? | A named person and a template |
| Retention | How long do chats stay? | A rule is written and applied |
For the vendor paperwork, our guide to a data processing agreement for live chat explains what to ask for.
Frequently Asked Questions
Does UK GDPR apply to live chat on my website?
Yes, if you are in the UK or you offer goods or services to people in the UK. Messages, names, e-mail addresses and order numbers are personal data. Treat the chat like any other data collection point and include it in your records and privacy notice.
Do I need consent to use live chat under UK GDPR?
Not always. Answering a customer’s question can rest on contract or legitimate interests. Consent is needed for marketing in many cases and for non-essential cookies under PECR. Record the basis for each use and keep marketing consent separate from support.
Is a chat vendor a processor under UK GDPR?
Normally yes. You decide why and how the data is used, so you are the controller, and the vendor handles it on your instructions as a processor. Ask for the vendor’s processing terms and its list of sub-processors, including any AI provider.
Can I use a chat provider that stores data in the EU?
UK rules currently treat the European Economic Area as adequate for transfers, so EU storage is generally workable. Talkmio stores data on servers in Germany. Confirm the current position with the ICO guidance and check sub-processors for transfers elsewhere.
How long should I keep chat transcripts?
Only as long as you need them for the purpose you stated, such as customer service or handling disputes. Set a written retention period for each purpose, apply it and delete or anonymise afterwards. There is no single legal number that fits every business.
Do I have to say that a chatbot is answering?
Transparency is a core principle, and visitors should not be misled about who they are talking to. Say clearly that an AI assistant answers first, explain that a person can take over and keep the wording simple, for example in the welcome text.
The Bottom Line
UK GDPR and live chat come down to knowing what the widget collects, choosing a lawful basis, controlling cookies, telling visitors clearly, handling rights requests quickly and keeping data only as long as needed. Review the chat once, write the answers on a single page and revisit them when your plan or provider changes. Create a free Talkmio account, add your site and use the checklist above to set up a chat that respects your visitors’ data.
