Chatbot security you can check
Your bot answers only from the content you give it, your data never trains a model, and every answer and action leaves a record. This page explains how we handle data, written for the person who has to approve a new tool.
Data handling at a glance
Answers come from your sources, with the page attached
The language model writes the reply, but the facts come from the pages and files you connected. Each answer shows the page it used, so visitors and your team can check it.
-
No source, no made up answer
When your content does not cover a question, the bot says it does not know and offers a person.
-
You choose what it reads
Add or exclude pages, files and sitemaps. Removed sources leave the knowledge at once.
-
Actions only when you allow them
Tickets, CRM leads, bookings and API calls run only if you switched them on, and every call is logged.
How data is protected
The controls below apply to every plan. SSO and the audit log are added on the Agency plan, see enterprise features.
Encryption
TLS for every connection between the visitor, the widget, the panel and our services. Stored data and connection secrets for your actions are encrypted at rest.
Roles and access
Owners, editors and viewers in your team, client logins limited to one client on Agency. Billing and white label stay with owners.
Workspace separation
Each workspace has its own sources, conversations and leads. A bot can only read the knowledge of its own workspace.
Widget iframe isolation
The chat runs in an iframe served from a separate domain. Browser origin rules keep it apart: it cannot read your page, your cookies or your forms, and your page cannot read the chat.
Rate limits
Widget messages are rate limited per visitor and bot, so a script cannot drain your monthly replies or flood your inbox.
Deletion and export
Delete sources, conversations or leads at any time. Export leads to CSV. Closing a workspace deletes its data.
Who else touches the data
We use a small number of service providers, described here by category. Each is bound by a data processing agreement and handles data only to provide the service.
| Category | What it does | Data it sees |
|---|---|---|
| Hosting provider (EU or US) | Runs the panel, the widget and the database | All workspace data, encrypted at rest |
| Language model provider | Writes the reply from the retrieved sources | The visitor question and the relevant source passages, not kept for training |
| Payment processor | Handles card payments for subscriptions | Billing name, email and card details (we never see full card numbers) |
| Email delivery provider | Sends sign-in codes, handoff emails and notices | Recipient address and the message |
GDPR, in plain terms
For the conversations on your widget you decide why and how visitor data is used, so you are the controller and we are your processor. For your own account data we are the controller, as described in the privacy policy.
- A data processing agreement is available on every paid plan.
- Access, correction and deletion requests from your visitors are handled in your panel, or by us on your instruction.
- The widget sets no tracking or advertising cookies on your site.
- You can tell visitors in the greeting that they are talking to an AI assistant and link your own privacy notice.
Security questions
Reporting a vulnerability or sending a questionnaire? Write to [email protected].
Is our content used to train a language model?
No. Your pages and files are used only to answer your own visitors. They are not used to train any model, ours or anyone else's, and they are not shared with other customers.
Can the bot answer from outside our content?
The bot answers from the sources you connected and cites the page it used. When the sources do not cover a question, it says so and offers a handoff to your team instead of guessing.
Where is our data stored?
With a hosting provider in the EU or the US, depending on where your workspace is set up. Data is encrypted in transit and at rest.
How do we delete data?
Delete a source and it is removed from the bot's knowledge. Delete a conversation or a lead and it is gone from your workspace. Close the workspace and all of its data is deleted.
Who is the controller of visitor conversations?
You are. For conversations on your widget we act as your processor and handle the data only on your instructions, as set out in the DPA.