Frequently Asked Questions.

A Consent Management Platform (CMP) automates cookie and user consent collection on your website. It ensures compliance with privacy regulations such as GDPR, ePrivacy, and CCPA by informing visitors about tracking technologies, collecting verifiable consent, blocking scripts until opt-in, and maintaining an auditable trail.

Learn more in our guide on what cookie consent is.

Non-essential cookies — such as those used for analytics, conversion tracking, marketing pixels, and personalization — require prior, explicit consent. Strictly necessary cookies (such as security tokens, shopping cart sessions, or load balancer states) do not require consent.

No. QookieQloud™ automatically categorizes detected scripts and cookies into standard categories (Necessary, Analytics, Marketing, Functional), eliminating the need for complex manual maintenance.

Log in to your account at app.qookieqloud.com. From the central dashboard, you can view analytics, configure consent modes, customize banner designs, and export audit logs for all your registered domains in one place.

Yes! Web agencies and developers can manage multiple client websites and domains centrally through a QookieQloud Partner account, while packaging and pricing the solution directly to their clients. Check our Partner documentation for more details.

Adding a domain takes less than a minute. In your dashboard, click Domains → Add Domain, enter your root URL, choose your consent mode, and copy your embed snippet. You can also follow our domain setup guide.

Yes! We offer official WordPress plugins, Statamic plugins, and a Shopify app. For other platforms, use our universal script installation by pasting this script inside your <head> tag:

<script src="https://cf-cdn.qookieqloud.com/consentLoader.js"></script>

The Free plan includes one primary language of your choice. Standard and Premium plans include automatic language switching across 28+ European and global languages based on the visitor's browser settings.

A Data Subject Request (DSR) is a formal request submitted by an individual to exercise their privacy rights under Chapter III of the GDPR:

• Article 15 (Right of Access): Requesting a copy and confirmation of all stored personal data and consent telemetry.
• Article 16 (Right to Rectification): Requesting the correction of inaccurate or incomplete personal records.
• Article 17 (Right to Erasure): Requesting the permanent and irreversible deletion of personal data ("Right to be Forgotten").

QookieQloud™ includes a built-in DSR mechanism directly inside the consent banner so visitors can submit requests seamlessly and website owners can resolve them in compliance with privacy regulations.

The two scores evaluate two complementary dimensions of privacy compliance:

1. Privacy Score (under Cookies / Dashboard): Evaluates the quality and completeness of your static cookie inventory and declaration. It checks if there are unclassified cookies, unreviewed AI suggestions, or cookies lacking confirmed legal purposes.
2. V3 Live Diagnostic Audit Score (Live Scanner & Public Report): Evaluates the runtime execution and browser behavior in real time. It tests whether trackers fire before consent, verifies Google Consent Mode v2 default signal timing, checks for Late Consent, and confirms that marketing tags halt upon consent rejection.

Visitors can submit privacy requests directly through the active consent widget at any time:

1. The visitor opens the banner preferences and clicks the Privacy Rights tab (or clicks a link/button with class="qookieqloud-dsr-panel").
2. They select their request type: Erasure (Art. 17), Access (Art. 15), or Rectification (Art. 16).
3. They enter their email address along with optional notes and submit the form.
4. An automated receipt is immediately emailed to the visitor, while domain administrators receive an instant notification in their dashboard and via email.

Tip: You can add a link in your website footer or privacy policy with <a href="#" class="qookieqloud-dsr-panel">Privacy Rights (GDPR)</a> to open the form directly.

Note: The DSR tab is included in Premium plans and can be toggled on or off under Customize > Layout in the admin dashboard.

Zero-Retention ensures that QookieQloud never retains sensitive personal data longer than strictly necessary to process the request:

• Requester email addresses and notes are temporarily encrypted purely to route notifications and match the consent log.
• The instant an administrator marks the request as Resolved in the dashboard, the requester's email address and submitted notes are permanently and irreversibly purged from QookieQloud servers.
• For erasure requests, the consent log is permanently anonymized as well.

This architecture eliminates lingering data liability and strictly aligns with GDPR's data minimization and storage limitation principles (Article 5.1.c & 5.1.e).

Yes. For Premium customers, the DSR tab (Privacy Rights) is enabled by default, but it can be easily toggled off if your organization prefers a separate compliance channel:

1. Log in to your admin dashboard and navigate to Domains.
2. Select your domain and click Customize in the sidebar.
3. In the Layout tab, scroll to the Data Subject Requests (DSR) card.
4. Toggle the switch off and click Save.

