Cookie compliance for Webflow.

QookieQloud for Webflow connects a published Webflow site to QookieQloud’s consent platform. The hybrid app combines a Webflow Designer app with a guided account and domain connection flow.

What the Webflow app provides

• Guided installation: Authorize the app, choose a Webflow site and select the domain that should be connected.
• Managed banner delivery: QookieQloud adds its consent bootstrap through Webflow Custom Code. You publish the site yourself when the setup is ready.
• Designer shortcuts: Open Customize, Cookies and Consents for the connected domain from the Webflow Designer.
• Webflow Consent Management API: When Webflow’s Browser API is available, the banner synchronizes visitor choices with Webflow’s Analyze and Optimize tracking consent switch.
• Consent signals: Supported integrations can receive visitor consent signals, including Google Consent Mode v2.
• AI-assisted classification: Discovered cookies and trackers can be classified and reviewed in QookieQloud.

Pricing and plan access

QookieQloud has Free, Standard and Premium plans. The available domain limits, scan capacity, customization options and advanced features depend on the current plan. Webflow installation does not require a separate Webflow payment. Paid QookieQloud features are managed in QookieQloud and should be tested with the reviewer account supplied in the Marketplace submission.

Data and permissions

The Webflow app uses OAuth and keeps Webflow tokens on the QookieQloud backend. It reads authorized sites and existing Custom Code, and writes only the QookieQloud-managed code needed for the banner. The public site receives a QookieQloud Site Key; it never receives a Webflow token.

On published sites, the runtime contacts https://cf-geo.qookieqloud.com before a consent choice to determine the visitor’s two-letter country code for regional consent rules and banner language without storing visitor IP addresses. When a visitor makes or updates a choice, QookieQloud stores a consent record (unique_id, page path, category preferences, and country code; retained for 3, 6, or 12 months by plan tier, up to 24 months maximum) and collects consent-gated cookie and storage key names (never values) to maintain the site’s cookie inventory. Declining or withdrawing consent disables optional categories, clears non-essential cookies, and stops optional key-name observations. Full details on purpose, data transmitted, recipients, retention periods, and rejection/withdrawal behavior are disclosed in the Privacy Policy.

For sites using Webflow Analyze or Optimize, the published banner can use Webflow’s Browser Consent Management API. QookieQloud requires both statistics and marketing consent before enabling the combined Webflow tracking switch. Set Webflow to “Don’t track by default” before publishing so tracking cannot start before the banner has loaded.

Disconnecting

Before choosing “Remove Access” in Webflow, sign in to QookieQloud and choose “Disconnect from Webflow” for each connected site. This removes QookieQloud-applied Custom Code at site and page level while preserving unrelated scripts. Publish each site in Webflow, then remove the app access. Webflow has no uninstall hook and revokes the app token during uninstall, so QookieQloud cannot clean up code afterwards. If access has already been revoked or cleanup fails, see the FAQ below for manual removal steps. The scheduled access check updates connection status; it does not remove code.