Scanned on 21 October 2026 at 09:19 UTC
As of , saarland.porsche.de has a GDPR compliance score of 100/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.
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.
saarland.porsche.de has a GDPR compliance score of 100/100.
A perfect score means no trackers, cookies, or third-party scripts that require consent were detected loading before user consent. On the page we scanned, nothing that requires consent ran before the visitor chose.
2 trackers detected loading before user consent:
Legal basis: This violates ePrivacy Directive Article 5(3) and EDPB Guidelines 2/2023. Even an empty container is third-party code that runs in the visitor's browser and contacts the provider's servers. The EDPB's Guidelines 2/2023 state that Article 5(3) of the ePrivacy Directive applies when code instructs the browser to send information, unless an exemption applies. We list it but do not deduct points, because no tracker fired through it.
No tracking cookies set before consent were counted as violations.
saarland.porsche.de scored 100/100. No trackers, tracking cookies, or third-party scripts that require consent were detected loading before user consent on the page we scanned.
Regular re-scanning is recommended so that new code or third-party integrations do not start loading tracking before consent.
This GDPR compliance scan of saarland.porsche.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.
Yes, saarland.porsche.de scores 100/100 for prior consent GDPR compliance. No consent requiring trackers or cookies were detected loading before user consent.
Our scan detected 15 tracker(s) loading before consent, including cdnjs.cloudflare.com, Storyblok, Google Tag Manager (Empty Container).
Yes, 4 cookie(s) were detected before the user interacted with any consent banner.
saarland.porsche.de has a GDPR compliance score of 100/100 as of 21 October 2026. A score of 100 means no trackers or cookies that require consent were detected before consent.
saarland.porsche.de achieves a perfect 100/100 score: no consent-requiring trackers, tracking cookies, or third-party scripts were detected loading before the user gives consent. The scan loads the page from the EU in a fresh browser and does not accept anything, so it measures what runs before a visitor chooses; it cannot see what happens after consent is given.