Technical audit · 2026-06-06

aboutyou.ee

European Online Clothing Retailer — an Otto Group Subsidiary

A German online retailer — the Russian-language version for Estonia. Usercentrics loads correctly and beats most trackers. One exception: the proprietary tracking API t2.aboutyou.com starts at the same time as the banner — before it actually appears.

Timeline of the leak

+129 ms · simultaneously
t2.aboutyou.com (lib.js?t=AYC) and the Usercentrics loader — fire within the same millisecond. The banner has not yet rendered.
+129–1904 ms · banner loading
Usercentrics fully loads over roughly 1.8 seconds: the loader, WebSdk, GDPR configuration for the Russian language, UI components.
+2898 ms · after the banner
unpkg.com (@rive-app/canvas 2.34.1, rive.wasm) — an animation library CDN. Data to the USA.
+3043 ms
Optimizely (logx.optimizely.com) — A/B testing, events. USA.
+3136 ms
tadarida-web.aboutyou.com — a proprietary gRPC API: cart, missions, navigation. Data on ABOUT YOU's infrastructure.

Declared versus actual

+ Optimizely (logx.optimizely.com) — USA — не заявлен
+ unpkg.com CDN — USA — не заявлен

Transfer timings

+129 ms t2.aboutyou.com

Tracking lib.js, simultaneous with Usercentrics

+129 ms web.cmp.usercentrics.eu

Usercentrics loader — starts loading

+1904 ms graphql.usercentrics.eu

Usercentrics fully loaded

+2898 ms unpkg.com

rive.wasm CDN. USA

+3043 ms logx.optimizely.com

A/B testing events. USA

Detected trackers

Indicators of GDPR non-compliance

Context

ru.aboutyou.ee is the Russian-language version of the Estonian ABOUT YOU store, a subsidiary of Otto Group (Hamburg). The audit was conducted on the Russian-language version of the site (ru.aboutyou.ee/vash-magazin) — a separate localization for Estonia’s Russian-speaking residents. HAR: 177 requests, 13 domains.

What is done correctly

ABOUT YOU has built an architecture substantially better than most retailers in the series. Usercentrics loads at +129 ms — among the very first requests. The GDPR configuration loads in Russian (/ru/GDPR/). Most trackers activate only after Usercentrics has loaded. Proprietary infrastructure (assets.aboutstatic.com, cdn.aboutstatic.com, tadarida-web.aboutyou.com) — no Google CDN, no Cloudflare for media content. Zero Set-Cookie responses.

t2.aboutyou.com — a borderline case

At +129 ms, both the Usercentrics loader and t2.aboutyou.com/tapi/basic-js/lib.js — ABOUT YOU’s own tracking API — fire simultaneously. Technically they start within the same millisecond, but the Usercentrics banner only rendered and became visible to the user roughly 1.5–2 seconds later. This means ABOUT YOU’s own tracker initialized before the user could physically see the banner and interact with it.

Optimizely and unpkg — undisclosed recipients

Optimizely (logx.optimizely.com, +3043 ms) is the A/B testing platform of the American company Optimizely Inc. It activates after Usercentrics has loaded, which is technically better — but Optimizely is not mentioned as a data recipient in ABOUT YOU’s Estonian privacy policy.

unpkg.com (+2898 ms) is a public npm-package CDN. It loads @rive-app/canvas@2.34.1/rive.wasm — an animation library. The IP address goes to Cloudflare (USA). Using a public CDN instead of self-hosting the library is a lapse against an otherwise fairly careful architecture.

Comparison with Zalando

Both sites use Usercentrics. Zalando loads GTM 1.5 seconds before the banner. ABOUT YOU loads Usercentrics among its very first requests and keeps most trackers behind the consent barrier. Architecturally, ABOUT YOU is closer to a correct implementation — with the caveat of t2.aboutyou.com and Optimizely.

Conclusion

ABOUT YOU demonstrates one of the best approaches to consent among the commercial sites in this series: Usercentrics starts immediately, most trackers sit behind the barrier, and infrastructure is proprietary. Two undisclosed recipients (Optimizely, unpkg.com) and the borderline case with t2.aboutyou.com are points to fix, not a systemic problem.

Evidence
Original (audit)
HAR file: ee/aboutyou-ee-2026-06-06.har
SHA-256: 58ece84f05e319c5e61e99c20a2fdd64cb35cb77d957bdcc849d331d4ef0b328
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 aboutyou.ee.

2. Circumstances
I visited the website aboutyou.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) t2.aboutyou.com (a tracking API) loads at the same time as Usercentrics, at +129 ms — before the banner has rendered and the user could see it. Optimizely (+3043 ms) activates after Usercentrics has loaded, but its consent mechanism is not evident from the HAR.

2) Optimizely (USA) and the unpkg.com CDN are not mentioned in the privacy policy as data recipients. No data-transfer mechanism for Optimizely to the USA is stated.

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

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

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]