Yes for live policy fetches and Consent Database queries. The API key stays in WordPress options, server-side, never in the browser. SleekAI only sends question context to your LLM provider under your own key. The Iubenda API key never leaves your hosting environment unless you choose to expose it.

It can suggest sections and list services to add, but the policy of record stays on Iubenda. Most teams use the bot to identify what to add and then use Iubenda's policy generator to make the change. That keeps the policy generation and versioning inside Iubenda where it belongs.

Yes. SleekAI reads the v2 settings, including per-category granularity, the deny-all button, and the banner template. Older v1 setups also work but expose fewer options. The bot quotes whichever version is configured and flags if you have v2 features available but disabled in the settings.

Yes. If your site is set up with both privacy and terms policies, the bot can fetch each by ID and quote the listed clauses. Useful when marketing wants to know whether a particular jurisdiction is mentioned, or when legal needs to confirm whether arbitration is in the latest published version.

Yes if you feed it a list of detected trackers, for example from a Complianz or Cookiebot scan or from a manual list. It can diff that list against the services in your Iubenda policy and flag trackers that are not yet disclosed, which is the most common compliance gap after a release.

Yes. Each subsite can have its own Iubenda policy ID and Consent Solution settings. The bot reads per-site options, so a network admin can ask about any subsite without logging in. Useful for publisher networks or franchise systems with shared policy oversight across many domains.

Only to your LLM provider. SleekAI sends record summaries and counts to the provider whose API key you supply. Individual subject identifiers can be omitted from the context. If your DPO requires zero personal data in prompts, scope the bot to aggregated counts only and exclude raw record fields.

Yes. Under multibot you can run a visitor-facing FAQ bot that summarizes which categories the site uses, points to the public policy page, and explains how to revoke consent. Keep that bot separate from the admin bot, which has the API key and access to the Consent Database records.