RU EN
www.
Technical audit · 2026-06-06

save24.ee

A Lithuanian Cosmetics and Household Goods Online Store — Estonian Branch
EE

Policy changed — see what exactly · 2026-07-11 →

A Lithuanian store on the Estonian market. Three trackers fire 330 ms before the banner. The HAR records a 'Reject' click — by which point GA, Google Ads, and Facebook have already transmitted data.

Timeline of the leak

+182 ms · before the banner
Optimizely (cdn.optimizely.com) — A/B testing. 331 ms before the banner.
+183 ms · before the banner
DigitalGenius AI chat (chat.digitalgenius.com) and Cloudflare Insights — simultaneously, 330 ms before the banner.
+331 ms · before the banner
GTM (GTM-NGN859N) — loads 182 ms before cookie-script.
+513 ms · banner
Cookie-script loads. The banner appears, but the trackers are already running.
+629 ms
Facebook Pixel (fbevents.js, ID: 557715056315793) — loads after the banner.
+1007 ms
Facebook PageView — the page URL goes to Meta. Before the user clicks any button.
+2129 ms
GA4 collect — data goes to Google. Before any interaction with the banner.
+2138 ms
Google Ads (4 requests) — page_view and view_item_list go to Google. Before any interaction.
+51559 ms · reject
The user clicks 'Reject' — cookie-script records action=reject. All the data has already been transmitted.

Declared versus actual

+ Optimizely (cdn.optimizely.com) — не заявлен
+ DigitalGenius (chat.digitalgenius.com, flow-server.eu.dgdeepai.com) — не заявлен
+ Cloudflare Insights — не заявлен
+ Google Tag Manager, GA4, Google Ads — не заявлен
+ Facebook Pixel — не заявлен

Transfer timings

+182 ms cdn.optimizely.com

A/B testing. USA

+183 ms chat.digitalgenius.com

AI chat init.js

+183 ms static.cloudflareinsights.com

Cloudflare beacon

+331 ms www.googletagmanager.com

GTM-NGN859N

+513 ms cdn.cookie-script.com

The banner appears

+1007 ms www.facebook.com

PageView — URL to Meta

+2129 ms region1.google-analytics.com

GA4 collect

+51559 ms consent.cookie-script.com

The user clicked Reject

Detected trackers

Indicators of GDPR non-compliance

Context

save24.ee is the Estonian site of the Lithuanian company MB “Savelita” (Marijampolė, Lithuania). An online store for cosmetics, household chemicals, and home goods. The privacy policy is written in Estonian, but names the Lithuanian data protection inspectorate as the regulator — incorrect for Estonian users, whose regulator is AKI. HAR: 118 requests, 12 domains.

Reject is recorded — the data has already gone out

The HAR captures the full session cycle: the page loading, the banner appearing, and at the end — a click on the “Reject” button (action=reject, +51559 ms). This is a rare case where the HAR shows the user’s actual interaction with the banner.

The problem is that by the time “Reject” is clicked, all the data has already been transmitted: a GA4 collect fired at +2129 ms, Google Ads made four requests at +2138–2140 ms, and a Facebook PageView fired at +1007 ms. Cookie-script technically works — it records the fact of the rejection — but it does not block trackers until consent is obtained.

Trackers before the banner

Optimizely (+182 ms), DigitalGenius (+183 ms), and Cloudflare Insights (+183 ms) fire 330 milliseconds before the banner appears. GTM — 182 ms before. This means A/B testing and the AI chat are initialized before the user even sees the banner.

DigitalGenius — partially EU servers

DigitalGenius is interesting: chat.digitalgenius.com — a CDN, likely in the USA. But flow-server.eu.dgdeepai.com is clearly an EU instance (the .eu suffix). The company took care to use European infrastructure for the main server, but the script CDN remains external.

The policy — not tailored for the Estonian market

The privacy policy is written under Lithuanian law: it names “Leedu Andmekaitse Inspektsioon” (the Lithuanian data protection inspectorate) as the regulator. For Estonian users visiting save24.ee, the regulator should be AKI. This isn’t just a formality — a user has the right to know which authority to file a complaint with. None of the actual data recipients (Google, Facebook, Optimizely, DigitalGenius) is named in the policy.

Conclusion

Cookie-script is in place, and rejection works — but the load order does not meet the principle of consent before processing. Three trackers fire before the banner, the rest before any interaction with it. The HAR shows this plainly: the user clicked “Reject” after 51 seconds, while their data had already gone to Google, Facebook, and Cloudflare 2 seconds after the page loaded.

Evidence
Original (audit)
HAR file: ee/save24-ee-2026-06-06.har
SHA-256: 10dff92a85e87b30729753d6ab48ea46235f6326a97242543e4a069f561b97bd
Re-check snapshot
Awaiting changes
HAR files are stored on EU infrastructure (Proton Drive). SHA-256 is published for integrity verification.
IMPORTANT: before filing a complaint with the regulator, first contact the company directly and give it 30 days to respond. Without this step the regulator may reject the complaint. Details and a template letter to the company are in the Methodology.
Ready-to-send complaint letter

Where to file: Estonian Data Protection Inspectorate (AKI) — write to info@aki.ee

Important: AKI only handles submissions in Estonian. Translate the letter before sending.

To: Estonian Data Protection Inspectorate (AKI)
From: [Your name], [contact email]

1. Subject of the complaint
I am filing a complaint regarding the processing of my personal data by the website save24.ee.

2. Circumstances
I visited the website save24.ee and found indications that the processing of my personal data does not comply with the GDPR. The technical analysis published on gdpru.eu on 6 June 2026 (open methodology, reproducible measurements) documents the following indications:

1) Optimizely (+182 ms), DigitalGenius (+183 ms), and Cloudflare Insights (+183 ms) fire 330 ms before the cookie-script banner (+513 ms). GTM (+331 ms) fires 182 ms before the banner. Facebook Pixel loads at +629 ms and sends a PageView at +1007 ms — after the banner, but before any interaction with it.

2) The cookie-script banner loads at +513 ms. The HAR records the user clicking 'Reject' at +51559 ms. Meanwhile, a GA collect fired at +2129 ms, Google Ads at +2138 ms, and a Facebook PageView at +1007 ms — all before the reject click. Cookie-script does not block trackers until consent.

3) The privacy policy is written under Lithuanian law (naming the Lithuanian data protection inspectorate as the regulator) and does not name a single specific data recipient. Optimizely, DigitalGenius, Cloudflare, Facebook, and Google are not declared.

4) Google, Facebook, Optimizely, and Cloudflare — servers in the USA. No transfer mechanism is stated. The policy is written under Lithuanian law — for Estonian users, the regulator should be AKI, not the Lithuanian inspectorate.

Full technical documentation is published at: https://gdpru.eu/en/audits/ee-save24-ee/

3. Provisions violated
GDPR Art. 6(1), Art. 5(1)(a); GDPR Art. 7; GDPR Art. 13(1)(e); GDPR Art. 13(1)(f), Chapter V

4. Request
I request that you investigate the violations described and apply the measures provided for in Article 58(2) GDPR.

5. Attachments
The full evidence base — the HAR file, its SHA-256 checksum and the quotation from the site's privacy policy documenting the stated contradiction — is published and verifiable at the link in point 2 above.

[Date]                                    [Signature / name]