Scanned on 19 October 2026 at 00:09 UTC
As of , citypartner.pl has a GDPR compliance score of 92/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.
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.
citypartner.pl has a GDPR compliance score of 92/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 trackers loading before consent were counted as violations.
| Cookie Name | Domain | Type | Service | Duration |
|---|---|---|---|---|
| locale | citypartner.pl | 1st party | Facebook - This cookie contains the display locale of the last logged in user on this browser. This cookie appears to only be set after the user logs out. The locale cookie has a lifetime of one week. | Session |
citypartner.pl has minor GDPR compliance issues, with 1 violation detected. Items such as external fonts, cookieless Google Consent Mode pings or unrecognised cookies loaded before consent reduced the score.
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.
This GDPR compliance scan of citypartner.pl 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.
citypartner.pl scores 92/100 with 1 violation(s) detected. Trackers or cookies were found loading before user consent.
Yes, 2 cookie(s) were detected before the user interacted with any consent banner.
citypartner.pl has a GDPR compliance score of 92/100 as of 19 October 2026. A score of 100 means no trackers or cookies that require consent were detected before consent. citypartner.pl currently has 1 violation(s) affecting its score.
citypartner.pl 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.