Technical audit · 22.09.2026

delice.ee

Website of the Delice grocery store chain in Estonia

Website of the Delice grocery store chain in Estonia — one recording, three pages, 275 requests, twelve nodes. There is no consent mechanism: a notice 'by using our services you agree' with a single 'Agree' button, and Google's consent mode is not configured. On every page load three counters — the legacy Universal Analytics and two Google Analytics 4 properties — send page views with one and the same persistent client identifier, and on the Russian version of the site that identifier goes to Google Ads remarketing audiences. The cookie document, meanwhile, calls the analytics collection 'anonymous' and does not mention advertising audiences. The browser did not send a DNT header.

Request timeline

+0 ms · navigation
Opening of the home page. Apache/ZoneOS server. No security headers (strict transport, content security policy, frame-embedding denial, referrer policy) are observed on the domain's responses in the recording. The browser did not send a DNT header.
+52…+208 ms · Google tags load immediately
From the markup: gtag/js (+52 ms), Google Maps (+59 ms), reCAPTCHA (+60 ms), the GTM-KF6C4HS container (+81 ms); the container loads Universal Analytics' analytics.js (+208 ms).
+341…+5459 ms · three counters
Universal Analytics UA-59280254-1 — a pageview at +341 ms; Google Analytics 4 G-W0828Y7MLN — a page_view at +5261 ms; G-WWYR9Z1KY4 — a page_view at +5459 ms. All three carry one client identifier 241698612.1790024287 and repeat at +38937…+44066 ms and +79913…+84799 ms.
+79998 ms · Google Ads remarketing audiences
www.google.ee/ads/ga-audiences (t=sr, slf_rd=1, tid=G-WWYR9Z1KY4) — the visitor is passed into Google Ads advertising audiences with the same client identifier, on the /ru/ page.

Declared versus actual

✓ Site cookie document: using the site means consent to cookies unless the browser is set to refuse them — declared
✓ Google Analytics is used to understand how the site is used; it collects data on visitor behaviour 'anonymously', and cookie data is transmitted to Google for statistical reports — declared
✓ How and from which sources visitors reached the site is tracked, to assess the effectiveness of advertising campaigns — declared
✓ Cookie management — through browser settings — declared
✓ Contact — info@abcsupermarkets.eu — declared
✓ The attached TKM Grupp AS data-processing terms (reg. code 10223439, Kaubamaja tn 1, Tallinn; dpo@tkmgrupp.ee) apply to visitors of the tkmgrupp.ee site — declared
+ Google Ads — remarketing audiences (ga-audiences), not named — not declared
+ Universal Analytics and a second GA4 property — three parallel counters with a shared persistent identifier — not declared
+ Google Tag Manager, reCAPTCHA, Google Maps — not named — not declared
+ The absence of a consent mechanism and of Google's consent mode — not declared

Transfer timings

+81 ms www.googletagmanager.com

GTM-KF6C4HS and gtag/js for G-W0828Y7MLN, G-WWYR9Z1KY4.

+341 ms www.google-analytics.com

Universal Analytics UA-59280254-1, pageview; gcd not set.

+5261 ms region1.google-analytics.com

GA4 G-W0828Y7MLN, page_view.

+5459 ms region1.analytics.google.com

GA4 G-WWYR9Z1KY4, page_view.

+79998 ms www.google.ee

ads/ga-audiences — Google Ads advertising audiences, the same client identifier.

Detected trackers

Indicators of GDPR non-compliance


Context

delice.ee is the website of the Delice grocery store chain in Estonia: promotions, news, stores, the Delice Ekspress format, the Partnerkaart loyalty card and a gift card. The site is served by an Apache/ZoneOS server and is available in Estonian, English and Russian.

Processing on the site itself is described by the cookie document ‘Delice Toidupoed veebilehe küpsisepoliitika’ with the contact info@abcsupermarkets.eu; it does not name a controller. Also attached to the material are the general personal-data processing terms of TKM Grupp AS (registration code 10223439, Kaubamaja tn 1, Tallinn), which by their own text apply to visitors of the tkmgrupp.ee site, and a screenshot of the home page with the cookie notice.

The measurement consists of one recording, three navigations: the home page, a repeat visit to the home page and the Russian version /ru/. Two hundred and seventy-five requests, twelve nodes. The recording was made on 22 September 2026.

Who data goes to directly

Google (Universal Analytics, Analytics 4 — two properties, Ads — remarketing audiences, Tag Manager, reCAPTCHA, Maps, Fonts).

Declared versus actual

The cookie document states that using the site means consent to cookies unless the browser is set to refuse them; that Google Analytics collects data on visitor behaviour ‘anonymously’ for statistical reports; that the source of visits is tracked to assess advertising campaigns; and it suggests managing cookies in browser settings.

The measurement shows the following.

There is no consent mechanism, and Google’s consent mode is not configured. A notice at the bottom of the page reads ‘by using our services you agree that we use cookies’, with a single ‘NÕUSTUN’ button — no refusal and no category choice; there is no consent-management platform in the recording. In every Google request the gcd parameter has the form 13l3l3l2l…, where ’l’ means ’not set’, and the gcs parameter is absent — consent mode is not connected at all.

