Privacy policy
Last updated: 2026-10-09
This policy explains what personal data ChatBot AI (“we”) processes, why we do it, which providers help us and what rights you have. It applies both to you as an account holder and to the visitors who chat with a bot that one of our customers has added to their website.
1. Data controller
The controller for the processing of your account data is ChatBot AI, [company name, registration number and address to be added]. Contact us at jonatanaman89@gmail.com.
2. What data we process
Account data
Email address, name, company name and phone number (if you provide it), password (stored only as a hash by our login provider), the plan you have chosen and when you signed up.
Bot configuration
The bot’s name, appearance, welcome message, quick replies, your own Q&A pairs (training data) and the settings of integrations you connect yourself (e.g. webhook addresses, shop addresses and API keys/tokens — the keys are stored encrypted).
Scanned site content
When you enter your website, we read public content from it (pages, products, prices, contact details, images) and store a summarised knowledge base that the bot answers from. If your website contains personal data (e.g. the names of employees), it may end up in the knowledge base. Pages built with JavaScript may be read via Jina Reader (r.jina.ai), which then receives the page’s address and fetches its content, and car dealers’ stock lists are fetched via api.swapi.se (see section 4).
Customer conversations
Messages that visitors write to the bot, and the bot’s replies, are stored with the bot so that you as a customer can follow up on the conversations. We ask visitors not to share sensitive information in the chat. For conversations in Telegram, WhatsApp, Messenger and Instagram, we also store the channel’s ID for the sender and the display name the channel sends along.
Leads
If a visitor chooses to leave contact details in the chat (name, email, message), they are stored and shown to the customer who owns the bot.
If a visitor writes an email address or a phone number in the chat itself — in the chat widget on a website, via the share link or in WhatsApp, Messenger, Instagram or Telegram — it is also stored as a lead for the company running the bot, together with the message it appeared in. For the messaging channels, the sender’s display name is stored too. This also happens when the chat is temporarily out of service. Like leads from the form, leads from the chat are kept until the company asks us to delete them or the account is closed — even if the bot is deleted (see section 5). There is no button in the app yet for deleting leads or closing the account yourself; we do it on request.
For each new lead, a notification is sent to the account’s email address by default, so that the company can reply to the visitor. The notification can be turned off under Settings → Notifications.
Ratings of answers
Visitors can give the bot’s answers a thumbs up or down (in the chat widget and via the share link). The rating is stored with the conversation’s internal ID and the answer’s ID — without a name, email address or IP address. Only the bot’s owner sees the ratings (under Conversations, Analytics and Training). Ratings are deleted together with the conversation or the bot, and a visitor can withdraw a rating by clicking the same thumb again.
Insights in the app
The app analyses your own stored conversations to show you which questions the bot couldn’t answer and which answers got a thumbs down. Questions you choose to dismiss, and the links between a question and a training pair, are stored only as hashes that can’t be turned back into the text. A visitor’s wording that you turn into a training pair yourself is stored in the bot’s settings until you delete it.
Automatic re-scan (if you turn it on)
Automatic re-scanning is turned on per bot and is off by default. When it is on, we read the public pages of your website from our servers about once a week — and if a scan failed because of an error on our side, we try once more the following night. Our own fetching respects robots.txt and sends an honest User-Agent; pages built with JavaScript may instead be read via Jina Reader, which then fetches the page under its own identification. The text of the pages is sent to the AI provider (Anthropic, US) to update the bot’s knowledge. You can turn it off in the bot builder under Knowledge.
The demo on our home page
On our home page, anyone can try a temporary demo bot without an account. We then read up to 10 public pages of the address you enter (robots.txt is respected). Pages built with JavaScript may be read via Jina Reader (r.jina.ai), and car dealers’ stock lists via api.swapi.se. The text of the pages, the site’s address and name, and the language are stored with Supabase in the EU (eu-west-1, Ireland). The demo is valid for two hours and everything belonging to it is deleted automatically within two days; a scan you cancel is deleted straight away. Your questions and the text of the pages are sent to Anthropic (US) to generate the answers — questions and answers are not stored by us.
To limit abuse, your IP address is used: at most 3 used demos and at most 8 attempts per IP address per 24 hours, and at most 50 demos per 24 hours for the whole service. The IP address is never stored in plain text, only as a keyed hash (HMAC-SHA256; IPv6 addresses per /64 network), and it is deleted together with the demo within two days. The hash still counts as pseudonymised personal data. Legal basis: legitimate interest (Art. 6(1)(f) GDPR) — protecting the service against abuse.
The waiting list
If you join the waiting list on our home page, we store your email address, your language (your browser’s language, or English if you sign up on the English website), the source (“landing”) and the time — solely to email you news about the product. Legal basis: your consent (Art. 6(1)(a) GDPR). The data is stored with Supabase in the EU until you unsubscribe or withdraw your consent, which you do by replying to any of our emails or contacting us at jonatanaman89@gmail.com. [Name the email provider for the mailings once they start.]
Moving a bot to another customer
A customer can move a bot to another customer’s account (e.g. when an agency has built the bot for its client). The sender then enters the recipient’s email address; we store it in the transfer offer and email an invitation to it. The offer is kept for as long as the bot exists. When the recipient accepts the transfer, everything moves with the bot — settings, knowledge base, training, integrations, conversations, leads and ratings — and from the transfer onwards the recipient is the controller of the visitors’ data. The sender is responsible for having a legal basis for handing it over (see the terms, section 2). [Decision: retention period for old transfer offers. Lawyer: review the handover of personal data between customers.]
Payment details
Payment takes place in our checkout at Shopify. Card details are entered directly there and never reach our servers. We store only the order ID, the chosen plan, the payment status and how long the period is paid for.
Technical data
IP address and time are used temporarily to limit the number of requests (protection against abuse) and in server logs at our hosting provider.
3. Why, and on what legal basis
- Providing the service (account, bot, chat answers, leads) — performance of a contract.
- Billing via Shopify — performance of a contract and legal obligation (bookkeeping).
- Security and abuse protection (rate limiting, logs) — legitimate interest.
- Communication about the service (e.g. password resets) — performance of a contract.
- Abuse protection for the demo on our home page (hashed IP address) — legitimate interest (Art. 6(1)(f)).
- The waiting list — consent (Art. 6(1)(a)), which you can withdraw at any time.
We don’t use your data for third-party marketing and we never sell personal data.
4. Providers (data processors)
We use the following providers to run the service. They process data on our behalf under data processing agreements. [Lawyer: assess whether Jina AI and Swapi are data processors — there are no data processing agreements with them yet.]
| Provider | What | Location |
|---|---|---|
| Supabase | Database and login — accounts, bot configuration, knowledge base, customer conversations and leads | EU (eu-west-1, Ireland) |
| Anthropic | The AI model that generates the bot's answers. The visitor's message, the conversation history and relevant site content are sent to produce the answer | US |
| Shopify International Limited (Ireland) | Checkout, payments and subscriptions — handles card details and the details you enter at checkout [Lawyer: confirm the role — processor or independent controller] | Ireland (EU). Under Shopify's terms, data may also be transferred to Canada and the United States |
| Vercel | Hosting of the website and the API, server logs. The server functions (the chat, the API) run in Vercel's Dublin region; the pages are delivered through Vercel's global network | EU (Ireland) for the server functions; possibly US for logs and support (under Vercel's terms) |
| Resend | Sending email — notifications of new leads to the account's email address and operational alerts to us. The emails contain the visitor's name, email address, phone number and message | US (under Resend's terms) |
| Jina AI | Jina Reader (r.jina.ai) reads public pages built with JavaScript during scans — for the bot's knowledge base, the demo and automatic re-scans. Receives the page's address and fetches its content | Under Jina’s terms [location to be verified] |
| Swapi | api.swapi.se — fetches car dealers' public stock lists during scans when the website uses Swapi. No visitor data is sent | Under Swapi’s terms [location to be verified] |
Transfers to the US are based on the European Commission’s standard contractual clauses and/or the provider’s certification under the EU–US Data Privacy Framework. [To be verified by a lawyer: the current transfer mechanism per provider.]
Integrations you connect yourself
Apart from the providers above, data is only sent to services that you as a customer choose to connect to your bot, and only what each integration needs: visitors’ messages and the bot’s replies go via Meta (WhatsApp, Messenger, Instagram) or Telegram when the visitor writes in those channels; new leads (name, email, message) and — depending on your choices — the first question and the bot’s reply in new conversations are sent to Slack, Discord, Zendesk, Freshdesk, your own webhook or Zapier; when a visitor chooses to talk to a person, LiveChat opens in the visitor’s browser with the visitor’s latest question. From Shopify and WooCommerce we only fetch product information. These services process the data under their own terms, and nothing is sent to an integration that isn’t connected.
5. How long we keep the data
- Account data — as long as the account exists. Deleted when the account is closed; we do that on request (you can’t close the account yourself in the app yet).
- Bot configuration and knowledge base — as long as the bot exists; deleted when you delete the bot or the account.
- Customer conversations and leads — you delete conversations yourself in the app (under Conversations); we delete leads on request (there is no delete button yet). Both are deleted when the account is closed and are kept even if you delete the bot. [Decision: a fixed retention period, e.g. 12 months.]
- Payment history — as required by the Swedish Bookkeeping Act (7 years).
- Technical logs — briefly, at the hosting provider.
- Ratings of answers — deleted together with the conversation or the bot.
- The demo on our home page — page text, address and hashed IP address are deleted automatically within two days.
- The waiting list — until you unsubscribe or withdraw your consent.
6. Cookies and local storage
We only use necessary cookies to keep you logged in, and one cookie that remembers your language (see below). The chat widget keeps the ongoing conversation in the browser’s session storage (deleted when the tab is closed) so that the conversation survives a page reload. We don’t use any tracking or advertising cookies.
If you choose a language on the website (Svenska/English) or in the app, or continue from the website to log in or sign up, the language is stored in a cookie (cb-locale) for one year so that the website and the service are shown in the same language. It contains only the language code.
When you are logged in to the app, settings and a local copy of your bots and conversations are kept in your browser’s local storage on your device, so that the app starts quickly and copes with brief interruptions. The copy isn’t passed on to anyone and is deleted when you log out.
7. Your rights
Under the General Data Protection Regulation (GDPR) you have the right to:
- access the data we hold about you,
- have inaccurate data corrected,
- have data erased (“the right to be forgotten”),
- restrict or object to the processing,
- receive your data in a machine-readable format (data portability),
- lodge a complaint with the Swedish Authority for Privacy Protection (IMY).
Contact us at jonatanaman89@gmail.com and we’ll help you. We normally reply within 30 days.
8. GDPR for you as a customer — and for your visitors
When you add a bot to your website, you are the controller of the data your visitors provide in the chat (messages and contact details). ChatBot AI is your data processor and processes the data solely to provide the service to you.
In practice, this means:
- Storage in the EU. Accounts, bot configuration, scanned site content, customer conversations and leads are stored with Supabase in the EU (eu-west-1, Ireland).
- AI answers from Anthropic (US). To be able to answer, the visitor’s message, the conversation history and relevant site content are sent to Anthropic. Under their contract terms for API customers, the data is not used to train their models.
- Payments via Shopify. We never see card numbers — they are handled entirely by Shopify.
- No made-up guarantees. We don’t claim to be “fully GDPR compliant” — we describe what actually happens and let you judge whether it suits your business.
- Data processing agreement. [A data processing agreement (DPA) between ChatBot AI and the customer is to be drawn up and linked here.]
- Inform your visitors. Below the chat box, the chat widget and the share link show that the visitor is chatting with an AI assistant, that the answers may contain errors and that the conversation is saved, with a link to this policy (the link is also shown when a visitor leaves contact details). We recommend adding to your own privacy policy that you use ChatBot AI.
9. Security
All traffic is encrypted (HTTPS). The database is protected with row-level permissions so that each customer can only read their own data. Passwords are never stored in plain text. Keys for the AI and payment providers exist only on the server. Keys and tokens for integrations you connect are stored encrypted (AES-256-GCM) and are never shown in plain text after they have been saved.
10. Changes
If we make material changes to this policy, we will let you know by email or in the service. The date at the top shows when the policy was last updated.
11. Contact
Questions about personal data: jonatanaman89@gmail.com.