Technical audit · 01.10.2026

eestiloto.ee

Website of the state lottery operator AS Eesti Loto

The website of the state lottery operator Eesti Loto — 115 requests, and the only things leaving its own domains are the Google Tag Manager container load and requests to the consent platform. A CookieYes banner with three buttons, including 'Keeldu kõigist'; the decision is recorded, and analytics, chat, and advertising wait for consent and do not load after refusal. No violations recorded.

Request timeline

+0 s · entering the homepage
The homepage, with game data from api.eestiloto.ee.
+0.7…+2.3 s · container and consent platform
GTM-MBNCCKKJ and CookieYes. Not a single request to analytics or advertising.
after the decision
No third-party requests: analytics, chat, and advertising never load.

Declared versus actual

✓ Controller — AS Eesti Loto, registration code 10281170; personal data processing principles as of 24.09.2026 — declared
✓ CookieYes banner: 'Kohanda', 'Keeldu kõigist', 'Nõustun kõigiga' — declared
✓ Policy: third-party cookies, such as Google Analytics and Facebook pixel, are used 'anonymously'; data is not transferred to third countries — declared
✓ Right to lodge a complaint with the Andmekaitse Inspektsioon — declared

Transfer timings

+0.7 s www.googletagmanager.com

GTM-MBNCCKKJ; launches no tags.

+0.7 s cdn-cookieyes.com

CookieYes.

+4.6 s log.cookieyes.com

api/v1/consent; content removed.

Detected trackers

Context

eestiloto.ee is the website of AS Eesti Loto (registration code 10281170), the state lottery operator in Estonia. Consent is managed by CookieYes, and the site’s own analytics layer connects services only after consent.

The measurement is a single capture of the homepage. In total, 115 requests. Processing is described by Eesti Loto’s personal data processing principles as of 24 September 2026.

Who receives data directly

Google — only the Tag Manager container load. CookieYes — as the consent platform. No one else.

Declared versus actual

Technically, the site is exemplary. The banner offers three buttons on the first screen: manage, refuse all, accept all. The decision is recorded. The Google Tag Manager container loads but launches no tags. Analytics, chat, and advertising never load — the site clearly holds them back until consent, and they do not appear after refusal.

The policy names the controller and the right to lodge a complaint with the Andmekaitse Inspektsioon.

One remark on the policy text that does not affect the conclusion. It states that third-party cookies — for example, Google Analytics and Facebook pixel — are used “anonymously”, and that data is not transferred to third countries. The Facebook pixel is not anonymous: its purpose is to recognise the visitor. In the capture, neither Google Analytics nor the pixel loaded after refusal, so in practice this did not come into play. But a visitor deciding whether to consent receives an inaccurate description of what consent will switch on.

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

Proven: there are no third-party services before or after the decision. Apart from the GTM container load and the consent platform — not a single external request.

Not established: which decision was recorded. The content of the request to log.cookieyes.com was removed. The absence of third-party services after the decision is consistent with refusal.

Not established: behaviour after full consent. Not tested.

Boundaries of this observation

The measurement covers the homepage. Login, ticket purchase, and games 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.

Legal assessment falls to the competent authority — the Andmekaitse Inspektsioon.

Conclusion

Eesti Loto keeps all third-party services locked away until the visitor consents: an equally weighted refusal on the first screen, and before the decision only the tag container load leaves the site. No violations recorded.

Suggestion: remove from the policy the claim that Google Analytics and Facebook pixel are used “anonymously”, and describe what these services receive 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/eestiloto-ee-2026-10-01.har
SHA-256: c8a7c65326f64a4098b9075609cd70240a41d96ac8459f7f4f8d581a8eed2183
Screenshot
Скриншот интерфейса
The CookieYes banner 'Hindame teie privaatsust': 'Kohanda', 'Keeldu kõigist', 'Nõustun kõigiga' · 01.10.2026
Скриншот интерфейса
'Kohandage nõusolekueelistused': 'Keeldu kõigist', 'Salvesta minu eelistused', 'Nõustun kõigiga' · 01.10.2026
HAR files are stored on EU infrastructure (Proton Drive). SHA-256 is published for integrity verification.