No, and that is the honest answer. BlogVault's plugin writes connection state, sync timestamps, and recent staging operation metadata into your WordPress install, and SleekAI reads those values. For dashboard-level data that only lives on BlogVault.com, the recommended pattern is a small daily export into a WordPress option that SleekAI then queries, so the data path stays explicit.

Not unless you configure it that way. Display conditions on user role, capability, logged-in state, and URL pattern keep the BlogVault bot scoped to administrators inside wp-admin. Any public chatbot you run on the same site is a separate bot under multibot, with its own data sources and no overlap.

The bot reads whatever BlogVault writes to your database, so anything visible to you in the plugin's local screens is queryable. Plan-specific features that only surface on BlogVault.com require the JSON export pattern described above, since SleekAI does not impersonate the BlogVault API.

By default SleekAI is read-only against BlogVault state. It surfaces what exists and points at the right BlogVault screen for the action. Wiring a custom PHP callback into a SleekAI tool is possible if you want a chat-initiated workflow, but most teams keep destructive actions inside BlogVault where confirmations are explicit.

Yes. Conversation logging is on by default per chatbot, with user messages, assistant replies, model name, token usage, and the page URL stored inside WordPress. For backup operations, that audit trail matters: when a question about a snapshot leads to a restore, the team can trace what the bot saw and said.

On the WP side, yes, for whatever staging metadata BlogVault has stored locally on this install. For aggregated staging activity across an agency's full BlogVault account, feed a periodic JSON export into a SleekAI data source and let the bot summarise creation, expiry, and push-back-to-live events from that.

A fast model handles routine reads like sync timestamps and connection health well. For longer prompts that compare a failed sync to last week's pattern, a stronger model from OpenAI, Anthropic, Google, or OpenRouter gives more useful synthesis. SleekAI lets you pick the model per chatbot.

Each SleekAI install runs its own chatbots with its own data sources, so the configuration is per site. You can export and import the chatbot config across sites and re-point the data sources, which suits agencies that want the same backup-help bot on every client site running BlogVault.