Scanned on 14 July 2026 at 01:58 UTC
As of , rudaauto.com has a GDPR compliance score of 86/100 with 4 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.
Consent platform: Google 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.
Services and cookies that comply with GDPR requirements. No consent needed.
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.
rudaauto.com has a GDPR compliance score of 86/100.
A score above 80 indicates minor issues such as non-essential fonts loaded from external servers or low-risk first-party cookies. The website has some room for improvement but avoids severe violations.
✓ No pre-consent tracking violations detected. All trackers and scripts loaded only after user consent or fall under legitimate interest exemptions.
| Cookie Name | Domain | Type | Service | Duration |
|---|---|---|---|---|
| _pk_ses.53.b425 | www.rudaauto.com | 1st party | Matomo - Matomo session cookie | Session |
| _gid | .rudaauto.com | 1st party | Google Analytics - Google Analytics session identifier | Session |
| _ga | .rudaauto.com | 1st party | Google Analytics - ID used to identify users | Session |
This GDPR compliance scan of rudaauto.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.
| _pk_id.53.b425 | www.rudaauto.com | 1st party | Matomo - Matomo unique visitor ID | Session |
rudaauto.com has minor GDPR compliance issues. While 4 violations were detected, these are typically low-severity items such as external font loading or empty tag containers.
Under GDPR, even minor violations can attract regulatory attention, particularly in jurisdictions with active data protection authorities such as France (CNIL), Ireland (DPC), and Austria (DSB). Addressing these issues proactively reduces legal risk.
The ePrivacy Directive requires consent for all non-essential device access. Even low-severity items like external fonts transfer visitor IP addresses to third-party servers without consent.
rudaauto.com scores 86/100 with 4 violation(s) detected. Trackers or cookies were found loading before user consent.
Our scan detected 4 tracker(s) loading before consent, including jsdelivr.net.
Yes, 4 cookie(s) were detected before the user interacted with any consent banner.
rudaauto.com has a GDPR compliance score of 86/100 as of 14 July 2026. A score of 100 means no trackers or cookies load before consent. rudaauto.com currently has 4 violation(s) affecting its score.
rudaauto.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 verify compliance.