Technical audit · 06.06.2026

save24.ee

A Lithuanian Cosmetics and Household Goods Online Store — Estonian Branch

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.

Request timeline

+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.

+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) — not declared

+ DigitalGenius (chat.digitalgenius.com, flow-server.eu.dgdeepai.com) — not declared

+ Cloudflare Insights — not declared

+ Google Tag Manager, GA4, Google Ads — not declared

+ Facebook Pixel — not declared

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

Optimizely (cdn.optimizely.com)
DigitalGenius AI chat (chat.digitalgenius.com)
Cloudflare Insights (static.cloudflareinsights.com)
Google Tag Manager (GTM-NGN859N)
Google Analytics GA4 (G-2XBQ2LE7HV)
Google Ads (AW-345546298, pagead2.googlesyndication.com)
Facebook Pixel (ID: 557715056315793)
DigitalGenius AI (flow-server.eu.dgdeepai.com)
Cookie-script (cdn.cookie-script.com)

Indicators of GDPR non-compliance

GDPR Art. 6(1), Art. 5(1)(a)
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.
GDPR Art. 7
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.
GDPR Art. 13(1)(e)
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.
GDPR Art. 13(1)(f), Chapter V
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.

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.

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

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/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.

Want a response from the company about this audit? → Open the tool

Fill in once — it will be inserted into every letter below:

Filing date:

All fields are required to print the document — this is a formal requirement of the letter itself (the particulars of an official submission), not data collection: nothing is sent or saved anywhere, it all stays in your browser and disappears when you close the page. See the methodology for details.

Step 1. Data access request (GDPR Art. 15)

Send this letter directly to the company first — before contacting the regulator it has the right to respond (GDPR Art. 12(3) — 30 days).

Тема: Запрос доступа к персональным данным (ст. 15 GDPR) — save24.ee

Кому: [укажите адрес компании — DPO / поддержка / юридический отдел]
От: [Ваше имя], [контактный email]

Прошу предоставить доступ к моим персональным данным, обрабатываемым в связи с использованием сайта save24.ee.

1. Категории данных и цели обработки (ст. 15(1)(a)-(c))
На основании независимого технического анализа сайта прошу подтвердить и подробно раскрыть следующие категории обработки:

1) Optimizely (+182 мс), DigitalGenius (+183 мс) и Cloudflare Insights (+183 мс) запускаются за 330 мс до баннера cookie-script (+513 мс). GTM (+331 мс) — за 182 мс до баннера. Facebook Pixel загружается на +629 мс и отправляет PageView на +1007 мс — после баннера, но до взаимодействия с ним.

2) Баннер cookie-script загружается на +513 мс. HAR фиксирует что пользователь нажал «Отклонить» на +51559 мс. При этом GA collect ушёл на +2129 мс, Google Ads — на +2138 мс, Facebook PageView — на +1007 мс — всё до нажатия reject. Cookie-script не блокирует трекеры до согласия.

3) Политика конфиденциальности написана по литовскому праву (регулятор — Литовская инспекция по защите данных), не упоминает ни одного конкретного получателя данных. Optimizely, DigitalGenius, Cloudflare, Facebook, Google не задекларированы.

4) Google, Facebook, Optimizely, Cloudflare — серверы в США. Механизм передачи не указан. Политика написана под литовское право — для эстонских пользователей регулятором должна быть AKI, а не Литовская инспекция.


2. Получатели, сроки хранения и передача за пределы ЕЭЗ (ст. 15(1)(c)-(d), 46)
Прошу также указать полный список третьих лиц-получателей, применимые сроки хранения по каждой категории и правовые основания передачи данных за пределы ЕЭЗ, если таковая происходит. Полный технический разбор с доказательствами (сохранённый сетевой журнал, контрольная сумма SHA-256) опубликован по адресу: https://gdpru.eu/en/audits/ee-save24-ee/

3. Автоматизированная обработка и профилирование (ст. 15(1)(h))
Прошу сообщить, применяется ли в отношении меня автоматизированное принятие решений или профилирование, и если да — раскрыть логику такой обработки.

С уважением,

[Ваше имя]
[контактный email]
[Страна]


[Дата]

Subject: Data access request (GDPR Art. 15) — save24.ee

