https://riotgames.com
Scanned Apr 15, 2026 · 35.9s
Your website score is
Grade
BannerConsent Banner
Yes
Regulatory Compliance
Multi-regulation overview — click any regulation for details
Technical scan only. A passing score does not equal legal compliance. Consult qualified legal counsel for your jurisdiction.
Tag Leak detected 9 user data leaks before consent on riotgames.com, including Osano (Tracker Tracker).
Security Headers
2/6 presentStrict-Transport-Security
max-age=31536000; includeSubDomains
Content-Security-Policy
Add a Content-Security-Policy header to prevent XSS and code injection attacks
X-Frame-Options
Sameorigin
X-Content-Type-Options
Set X-Content-Type-Options to 'nosniff' to prevent MIME type sniffing
Referrer-Policy
Set a Referrer-Policy header to control how much referrer information is shared
Permissions-Policy
Add a Permissions-Policy header to restrict browser features like camera, microphone, and geolocation
Google Consent Mode
V2Consent Parameters
Post-Rejection Audit
Reject Button
Missing
Post-Rejection Fires
0 vendors
Consent Mode
Not Detected
GTM Load
962ms pre-consent
Google Tag Manager(GTM-KWJH)
Loaded 962ms after page load — before the consent banner was detected (banner appeared at 9039ms). Per a 2022 German court ruling, GTM itself transmits the user's IP to Google pre-consent.
Consent Mode V2: Not Detected
Google Consent Mode was not detected on this site.
Consent Record Audit
Issues detectedConsent record stored after interaction
GDPR Art. 7(1)Found: localStorage:osano_consentmanager_tattles
Record contains timestamp
Art. 7(1)No timestamp found in consent record
Record contains consent state
Art. 7(1)Consent state (accepted/rejected) not found in record
Record contains consent categories
Art. 7(1)Consent categories detected
Consent withdrawal mechanism accessible
GDPR Art. 7(3)No way for users to withdraw consent found on page
No cookie settings link, footer link, or floating consent button was detected. GDPR requires users to withdraw consent as easily as they gave it.
Why this matters
Under GDPR Article 7, controllers must be able to demonstrate that consent was given (Art. 7(1)) and ensure users can withdraw consent at any time, as easily as giving it (Art. 7(3)). Sites with no consent record or no withdrawal mechanism cannot legally rely on consent as a lawful basis.
Tracker categories detected
Critical3
Osano (tracker) loaded before consent
No "reject all" option found — users cannot refuse non-essential cookies (ICO guidance requires this)
No recognizable consent withdrawal mechanism detected — GDPR Article 7(3) requires users can withdraw consent as easily as giving it (cookie settings link or floating button expected)
Warnings8
Google Tag Manager2 findingsID trackedwww.googletagmanager.com
www.googletagmanager.com
Google Tag Manager loads before consent — this is expected and required for GCM v2 to initialise consent defaults before any tags fire
GTM loaded before consent banner — IP address transmitted to Google pre-consent (container: GTM-KWJH)
Google Tag Manager loads before consent — this is expected and required for GCM v2 to initialise consent defaults before any tags fire
Unknown third-party request to cdn.rgpub.io before consent
Unknown third-party request to cdn.ravenjs.com before consent
Unknown third-party request to lolstatic-a.akamaihd.net before consent
Unknown third-party request to fast.fonts.net before consent
localStorage key "_1776283264287" written before consent
Info1
Cloudflare bot management — necessary for site operation
Compliant21
TikTok Pixel6 findingsID trackedanalytics.tiktok.com, analytics-ipv6.tiktokw.us, _ttp, tt_sessionId, tt_appInfo, tt_pixel_session_index
analytics.tiktok.com, analytics-ipv6.tiktokw.us, _ttp, tt_sessionId, tt_appInfo, tt_pixel_session_index
TikTok Pixel (TikTok) loaded correctly after consent
TikTok Pixel (TikTok) loaded correctly after consent
TikTok Pixel cookie "_ttp" set correctly after consent
TikTok Pixel (TikTok) wrote "tt_sessionId" to sessionStorage correctly after consent
TikTok Pixel (TikTok) wrote "tt_appInfo" to sessionStorage correctly after consent
TikTok Pixel (TikTok) wrote "tt_pixel_session_index" to sessionStorage correctly after consent
Meta Pixel3 findingsID trackedwww.facebook.com, connect.facebook.net, _fbp
www.facebook.com, connect.facebook.net, _fbp
Meta Pixel (Meta) loaded correctly after consent
Meta Pixel (Meta) loaded correctly after consent
Meta Pixel cookie "_fbp" set correctly after consent
Sentry (Sentry) loaded correctly after consent
Google Ads4 findingswww.google.com, googleads.g.doubleclick.net, _gcl_au, _gcl_ls
www.google.com, googleads.g.doubleclick.net, _gcl_au, _gcl_ls
Google Ads (Google) loaded correctly after consent
Google Ads (Google) loaded correctly after consent
Google Ads cookie "_gcl_au" set correctly after consent
Google Ads (Google) wrote "_gcl_ls" to localStorage correctly after consent
New Relic2 findingsjs-agent.newrelic.com, bam.nr-data.net
js-agent.newrelic.com, bam.nr-data.net
New Relic (New Relic) loaded correctly after consent
New Relic (New Relic) loaded correctly after consent
Osano2 findingsosano_consentmanager_uuid, osano_consentmanager
osano_consentmanager_uuid, osano_consentmanager
Osano cookie "osano_consentmanager_uuid" set correctly after consent
Osano cookie "osano_consentmanager" set correctly after consent
Google Analytics2 findings_ga_7VLGVTHBTW, _ga
_ga_7VLGVTHBTW, _ga
Google Analytics cookie "_ga_7VLGVTHBTW" set correctly after consent
Google Analytics cookie "_ga" set correctly after consent
DoubleClick/Google Marketing cookie "test_cookie" set correctly after consent
Is this your site?
Run a full multi-page scan with monitoring and get detailed remediation steps
Scan riotgames.com →This audit is based on publicly observable website behavior. To request removal from the index, email support@tagleak.com