Skip to main content

Cookie Craft

Frequently asked questions

The questions technical and commercial buyers actually ask. If yours is not here, ask us.

About the product

Yes — fully. It is a first-party solution: the code is installed, loaded and executed from your own server. Hosted CMPs such as CookieYes and Cookiebot deliver a JavaScript file from the vendor’s own domain, a third-party dependency on every page. Cookie Craft has none. (The trackers you enable still contact their own providers, under the consent rules you configure.)

The banner runs entirely on your own server. A temporary API outage does not interrupt it — Cookie Craft keeps using the last valid signed verdict for the documented tolerance period. License validation is a separate background check a few times a day, never while a visitor waits.

Yes. For EEA traffic, Google requires consent choices to be passed to its tags to keep key measurement, personalization and remarketing capabilities — that is what Consent Mode v2 does, and it is built in. Cookie Craft handles the container or tag placement and consent-aware loading; your tracking plan still defines the events and conversions.

One root domain and every subdomain under it, with unlimited pages and traffic, across as many installs and platforms as you run there. You are billed per root domain only.

No. Different TLDs are separate registrable domains — the browser treats them independently, so the consent cookie is not shared between them, and under per-root-domain pricing each is its own license. Subdomains of one root (www, shop., fr.) are all covered together.

WordPress (with WooCommerce), custom PHP-MySQL, PrestaShop, OpenCart, Shopware, Joomla, Drupal, Laravel, Symfony, CS-Cart, Bagisto and Concrete CMS — twelve in total.

No. Cookie Craft gives you the mechanism — a banner, real script blocking and correct Consent Mode v2 signals — but it does not scan your site to discover and classify cookies automatically. If an automatic scanner is a hard requirement today, an established competitor may suit you better.

No. It does not write your legal documents. What you declare is up to you; Cookie Craft enforces the choice.

Not currently. Cookie Craft keeps a local consent log in your own database, but it is not positioned as an IAB TCF framework or a full enterprise-grade, exportable audit trail. If that is a requirement, see how it compares.

It is designed to support GDPR-compliant consent and blocks or delays configured scripts until consent is granted. Full compliance also depends on your configuration, cookie categorisation, legal basis and policy texts — Cookie Craft is a tool, not legal advice, and cannot guarantee compliance by itself.

A 30-day money-back guarantee, for any reason, on your first annual purchase. It does not apply to monthly plans or to renewals.

Still deciding?

See how it compares, or get in touch.