Adding an AI Chatbot to Your Small Business Website? Start With the Paperwork

DocPro Legal
Last Updated:

20 Nov 2026

Published On:

4 Nov 2026

min read

Preview Image

Adding an AI Chatbot to Your Small Business Website? Start With the Paperwork

In November 2022, Jake Moffatt asked the chatbot on Air Canada's website about bereavement fares after his grandmother died. The bot told him he could buy a regular ticket and apply for the bereavement rate within 90 days. Air Canada's real policy didn't allow claims after travel, so when Moffatt asked for the money back, the airline said no.

 

At the tribunal, Air Canada argued that the chatbot was a separate legal entity responsible for its own actions (yes, that was the argument). British Columbia's Civil Resolution Tribunal didn't buy it. In February 2024 it held Air Canada responsible for everything on its website, chatbot included, and ordered it to pay Moffatt about C$812 in damages, interest and fees.

 

C$812 won't sink anyone, but the reasoning reaches well beyond airlines: whatever appears on your website is your statement, and that includes the parts a widget writes for you. If you run a five-person bakery and add an AI chatbot or a live feed of Google reviews, you take on the same responsibility. You usually do it in an afternoon, and usually without touching a privacy policy or terms that were written years earlier.

 

So here's what to update, in roughly the order it makes sense to do it.

 

Your chatbot answers from your documents

 

Give it one current version of each policy

Website chatbots answer from the content you give them. An AI chatbot widget like Elfsight's, to take one example, learns from your site's pages, from files you upload (PDF, DOCX and others) and from question-and-answer pairs you write yourself. So if the refund policy on your site dates from 2023 and the PDF you uploaded is from 2025, the bot can quote either one. And when your content doesn't cover a question at all, many bots fall back on general knowledge, which is how a refund policy gets invented.

 

Before you switch a chatbot on:

  1. Pick one current version of each customer-facing policy (refunds, shipping, cancellations, warranties) and make it the only version the bot learns from.
  2. Write fixed answers for questions where a wrong answer costs money: refunds, prices, deadlines, eligibility.
  3. Set up a handoff to a person for anything your documents don't cover.
  4. Put a "last updated" date on each policy page, and resync the bot the same day you change one.

Air Canada also argued that the correct policy was on another page of its site. The tribunal's answer was that customers shouldn't have to cross-check one part of a website against another. Keeping the bot and the policy pages in sync is a chore, but it's a cheaper one than explaining the difference later.

 

Tell visitors they're talking to a bot

Since 2 August 2026, Article 50 of the EU AI Act has required AI systems that talk to people to make it clear they're AI, unless that's obvious from context. The duty sits mainly with the company that builds the chatbot (your vendor, in other words), but if you have customers in the EU, there's no reason not to say it yourself. In the US, California's BOT Act has made it unlawful since 2019 to talk to Californians online through a bot that misleads them about being a bot in order to push a sale.

 

You can cover this in one sentence. Put it in the welcome message – something like "Hi, I'm the AI assistant for Rosa's Bakery. I can help with orders and opening hours, or put you in touch with our team." – and add a short line in the chat footer that links to your privacy policy. Chatbot widgets usually have a field for both.

 

Update your privacy policy for chat data

People type all sorts of things into chat windows – order numbers, phone numbers, health details, complaints about a neighbour. And if your chatbot has a lead form, it's collecting names and emails on purpose. If your privacy policy was written before you had a chat window, it probably doesn't mention any of this.

 

Add a section that covers:

  • that you use a chat assistant, and what it collects (messages, plus contact details from lead forms);
  • which provider processes the chats;
  • what you use the conversations for, such as answering questions, following up on leads and improving answers;
  • how long you keep transcripts, and how someone can ask you to delete theirs;
  • the consent you collect before sending marketing to someone who left an email in the chat.

If you're starting from scratch, DocPro's Privacy Policy (with GDPR) template gives you the structure, and you can add the chat section to it.

 

Add a line to your terms, but don't lean on it

