Real Cookie Banner registers a set of custom post types, including rcb-service for each third-party integration, rcb-cookie for individual cookies, and rcb-cookie-group for the categories shown in the banner (Essential, Statistics, Marketing, Functional). Consent groups, opt-in mechanics, and TCF integration settings live in plugin options. Recorded consents are persisted with a hash, version, and timestamp for the GDPR audit trail.

SleekAI maps those structures, so the system message exposes the actual services you have configured, the cookies each service sets, the purpose statements your team wrote, retention periods, and the current consent state for the visitor if they have already chosen. That changes the conversation. "What does Google Analytics do on this site?" returns the purpose statement and retention you actually published in rcb-service, not a generic explanation. "Have I given consent yet?" reads the consent cookie and answers honestly.

Display conditions can scope the bot to logged-in users or specific roles, multibot lets a public consent-help bot run alongside a customer-service bot, and conversation logs capture every privacy question with model and token usage. SleekAI reads Real Cookie Banner; the plugin still owns every consent write, withdrawal, and TCF signal.

Cookie banners exist to give visitors a real choice. The choice only matters if it's understood. A generic chatbot has no idea which services your site actually runs, which retention periods you publish, or whether the visitor opted in five seconds ago.

So when someone asks 'what is tracking me' a generic widget either dodges or makes something up, neither of which serves the visitor or the audit trail. SleekAI gets this right because it reads Real Cookie Banner's own data. The rcb-service post is where the purpose statement lives.

The rcb-cookie post is where the cookie name, provider, and retention live. The rcb-cookie-group post defines the categories the banner shows. The visitor's consent cookie reveals what they've decided so far.

With those pieces in the prompt, the bot can answer privacy questions in your own language, route the withdrawal to your real preference center URL, and explain the difference between Statistics and Functional in the same words your DPO approved. None of this requires the bot to write consent. SleekAI reads, Real Cookie Banner writes.

Every opt-in, opt-out, and TCF signal stays in the plugin where the audit log is canonical. Combined with multibot, a consent-help bot can run on the privacy page while a separate sales bot handles the rest of the site, each scoped by URL pattern and each backed by the same bring-your-own-key billing. Compliance teams gain a feedback loop from the conversation log: when visitors ask the same question repeatedly, the purpose copy needs work, not the bot.