Consiva.ai

No. No plugin or service can make a website legally compliant. Consiva.ai helps you implement privacy and consent controls and keep evidence of them. Responsibility for your site's compliance remains with you.

No request to Consiva ever happens while a page is being built, and the plugin adds no database queries to your pages. It adds about 2–3 ms of PHP time and a 1.4 KB (gzipped) inline script, and causes no layout shift. The banner script loads asynchronously; on a visitor's first page view the banner is often the largest thing painted, so speed tools may report a later Largest Contentful Paint while it appears. See Performance above.

Consiva stores customer privacy records and evidence in India. Certain non-persistent application and runtime assets may be delivered through global infrastructure for performance.

Yes. You create one (or sign in) while connecting, in a few clicks. There is a free plan.

Yes. The plugin is free and open source (GPLv2 or later), and a free Consiva plan is available. Paid plans add service capability, such as more sites or scheduled scans, and are purchased at app.consiva.ai. The plugin's code is the same on every plan.

Consiva is told to revoke this site's credentials and pause the banner, and all of the plugin's settings are removed from WordPress. Your Consiva account, consent records and evidence are kept, because deleting consent evidence without asking would be indefensible. If you want your account deleted too, choose that when you deactivate.

Yes. It detects WooCommerce, keeps the cookies your cart and checkout need, and can add an optional marketing opt-in to checkout (never pre-ticked), recorded with the order number. It works with both the classic and the block checkout.

Contact Form 7 and WPForms forms, and WooCommerce checkout. You choose the forms on the Consiva.ai → Form and checkout consent screen. The opt-in follows the form wherever it is placed (any page, widget or popup), whatever its fields. A new or duplicated form has no opt-in until you turn it on.

It uses the form plugin's own checkbox markup, so it takes the look of the other checkboxes in your form and your theme. To restyle it, target .consiva-consent-optin (every opt-in) or .consiva-consent-optin--wpforms-12 / .consiva-consent-optin--contact-form-7-12 (one form; use your form's ID), or .consiva-consent-optin--checkout, in Appearance → Customize → Additional CSS. Developers can replace the markup with the consiva_consent_optin_html filter; it must keep the checkbox named consiva_consent_marketing, and the box can never be pre-ticked.

Yes. Each site connects to Consiva separately, so each client's settings and records stay separate. On multisite, network admins see every site's status on one read-only screen; each site's own administrator connects it.

Each time you activate or change your consent settings, Consiva re-scans your site, so the results you see reflect your current setup. The plugin shows when the re-scan is running and when it has finished.

Yes. Nothing about a visitor's consent is written into the page: the banner and the blocking read the visitor's choice in their browser, so a cached page is correct for everyone, and you do not need to exclude pages from your cache. Tested with WP Super Cache, W3 Total Cache (page cache and JS minify/combine) and LiteSpeed Cache (JS minify, combine, defer and delay, iframe lazy load), and with a simulated Cloudflare APO edge cache and Rocket Loader. Consiva.ai marks its own scripts so optimisation plugins leave them alone (data-no-optimize, data-no-defer, data-cfasync="false", nowprocket) and adds itself to the exclusion lists of W3 Total Cache, LiteSpeed Cache, WP Rocket and Autoptimize. If you use another optimisation plugin, exclude scripts containing consivaBootstrap or consiva-consent-runtime, and tags with data-cookiecategory or data-consiva-category, from minify, combine, defer and delay.

Only if your CDN caches every URL regardless of what WordPress says (for example a Cloudflare "Cache Everything" rule that ignores origin headers). Then add a bypass for URLs with the consiva-verify query parameter: Consiva uses it once, while you connect, to check you control the domain. It is sent with no-store headers, which WordPress caching plugins respect.

On WordPress 6.9 or later, Consiva.ai holds back tracker scripts and embeds written directly into your theme by checking each page before it is sent, through WordPress's own page output filter. If another plugin (usually a caching or optimisation plugin that rewrites the whole page) keeps replacing that output, Consiva.ai stops checking page output on your site after a few pages, so it cannot break them, and tells you on the Dashboard, Plugins and Consiva screens and in Site Health. Trackers added the normal WordPress way, and by other scripts, stay blocked. Change the other plugin's setting, then choose "Try again".