Scanned on 19 August 2026 at 04:26 UTC
As of , xn--80ahdaaocuwb3adye1k.xn--p1ai has a GDPR compliance score of 0/100 with 12 pre-consent tracking violations detected.
Only Privacy Score 100 means full compliance. These violations mean that before you could even click the Cookie Consent banner, this website already collected your personal data and shared it with third parties. Learn why this matters (our blog) →
Who is responsible? The website owner is solely responsible for these violations and in general often benefits monetarily (directly or indirectly) from collecting and sharing your data without your consent.
No consent platform recognised
The site may use a custom or unrecognised banner. This is informational and does not affect the score.
Tracks your browsing behaviour to build a profile and serve targeted ads before you give consent.
Records mouse movements, keystrokes, and clicks to capture your exact behaviour on the page.
Tracking cookies are used to identify and follow users across websites. Under GDPR, these require explicit consent before being set, but on this website they are active immediately.
Low-severity concerns: external fonts, empty tag containers, WebSocket connections, and third-party storage.
Services and cookies that comply with GDPR requirements. No consent needed.
Recognised and seen loading before consent, but we did not observe them transmit tracking data, so they are not counted in your score. Worth checking each still respects consent.
Recognised but not counted. No impact on your privacy score.
Pending classification by our team. No impact on your privacy score.
These items are pending classification. No impact on your privacy score.
Most findings on this page are configuration problems, not catastrophes. These plain-language guides explain what each one means and how to fix it, written for website owners rather than lawyers.
All guides live at gdprscanner.eu/guides.
xn--80ahdaaocuwb3adye1k.xn--p1ai has a GDPR compliance score of 0/100.
A score below 50 indicates serious GDPR compliance failures. Multiple high-severity trackers or advertising scripts load before consent, exposing the website to potential fines of up to €20 million or 4% of annual global turnover under GDPR Article 83.
25 trackers detected loading before user consent:
Legal basis: This violates GDPR Article 6(1)(a), ePrivacy Directive Article 5(3), and CJEU Planet49 (C-673/17). Advertising trackers profile visitors for targeted ads, which needs the visitor's consent. The Court of Justice of the EU held in Planet49 (C-673/17, 1 October 2019) that a pre-ticked checkbox is not valid consent: consent requires an active choice by the visitor.
Legal basis: This violates ePrivacy Directive Article 5(3), GDPR Article 6(1)(a), and GDPR Article 9 where sensitive data is captured. Session recording scripts read clicks, scrolling, mouse movements and sometimes form inputs from the visitor's browser. This is not strictly necessary to provide the website, so Article 5(3) of the ePrivacy Directive requires prior consent. The CNIL's draft recommendation on session replay (February 2026) takes the same view. If health or financial data is captured, Article 9 of the GDPR also applies.
This GDPR compliance scan of xn--80ahdaaocuwb3adye1k.xn--p1ai was performed by GDPR Scanner, a pre-consent privacy scanning tool. The scan captures all trackers, cookies, and third-party scripts that load before a user clicks any consent button.
Under GDPR (General Data Protection Regulation), websites must obtain explicit consent before processing personal data. Any tracker or cookie that fires before consent is a potential violation of EU privacy law.
A privacy score of 100/100 means the website loads zero trackers and zero tracking cookies before the user gives consent. This is the standard required by GDPR Article 5(1)(a) and Article 7.
Essential cookies (session management, security tokens) and first-party functional cookies do not incur penalties, as they are covered by the legitimate interest legal basis. See an example: playhth.com scores 100/100.
Legal basis: This violates ePrivacy Directive Article 5(3) and GDPR Article 6(1)(a). WebSocket connections to third-party servers send visitor data, including the IP address, to an external server as soon as they open, and keep a live channel open for more. When third-party code opens the connection before consent, Article 5(3) of the ePrivacy Directive requires consent unless the connection is strictly necessary for a service the visitor asked for.
Legal basis: This violates ePrivacy Directive Article 5(3), GDPR Article 6(1)(a), and GDPR Article 9 where sensitive data is captured. Session recording scripts read clicks, scrolling, mouse movements and sometimes form inputs from the visitor's browser. This is not strictly necessary to provide the website, so Article 5(3) of the ePrivacy Directive requires prior consent. The CNIL's draft recommendation on session replay (February 2026) takes the same view. If health or financial data is captured, Article 9 of the GDPR also applies.
Legal basis: This violates GDPR Article 6(1)(a), ePrivacy Directive Article 5(3), and CJEU Planet49 (C-673/17). Advertising trackers profile visitors for targeted ads, which needs the visitor's consent. The Court of Justice of the EU held in Planet49 (C-673/17, 1 October 2019) that a pre-ticked checkbox is not valid consent: consent requires an active choice by the visitor.
| Cookie Name | Domain | Type | Service | Duration |
|---|---|---|---|---|
| _ym_isad | .xn--80ahdaaocuwb3adye1k.xn--p1ai | 1st party | Yandex.Metrica - Determines whether a user has ad blockers | Session |
| _ym_uid | .xn--80ahdaaocuwb3adye1k.xn--p1ai | 1st party | Yandex.Metrica - Used for identifying site users | Session |
| tildauid | xn--80ahdaaocuwb3adye1k.xn--p1ai | 1st party | Tilda - Tilda website builder visitor ID | Session |
| tildasid | xn--80ahdaaocuwb3adye1k.xn--p1ai | 1st party | Tilda - Tilda website builder session ID | Session |
| _ym_visorc | .xn--80ahdaaocuwb3adye1k.xn--p1ai | 1st party | Yandex Metrica - Yandex Metrica webvisor session recording | Session |
| _fbp | .xn--80ahdaaocuwb3adye1k.xn--p1ai | 1st party | Facebook - Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers | Session |
| _ym_d | .xn--80ahdaaocuwb3adye1k.xn--p1ai | 1st party | Yandex.Metrica - Saves the date of the user's first site session | Session |
xn--80ahdaaocuwb3adye1k.xn--p1ai has serious GDPR compliance deficiencies with a score of 0/100 and 12 violations detected. Multiple trackers and cookies are loading before user consent, which constitutes a clear breach of the ePrivacy Directive Article 5(3).
This level of non-compliance exposes the website operator to significant regulatory risk. Under GDPR Article 83(5), infringements of the basic principles for processing, including the conditions for consent, can be fined up to €20 million or 4% of worldwide annual turnover. Recent enforcement trends show increasing DPA activity across the EU.
Immediate action is recommended: audit all third-party scripts, implement a Consent Management Platform (CMP) that blocks non-essential trackers before consent, and verify compliance through re-scanning.
xn--80ahdaaocuwb3adye1k.xn--p1ai scores 0/100 with 12 violation(s) detected. Trackers or cookies were found loading before user consent.
Our scan detected 46 tracker(s) loading before consent, including Facebook Pixel, VK, Yandex Metrica.
Yes, 8 cookie(s) were detected before the user interacted with any consent banner.
xn--80ahdaaocuwb3adye1k.xn--p1ai has a GDPR compliance score of 0/100 as of 19 August 2026. A score of 100 means no trackers or cookies that require consent were detected before consent. xn--80ahdaaocuwb3adye1k.xn--p1ai currently has 12 violation(s) affecting its score.
xn--80ahdaaocuwb3adye1k.xn--p1ai should implement a Consent Management Platform (CMP) that blocks all non-essential trackers and cookies until the visitor gives explicit consent. This includes configuring tag managers like Google Tag Manager to use consent-aware triggers, self-hosting external fonts, and auditing all third-party scripts. After making changes, re-scan with GDPR Scanner to check the result.