Chatbot privacy notice: template for sites running Botshido
Related: AI Act, Art. 50: checklist.
How to use this
Section titled “How to use this”- Fill every bracket. A notice with
[COMPANY]left in it is worse than no notice. - Delete the blocks you do not use. If the consent notice is off, if guided flows collect no contact details, if Freemius was skipped at activation — cut that paragraph. A notice describes what the site does, not what the plugin could do.
- Keep it aligned with the settings. If you change the retention period, the provider or the consent toggle, edit the notice the same day and re-date it.
Part 1 — Text to paste into your privacy policy
Section titled “Part 1 — Text to paste into your privacy policy”[SECTION] Chatbot
Section titled “[SECTION] Chatbot”What the chatbot is. This website uses Botshido, an AI chatbot that answers visitors’ questions using the content of this website (pages, posts, documents) and can guide them towards a next step such as a booking, a quote request or a contact. The chatbot is provided as software installed on this website; it is operated by [COMPANY NAME], [ADDRESS], which is the controller of the personal data described below. Contact: [PRIVACY EMAIL].
What we process when you use the chatbot.
- Your messages, including anything you choose to write in them.
- The conversation as a whole, so that the chatbot can follow the thread within the same session.
- Contact details you enter, only if you use a guided flow that asks for them:
[NAME],[EMAIL],[PHONE — delete if not collected],[ANY OTHER FIELD — delete if not collected]. - Technical data needed to run the service: date and time, the page address where the conversation started (with tracking parameters and personal data in the query string removed by the plugin), the language, and a shortened identifier derived from your IP address used for rate limiting.
- Consent choice, i.e. whether you accepted or declined the chatbot notice.
Conversations and analytics are stored in this website’s own database. [BOTSHIDO — the software vendor — does not receive your conversations: messages travel from this website's server to the AI provider we selected, and nowhere else. Delete this sentence only if you have modified the plugin's data flow.]
Who receives the data.
- The AI provider we selected:
[PROVIDER — OpenAI / Anthropic Claude / Mistral AI / xAI Grok], which processes the messages only to generate a reply, as our processor under[its data processing terms / our agreement]. [See the provider annex below for entity, location and transfer mechanism.] - Our hosting provider
[HOST, COUNTRY], which stores the website database. [IF APPLICABLE]Freemius, our licensing and update service, which receives the site URL, the WordPress and PHP versions, the plugin version and the administrator’s name and email address — only because an administrator of this website opted in at activation. It never receives conversations, content or API keys.- Our staff
[or: nobody, if the inbox is unattended], when a conversation is handed over to a human, with the conversation attached.
We do not sell your data and we do not use it for advertising.
Why we process it (purposes and legal basis).
- Answering your questions and guiding you to the right next step: performance of pre-contractual measures at your request (Art. 6(1)(b) GDPR), and our legitimate interest in providing the service (Art. 6(1)(f)).
[IF CONSENT NOTICE IS ENABLED]Running the chatbot at all for you: your consent (Art. 6(1)(a)), given through the notice shown before the chat starts. Until you accept, no message is sent to the AI provider and no conversation is recorded. You can decline and still browse the site.- Collecting contact details to reply to you: consent, given by submitting the flow that contains the field
(Art. 6(1)(a));
[or: pre-contractual measures, Art. 6(1)(b) — pick one and delete the other]. - Measuring how the chatbot is used, with minimised page addresses (Art. 6(1)(f), legitimate interest in improving the service).
Transfers outside the EEA. [PROVIDER] is established in [COUNTRY], and its processing takes place
[in the EEA / outside the EEA]. Where data leaves the EEA, the transfer relies on
[an adequacy decision, including the EU–US Data Privacy Framework to which the provider is certified / the European Commission's Standard Contractual Clauses under the provider's data processing addendum].
How long we keep it. Conversations: [30 / 60 / 90] days from the last message. Analytics events:
[12] months. Contact details collected through a guided flow: [24] months from collection
[or: until you ask us to delete them]. Everything older is deleted automatically by the plugin’s retention
setting.
Cookies and local storage. The chatbot stores [the fact that you accepted or declined the notice] and
[a session identifier for the current conversation] in your browser. These are strictly necessary for the
service you asked for and do not require consent. [If the analytics feature is enabled and uses cookies: "Analytics cookies are set only after you accept the notice." Delete if the analytics feature is off or cookieless.]
What we ask you not to do. Please do not enter health data, judicial data or other sensitive information
about yourself or third parties in the chat. If you do, we will delete those messages as soon as we notice
[or: on request].
Minors. The chatbot is not intended for children under [14 / 16] years.
Your rights. You can ask for access, rectification, erasure, restriction, portability and object to
processing based on legitimate interest, and withdraw consent at any time without affecting processing already
carried out. Write to [PRIVACY EMAIL]. [If the plugin's WordPress privacy integration is active: "You can also export or erase the conversations linked to your email address through the site's privacy tools."] You can lodge a
complaint with the supervisory authority: [AUTHORITY — e.g. Garante per la protezione dei dati personali, or the authority of your habitual residence].
Part 2 — Provider annex (fill in once, reference from the notice)
Section titled “Part 2 — Provider annex (fill in once, reference from the notice)”| Provider | Legal entity | Role | Processing location | DPA / terms | Transfer mechanism |
|---|---|---|---|---|---|
| OpenAI | [OpenAI, L.L.C. / OpenAI Ireland Ltd.] |
processor | [US / EU] |
platform.openai.com/… | [DPF / SCCs] |
| Anthropic (Claude) | [Anthropic PBC / Anthropic Ireland Ltd.] |
processor | [US / EU] |
anthropic.com/legal | [DPF / SCCs] |
| Mistral AI | [Mistral AI SAS] |
processor | [EU — France] |
mistral.ai/terms | [not needed if EEA] |
| xAI (Grok) | [X.AI Corp.] |
processor | [US] |
x.ai/legal | [DPF / SCCs] |
Rules for this table:
- Fill only the row(s) for the provider you configured. Delete the others.
- The provider is a processor only if you have accepted its data-processing terms; if you are on consumer terms, the provider may act on its own purposes — check before writing “processor”.
- “Processing location” is not the same as the registered seat: check the provider’s trust/DPA page, not the homepage.
- Do not copy a transfer mechanism from another site’s notice. Verify it in the provider’s DPA you actually accepted.
Part 3 — Checklist: does your site match the notice?
Section titled “Part 3 — Checklist: does your site match the notice?”Tick only what is true on the site; then delete the corresponding paragraph if unticked.
- Consent notice enabled in Botshido settings → the “consent” paragraph stays. If it is off, remove the consent legal basis and declare legitimate interest instead — and expect a harder position, because the chat then starts before any choice is made.
- Retention values read from the settings match the numbers in the notice.
- One provider configured, and that is the provider named. If you switch provider, the notice changes the same day.
- Guided flows: list the fields they actually collect. If a flow collects email and phone, name both.
- Human handoff: is there an inbox someone reads? If not, delete the “our staff” sentence and say the handoff collects a message for later reply.
- Freemius opt-in: if the administrator skipped it, delete the Freemius paragraph entirely.
- Analytics feature: on or off — and if on, does it set cookies? That decides the cookie sentence.
- Privacy email exists and someone answers it within 30 days. Test it from outside the organisation.
- The AI provider’s own terms are accepted, and its DPA/annex is filed with your documents.
- Your team knows that conversations can be exported and erased on request, and how to do it in WordPress.
Part 4 — Sentences to avoid
Section titled “Part 4 — Sentences to avoid”- ❌ “No data is stored.” — Conversations are stored in your database unless retention deletes them immediately.
- ❌ “Everything stays on your site.” — Messages leave the site for the AI provider; that is a transfer to declare.
- ❌ “Fully GDPR compliant.” — It is a claim, not a fact: the plugin gives you the tools, the compliance is your configuration plus this notice.
- ❌ “The AI cannot identify you.” — Identifying a person is not what determines whether data is personal.
- ❌ “We are not responsible for the AI’s answers.” — You are the controller of the conversation; a disclaimer does not move that role.
- ❌ Naming Freemius in a notice on a site that skipped the opt-in.
Part 5 — Why this template is short (and it should stay short)
Section titled “Part 5 — Why this template is short (and it should stay short)”A site running Botshido usually needs three things declared: the AI provider as recipient, the retention period, and the consent mechanism. Everything else — the licensing SDK, the analytics, the handoff — is conditional and gets cut when it does not apply. A two-page notice that matches the configuration beats a five-page notice copied from a SaaS template.
If the site is in the EU and the chatbot is enabled for consumers, check with a lawyer before publishing. This template is a drafting tool, not a legal opinion.