Skip to main content
cquence.co.in

cquence.co.in

https://cquence.co.in

Last scanned August 29, 2026

A cookie scan of cquence.co.in performed on August 29, 2026 found 15 cookies and 9 third-party tracking requests. The assessment covered 10 pages across 10 unique page templates. The site employs CookieYes as its consent management platform with IAB TCF v2.3; Google Consent Mode v2 was not observed. 9 third-party requests were detected from 5 vendors.

Cookies

15

Third-party

0

Trackers

9

Vendors

5

Consent banner

CookieYes

Scans

1

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

15 cookies detected: 1 necessary, 10 analytics, 2 marketing

Total

15

Necessary

1

Functional

2

Analytics

10

Marketing

2

Unknown

0

Filter by category
Name Domain Category Provider Expiry Secure HttpOnly Party
FCCDCF .cquence.co.in Analytics Google 1 yr 1st
sbjs_current before consent .cquence.co.in Analytics WooCommerce Session 1st
sbjs_current_add before consent .cquence.co.in Analytics WooCommerce Session 1st
sbjs_first before consent .cquence.co.in Analytics WooCommerce Session 1st
sbjs_first_add before consent .cquence.co.in Analytics WooCommerce Session 1st
sbjs_migrations before consent .cquence.co.in Analytics WooCommerce Session 1st
sbjs_session before consent .cquence.co.in Analytics WooCommerce Expired 1st
sbjs_udata before consent .cquence.co.in Analytics WooCommerce Session 1st
tk_qs before consent .cquence.co.in Analytics WordPress Expired 1st
tk_r3d before consent .cquence.co.in Analytics WordPress Expired 1st
cookieyes-consent cquence.co.in Functional CookieYes 349 d 1st
tk_ai before consent .cquence.co.in Functional WooCommerce / Jetpack 1.1 yr 1st
tk_lr before consent .cquence.co.in Marketing WordPress 349 d 1st
tk_or before consent .cquence.co.in Marketing WordPress 1.1 yr 1st
__eoi .cquence.co.in Necessary Google AdSense 164 d 1st

Browser storage set by the site

Name Domain Party
elementor set by cquence.co.in/frontend.min.js https://cquence.co.in 1st before consent
elementor set by cquence.co.in/frontend.min.js https://cquence.co.in 1st before consent

Third-Party Trackers

9 requests detected from 5 vendors: Microsoft, Google LLC, media.net, Automattic, Yahoo!

Analytics

1

Marketing

2

Necessary

5

Functional

0

Other

1

Vendor Category Type Domain
Microsoft before consent Microsoft tracker domain (source: Disconnect.me, category: Analytics) Analytics script scripts.clarity.ms
Google LLC before consent Google tracker domain (source: Disconnect.me, category: Advertising) Marketing script ep1.adtrafficquality.google
media.net before consent media.net tracker domain (source: Disconnect.me, category: Advertising) Marketing script contextual.media.net
Automattic Automattic tracker domain (source: Disconnect.me, category: Content) Necessary script c0.wp.com
Automattic Automattic tracker domain (source: Disconnect.me, category: Content) Necessary script i0.wp.com
Google LLC Google Fonts stylesheet Necessary script fonts.googleapis.com
Google LLC Google Fonts files Necessary script fonts.gstatic.com
Yahoo! Yahoo! tracker domain (source: Disconnect.me, category: Content) Necessary script s.yimg.com
Google LLC before consent Google tracker domain (source: Disconnect.me, category: FingerprintingGeneral) Unknown script pagead2.googlesyndication.com

Scan history

One completed scan: cookies and trackers from the scan on August 29, 2026.

Recent scans

August 29, 2026 15 9

Is cquence.co.in your website?

Claim it to monitor your cookies and trackers, set up a consent banner with automatic script blocking, and keep your cookie policy up to date.