How to Write a Chatbot Privacy Notice (Simple 2026 Guide)
If your website has a chatbot, it is collecting information from your visitors. Names, email addresses, questions about orders, sometimes payment details. In most places you are required to tell people what you do with that information before or while you collect it.
That is what a chatbot privacy notice does. It is a short, plain-language explanation that sits next to your chat window or on a dedicated page, telling visitors what data the bot collects, why, and how they can opt out.
This guide covers what to include, where to put it, and how three popular tools (Tidio, Chatbase and Crisp) handle privacy settings. The prices and limits come from each vendor's public pricing pages and documentation, not from paid testing. Treat it as a writing guide rather than legal advice: for a regulated industry or a large volume of sensitive data, have a lawyer read the final text.
Why a chatbot privacy notice is not optional
Most privacy laws (GDPR in Europe, CCPA in California, and similar rules elsewhere) require you to disclose data collection at the point it happens. A chatbot is a data collection point. If a visitor types "my order number is 44821 and my email is..." into your chat window, that is personal data entering your systems.
It is easy to assume the chatbot vendor handles all of this. That is only half true. Tools like Tidio and Crisp give you the plumbing: consent settings, data retention controls, deletion tools. The notice text itself belongs to you as the business collecting the data.
Picture a small bakery whose Tidio bot answers questions about custom cake orders, with no privacy notice anywhere on the site. A customer asks "who sees my messages?" and there is no good answer. That is the moment worth designing around.
What to include in your chatbot privacy notice
A good notice answers five questions in plain English. You do not need legal jargon. You need clarity.
- **What data you collect.** Names, emails, phone numbers, order details, the content of the chat itself, and technical data like IP address or browser type.
- **Why you collect it.** Answering questions, processing orders, improving the bot, marketing (only if true).
- **Who sees it.** Your team, plus any third-party tools the chatbot runs on. If you use Tidio's Lyro AI, that is a vendor processing data on your behalf.
- **How long you keep it.** Be specific. "We delete chat transcripts after 12 months" is better than "we retain data as needed."
- **How visitors can opt out or delete their data.** An email address or a link to a request form.
You should also state whether the bot uses AI to generate answers. Visitors have a right to know they are talking to a machine. Chatbase, for example, trains bots on your own uploaded content, which is worth mentioning in the notice if you use it.
How to write the notice, step by step
Here is a process that works for non-technical owners.
**Step 1: List every tool that touches the chat.** Open your chatbot dashboard and your website's plugin list. Write down every service that could see chat data. Tidio, Chatbase and Crisp each publish their own privacy documentation you can reference.
**Step 2: Draft in plain language.** Write at a 9th-grade reading level. Instead of "we process personal data for legitimate business purposes," write "we use your email to reply to your question and to send order updates."
**Step 3: Put a short version at the chat window.** A single line above the input box works: "By chatting, you agree to our privacy notice." Link to the full page. Tidio and Crisp both expose pre-chat and consent settings in their widget configuration, so confirm the current options on your own plan before promising a checkbox to visitors.
**Step 4: Publish a full notice page.** This is the long version, linked from your footer and from the chat widget. A few hundred words is usually enough for a small business.
**Step 5: Review it every time you change tools.** If you switch from Crisp to Tidio, or add Chatbase for a docs bot, update the notice. A stale notice is worse than no notice because it misleads.
Where to place the notice so people actually see it
The notice has to appear before or at the moment of data collection. Practically, that means three places.
First, a short consent line inside the chat widget itself. Second, a link in your site footer labeled "Privacy" or "Chat Privacy." Third, a dedicated page with the full text.
A footer link alone is the common shortcut, and it is technically weak under GDPR, because the visitor has already started typing before they see it. The in-widget line is the one that carries the weight.
Tidio makes this straightforward. The vendor documents a pre-chat message with a consent checkbox that you configure in the widget settings without touching code. Crisp offers comparable options in its chatbox settings. Chatbase is more minimal, so you may need to add the line manually inside your site's chat embed container.
How Tidio, Chatbase and Crisp handle privacy settings
The three tools differ in how much of the consent plumbing they hand you, and in what the plans cost.
**Tidio** is the friendliest for non-technical owners. The vendor describes a working live chat in under 10 minutes, and the consent options sit in the same settings panel. The free plan includes 50 billable conversations per month plus 50 Lyro AI chats as a one-off, which is enough to walk through the privacy flow before paying. Paid plans start at $24.17/mo billed yearly on Starter. Downside: Lyro AI credits run out quickly on cheaper plans, so a chatty bot needs budgeting.
**Chatbase** is the tool to look at if your bot runs on your own documents. You upload docs or a website and get a trained bot in minutes. That is powerful, and it also means the bot may quote your content back to visitors, worth disclosing. There is no free plan anymore (the free tier was withdrawn in October 2026), so testing means the 7-day trial or paying $40/mo for Hobby. Helpdesk with human handover requires Basic at $150/mo.
**Crisp** is the budget pick. Flat per-workspace pricing from $45/mo on Mini, which includes 4 seats, keeps the bill predictable for a small team, and the free plan covers 2 seats. Shared inbox, chatbot and campaigns live in one place, which simplifies your privacy story: fewer tools, fewer disclosures. The tradeoff is that AI features are lighter than Tidio's, and the free tier includes zero AI credits.
As a starting point, Tidio suits a small store that wants consent settings built in, Chatbase suits a content-heavy site, and Crisp suits a team that wants one inbox for chat and email under a flat workspace fee.
Common mistakes in chatbot privacy notices
The same problems come up again and again.
- **Copying a template from a different industry.** A SaaS notice does not fit a bakery. Rewrite it.
- **Forgetting the AI disclosure.** If the bot uses AI to answer, through Tidio's Lyro or Chatbase's models, say so.
- **No retention period.** "We keep data as long as necessary" is vague. Give a number.
- **No way to delete data.** Visitors need a real path, an email or a form, to request deletion.
- **Not updating after a tool change.** Every new chatbot is a new data processor. Update the notice.
One more: do not bury the notice inside a long general privacy policy. A dedicated chatbot page is easier to keep current.
A quick template you can adapt
Here is a starting point. Replace the bracketed parts.
> **How we use our chatbot** > Our website chatbot is powered by [tool name]. When you chat with us, we collect your name, email (if you share it), and the content of your messages. We use this to answer your questions and improve our service. Chat transcripts are stored for [X months] and then deleted. Our chatbot uses AI to generate some answers. You can ask us to delete your chat data at any time by emailing [address]. Read our full privacy policy [link].
It covers the essentials without legal fog. Adapt the wording to your business, then have someone outside the company read it. If they understand it, you are done.
Frequently asked questions
Do I need a chatbot privacy notice if my bot is just a simple FAQ script?
Yes. Even a scripted bot collects the messages visitors type. Any tool that stores chat transcripts, whether Tidio, Crisp or Chatbase, is processing personal data, so you need a notice.
Can I just link to my main privacy policy instead of writing a separate notice?
You can, but a dedicated chatbot notice is clearer and easier to keep updated. If you do link to the main policy, make sure that policy actually mentions the chatbot, the AI vendor, and the retention period.
Does the chatbot vendor provide the privacy notice text for me?
No. Vendors like Tidio and Crisp give you the settings, meaning consent checkboxes, retention controls and deletion tools, but the notice itself is your responsibility as the business collecting the data. Some offer templates you can adapt.
What happens if I do not have a chatbot privacy notice?
In most jurisdictions, missing disclosure is a compliance problem that can lead to fines or complaints. Beyond legal risk, visitors who cannot find out what happens to their data are less likely to trust the bot, and less likely to use it.
Ready to pick one?
Marcus Reed — Marcus Reed is the senior editor at ChatbotRadar. He tracks live chat and AI chatbot tools for small teams, verifying pricing on vendor sites and trialling tools on their free plans. How he tests · Report an error
Disclosure: this article contains affiliate links. If you buy through them we may earn a commission at no extra cost to you. Pricing and features are re-checked regularly but can change — always confirm on the vendor's site.