Egenverk Babbla · Documentation
Data and privacy
In short
- The chat makes no external requests. Messages and attached files stay on your server.
- The assistant is off until you enter an API key. From then on each question is sent with its context to the provider you chose.
- The Google sources are off until you switch on the integration.
- Nothing is deleted when you delete the plugin, unless you have switched on Purge data on uninstall.
What is stored
| What | Where | How long |
|---|---|---|
| Channels, messages, read markers, room members, mentions and the assistant's jobs | Database tables with the prefix bbl_ | Until removed |
| Settings and access | The options egvb_settings and egvb_access | Until removed |
| The Google key | An option of its own, egvb_google_key, not autoloaded | Until you remove it |
| Attached files | A folder above the site's document root when the server allows it, otherwise wp-content/uploads/egenverk-babbla-files/ | As long as their message; unsent files 24 hours |
| The diagnostic log | A protected folder with a random name under wp-content/uploads/ | 14 days |
| Signal files for new messages | wp-content/uploads/egenverk-babbla-signal/, one file per user | Until uninstall |
| Server load measurements | The site's persistent object cache, if there is one | At most two hours |
Messages are stored as plain text and never shown as HTML.
Attached files are stored under names that cannot be derived from anything the browser sees, and are handed out only through Babbla to people who may see the conversation. No direct link into wp-content is ever sent to the browser.
The signal files hold a timestamp only. They say that something changed, never what, where or by whom, and a colleague cannot work out the file names.
The diagnostic log holds job and provider events, with times in UTC. Message text, tool results, channel names and API keys are never written to it.
In the browser
So that the chat shows at once, it keeps a bounded cache in the browser's local storage, per user and site: at most 30 messages of one conversation, at most 24 hours old and at most 48 KB. Drafts and uncertain sends are kept in the tab for as long as it is open. The choices of theme, drawer or window and bubble size are also stored locally. Nothing is cached when the chat does not know who the user is.
Who sees what
- No role can read anyone else's direct messages, private rooms or assistant conversation, not even the Babbla owner or an administrator.
- The Usage tab shows facts about the questions only, never message text or channel names.
- When a user is deleted in WordPress, their private room memberships are removed.
What is sent to the AI provider
With the assistant on, each question sends the following to Anthropic or OpenAI, whichever you chose:
- the question and the recent history of the conversation, as colleagues wrote it
- the system prompt
- the results of the tools the assistant used
- the images in your newest message in the assistant conversation, at most three
Tool results can include order and customer data. Before a result is sent, Babbla removes fields holding names, e-mail addresses, phone numbers, street addresses, postcodes, cities, personal identity numbers and IP addresses, and masks e-mail addresses in free text. Order notes and refund reasons are free text and can still name a customer; e-mail addresses and phone numbers are masked there, but the rest is sent.
Colleagues' chat is sent only when it is part of the conversation with the assistant or of a tool result the asker may already read.
The providers' terms:
- Anthropic: terms, privacy policy
- OpenAI: terms, privacy policy
The API key is your own and can live in wp-config.php instead of the database.
What is sent to Google
With the Google integration on, the server calls the Google Analytics Data API, the Search Console API and the Merchant API with your service account. What the tools read, such as aggregated figures like sessions and clicks, search queries, landing pages, product titles and feed issues, is sent with the question to the AI provider. The key is never sent to the provider and never appears in the log, an error message or a tool result.
Removing data
- Your assistant conversation: choose Clear conversation in the More menu (⋯) and confirm with Delete the messages. The messages and their files are deleted for good.
- The log: the Diagnostics tab has the button Delete all log files.
- Everything on uninstall: switch on Purge data on uninstall in the Data card on the Settings tab before you delete the plugin. The tables, settings, access list, Google key, log folder, signal files and attached files are then deleted. Without that setting everything stays.
Deactivating Babbla removes the scheduled log cleanup, and the must-use plugin for lean chat reads if it is installed. On a multisite network it is removed only by a network-wide deactivation.