It's worth adding a sentence to your website terms and conditions saying that chatbot answers are general information and that the written policy on your site takes priority, because it sets expectations for anyone who reads it. It won't save you from a bot that misstates your own policy, though – Air Canada had the right policy on its own site and still lost. So write the disclaimer, but count on the first step (accurate source documents) to do the bulk of the protecting.

 

Reviews on your site are a claim too

 

What the FTC's review rule bans

 

A reviews section looks like customers talking about you, but once it's on your own website it works as your advertising. The FTC's Rule on the Use of Consumer Reviews and Testimonials has applied to US businesses since 21 October 2024, and the FTC can seek civil penalties from knowing violators. Among other things, it bans:

  • fake reviews, including AI-generated ones attributed to people who don't exist;
  • paying or rewarding customers for reviews that have to be positive;
  • reviews by your own staff or managers posted without disclosing the connection;
  • threats or intimidation to get a negative review taken down;
  • presenting the reviews on your site as all or most of what you received when you've filtered out the bad ones by rating.

The FTC does seem to be following up, too – on 22 December 2025 it announced warning letters to ten companies about possible violations.

 

Filtering without misleading

The last item on that list is the one you can break without meaning to. Reviews widgets let you filter, and plenty of filters make sense: hiding spam, slurs, star-only ratings with no text, or a review that was clearly meant for another company. The trouble starts when a feed of hand-picked five-star reviews sits under a heading that implies it's everything customers said.

 

Two habits help:

  • Show the overall rating and total count from the source. Elfsight's All-in-One Reviews widget, for example, pulls reviews from Google, Facebook, Yelp and other platforms, and its header shows the overall star rating and the total number of reviews. That way a visitor sees your real average even if the carousel below shows only recent five-star reviews.
  • Label the feed for what it is. "Recent five-star reviews from Google" is accurate and still sells. "What our customers say" over a filtered feed can read as a claim that this is the full picture.

Write a one-page review policy

The rule covers what your staff do as much as what your website shows, so it's worth putting your own rules in writing:

  • who can ask customers for reviews, and when;
  • that a reward for leaving a review doesn't depend on the rating (Google goes further and bans rewards for Google reviews altogether, so check each platform's rules);
  • that employees don't review the business, or clearly say they work there if they do;
  • what you remove from your own site and why: spam, abuse, off-topic posts, someone else's personal data;
  • who replies to negative reviews, and that nobody threatens a reviewer.

A checklist before launch

 

Document

What to add

Refund, shipping and cancellation policies

One current, dated version of each, used as the bot's source

Chatbot welcome message and footer

A plain line saying it's an AI assistant, plus a privacy policy link

Privacy policy

Chat transcripts, lead-form data, the chat provider, retention, deletion requests

Website terms

Bot answers are general information; the written policy prevails

Review policy (internal)

Who asks for reviews, no rewards tied to ratings, staff disclosure, moderation rules

Reviews section on the site

The source's overall rating and count, and a label that matches the filter

 

All of this is roughly an afternoon of work, which is about what it took to install the widgets in the first place. If you work in a regulated field like healthcare, finance or law, have a lawyer look at your chatbot setup before it goes live.

 

This article is general information, not legal advice.

DocPro Legal

DocPro Legal is a team of legal professionals with a passion for making quality documents and legal contract templates widely available to the public through cutting-edge technology. Our lawyers are qualified in numerous common law jurisdictions including the United Kingdom, Australia, New Zealand, India, Singapore and Hong Kong. We have experience in major law firms and international banks with expertise in business, commercial, finance, banking, litigation, family, succession and company laws. If you would like to become a blog contributor to DocPro, please click the link below:

Keywords:

Ai Chatbot Website Legal, Chatbot Privacy Policy, Website Terms Ai Chatbot, Ai Chatbot Liability, Small Business Chatbot Compliance, Review Widget Ftc Rules, Chatbot Disclosure Requirements

,  

Join Now

You are Master and Commander of
Thousands of Documents

Join one of the largest online documents database created by legal
professionals, with easy to use tools for customization and
jurisdiction selection engine