A website chatbot sits between your visitors and your business, so it handles personal information whether you intend it or not. Visitors type names, emails and sometimes much more. Before you install one, it helps to know what data a website chatbot collects, where it goes and what you should say about it.
This is general information, not legal advice. Privacy rules differ by country, so check with your own adviser and read your vendor's privacy policy.
What Kinds of Data Can a Chatbot Collect?
A chatbot can collect the messages visitors type, contact details they submit, conversation ratings, files they attach and basic technical information such as the page they were on. Exactly what is collected depends on the product and how you configure it.
| Data | Where it comes from | Why it exists |
|---|---|---|
| Chat messages | Typed by the visitor | To answer and for your team to review |
| Name, email, phone | Short contact form when the bot cannot answer | So your team can follow up |
| Ratings | Optional rating at the end of a chat | To measure how the conversation went |
| Attached files | Uploaded by the visitor | To share documents with your team |
| Page context | The page the chat was started on | To give page-aware greetings and context |
In ConvoRail, the contact form asks for name, email and phone when the bot has no confirmed answer, and those details arrive attached to the conversation in your shared inbox. Check the vendor's privacy policy for the full, current list.
How Can You Collect Less?
Collect only what you need, ask for it only when it is needed and tell visitors not to share sensitive information in chat. Less data is easier to protect and explain.
- Ask for name and one contact method, not a long form.
- Add a line near the form: "Please do not share passwords, payment details or confidential information in chat."
- Avoid asking visitors to describe health, legal or financial details in chat.
- Delete conversations you no longer need, if your policy and tools allow it.
What Should You Tell Visitors?
Tell visitors that they are talking to an automated assistant, what you collect and how to reach a person, and link to your privacy policy. Plain language builds trust.
Make the disclosure part of the greeting and the form. For wording and rules, see should your chatbot say it is a bot? and AI regulation for small business chatbots.
What Should You Ask a Vendor About Data?
Ask where data is stored, who can access it, how accounts are separated, how files are protected and what the vendor does not yet have, such as formal certifications.
- 1Is each customer's data separated from other customers' data? How?
- 2Who at the vendor can access my conversations, and when?
- 3How are uploaded files stored and shared?
- 4Can I delete conversations or an account?
- 5Which certifications exist today, and which are only planned?
ConvoRail states that each account's knowledge base and conversations are scoped to that account at the database layer. Attached files are checked against an allowlist, stored privately and opened through short-lived links. SOC 2 and similar certifications are not in place yet. Ask any vendor for the same honesty; the vendor security questions post goes deeper.
How Do Blocked Senders and Spam Fit In?
If a particular sender keeps sending unwanted messages, you can block them so spam does not reach your team. This also limits the amount of unnecessary data you hold.
Pro Tip: Write a short internal note on what the chatbot collects and who may see it. When a customer asks, you can answer in a minute.
What Does a Visitor-Facing Data Notice Look Like?
A good notice is short, specific and linked to your policy. Adapt this template and have it reviewed for your location.
"You are chatting with an automated assistant. If you share your name, email or phone number, our team will use it to reply to you. Please don't share passwords, payment details or confidential information. See our privacy policy at [link]."
This is a template, not legal advice. Your notice should match what your chatbot and your business actually do.
How Long Should You Keep Chat Data?
Keep conversations only as long as you need them for support, follow-up and improvement, and decide a rule in advance. Indefinite storage of everything increases risk.
- Decide a retention period that suits your business and local rules.
- Delete conversations that contain information you should not hold.
- Check what your vendor lets you delete and how.
- Document the rule so staff apply it consistently.
How Does Data Handling Differ for Sensitive Industries?
Healthcare, legal and financial businesses should be especially careful, collect less and involve a professional before launch. Chat is a poor place for sensitive details.
The industry guides for dental clinics and professional services firms show how to keep the chatbot to general information and move sensitive conversations to a proper intake process. Whatever your industry, review what your chatbot stores before you promote it.
What Should You Do If a Visitor Shares Something Sensitive?
If a visitor shares something sensitive, do not repeat it, move the conversation to a proper channel and delete it if your policy requires. Prepare this in advance.
- Reply with a short note asking them not to share sensitive details in chat.
- Offer a phone call or secure channel if appropriate.
- Do not copy the detail into other tools.
- Follow your retention and deletion rules.
A Worked Example of Data Minimisation
This fictional example shows the idea. A business starts with a form asking for name, email, phone, company, address and message. After review it keeps name, email and message, because it replies by email, and removes the rest. Fewer fields mean less data to protect and a form more visitors will finish.
Related reading: prompt injection in website chatbots, chatbots for professional services and the shared inbox guide.
Conclusion
A website chatbot collects messages, contact details, ratings, files and page context. Collect the minimum, tell visitors it is automated and link to your privacy policy, and ask any vendor how data is separated, protected and deleted, including which certifications they do not yet hold.
Key takeaways
- Chatbots handle messages, contact details, ratings, files and page context.
- Collect the minimum and ask for it only when needed.
- Tell visitors it is automated, what you collect and how to reach a person.
- Ask vendors how data is separated, accessed, stored and deleted.
- Choose vendors who state clearly what they do not have yet.
Quick Summary
A website chatbot collects the messages visitors type, contact details they submit, optional ratings, attached files and page context. Collect only what you need, tell visitors they are talking to an automated assistant and link to your privacy policy. Ask any vendor how data is separated, who can access it and which certifications are still only planned. ConvoRail scopes data to each account; SOC 2 is not in place yet. This is not legal advice.
Want to see grounded answers on your own site?
Start free, add your Q&A pairs and paste one script tag. No credit card required.

Founder & CEO
Writes about grounded AI chatbots for websites: how they work, how to measure them and what to check before you buy.
Topics
Get new posts by email
Guides on AI chatbots for websites, straight to your inbox.
