Scanned on 27 June 2026 at 03:09 UTC· 3 total scans
As of , travelbook.de has a GDPR compliance score of 26/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.
Tracks your browsing behaviour to build a profile and serve targeted ads before you give consent.
Collects usage statistics (pages visited, clicks, session duration) without 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.
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.
travelbook.de has a GDPR compliance score of 26/100.
A score below 50 indicates serious GDPR compliance failures. Multiple high-severity trackers or advertising scripts load before consent, exposing the website to potential fines of up to €20 million or 4% of annual global turnover under GDPR Article 83.
13 trackers detected loading before user consent:
Legal basis: This violates GDPR Article 6(1)(a), ePrivacy Directive Article 5(3), and Austrian DSB Decision (DSB-D155.027, 2022). Analytics trackers process personal data such as IP addresses and browsing behaviour. The Austrian Data Protection Authority ruled in January 2022 that Google Analytics use without consent violates GDPR, as data is transferred to the US without adequate safeguards. The ePrivacy Directive requires prior consent for accessing information on a user's device unless strictly necessary.
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. The CJEU's Planet49 ruling (1 October 2019) confirmed that consent must be active and informed — pre-ticked boxes or implied consent are insufficient. This applies to all cookies and tracking mechanisms used for advertising purposes.
This GDPR compliance scan of travelbook.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.
| Cookie Name | Domain | Type | Service | Duration |
|---|---|---|---|---|
| AMCVS_B21B678254F601E20A4C98A5%40AdobeOrg | .travelbook.de | 1st party | Adobe Audience Manager - The AMCVS cookie serves as a flag indicating that the session has been initialized. Its value is always 1 and discontinues when the session has ended. | Session |
| s_ecid | .travelbook.de | 1st party | Adobe Analytics - This cookie is set by the customer's domain after the AMCV cookie is set by the client. The purpose of this cookie is to allow persistent ID tracking in the 1st-party state and is used as a reference ID if the AMCV cookie has expired. | Session |
| s_cc | .travelbook.de | 1st party | Adobe Analytics - Used to determine if browser of user accepts cookies or not | Session |
| AMCV_B21B678254F601E20A4C98A5%40AdobeOrg | .travelbook.de | 1st party | Adobe Audience Manager - Adobe Experience Cloud uses a cookie to store a unique visitor ID that is used across Experience Cloud Solutions. | Session |
| utag_main | .travelbook.de | 1st party | Tealium - Tealium tag manager data | Session |
travelbook.de has serious GDPR compliance deficiencies with a score of 26/100 and 20 violations detected. Multiple trackers and cookies are loading before user consent, which constitutes a clear breach of the ePrivacy Directive Article 5(3).
This level of non-compliance exposes the website operator to significant regulatory risk. Under GDPR Article 83(5), infringements of the basic principles for processing — including conditions for consent — are subject to administrative fines of up to €20 million or 4% of annual global turnover. Recent enforcement trends show increasing DPA activity across the EU.
Immediate action is recommended: audit all third-party scripts, implement a Consent Management Platform (CMP) that blocks non-essential trackers before consent, and verify compliance through re-scanning.
travelbook.de scores 26/100 with 20 violation(s) detected. Trackers or cookies were found loading before user consent.
Our scan detected 15 tracker(s) loading before consent, including Clever Push, ad-delivery.net, Google Ads.
Yes, 7 cookie(s) were detected before the user interacted with any consent banner.
travelbook.de has a GDPR compliance score of 26/100 as of 27 June 2026. A score of 100 means no trackers or cookies load before consent. travelbook.de currently has 20 violation(s) affecting its score.
travelbook.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.