Scanned on 22 June 2026 at 16:35 UTC· 3 total scans
As of , kfzteile24.de has a GDPR compliance score of 56/100 with 20 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.
A tag manager loading tracking scripts before the visitor has given consent.
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.
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.
kfzteile24.de has a GDPR compliance score of 56/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.
16 trackers detected loading before user consent:
Legal basis: This violates GDPR Article 6(1)(a), ePrivacy Directive Article 5(3), and CNIL Decision SAN-2022-023. Tag managers that actively load tracking scripts before consent enable personal data processing without a legal basis. The CNIL fined Google €150 million in 2022 partly because its tag manager loaded tracking before users could refuse cookies.
Legal basis: This violates ePrivacy Directive Article 5(3) and CJEU Planet49 (C-673/17). Third-party storage access (localStorage, sessionStorage) on external domains constitutes accessing device information without user consent. The Planet49 ruling confirmed that the ePrivacy Directive's consent requirement applies to all information stored on or accessed from a user's terminal equipment.
This GDPR compliance scan of kfzteile24.de 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 CJEU Planet49 (C-673/17). Third-party storage access (localStorage, sessionStorage) on external domains constitutes accessing device information without user consent. The Planet49 ruling confirmed that the ePrivacy Directive's consent requirement applies to all information stored on or accessed from a user's terminal equipment.
| Cookie Name | Domain | Type | Service | Duration |
|---|---|---|---|---|
| __exponea_etc__ | .kfzteile24.de | 1st party | Exponea - Exponea Bloomreach Engagement - This cookie is used to determine which products the visitor has viewed. This information is used to promote related products and optimize ad-efficiency. | Session |
| __exponea_time2__ | .kfzteile24.de | 1st party | Exponea - Exponea Bloomreach Engagement - This cookie is used to determine which products the visitor has viewed. This information is used to promote related products and optimize ad-efficiency. | Session |
| _fbp | .kfzteile24.de | 1st party | Facebook - Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers | Session |
| _gtmeec | .kfzteile24.de | 1st party | Stape - Used by Meta to store user data for reuse, enabling more efficient and accurate tracking and targeting. | Session |
kfzteile24.de has 20 GDPR compliance violations with 16 trackers loading before user consent. This level of non-compliance carries meaningful regulatory risk.
Under GDPR Article 83, supervisory authorities can impose fines of up to €20 million or 4% of annual global turnover, whichever is higher. While fines for consent violations typically range from €10,000 to €500,000, larger organisations have faced fines exceeding €50 million.
Implementation of a properly configured Consent Management Platform (CMP) that blocks all non-essential scripts until consent is obtained is the recommended remediation step.
kfzteile24.de scores 56/100 with 20 violation(s) detected. Trackers or cookies were found loading before user consent.
Our scan detected 23 tracker(s) loading before consent, including Exponea by BloomReach, Google Tag Manager (active - loading: tracking cookies), Storage (api.exponea.com).
Yes, 8 cookie(s) were detected before the user interacted with any consent banner.
kfzteile24.de has a GDPR compliance score of 56/100 as of 22 June 2026. A score of 100 means no trackers or cookies load before consent. kfzteile24.de currently has 20 violation(s) affecting its score.
kfzteile24.de 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 verify compliance.