To: [insert the company's address — DPO / support / legal department]
From: [Your name], [contact email]

I request access to my personal data processed in connection with the website save24.ee.

1. Categories of data and purposes of processing (Art. 15(1)(a)-(c))
Based on an independent technical analysis of the site, I request confirmation and detailed disclosure of the following categories of processing:

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.

2. Recipients, retention periods, and transfers outside the EEA (Art. 15(1)(c)-(d), 46)
I also request the full list of third-party recipients, the applicable retention period for each category, and the legal basis for any transfer of data outside the EEA. The full technical audit with evidence (saved network log, SHA-256 checksum) is published at: https://gdpru.eu/en/audits/ee-save24-ee/

3. Automated processing and profiling (Art. 15(1)(h))
Please state whether I am subject to automated decision-making or profiling, and if so, disclose the logic involved.

Sincerely,

[Your name]
[contact email]
[Country]

[Date]

Teema: Isikuandmetele juurdepääsu taotlus (IKÜM art 15) — save24.ee

Kellele: [märkige ettevõtte aadress — DPO / tugi / juriidiline osakond]
Kellelt: [Teie nimi], [kontakt-e-post]

Palun anda mulle juurdepääs minu isikuandmetele, mida töödeldakse seoses veebisaidi save24.ee kasutamisega.

1. Andmekategooriad ja töötlemise eesmärgid (IKÜM art 15(1)(a)-(c))
Sõltumatu tehnilise analüüsi põhjal palun kinnitada ja üksikasjalikult avaldada järgmised töötlemiskategooriad:

1) Optimaalselt (+182 ms), DigitalGenius (+183 ms) ja Cloudflare Insights (+183 ms) töötavad 330 ms enne küpsiseskripti bännerit (+513 ms). GTM (+331 ms) - 182 ms enne bännerit. Facebook Pixel laadib +629 ms ja saadab PageView +1007 ms - pärast bännerit, kuid enne sellega suhtlemist.

2) Küpsiste skripti bänner laaditakse +513 ms-le. HAR tuvastab, et kasutaja on klõpsanud +51559 ms-l "Deflect". GA kogub vasakule +2129 ms, Google Ads +2138 ms, Facebook PageView +1007 ms - kõik enne klõpsates tagasi lükata. Cookie-Script ei blokeeri jälgijaid enne nõusoleku saamist.

3) Privaatsuspoliitika on koostatud Leedu õiguse alusel (regulaatoriks on Leedu Andmekaitse Inspektsioon), ei mainita ühtegi konkreetset andmete saajat. Optimizely, DigitalGenius, Cloudflare, Facebook, Google ei deklareerita.

4) Google, Facebook, Optimizely, Cloudflare on Ameerika Ühendriikide serverid. Ülekandemehhanism ei ole määratletud. Poliitika on kirjutatud Leedu seaduste järgi - Eesti kasutajate jaoks peaks reguleerijaks olema AKI, mitte Leedu Inspektsioon.


2. Vastuvõtjad, säilitustähtajad ja edastamine väljapoole EMP-d (IKÜM art 15(1)(c)-(d), 46)
Palun samuti esitada täielik loetelu kolmandatest isikutest vastuvõtjatest, iga kategooria puhul kohaldatavad säilitustähtajad ning andmete EMP-välisele edastamisele kohaldatav õiguslik alus, kui selline edastamine toimub. Täielik tehniline analüüs koos tõenditega (salvestatud võrgulogi, SHA-256 kontrollsumma) on avaldatud aadressil: https://gdpru.eu/en/audits/ee-save24-ee/

3. Automatiseeritud töötlemine ja profiilianalüüs (IKÜM art 15(1)(h))
Palun teatada, kas minu suhtes kohaldatakse automatiseeritud otsuste tegemist või profiilianalüüsi, ning kui jah, siis avaldada selle loogika.

Lugupidamisega,

[Teie nimi]
[kontakt-e-post]
[Riik]


[Kuupäev]

30 days have passed since contacting the company with no response? → Show the regulator complaint letter

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.

The regulator reviews complaints in its national language. There is an officially translated template from the European Data Protection Board (EDPB) — you can use it instead of or alongside this letter: Official EDPB complaint form (PDF, your language)

Тема: Жалоба на обработку персональных данных — save24.ee

1. Предмет жалобы
Я подаю жалобу в отношении обработки моих персональных данных сайтом save24.ee.

2. Обстоятельства
Я посетил сайт save24.ee и обнаружил признаки несоответствия обработки моих персональных данных требованиям GDPR. Технический разбор, опубликованный на gdpru.eu 06.06.2026 (открытая методология, воспроизводимые измерения), документирует следующие признаки:

1) Optimizely (+182 мс), DigitalGenius (+183 мс) и Cloudflare Insights (+183 мс) запускаются за 330 мс до баннера cookie-script (+513 мс). GTM (+331 мс) — за 182 мс до баннера. Facebook Pixel загружается на +629 мс и отправляет PageView на +1007 мс — после баннера, но до взаимодействия с ним.