The setting is encrypted and immediately updated on the live visitor banner without affecting your cookie consent tracking.

While cookie consents are binary records, a Rectification request under GDPR Article 16 typically pertains to personal records held across your connected business systems (such as CRM databases, customer accounts, or newsletter lists):

1. Navigate to Domains > Consents and click Resolve DSR on the pending request.
2. Review the requester's notes and correct the relevant records within your internal database.
3. Add an optional explanation in the Response message to visitor text area.
4. Click Complete. The visitor receives your response note in a formal completion email, and their contact information is automatically purged from QookieQloud.

When a visitor requests a data export (Right of Access under GDPR Article 15), QookieQloud automates the reporting process entirely:

1. QookieQloud retrieves the associated consent record and aggregates all relevant parameters: timestamp, unique consent ID, anonymized IP/country, user agent, and approved cookie categories.
2. The moment an administrator resolves the request in the dashboard, a structured consent summary table is automatically compiled and embedded directly into the completion email sent to the visitor.
3. You can also append supplementary notes or links regarding internal CRM customer records in the response field before completing the request.

When an administrator resolves an Erasure request (GDPR Article 17 / "Right to be Forgotten"):

1. Purge internal systems: You verify that the user's customer records, profiles, or newsletter subscriptions have been deleted across your internal systems.
2. Resolve in QookieQloud: Open the pending request in the admin dashboard and click Complete.
3. Anonymize consent records: The visitor's consent telemetry in QookieQloud is immediately and irreversibly anonymized.
4. Enforce Zero-Retention: The requester's email address and submitted notes are permanently purged from QookieQloud servers.
5. Visitor notification: A final confirmation email is automatically delivered to the visitor certifying that their data has been erased.

A subpage is any unique URL indexed and crawled by our cookie scanner on your verified domain (e.g. /about, /shop/product-1). Assets like images, CSS, and API endpoints are not counted as subpages.

Yes. You can switch between Free, Standard, and Premium at any time. When using Premium, you can seamlessly scale between 100 and 5,000 subpages straight from your account dashboard with prorated billing.

No. Our consent banner script is delivered via global edge CDN, weighing less than 15 KB gzipped. It loads asynchronously without blocking your page paint, keeping Core Web Vitals green.

QookieQloud has native built-in Consent Mode v2 support. When visitors give or deny consent, Google Analytics, Ads, and Tag Manager tags update their consent parameters automatically with zero custom coding required.

Yes! Web agencies and developers can manage multiple client websites and domains centrally through a QookieQloud Partner account, while packaging and pricing the solution directly to their clients. Check our Partner documentation for more details.

Absolutely. There are no lock-in periods on monthly plans. You can cancel with one click from your billing portal, and your plan will remain active until the end of the paid billing period.

No. QookieQloud is built as a native Shopify Theme App Extension for Online Store 2.0. You simply toggle the App Embed on in your Shopify Theme Editor. No code editing is required, and your theme files remain 100% clean and updateable.

QookieQloud automatically connects with Shopify's native window.Shopify.customerPrivacy API. When a visitor accepts or rejects tracking, consent signals are instantly synchronized across Shopify analytics, marketing pixels, and installed store apps.

Yes, out of the box. QookieQloud automatically pushes ad_storage, ad_user_data, ad_personalization, and analytics_storage updates to Google Consent Mode v2, preserving your conversion modeling in Google Analytics 4 and Google Ads while remaining GDPR compliant.

Not at all. The embed script is ultra-lightweight (<12 KB), loads asynchronously from global edge networks, and has zero negative impact on your Core Web Vitals or checkout performance.

Because QookieQloud uses Shopify App Embeds, none of your cookie classifications, regional rules, or audit history are stored in theme files. When you publish a new theme, simply toggle the QookieQloud app embed on in the Theme Editor.

By default, the floating Qookie Eyes icon automatically appears in the corner of your storefront once consent is saved, allowing visitors to click and reopen their preferences anytime. If you prefer a menu or text link (such as in your store footer), you can also add the custom attribute data-qookie-open-settings to any link or button, and customize icon visibility in your dashboard.

Connect your local installation to a domain you manage in QookieQloud. HTTP is supported on localhost and 127.0.0.1; other origins require HTTPS. If local and production installations share a domain, their reported cookies and consent statistics are combined. Use a separate demo domain when you want to keep test data separate.

