Technical audit · 28.09.2026

trampolino.ee

Website of the Trampolino trampoline park and entertainment centre in Tallinn

The website of the Trampolino trampoline park — two pages, 318 requests. The CookieScript banner with a refuse button is in place, and Google Analytics respects it. The Meta pixel does not: in the fourth second it sends Meta a page view with a browser identifier, and after the visitor refuses, it loads again and sends another event. The banner itself, meanwhile, declares that using the site already means consent to all cookies.

Request timeline

+0 s · entering the homepage
Redirect to www.trampolino.ee. The site runs on WordPress with WooCommerce.
+1.0…+3.6 s · tags before any choice
GTM-K7WQ5PJH (+1.0 s), CookieScript (+3.0 s), gtag for G-6CNK2GLRM3 (+3.0 s), fbevents.js (+3.1 s), configuration of pixel 667420978407020 (+3.6 s).
+3.9 s · Google in denied mode
A page_view to GA4 with gcs=G100; a service request to pagead2.googlesyndication.com.
+4.1 s · the Meta pixel before any choice
www.facebook.com/tr — PageView and ViewContent with the page address and the _fbp identifier. Then five more events on the homepage (+31…+106 s).
+148 s · the pixel after refusal
The privacy terms page: fbevents.js and the pixel configuration load again, and at +148.7 s an event goes to www.facebook.com/tr.

Declared versus actual

✓ Controller — Reds OÜ, registration code 12106028, Pärnu mnt 139d, Tallinn; info@trampolino.ee — declared
✓ Banner: by using the website, you agree to all cookies in accordance with the cookie policy — declared
✓ CookieScript declaration: _fbp (Meta) — advertising cookies; _ga (Google) — performance cookies — declared
✓ Supervisory authority — the Andmekaitse Inspektsioon — declared
+ The Meta pixel runs before any choice and after refusal, although the declaration itself classifies _fbp as an advertising cookie — not declared

Transfer timings

+3.1 s connect.facebook.net

fbevents.js and the configuration of pixel 667420978407020.

+3.9 s region1.google-analytics.com

page_view, gcs=G100.

+4.1 s www.facebook.com

PageView and ViewContent with the _fbp identifier.

+148.4 s region1.google-analytics.com

gcs=G100, consent mode records the visitor's refusal.

+148.7 s www.facebook.com

A Meta pixel event on the privacy terms page.

Detected trackers

Indicators of GDPR non-compliance

Context

trampolino.ee is the website of the Trampolino trampoline park and entertainment centre in Tallinn. The controller is Reds OÜ (registration code 12106028, Pärnu mnt 139d, Tallinn). The site runs on WordPress with a WooCommerce shop, and consent is managed by CookieScript.

The measurement is a single capture of two pages: the homepage and the privacy terms page. In total, 318 requests. Processing is described by the “Privaatsustingimused” page together with the CookieScript cookie declaration.

Who receives data directly

Meta — through the pixel, before any choice and after refusal. Google — Analytics in denied mode, Tag Manager. CookieScript — as the consent platform.

Declared versus actual

At first glance, the banner is set up correctly: “Nõustu kõigiga” and “Keeldu kõigist” sit side by side and look the same, and categories are switched off. Google Analytics runs in denied mode throughout the capture, and after refusal, consent mode records that denial as updated by the visitor’s decision. The discrepancies lie in the Meta pixel and in the banner’s own text.

First — the Meta pixel does not wait for a choice. The pixel script loads alongside the consent platform, and at +4.1 s PageView and ViewContent go to www.facebook.com/tr with the page address and the browser identifier _fbp. The identifier was created a tenth of a second earlier — at the very moment the pixel loaded. While the visitor reads the banner, five more events are sent from the homepage. Then the visitor refuses. On the next page, Google sees this and complies. The Meta pixel loads again and sends one more event. The site’s own cookie declaration, meanwhile, classifies _fbp as an advertising cookie.

Second — the banner itself says consent has already been given. Above the buttons it reads: by using the website, you agree to all cookies. If that were true, the refuse button would mean nothing. If not, the text is misleading. In this capture, the Meta pixel behaves exactly as the text describes: as if consent had been obtained by the mere act of opening the site.

Proven: the Meta pixel sends events before any choice. PageView and ViewContent at +4.1 s with the _fbp identifier.

Proven: a refusal took place. On the second page, Google consent mode transmits a denial updated by the visitor’s decision. On the first page, the denial was only the default.

Proven: the Meta pixel runs after refusal. The script loads again, with an event at +148.7 s.

Proven: the banner declares use of the site to be consent. The banner text in screenshots 2 and 3.

Not established: the exact moment of refusal. CookieScript does not send the decision to a server. The refusal is established from Google consent mode on the second page. The five Meta events on the homepage (+31…+106 s) are therefore classed as “before or during the choice”, not “after refusal”.

Not established: the content of the Meta events sent via POST. The bodies of these requests were removed during cleaning.

Boundaries of this observation

The measurement covers the homepage and the privacy terms page. Booking and purchasing were not examined. The observation records browser behavior, not server-side processing. The file has been published cleaned: Cookie headers and POST request bodies were removed. The parameters of Meta events transmitted in the request address are preserved.

Legal assessment falls to the competent authority — the Andmekaitse Inspektsioon, which is named in the terms themselves.

Conclusion

Trampolino has installed a proper banner with a refuse button, and Google obeys it. The Meta pixel does not: it sends a page view with a browser identifier in the fourth second and keeps working after refusal. The banner text declaring mere use of the site to be consent describes, in this capture, not a breach of the rules on paper but the pixel’s actual behaviour.

Remedy: bring the Meta pixel under CookieScript — do not load it without consent to advertising cookies, and stop sending events after refusal; remove the sentence about consent through use of the site from the banner.

Evidence

How to verify: download the file and compute its checksum — sha256sum file.har (Linux, macOS) or certutil -hashfile file.har SHA256 (Windows); it must match the one shown. The conclusions apply to the scope of this measurement — see the limitations of the method.

Original (audit)
HAR file: ee/trampolino-ee-2026-09-28.har
SHA-256: da7762b4b4c96b6716751d74b34a15fd521d0b3d1df02026eb114122729e0108
Screenshot
Скриншот интерфейса
The compact CookieScript banner on the homepage: 'Nõustu kõigiga' and 'Keeldu kõigist', categories switched off · 28.09.2026
Скриншот интерфейса
The expanded banner: 'Meie veebisaiti kasutades nõustute … kõikide küpsistega', cookie categories · 28.09.2026
Скриншот интерфейса
The 'Küpsiste kasutamise avaldus' tab with the same text about consent through use of the site · 28.09.2026
Re-check snapshot
Awaiting changes
HAR files are stored on EU infrastructure (Proton Drive). SHA-256 is published for integrity verification.