2) Баннер cookie-script загружается на +513 мс. HAR фиксирует что пользователь нажал «Отклонить» на +51559 мс. При этом GA collect ушёл на +2129 мс, Google Ads — на +2138 мс, Facebook PageView — на +1007 мс — всё до нажатия reject. Cookie-script не блокирует трекеры до согласия.

3) Политика конфиденциальности написана по литовскому праву (регулятор — Литовская инспекция по защите данных), не упоминает ни одного конкретного получателя данных. Optimizely, DigitalGenius, Cloudflare, Facebook, Google не задекларированы.

4) Google, Facebook, Optimizely, Cloudflare — серверы в США. Механизм передачи не указан. Политика написана под литовское право — для эстонских пользователей регулятором должна быть AKI, а не Литовская инспекция.

Полная техническая документация опубликована по адресу: https://gdpru.eu/en/audits/ee-save24-ee/

3. Положения GDPR, соблюдение которых прошу проверить
GDPR Art. 6(1), Art. 5(1)(a); GDPR Art. 7; GDPR Art. 13(1)(e); GDPR Art. 13(1)(f), Chapter V

4. Требование
Прошу проверить изложенные обстоятельства и, если несоответствие подтвердится, принять меры, предусмотренные статьёй 58(2) GDPR.

5. Приложения
Полная доказательная база — HAR-файл, контрольная сумма SHA-256 и цитата из политики конфиденциальности сайта, документирующая указанное противоречие — опубликована и проверяема по ссылке в пункте 2 выше.

С уважением,

[Ваше имя]
[контактный email]
[Страна]

[Дата]

Subject: Complaint regarding personal data processing — save24.ee

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. GDPR provisions I ask you to examine
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 examine the circumstances described and, if non-compliance is confirmed, 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.

Sincerely,

[Your name]
[contact email]
[Country]


[Date]

1. Kaebuse ese
Esitan kaebuse seoses minu isikuandmete töötlemisega veebisaidil save24.ee.

2. Asjaolud
Külastasin veebisaiti save24.ee ja tuvastasin märke sellest, et minu isikuandmete töötlemine ei vasta isikuandmete kaitse üldmääruse (IKÜM) nõuetele. Tehniline analüüs, mis on avaldatud aadressil gdpru.eu 06.06.2026 (avatud metoodika, korratavad mõõtmised), dokumenteerib järgmist:

1) Optimaalselt (+182 ms), DigitalGenius (+183 ms) ja Cloudflare Insights (+183 ms) töötavad 330 ms enne küpsiseskripti bännerit (+513 ms). GTM (+331 ms) - 182 ms enne bännerit. Facebook Pixel laadib +629 ms ja saadab PageView +1007 ms - pärast bännerit, kuid enne sellega suhtlemist.

2) Küpsiste skripti bänner laaditakse +513 ms-le. HAR tuvastab, et kasutaja on klõpsanud +51559 ms-l "Deflect". GA kogub vasakule +2129 ms, Google Ads +2138 ms, Facebook PageView +1007 ms - kõik enne klõpsates tagasi lükata. Cookie-Script ei blokeeri jälgijaid enne nõusoleku saamist.

3) Privaatsuspoliitika on koostatud Leedu õiguse alusel (regulaatoriks on Leedu Andmekaitse Inspektsioon), ei mainita ühtegi konkreetset andmete saajat. Optimizely, DigitalGenius, Cloudflare, Facebook, Google ei deklareerita.

4) Google, Facebook, Optimizely, Cloudflare on Ameerika Ühendriikide serverid. Ülekandemehhanism ei ole määratletud. Poliitika on kirjutatud Leedu seaduste järgi - Eesti kasutajate jaoks peaks reguleerijaks olema AKI, mitte Leedu Inspektsioon.

Täielik tehniline dokumentatsioon on avaldatud aadressil: https://gdpru.eu/en/audits/ee-save24-ee/

3. Sätted, mille järgimist palun kontrollida
GDPR artikli 6 lõige 1, artikli 5 lõike 1 punkt a; GDPR artikkel 7; GDPR artikli 13 lõike 1 punkt e; GDPR artikli 13 lõike 1 punkt f, V peatükk

4. Nõue
Palun kontrollida kirjeldatud asjaolusid ja mittevastavuse kinnitamisel kohaldada IKÜM artikli 58 lõikes 2 ette nähtud meetmeid.

5. Lisad
Täielik tõendusmaterjal — HAR-fail, kontrollsumma SHA-256 ning veebisaidi privaatsuspoliitika tsitaat, mis dokumenteerib nimetatud vastuolu — on avaldatud ja kontrollitav punktis 2 viidatud lingil.

Lugupidamisega,

[Teie nimi]
[kontakt-e-post]
[Riik]

[Kuupäev]