By default, the addon automatically injects the required script into your <head> via Laravel middleware, requiring zero template edits. If your theme requires custom script placement or bundling, you can turn off auto-injection in the Statamic Control Panel and use the {{ qookieqloud }} Antlers tag (or @qookieqloud in Blade) anywhere in your layout.

Yes. Under the addon settings in the Statamic Control Panel, you can toggle "Bypass for authenticated users". This prevents the consent banner from popping up while you or your content editors are logged in, editing entries, or reviewing content in Statamic Live Preview.

QookieQloud automatically blocks scripts matching your cookie scan rules client-side. For explicit template control, change your script tag to type="text/plain" with data-qq-category="marketing" (or "analytics"). QookieQloud will execute the script automatically the moment the visitor grants consent.

Yes. Because consent evaluation and script unblocking execute asynchronously client-side via edge CDN, static HTML files generated via php please ssg:generate (hosted on Netlify, Cloudflare Pages, Vercel, or AWS S3) work seamlessly without server runtime dependencies.

In multi-site installations, the addon automatically resolves the active Statamic site locale and renders the banner and preference center in the visitor's language. If your sites operate on separate country top-level domains (e.g. .se vs .com), you can assign individual compliance presets per site.

Install and activate WP Consent API and QookieQloud. Use the connection flow below if your plugin and account have v2 access. In the v2 plugin, open QookieQloud in WordPress and click Connect. Sign in in the popup, select a domain you manage or add one, and approve. The public and private API keys are saved automatically; no keys to copy. Existing v1 installations keep their current banner until you explicitly connect to v2. After connecting, changing banner settings or disconnecting, clear your page and CDN caches.

Yes. QookieQloud works flawlessly with WooCommerce, WP Rocket, LiteSpeed Cache, and W3 Total Cache without requiring cache-busting workarounds.

Paste the script snippet <script src="https://cf-cdn.qookieqloud.com/consentLoader.js"></script> inside the <head> tag of your HTML template, website builder (such as Webflow, Framer, Squarespace), or tag manager. Once loaded on your domain, QookieQloud immediately begins managing banner display and tag interception.

By default, the floating Qookie Eyes icon automatically appears in the corner of your website, allowing visitors to reopen and adjust their preferences anytime. You can also trigger the modal from any text link or button using the data-qookie-open-settings attribute, or programmatically invoke window.QookieConsent.open().

Yes. QookieQloud works with Custom JS, Google Tag Manager, React, and headless sites. For new installations, use API v2 with a public Site Key and the v2 script. API v1 can remain enabled while you migrate and verify v2. After v2 is working, disable API v1 in Customize → Connection because that is the safer production configuration. The Site Key alone is not enough: the v2 script must be installed on the website.

Sign in at app.qookieqloud.com and open the domain that should use the banner. Go to Customize → Connection and choose Generate new Site Key. Confirm the dialog, then copy the key into the v2 script shown in step 2 of the Custom JS page. The Site Key is public and scoped to the domain. It only becomes active once the script is installed on the website.

If Google Tag Assistant or your debug console flags a "late consent" warning, follow these troubleshooting steps:

1. Verify Google Tag Gateway (GTG) adoption: Check if your website routes Google tags through a CDN edge integration or server-side Google Tag Gateway (GTG).
2. If GTG is adopted: Ensure that global consent default commands are dispatched prior to edge routing so tags receive default states immediately.
3. If using standard Google Tag Manager: Verify that your QookieQloud GTM tag is configured to fire on the Consent Initialization - All Pages trigger so consent defaults are established before any other tags execute.

API v2 works with React, Vue, Next.js, Nuxt, Astro, and other client-rendered web apps. Add the v2 script to the app’s global HTML head, such as index.html or a layout file loaded on every page. The Site Key may be included in client-side code: it is public and scoped to the registered domain. Never put a private server key in the browser. Example: <script src="https://cf-cdn.qookieqloud.com/v2/consentLoader.js" data-site-key="qq_pk_..." defer></script>. Verify that the script loads on the correct domain, then disable API v1 under Customize → Connection.

Yes. The QookieQloud™ agent has been rigorously audited and certified compliant with WCAG 2.1 Level AA standards. It supports full keyboard navigation, screen readers, focus traps, and high-contrast color modes. Read more in our WCAG compliance guide.

Our built-in Live WCAG Validator tests your background and text color contrast ratios in real time. If a color combination falls below the required 4.5:1 ratio, the validator flags it instantly so you can maintain accessibility standards.