Does crypto.org use cookies?

crypto.org uses 9 cookies, 6 of which are set by third-party domains. The site uses OneTrust as its consent management platform.

Does crypto.org use a cookie banner (CMP)?

Yes. crypto.org uses OneTrust as its consent management platform. IAB TCF v2.3 was not detected. Google Consent Mode v2 was not detected.

Which third-party trackers does crypto.org use?

crypto.org loads 38 third-party requests from 4 vendors, including Google LLC, SmartBear, OneTrust LLC, OneTrust.

How many marketing and analytics cookies does crypto.org set?

crypto.org sets 0 marketing and 5 analytics cookies, alongside 3 strictly necessary cookies. Under GDPR and the ePrivacy Directive, non-essential cookies require prior consent.

crypto.org

Item: crypto.org
Rating: 34
Author: Passiro

https://crypto.org

Last scanned July 24, 2026

A cookie scan of crypto.org completed on July 24, 2026 found 9 cookies and 38 third-party tracking requests. The assessment covered 8 pages across 8 unique page templates. The site employs OneTrust as its consent management platform. Neither IAB TCF v2.3 nor Google Consent Mode v2 was observed on our check. 38 third-party requests were detected from 4 vendors.

Claim & unlock

Third-party

Trackers

Vendors

Consent banner

OneTrust

Scans

What this setup is missing

Google tags were observed, but Google Consent Mode v2 was not detected.

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

9 cookies detected: 3 necessary, 5 analytics, 0 marketing, 6 third-party

Total

Necessary

Functional

Analytics

Marketing

Unknown

6 third-party cookies detected

Third-party cookies require explicit user consent under GDPR/ePrivacy.

Filter by category

Name	Domain	Category	Provider	Expiry	Secure	HttpOnly	Party
_ga before consent	.cronos-pos.org	Analytics	Google Analytics	1.1 yr lifetime over 13 months	–	–	3rd
_ga before consent	.crypto.org	Analytics	Google Analytics	1.1 yr lifetime over 13 months	–	–	1st
_ga_87EQJGM0VE before consent	.cronos-pos.org	Analytics	Google Analytics	1.1 yr lifetime over 13 months	–	–	3rd
_ga_87EQJGM0VE before consent	.crypto.org	Analytics	Google Analytics	1.1 yr lifetime over 13 months	–	–	1st
_ga_QWMKE0PS97 before consent	.cronos-pos.org	Analytics	Google Analytics	1.1 yr lifetime over 13 months	–	–	3rd
theme before consent	cronos-pos.org	Functional	UI Preference	180 d	–	–	3rd
OptanonConsent	.cronos-pos.org	Necessary	OneTrust	365 d	–	–	3rd
__cf_bm	.cronos-pos.org	Necessary	Cloudflare	Expired	✓	✓	3rd
__cf_bm	.crypto.org	Necessary	Cloudflare	Expired	✓	✓	1st

Browser storage set by the site

Name	Domain	Party
__GITHUB_API_CRYPTO-ORG-CHAIN/CHAIN-MAIN_TAGS_CACHE__ set by crypto.org/umi.433b76a6.js:1:455179	https://crypto.org	1st	before consent
__GITHUB_API_CRYPTO-ORG-CHAIN/CHAIN-MAIN_CONTRIBUTORS_CACHE__ set by crypto.org/umi.433b76a6.js:1:455179	https://crypto.org	1st	before consent
__GITHUB_API_CRYPTO-ORG-CHAIN/CHAIN-MAIN_OPENPR_CACHE__ set by crypto.org/umi.433b76a6.js:1:455179	https://crypto.org	1st	before consent
__GITHUB_API_CRYPTO-ORG-CHAIN/CHAIN-MAIN_CODEFREQUENCY_CACHE__ set by crypto.org/umi.433b76a6.js:1:455179	https://crypto.org	1st	before consent
__GITHUB_API_CRYPTO-ORG-CHAIN/CHAIN-MAIN_OPENISSUE_CACHE__ set by crypto.org/umi.433b76a6.js:1:455179	https://crypto.org	1st	before consent
__GITHUB_API_CRYPTO-ORG-CHAIN/CHAIN-MAIN_COMMITACTIVITY_CACHE__ set by crypto.org/umi.433b76a6.js:1:455179	https://crypto.org	1st	before consent
__GITHUB_API_CRYPTO-ORG-CHAIN/CHAIN-MAIN_CLOSEDISSUE_CACHE__ set by crypto.org/umi.433b76a6.js:1:455179	https://crypto.org	1st	before consent
__GITHUB_API_CRYPTO-ORG-CHAIN/CHAIN-MAIN_CLOSEDPR_CACHE__ set by crypto.org/umi.433b76a6.js:1:455179	https://crypto.org	1st	before consent
__GITHUB_API_CRYPTO-ORG-CHAIN/CHAIN-MAIN_RELEASES_CACHE__ set by crypto.org/umi.433b76a6.js:1:455179	https://crypto.org	1st	before consent
bugsnag-anonymous-id set by cronos-pos.org/vendors.js:1:754243	https://cronos-pos.org	3rd	before consent
__storage_test__ set by cronos-pos.org/vendors.js:1:2242600	https://cronos-pos.org	3rd	before consent

Third-Party Trackers

38 requests detected from 4 vendors: Google LLC, SmartBear, OneTrust LLC, OneTrust

Analytics

Marketing

Necessary

Functional

Other

Vendor	Category	Type	Domain
Google LLC before consent Google Tag Manager	Analytics	script	www.googletagmanager.com
SmartBear before consent SmartBear tracker domain (source: Disconnect.me, category: Analytics)	Analytics	script	sessions.bugsnag.com
Google LLC before consent Google reCAPTCHA bot protection	Functional	script	www.google.com
Google LLC Google tracker domain (source: Disconnect.me, category: Content)	Necessary	script	www.gstatic.com
Google LLC Google Fonts files	Necessary	script	fonts.gstatic.com
OneTrust LLC OneTrust consent management	Necessary	script	cdn.cookielaw.org
Google LLC before consent Google tracker domain (source: Disconnect.me, category: FingerprintingGeneral)	Unknown	script	region1.google-analytics.com
OneTrust OneTrust tracker domain (source: Disconnect.me, category: ConsentManagers)	Unknown	script	geolocation.onetrust.com