Does i-run.com use cookies?

i-run.com uses 10 cookies. The site uses Didomi as its consent management platform.

Does i-run.com use a cookie banner (CMP)?

Yes. i-run.com 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 i-run.com use?

i-run.com loads 3 third-party requests from 3 vendors, including Google LLC, tags.pw.adn.cloud, Didomi.

How many marketing and analytics cookies does i-run.com set?

i-run.com sets 0 marketing and 0 analytics cookies, alongside 5 strictly necessary cookies. Under GDPR and the ePrivacy Directive, non-essential cookies require prior consent.

i-run.com

Item: i-run.com
Rating: 67
Author: Passiro

https://i-run.com

Last scanned October 1, 2026

A cookie scan of i-run.com conducted on October 1, 2026 found 10 cookies and 3 third-party tracking requests. The assessment covered 10 pages across 10 unique page templates. The site relies on Didomi as its consent management platform with IAB TCF v2.3 and Google Consent Mode v2. 3 third-party requests were detected from 3 vendors.

Claim & unlock

Third-party

Trackers

Vendors

Consent banner

Didomi

Scans

What this setup is missing

Google Consent Mode v2 is present but does not default to denied for all storage types.
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

10 cookies detected: 5 necessary, 0 analytics, 0 marketing

Total

Necessary

Functional

Analytics

Marketing

Unknown

Filter by category

Name	Domain	Category	Provider	Expiry	Secure	HttpOnly	Party
didomi_token	.i-run.com	Functional	Didomi	1 yr	–	–	1st
ak_bmsc	.i-run.com	Necessary	Akamai	Expired	–	✓	1st
bm_sv	.i-run.com	Necessary	Akamai	Expired	✓	–	1st
bm_sz	.i-run.com	Necessary	Akamai	Expired	–	–	1st
JSESSIONID	www.i-run.com	Necessary	Java	Session	✓	✓	1st
_abck	.i-run.com	Necessary	Akamai	365 d	✓	–	1st
ty_ead before consent	.i-run.com	Unknown	-	180 d	✓	✓	1st
ty_id before consent	.i-run.com	Unknown	-	180 d	✓	✓	1st
ty_session before consent	.i-run.com	Unknown	-	Expired	✓	✓	1st
VI_ID before consent	.i-run.com	Unknown	-	365 d	–	–	1st

Browser storage set by the site

Name	Domain	Party
didomi_token set by sdk.privacy-center.org/sdk.2af281429ae434027f53ac77f93097d5b4488b76.js:2:73627	https://www.i-run.com	1st	before consent
dummy set by www.i-run.com/Ad2M:1:561069	https://www.i-run.com	1st	before consent
productId set by static.i-run.fr/4ec23ea8.js:723:60	https://www.i-run.com	1st	before consent

Third-Party Trackers

3 requests detected from 3 vendors: Google LLC, tags.pw.adn.cloud, Didomi

Analytics

Marketing

Necessary

Functional

Other

Vendor	Category	Type	Domain
Google LLC before consent Google Tag Manager	Analytics	script	www.googletagmanager.com
tags.pw.adn.cloud before consent	Analytics	script	tags.pw.adn.cloud
Didomi Didomi tracker domain (source: Disconnect.me, category: ConsentManagers)	Unknown	script	sdk.privacy-center.org