Technical audit · 18.10.2026

merko.ee

Website of the construction group and housing developer Merko

The website of the Merko construction group — a click from a Google ad to a project page and then to the homepage, 252 requests. The capture contains no analytics or advertising: Google Tag Manager containers load, but no tag fires. But in the CookieScript banner all optional categories are ticked in advance, statistics are described in the documents as anonymous although the declaration itself names identifiers, and Sentry and Google Maps are named nowhere.

Request timeline

+0…+43.1 s · Google search
Requests from the Google search page itself. At +43.1 s — a click on an ad link carrying a gclid click identifier.
+43.1…+45.7 s · project page
Navigation with campaign tags. CookieScript, GTM-5G86ZN, Google Maps, Google Fonts, jQuery UI (+44.3…+45.7 s).
+63.5…+75.0 s · homepage
Navigation to the homepage from the search results. GTM-NR8B8CM7 and CookieScript (+64.5…+65.2 s), three submissions to Sentry (+66.4, +69.4 and +75.0 s — the last about 260 KB).

Declared versus actual

✓ Controller — OÜ Merko Kodud or another company of the AS Merko Ehitus group; merko@merko.ee, Pärnu mnt 141, Tallinn — declared
✓ CookieScript banner: 'Nõustu kõigiga', 'Keeldu kõigist'; optional categories ticked — declared
✓ Cookie declaration: Google Analytics, Google Ads, Microsoft Clarity and Bing, Adform, Meta — in the performance and advertising categories — declared
✓ Principles: legal bases — contract, law, legitimate interest, consent; retention periods; transfers outside the EEA — with standard contractual clauses; statistics — on anonymised data — declared
✓ Supervisory authority — Andmekaitse Inspektsioon — declared
+ Sentry — not declared
+ Google Maps — not declared
+ The right to data portability — not declared
+ Optional categories unticked by default — not declared

Transfer timings

+44.3 s maps.googleapis.com

Google Maps on the project page; not named in the documents.

+44.5 s www.googletagmanager.com

GTM-5G86ZN; no tag fired.

+66.4 s o4510306345549824.ingest.de.sentry.io

Sentry, first submission from the homepage.

+75.0 s o4510306345549824.ingest.de.sentry.io

Sentry, a submission of about 260 KB; content removed in cleaning.

Detected trackers

Indicators of GDPR non-compliance

Context

merko.ee is the website of the Merko construction group: construction, Merko Kodud housing projects and commercial premises. The controller is OÜ Merko Kodud or another company of the AS Merko Ehitus group. Consent is managed by CookieScript.

The measurement is a single capture: a Google search, a click on an ad link to the Uus-Karlowa project page, a return to the search and a visit to the homepage. In total, 252 requests, 16 of them from the Google search page itself.

Who receives data directly

Google — Tag Manager with no fired tags, Maps, Fonts, libraries. Sentry — error monitoring. CookieScript — as the consent platform.

Declared versus actual

First — the boxes are ticked for the visitor. In the CookieScript banner, all four optional categories are ticked before any choice. The “Keeldu kõigist” button is nevertheless present on the first layer.

Second — the traffic is cleaner than the declaration. The cookie declaration lists Google Analytics, Google Ads, Microsoft Clarity, Adform and Meta. None of them fires in the capture: the Google Tag Manager containers load but launch no tags.

Third — “anonymous” statistics. The principles and the declaration call statistics anonymous, while the declaration itself describes Google and Microsoft identifiers designed to recognise users.

Fourth — Sentry and Google Maps are not named. Sentry receives three submissions from the homepage, the last of about 260 KB. Google Maps loads on the project page before any choice. Neither is mentioned in the documents. Rights are listed without the right to data portability.

Proven: there is a refusal on the first layer. The “Keeldu kõigist” button on screenshot 1.

Proven: optional categories are ticked in advance. Screenshots 1 and 2.

Proven: analytics and advertising do not fire in the capture. Not a single request to Google Analytics, Clarity, Adform or Meta.

Proven: Sentry and Google Maps are not named. A search of the saved principles and declaration.

Not established: whether a decision was made in the banner. CookieScript does not send the decision to a server, and there is no Google consent mode in the capture.

Not established: what the Sentry submission of about 260 KB contains. Request bodies were removed; by its size it may be a session recording rather than just an error report.

Boundaries of this observation

The measurement covers the Uus-Karlowa project page and the homepage. The capture starts on the Google results page: its own requests, including the recording of the ad click on www.googleadservices.com, are made by Google itself and are not attributed to the site. The observation records browser behavior, not server-side processing. The file has been published cleaned: Cookie headers and POST bodies were removed.

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

Conclusion

On the Merko website, neither analytics nor advertising runs in the capture, and there is a refusal on the first layer. The violations lie in the banner configuration and the documents: all optional categories are ticked in advance, statistics are described as anonymous despite explicit identifiers, Sentry and Google Maps are not named, and rights are listed incompletely.

Remedy: untick optional categories by default in CookieScript; remove the claims of anonymous statistics; name Sentry and Google Maps in the principles and the declaration; add the right to data portability. Suggestion: load the Google map on the project page after consent.

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/merko-ee-2026-10-18.har
SHA-256: 4f4586f609b856cbbbbdfb015a1940acf0912716798398e58a4127af32e5fc26
Screenshot
Скриншот интерфейса
CookieScript banner on the homepage: 'Nõustu kõigiga' and 'Keeldu kõigist'; optional categories ticked by default · 18.10.2026
Скриншот интерфейса
Banner details: the same ticked categories and the table of necessary cookies · 18.10.2026
Re-check snapshot
Awaiting changes
HAR files are stored on EU infrastructure (Proton Drive). SHA-256 is published for integrity verification.