Does drizzy.eu use cookies?

drizzy.eu uses 13 cookies. The site uses Complianz as its consent management platform.

Does drizzy.eu use a cookie banner (CMP)?

Yes. drizzy.eu uses Complianz as its consent management platform. IAB TCF v2.3 was not detected. Google Consent Mode v2 was not detected.

Which third-party trackers does drizzy.eu use?

drizzy.eu loads 2 third-party requests from 2 vendors, including Automattic, Google LLC.

How many marketing and analytics cookies does drizzy.eu set?

drizzy.eu sets 2 marketing and 9 analytics cookies, alongside 0 strictly necessary cookies. Under GDPR and the ePrivacy Directive, non-essential cookies require prior consent.

drizzy.eu

Item: drizzy.eu
Rating: 38
Author: Passiro

https://drizzy.eu

Last scanned September 6, 2026

A cookie scan of drizzy.eu performed on September 6, 2026 found 13 cookies and 2 third-party tracking requests. The assessment covered 5 pages across 5 unique page templates. The site relies on Complianz as its consent management platform. Neither IAB TCF v2.3 nor Google Consent Mode v2 was observed on our check. 2 third-party requests were detected from 2 vendors.

Claim & unlock

Third-party

Trackers

Vendors

Consent banner

Complianz

Scans

Compliance by audience

European Union

✗ Not met

GDPR + ePrivacy · Prior consent (opt-in)

United Kingdom

✗ Not met

UK GDPR + PECR · Consent-based

United States

✓ Meets this model

CCPA/CPRA + state laws · Notice & opt-out

Canada

! Needs attention

PIPEDA + Québec Law 25 · Consent-based

Brazil

! Needs attention

LGPD · Consent-based

Scanned from the EU; sites may serve different banners or tracking to other regions. Verdicts reflect observed behaviour measured against each audience's rules.

Connection security

HTTPS supported

✓

Redirects HTTP to HTTPS

✓

HSTS

✓

Content Security Policy

✗

Cookies

13 cookies detected: 0 necessary, 9 analytics, 2 marketing

Total

Necessary

Functional

Analytics

Marketing

Unknown

Filter by category

Name	Domain	Category	Provider	Expiry	Secure	HttpOnly	Party
sbjs_current before consent	.drizzy.eu	Analytics	WooCommerce	Session	–	–	1st
sbjs_current_add before consent	.drizzy.eu	Analytics	WooCommerce	Session	–	–	1st
sbjs_first before consent	.drizzy.eu	Analytics	WooCommerce	Session	–	–	1st
sbjs_first_add before consent	.drizzy.eu	Analytics	WooCommerce	Session	–	–	1st
sbjs_migrations before consent	.drizzy.eu	Analytics	WooCommerce	Session	–	–	1st
sbjs_session before consent	.drizzy.eu	Analytics	WooCommerce	Expired	–	–	1st
sbjs_udata before consent	.drizzy.eu	Analytics	WooCommerce	Session	–	–	1st
tk_qs before consent	.drizzy.eu	Analytics	WordPress	Expired	–	–	1st
tk_r3d before consent	.drizzy.eu	Analytics	WordPress	Expired	–	–	1st
pll_language before consent	drizzy.eu	Functional	Polylang	353 d	✓	–	1st
tk_ai before consent	drizzy.eu	Functional	WooCommerce / Jetpack	353 d	✓	–	1st
tk_lr before consent	.drizzy.eu	Marketing	WordPress	353 d	–	–	1st
tk_or before consent	.drizzy.eu	Marketing	WordPress	1.1 yr	–	–	1st

Browser storage set by the site

Name	Domain	Party
__wpDataTestLocalStorage set by drizzy.eu/data.min.js	https://drizzy.eu	1st	before consent
storeApiNonce set by drizzy.eu/wc-blocks-middleware.js	https://drizzy.eu	1st	before consent
storeApiCartData set by drizzy.eu/wc-blocks-data.js	https://drizzy.eu	1st	before consent
wc-blocks_dismissed_incompatible_extensions_notices set by drizzy.eu/wc-cart-checkout-base-frontend.js	https://drizzy.eu	1st	before consent

Third-Party Trackers

2 requests detected from 2 vendors: Automattic, Google LLC

Analytics

Marketing

Necessary

Functional

Other

Vendor	Category	Type	Domain
Automattic before consent Automattic tracker domain (source: Disconnect.me, category: Content)	Analytics	script	stats.wp.com
Google LLC Google tracker domain (source: Disconnect.me, category: Content)	Necessary	script	www.gstatic.com