Chat Platforms and Your Privacy Notice: What Website Chat Records About Visitors, and the Paragraph to Add (Free Notice Builder)
Chat platforms collect more than the messages people type, and most small-business privacy notices never mention any of it. A website chat can record which pages a visitor viewed, where they came from, their country and device, the email they left in an away form, and the ticket their question became. This guide shows you how to list what your own chat records, write it down in plain words, decide how long to keep it, and tell visitors how to ask for it to be deleted. A free builder writes the first draft from a few ticks.
⚡ In short
- Your website chat records visit details, messages and contact details. Your privacy notice should say so in plain words.
- List what is switched on in your own chat dashboard before you write anything.
- Write one short section: what is collected, why, who stores it, how long you keep it, and how to ask for deletion.
- Pick a retention period and actually delete old chats, including copies in sheets and CRMs.

Why it matters
What chat platforms record that visitors don’t expect
Most visitors think of a chat box as a conversation, like a phone call that ends when they close the tab. In practice, the tool behind it keeps a record. That record is useful for you: it lets your team see what the visitor was looking at, pick up where yesterday’s chat left off, and follow up by email when nobody was online. But it also means your business is holding personal data, and the people it belongs to should be told.
In India, the Digital Personal Data Protection Act, 2023 (the DPDP Act) sets the rules for this. When you ask someone for personal data based on their consent, you are expected to give them a notice that describes the personal data and why you need it, how they can exercise their rights, such as getting it corrected or erased, and how they can complain to the Data Protection Board of India. Visitors can also ask for the notice in English or in any language listed in the Eighth Schedule of the Constitution.
You don’t need to be a lawyer to see what’s missing on most small websites. The privacy page, if there is one, was copied from a template years ago. It talks about cookies and newsletters, and says nothing about the chat that now handles half the enquiries.
This guide is not legal advice. It is a practical way to get from “we never wrote anything down” to a clear, honest draft you can show a lawyer, in about fifteen minutes. If you are still choosing a tool, our security and privacy checklist for AI chat software covers the questions to ask the vendor. This post covers the other half: what you tell your own visitors.
The data
What a typical website chat can hold
Not every business switches on every feature. Use this table to see what each one adds, then tick only what you use in the builder below.
| Data | Where it comes from | Why you keep it | What to say |
|---|---|---|---|
| Messages and replies | Every chat | To answer and follow up | Always mention it |
| Pages viewed, source, country, device | Visitor tracking | Context for replies; deciding when to show messages | Say what is recorded and why |
| Number of visits | Visitor tracking | Recognising returning visitors | Include with visit details |
| Email or phone number | Away form when offline | Replying later | Say you use it only to answer |
| Ticket history | Chats turned into tickets | Tracking a request until solved | Mention the ticket page link |
| Name and email of logged-in customers | Your website passing them to the chat | Saving customers retyping | Say it happens automatically |
| IP address | Blocking abusive visitors | Stopping spam and abuse | Say why you use it |
| Copies in other tools | Zapier, webhooks, REST API | Orders, CRM, follow-ups | Name the tools |
| Text processed for AI replies | AI answers | Answering common questions quickly | Say replies may be automated |
Step 1
Map your own setup before you write a word
Generic templates fail because they describe someone else’s chat. Spend ten minutes in your own dashboard instead and write down what is actually switched on. Here is the order that works in most chat tools, including LiveChatBot.
Visitor tracking. Open the visitors view. If you can see the page a visitor is on, the website that sent them, their country and device, your chat is recording visit details. In LiveChatBot this is part of visitor tracking and it is what powers Flow conditions such as page, source, country and number of visits.
Away form and opening hours. Check whether the widget asks for an email or phone number when you’re offline. If you set opening hours, it probably does.
Tickets. Do offline messages or chats become tickets? Do customers get a link to a ticket page? See turning a chat into a ticket if you’re not sure what that looks like.
AI replies. If an AI assistant answers some questions, visitors’ messages are being processed to produce those replies. Note it.
Your website’s code. Ask whoever built your site whether it passes logged-in customers’ names and emails to the chat with setVisitor. Many shops do this without remembering.
Connections. List every Zapier zap, webhook or API connection that copies chat details elsewhere. A Google Sheet of leads is still personal data. Our Zapier guide shows where these live.
People and devices. Who can read chats, and on which phones and laptops?
Most chat platforms make all of this easy to switch on and easy to forget. The list you end up with is the brief for your notice.
Free tool
Build your chat privacy section
Tick what your chat actually does, choose how long you keep chats, and get a plain-English draft plus a list of gaps to fix. Load the example to see how it works.
Tell the builder how your website chat is set up. Tick only what you actually use. It writes a plain-English chat section for your privacy notice and lists the gaps to fix.
Business name
Email for privacy requests
Chat provider
What is switched on
How long you keep chats and contact details
Runs only in your browser; nothing is sent or saved. This is a starting draft, not legal advice.
Step 2
Write it in plain words, one layer at a time
A privacy notice that nobody can read doesn't help anyone. The builder's draft follows a simple shape you can keep if you edit it by hand.
Start with what and why
Name the data and the reason in the same sentence. "We record the pages you view so we can answer you with context" is clearer than a separate list of data types and a separate list of purposes that readers have to match up.
Then who holds it
Say that a chat provider stores the data for you, and name it. Visitors don't need your contract details, but they should know a third party is involved. If staff use phones to reply, say so.
Then how long
A number of months, not "as long as necessary". If you can't name a number yet, that is the first thing to fix (more on that below).
Then what they can do
Give a real email address, say what they can ask for (to see, correct or delete their data, or withdraw consent), and mention the Data Protection Board of India for complaints.
Keep the language short
Use "we" and "you". Avoid words like "hereinafter" and "data subject". Short sentences translate better too, which matters if you serve customers in Hindi, Tamil or Marathi; LiveChatBot can translate welcome messages automatically, but your privacy page is yours to translate.
Put the chat section under its own heading, such as "Website chat", so a visitor who has just used the chat can find it in seconds.
Before and after
Vague lines and clear lines
Step 3
Pick a retention period and actually delete
The gap the builder flags most often is retention. Almost nobody decides how long to keep chats, so they keep them forever by default. That is the opposite of what the DPDP Act expects: data you no longer need for the purpose you collected it should be erased.
A practical way to choose:
- Look at how far back you really look. If your team never opens chats older than six months, six or twelve months is a sensible period.
- Allow for open matters. Keep a chat longer if it relates to an open order, a warranty claim, a complaint or a legal reason. Say so in the notice.
- Write it down as one number. "12 months after the last message" is easy to follow and easy to check.
- Put a monthly reminder in your calendar. On the first working day of each month, delete chats and tickets older than your period.
- Don't forget the copies. If Zapier sends leads to a sheet, or a webhook posts tickets to your CRM, those copies need the same schedule. Deleting the chat and keeping the sheet is not deleting.
Deletion requests from visitors follow the same path. When someone emails asking for their data to be removed, search for their email or name in the chat inbox, tickets and every connected tool, delete what you find, and reply to confirm. Keep a one-line note of the request and the date, without the deleted content.
If a visitor is abusive and you block them, you may need to keep the block record itself. Say in your notice that you may record an IP address to stop abuse.
Special cases
AI replies, WhatsApp, staff phones and sensitive questions
A few situations need an extra line in the notice, or an extra rule for your team.
AI replies. If your chat uses an AI assistant, like the LiveChatBot AI Agent, say that some replies are automated and that visitors can ask for a person. Check what you have fed into the AI's knowledge: it should be your policies and product information, never another customer's order details. Our policy for pasting into AI chat at work is a good companion for staff.
The WhatsApp button. A WhatsApp button card in the widget hands the visitor over to WhatsApp. From that point, the conversation is on WhatsApp and WhatsApp's own policy applies. One sentence covers it.
Staff phones. Replying from the Android app is convenient, but every phone that can open chats is a place customer data lives. Require a screen lock, and remove the person's access the day they leave.
Sensitive questions. Clinics, coaching institutes, finance and insurance businesses get questions that reveal health, money or family details. Add a line asking visitors not to share card numbers, passwords, OTPs or ID numbers in chat, and train staff to move those conversations to a secure channel. India's cybercrime helpline is 1930 if a customer reports being tricked by someone pretending to be you.
Children. If your business serves school students, remember that the DPDP Act has stricter rules for children's data, including verifiable consent from a parent. Talk to a lawyer before collecting contact details from under-18s through chat.
None of this is unique to one tool. Every one of the chat platforms a small business is likely to use raises the same questions; the answers depend on which features you switch on.
Checklist
Chat privacy section, done properly
Keep it current
Update the notice whenever the chat changes
A notice is only accurate on the day you write it. The chat changes more often than the privacy page does: someone adds a Zapier connection, switches on AI replies, or starts sending offline messages to tickets. Each of those changes what you collect.
The simplest fix is a rule: whenever you switch on a chat feature, update the chat section the same day. Keep the builder's output in a document so you can tick the new box, regenerate the draft and paste in the change.
Twice a year, repeat the ten-minute dashboard walk from Step 1. Compare what you find with what the notice says. Remove anything you have switched off, too; a notice that mentions features you no longer use is confusing as well.
Finally, make the section easy to find. Link it from your website footer, and if your away form asks for contact details, a short line nearby such as "We use this only to reply to you" builds trust at exactly the right moment. You can see what the widget shows and adjust its text in the widget settings guide.
If you are setting up chat for the first time, LiveChatBot's free plan includes the widget, team inbox, Android app, visitor tracking, Flows, opening hours with an away form, tickets and an AI Agent with a small free monthly allowance, for two websites with 100 visitors per website each month. See pricing or start at livechatbot.in.
Frequently asked questions
Do chat platforms need to be mentioned in my privacy notice?
If your website chat collects personal data such as messages, contact details or visit details, it is good practice, and under India's DPDP Act 2023 a notice should describe the data and why you collect it. Ask a lawyer to confirm the wording for your business.
What should the chat section of a privacy notice include?
What the chat records, why, who stores it, which other tools receive copies, how long you keep it, and how visitors can ask to see, correct or delete it, including the option to complain to the Data Protection Board of India.
How long should I keep chat transcripts?
Choose a fixed period based on how far back your team really looks, often six to twelve months, with longer periods only for open orders, complaints or legal reasons. Then delete on a monthly schedule.
Do I need to say that replies come from an AI?
It is clearer and fairer to say so. One sentence that some replies are automated and that visitors can ask for a person at any time is enough.
Does the notice builder send my answers anywhere?
No. It runs entirely in your browser and nothing is sent or saved. The draft is a starting point, not legal advice.
Keep reading
Related guides
Chat for Websites Being Rebuilt: Keep Your Chat, Flows and Page Rules Working Through a Redesign or Platform Move (Free Rule Checker)
Chat Widget Settings, One by One: What Every Option Does and the Value to Pick
Chat Box for Website Briefs: What to Send Your Web Developer So It's Added Right the First Time (Free Brief Builder)
Chat your visitors can trust
Set up a chat widget, inbox, tickets and away form, then describe them honestly in your notice. Start free on livechatbot.in.