Scanned on 19 October 2026 at 09:58 UTC
As of , metaweep.com has a GDPR compliance score of 70/100 with 1 pre-consent tracking violation 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.
Services and cookies that comply with GDPR requirements. No consent needed.
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.
metaweep.com has a GDPR compliance score of 70/100.
A score between 50 and 79 indicates moderate GDPR compliance issues. Analytics trackers or advertising scripts are likely loading before user consent, which may result in regulatory attention.
1 tracker 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.
No tracking cookies set before consent were counted as violations.
metaweep.com has 1 GDPR compliance violation with 1 tracker loading before user consent. This level of non-compliance carries meaningful regulatory risk.
Under GDPR Article 83(5), fines can reach €20 million or 4% of worldwide annual turnover, whichever is higher. Cookie consent failures are also fined under national law: the CNIL fined Google €150 million (2021), Microsoft €60 million (2022) and SHEIN €150 million (2025).
Implementation of a properly configured Consent Management Platform (CMP) that blocks all non-essential scripts until consent is obtained is the recommended remediation step.
This GDPR compliance scan of metaweep.com 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.
metaweep.com scores 70/100 with 1 violation(s) detected. Trackers or cookies were found loading before user consent.
Our scan detected 2 tracker(s) loading before consent, including Baidu Static, Baidu Ads.
Yes, 1 cookie(s) were detected before the user interacted with any consent banner.
metaweep.com has a GDPR compliance score of 70/100 as of 19 October 2026. A score of 100 means no trackers or cookies that require consent were detected before consent. metaweep.com currently has 1 violation(s) affecting its score.
metaweep.com 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.