An Estonian perfume store with 24 external domains. Google reCAPTCHA launches at +51 ms, and Klaviyo, with 14 requests, at +1644 ms. No consent banner is recorded in the HAR — only internal GDPR-related requests to GraphQL.
Timeline of the leak
Declared versus actual
Transfer timings
reCAPTCHA, recaptcha__ru.js. US
Personalization, 3 GraphQL requests
Klaviyo tracking, 14 requests
GTM-N8Q799
Facebook Pixel fbevents.js
leadtag.js — unidentified tracker
Conversion pixel
PageView — page URL to Meta
Detected trackers
- Google reCAPTCHA Enterprise (www.google.com)
- Nosto (api.nosto.com) — personalization
- Klaviyo (static.klaviyo.com) — email marketing
- Google Tag Manager (GTM-N8Q799)
- Google Analytics GA4 (G-BMZWHV927B)
- Google Ads / DoubleClick (googleads.g.doubleclick.net)
- Facebook Pixel (ID: 457353994820689)
- kk-resources.com (leadtag.js)
- Adobe Typekit (use.typekit.net)
- Google Fonts
- Instagram CDN (scontent-hel3-1.cdninstagram.com)
- Cloudfront CDN (d3k81ch9hvuctc.cloudfront.net)
Indicators of GDPR non-compliance
- GDPR Art. 6(1), Art. 5(1)(a)Google reCAPTCHA (+51 ms), Nosto (+703 ms), Klaviyo (+1644 ms), and GTM (+2575 ms) launch before any consent banner appears. The site makes a GDPR-related request to its own GraphQL endpoint at +1659 ms — but this is not a banner, it's an internal configuration check. No banner ever appears in the HAR.
- GDPR Art. 7No consent banner appears in the HAR. Requests to /graphql?query=gdprCookieData indicate the site queries GDPR settings — but no actual consent banner was recorded. The Facebook Pixel sends a PageView at +4660 ms.
- GDPR Art. 13(1)(e)The policy is a Cookie Policy that does not name specific recipients. Nosto, Klaviyo, kk-resources.com, Adobe Typekit, and Instagram CDN are not mentioned. Only Google Analytics is mentioned, in general terms.
- GDPR Art. 13(1)(f), Chapter VGoogle (US), Facebook (US), Klaviyo (US), Nosto (Finland/US), Adobe Typekit (US), kk-resources.com (unknown jurisdiction) — a data-transfer mechanism is not specified for any of them.
Context
loverte.com is an Estonian online perfume and cosmetics store, operated by Loverte OÜ. The site runs on Magento/Adobe Commerce and serves the Estonian market (/et/). HAR: 310 requests, 24 domains. The session was captured on the perfume catalog page.
The banner — code exists, no banner appears
The site makes requests to its own GraphQL endpoint with the parameter gdprCookieData — at +1659, +4062, and +4793 ms. This means GDPR-related logic exists in the code. But no actual consent banner is recorded in the HAR — not a single request to an external CMP (Cookiebot, Usercentrics, privacy-center, or similar). By the time these requests occur, reCAPTCHA, Nosto, Klaviyo, and GTM had already been running.
kk-resources.com — an unfamiliar recipient
s.kk-resources.com/leadtag.js (+3987 ms) — this domain is not mentioned in the policy and is not a known public service. Judging by its name (leadtag), this is a lead-generation tracker. Its jurisdiction and operator are unknown from the HAR.
Klaviyo — 14 requests
Klaviyo launches at +1644 ms and generates 14 requests during the session: script loading, company font configuration, full forms, geo-IP detection. This is an email-marketing platform that builds a visitor profile before the visitor has purchased or subscribed to anything.
Instagram CDN
The Instagram feed on the homepage loads images from Meta’s servers (scontent-hel3-1.cdninstagram.com) — the user’s IP is transmitted to Meta (US) on every visit to the homepage. Images with -hel3- in the domain point to a Helsinki CDN node, but the data still passes through Meta’s infrastructure.
The policy — only a Cookie Policy
The document describes cookie types (session, functional, analytics, marketing) without naming specific recipients. It mentions Google Analytics in general terms. Nosto, Klaviyo, Facebook Pixel, Adobe Typekit, and kk-resources.com — not a single specific name is given. Under Art. 13(1)(e), the user must know all recipients of their data.
Conclusion
310 requests, 24 domains, no consent banner recorded. reCAPTCHA starts at the 51st millisecond. Klaviyo begins building a visitor profile from the 1644th millisecond. Facebook receives a PageView with the page URL. The policy describes cookie categories but names not a single specific recipient. This is a typical picture for an average Estonian online store — much like euronics.ee earlier in the series, just with a different vendor mix.
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 loverte.com. 2. Circumstances I visited the website loverte.com 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) Google reCAPTCHA (+51 ms), Nosto (+703 ms), Klaviyo (+1644 ms), and GTM (+2575 ms) launch before any consent banner appears. The site makes a GDPR-related request to its own GraphQL endpoint at +1659 ms — but this is not a banner, it's an internal configuration check. No banner ever appears in the HAR. 2) No consent banner appears in the HAR. Requests to /graphql?query=gdprCookieData indicate the site queries GDPR settings — but no actual consent banner was recorded. The Facebook Pixel sends a PageView at +4660 ms. 3) The policy is a Cookie Policy that does not name specific recipients. Nosto, Klaviyo, kk-resources.com, Adobe Typekit, and Instagram CDN are not mentioned. Only Google Analytics is mentioned, in general terms. 4) Google (US), Facebook (US), Klaviyo (US), Nosto (Finland/US), Adobe Typekit (US), kk-resources.com (unknown jurisdiction) — a data-transfer mechanism is not specified for any of them. Full technical documentation is published at: https://gdpru.eu/en/audits/ee-loverte-com/ 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]