Scanned on 19 October 2026 at 20:36 UTC
As of , adventureridingnz.co.nz has a GDPR compliance score of 20/100 with 13 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: CookieYes
A tag manager loading tracking scripts before the visitor has given 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.
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.
adventureridingnz.co.nz has a GDPR compliance score of 20/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.
7 trackers detected loading before user consent:
Legal basis: This violates GDPR Article 6(1)(a) and ePrivacy Directive Article 5(3). Analytics trackers read information from the visitor's device and send it to the analytics provider together with the visitor's IP address, which can be personal data under the GDPR. The ePrivacy Directive (Article 5(3)) requires consent before that happens unless it is strictly necessary for a service the visitor asked for. Analytics generally does not qualify; only narrowly configured audience measurement can, under national guidance such as the CNIL's.
Legal basis: This violates ePrivacy Directive Article 5(3) and CNIL Decisions SAN-2020-012 and SAN-2025-005. Tag managers that load tracking scripts before the visitor has chosen let those trackers run without consent. The CNIL has fined companies for trackers that ran before consent, including Google (€100 million, December 2020) and SHEIN (€150 million, September 2025), and in March 2025 the Hanover Administrative Court (10 A 5385/22) held that Google Tag Manager itself needs consent under the German law implementing Article 5(3).
This GDPR compliance scan of adventureridingnz.co.nz 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 GDPR Article 6(1)(a) and ePrivacy Directive Article 5(3). Analytics trackers read information from the visitor's device and send it to the analytics provider together with the visitor's IP address, which can be personal data under the GDPR. The ePrivacy Directive (Article 5(3)) requires consent before that happens unless it is strictly necessary for a service the visitor asked for. Analytics generally does not qualify; only narrowly configured audience measurement can, under national guidance such as the CNIL's.
Legal basis: This violates GDPR Article 6(1)(a) and ePrivacy Directive Article 5(3). Analytics trackers read information from the visitor's device and send it to the analytics provider together with the visitor's IP address, which can be personal data under the GDPR. The ePrivacy Directive (Article 5(3)) requires consent before that happens unless it is strictly necessary for a service the visitor asked for. Analytics generally does not qualify; only narrowly configured audience measurement can, under national guidance such as the CNIL's.
| Cookie Name | Domain | Type | Service | Duration |
|---|---|---|---|---|
| sbjs_session | .adventureridingnz.co.nz | 1st party | WooCommerce - The number of page views in this session and the current page path | Session |
| sbjs_first_add | .adventureridingnz.co.nz | 1st party | WooCommerce - Timestamp, referring URL, and entry page for your visitor’s first visit to your store (only applicable if the visitor returns before the session expires) | Session |
| sbjs_migrations | .adventureridingnz.co.nz | 1st party | WooCommerce - Technical data to help with migrations between different versions of the tracking feature | Session |
| _ga | .adventureridingnz.co.nz | 1st party | Google Analytics - ID used to identify users | Session |
| sbjs_current_add | .adventureridingnz.co.nz | 1st party | WooCommerce - Timestamp, referring URL, and entry page for your visitor’s current visit to your store | Session |
| sbjs_current | .adventureridingnz.co.nz | 1st party | WooCommerce - Traffic origin information for the visitor’s current visit to your store | Session |
| sbjs_first | .adventureridingnz.co.nz | 1st party | WooCommerce - Traffic origin information for the visitor’s first visit to your store (only applicable if the visitor returns before the session expires) | Session |
| sbjs_udata | .adventureridingnz.co.nz | 1st party | WooCommerce - Information about the visitor’s user agent, such as IP, the browser, and the device type | Session |
| _ga_V83F0E7B70 | .adventureridingnz.co.nz | 1st party | Google Analytics - ID used to identify users | Session |
adventureridingnz.co.nz has serious GDPR compliance deficiencies with a score of 20/100 and 13 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 the conditions for consent, can be fined up to €20 million or 4% of worldwide annual 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.
adventureridingnz.co.nz scores 20/100 with 13 violation(s) detected. Trackers or cookies were found loading before user consent.
Our scan detected 8 tracker(s) loading before consent, including AddToAny, Google Tag Manager (active - loading: AddToAny, Google Analytics, AddToAny (hidden iframe)), WikiMedia.
Yes, 12 cookie(s) were detected before the user interacted with any consent banner.
adventureridingnz.co.nz has a GDPR compliance score of 20/100 as of 19 October 2026. A score of 100 means no trackers or cookies that require consent were detected before consent. adventureridingnz.co.nz currently has 13 violation(s) affecting its score.
adventureridingnz.co.nz 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.