Three counters on every page. The Google Tag Manager container (GTM-KF6C4HS) loads at +81 ms and loads the legacy Universal Analytics, which sends a pageview (UA-59280254-1) at +341 ms. Then Google Analytics 4 sends a page_view to property G-W0828Y7MLN (+5261 ms) and to property G-WWYR9Z1KY4 (+5459 ms). All three repeat on each of the three pages of the session. Universal Analytics, which Google no longer supports, continues to run in parallel with the two GA4 properties.

One persistent identifier — and remarketing. All three counters carry one and the same client identifier 241698612.1790024287 on every page. At +79998 ms, on the Russian version of the site, property G-WWYR9Z1KY4 sends a request to www.google.ee/ads/ga-audiences (t=sr, slf_rd=1) with the same identifier — the visitor is passed into Google Ads advertising audiences. The cookie document’s claim of ‘anonymous’ collection is inconsistent with this, and the document says nothing at all about building advertising audiences.

Recipients and the controller are not disclosed. Of the recipients the cookie document names only Google Analytics; Google Ads, Google Tag Manager, reCAPTCHA and Google Maps are not named. The controller, legal bases, retention periods and supervisory authority are not stated in the cookie document.

Functional nodes: Google reCAPTCHA (www.google.com/recaptcha, www.gstatic.com) loads on every page; Google Maps (maps.google.com, maps.googleapis.com) — a store map; Google Fonts — fonts for the site and the reCAPTCHA widget. In every case the visitor’s IP address is visible to Google.

Proven: there is no consent mechanism. A notice with a single ‘Agree’ button (screenshot); not a single request to a consent-management platform.

Proven: Google’s consent mode is not configured. By the value gcd=13l3l3l2l… and the absence of gcs in every request.

Proven: three counters and remarketing operate without consent. The requests of Universal Analytics, two GA4 properties and ga-audiences with a shared client identifier.

Not proven and not asserted: when the identifier was first set. The timestamp in the client identifier corresponds to 20:58:07 UTC — about two minutes before the start of the recording; the cookie already existed at the start of the session. The recording captures its use, not its creation.

Separately: the browser did not send a DNT header in this recording.

Bounds of observation

The measurement covers three pages of the site. Observation captures the browser’s behaviour, not the internal side of the services: server-side processing and contractual relationships with recipients are not verified by a browser measurement. The legal assessment is made by the competent authority — in Estonia, Andmekaitse Inspektsioon.

The attached TKM Grupp AS data-processing terms, by their own text, apply to visitors of tkmgrupp.ee; whether they extend to delice.ee, and who is the controller of the data of delice.ee, cannot be established from the material.

The file is published redacted under a “lean” profile: cookie values in requests have been removed, the Cookie and Set-Cookie headers stripped; the redaction registry records 108 redactions and a checksum. The property identifiers, consent-mode parameters, client identifier and timings are read from the parameters of the requests themselves. No security headers are observed on the domain’s own responses.

The identification of services relies on domains and address patterns: Universal Analytics — by google-analytics.com/j/collect and UA-59280254-1; GA4 — by /g/collect and the properties G-W0828Y7MLN, G-WWYR9Z1KY4; remarketing — by google.ee/ads/ga-audiences; the container — by GTM-KF6C4HS; reCAPTCHA, the map and the fonts — by their domains. The gcd values are interpreted according to Google’s documentation on consent-mode parameters.

Conclusion

On every page load, without any consent, the Delice store chain’s website sends data to three counters at once — the legacy Universal Analytics and two Google Analytics 4 properties — with one and the same persistent client identifier, and on the Russian version of the site that identifier goes to Google Ads remarketing audiences. There is no consent mechanism: the notice declares use of the site itself to be consent and offers only an ‘Agree’ button; Google’s consent mode is not configured. The cookie document calls the analytics collection ‘anonymous’, says nothing about advertising audiences, names only Google Analytics among the recipients, and states no controller, legal bases, retention periods or supervisory authority.

Remediation: deploy a consent-management platform with an equal-weight reject button and prior blocking, so that Google Analytics, Google Ads remarketing and the other tags neither load nor transmit data before consent; connect Google’s consent mode; disable the legacy Universal Analytics and reduce the number of parallel analytics properties; remove from the cookie document the formula of consent through use of the site and the claim of anonymity, name Google Analytics, Google Ads, Google Tag Manager, reCAPTCHA and Google Maps, and state the controller, legal bases, retention periods and supervisory authority; set security headers on the domain.

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/delice-ee-2026-09-22.har
SHA-256: dfa9c018dc65d5f7744abbc6e7187b18cfc8bf4d096801f0fb50c6d3f46b1ed7
Screenshot
Скриншот интерфейса
Implied-consent notice on the Delice home page: 'by using our services you agree', a single 'NÕUSTUN' button, no refusal · 22.09.2026
Re-check snapshot
Awaiting changes
HAR files are stored on EU infrastructure (Proton Drive). SHA-256 is published for integrity verification.