Does cruisetopic.ro use cookies?

cruisetopic.ro uses 3 cookies. The site uses Didomi as its consent management platform.

Does cruisetopic.ro use a cookie banner (CMP)?

Yes. cruisetopic.ro uses Didomi as its consent management platform. IAB TCF v2.3 consent signals were detected. Google Consent Mode v2 appears to be configured.

Which third-party trackers does cruisetopic.ro use?

cruisetopic.ro loads 5 third-party requests from 4 vendors, including Google LLC, Snap, TrustPilot, Didomi.

How many marketing and analytics cookies does cruisetopic.ro set?

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

cruisetopic.ro

Item: cruisetopic.ro
Rating: 54
Author: Passiro

https://cruisetopic.ro

Last scanned August 29, 2026

A cookie scan of cruisetopic.ro conducted on August 29, 2026 found 3 cookies and 5 third-party tracking requests. The site uses Didomi as its consent management platform with IAB TCF v2.3 and Google Consent Mode v2. 5 third-party requests were detected from 4 vendors.

Claim & unlock

Third-party

Trackers

Vendors

Consent banner

Didomi

Scans

What this setup is missing

No Reject option on the first layer; declining requires extra steps.

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

3 cookies detected: 0 necessary, 0 analytics, 2 marketing

Total

Necessary

Functional

Analytics

Marketing

Unknown

Filter by category

Name	Domain	Category	Provider	Expiry	Secure	HttpOnly	Party
didomi_token	.cruisetopic.ro	Functional	Didomi	183 d	✓	–	1st
_scid before consent	.cruisetopic.ro	Marketing	Snapchat	1.1 yr	–	–	1st
_scid_r before consent	.cruisetopic.ro	Marketing	Snapchat	1.1 yr	–	–	1st

Browser storage set by the site

Name	Domain	Party
u_sclid set by sc-static.net/scevent.min.js:2:12021	https://cruisetopic.ro	1st	before consent
u_scsid set by sc-static.net/scevent.min.js:2:12021	https://cruisetopic.ro	1st	before consent
u_sclid_r set by sc-static.net/scevent.min.js:2:12021	https://cruisetopic.ro	1st	before consent
u_scsid_r set by sc-static.net/scevent.min.js:2:12021	https://cruisetopic.ro	1st	before consent
crtopic-token-interactions set by cruisetopic.ro/chunk-4X7EFCCA.js:1:881	https://cruisetopic.ro	1st	before consent
didomi_token set by sdk.privacy-center.org/sdk.abaeabbc5c9ea4e83527821f4ce8f3210f2c1146.js:2:81546	https://cruisetopic.ro	1st	before consent

Third-Party Trackers

5 requests detected from 4 vendors: Google LLC, Snap, TrustPilot, Didomi

Analytics

Marketing

Necessary

Functional

Other

Vendor	Category	Type	Domain
Google LLC before consent Google Maps API	Functional	script	maps.googleapis.com
Snap before consent Snap tracker domain (source: Disconnect.me, category: Advertising)	Marketing	script	sc-static.net
TrustPilot TrustPilot tracker domain (source: Disconnect.me, category: Content)	Necessary	script	widget.trustpilot.com
Didomi Didomi tracker domain (source: Disconnect.me, category: ConsentManagers)	Unknown	script	sdk.privacy-center.org
Google LLC before consent Google tracker domain (source: Disconnect.me, category: FingerprintingGeneral)	Unknown	script	www.google-analytics.com