Complianz GDPR drives consent through regional configuration: GDPR for the EU and UK, CCPA for California, LGPD for Brazil, plus optional regimes via the same wizard. The banner itself is a cmplz-banner custom post with text variants per region and per language. Detected cookies live in wp_cmplz_cookies and detected services in wp_cmplz_services. Geo-resolution decisions are logged in wp_cmplz_geo_ip, and aggregated consent statistics sit in wp_cmplz_statistics.

SleekAI maps that stack, so the system message can include the visitor's resolved region, the banner text variant that applies to them, the cookie list Complianz scanned, and the active services per category. "Am I covered by GDPR or CCPA here?" returns the regional decision from the plugin. "What cookies will load if I accept Marketing?" reads the live detected list. "Where do I delete my data?" answers from the data-request page you wired into Complianz.

Display conditions scope the bot per template, multibot keeps a privacy-help bot separate from product support, and conversation logs capture every privacy question with model and token usage. SleekAI reads Complianz; Complianz still owns every consent write, geo signal, and DSAR routing.

Privacy law is not one rule. It's a stack of regional regimes layered on the same site: GDPR for EU visitors, CCPA for Californians, LGPD for Brazilians, more coming. A generic chatbot blurs all of that into a paragraph about cookies and hopes the visitor doesn't notice.

That used to be tolerable. It isn't anymore, because rights vary by region and visitors increasingly know to ask. SleekAI fixes the gap by reading Complianz GDPR directly.

The cmplz-banner post holds the regional text variants. wp_cmplz_geo_ip stores the resolved region for the current request. wp_cmplz_cookies and wp_cmplz_services carry the live scan of what's actually running on the site.

With that data in the prompt, the bot can answer a California visitor in CCPA terms and an EU visitor in GDPR terms, quote the right opt-out control, and route DSAR requests to the working URL with the real response window. Compliance teams get a feedback loop, because the conversation log shows which framework's wording confuses visitors and which detected cookies prompt repeat questions. None of this requires the bot to touch consent state.

SleekAI reads, Complianz writes. Region resolution, consent recording, Consent Mode signals, and DSAR token issuance all stay in the plugin where the audit trail is canonical. Combined with multibot, a privacy-help bot can run on key flows while a separate product bot covers the rest of the site, each with its own user-supplied key and its own prompt scope.

The result is a privacy experience that finally matches the regulation it's supposed to honor.