Official website of Vienna — 40 requests, 4 domains. A Truendo CMP is present, the privacy policy is detailed, Adform is in the code. But Siteimprove reaches an external server at 271 ms — before the consent banner has time to appear.
Timeline of the leak
Declared versus actual
Transfer timings
Script loaded before consent. Cookieless tracking based on a Visitor Hash (IP + User-Agent).
Audio stream loaded before consent. Buzzsprout — USA, SCC + EU-US DPF.
Detected trackers
- Siteimprove Analytics
- Buzzsprout (audio)
Indicators of GDPR non-compliance
- GDPR Art. 6(1)(a), TKG § 165Siteimprove Analytics loads 271 ms after the page opens — before the Truendo CMP has finished initializing and displaying the consent banner. There is no consent, yet the request has already gone out.
- GDPR Art. 6(1)(a)Buzzsprout loads audio 315 ms after the page opens — also before consent. By the site's own policy, embedded media requires Art. 6(1)(a).
Context
wien.gv.at is the official portal of the City of Vienna, one of Austria’s largest municipal sites. Operator: Stadt Wien, MA 53 (Kommunikation und Medien). HAR: 40 requests, 4 domains.
Proprietary infrastructure, detailed policy
38 of 40 requests go to proprietary infrastructure: www.wien.gv.at and assets.wien.gv.at — the city’s own CDN. No Google, no Meta, no external fonts. HSTS with max-age=31536000 and preload. The server identifies itself as “Magistrat der Stadt Wien — Web Gateway.” The privacy policy is structured around GDPR Art. 13: four separate processing sections, legal bases, retention periods, DPO with contact details.
Siteimprove ahead of the banner
There is one main problem, but a specific one: Siteimprove Analytics loads 271 ms after the page opens. The Truendo CMP — the city’s consent management platform — only finishes initializing at 902 ms. There is no banner, there is no consent, and the script has already reached siteimproveanalytics.com and returned a 200. The city justifies Siteimprove via Art. 6(1)(e) — public interest — and treats it as not requiring consent. Austria’s TKG § 165 requires consent for any identifier, including a Visitor Hash. This is a disputed but real conflict.
Adform declared, absent from the HAR
Adform is listed in the CSP (track.adform.net, *.adform.net) and described in detail in the policy as a consent-based marketing tool. Not a single request to Adform appears in the HAR for the homepage. Either it’s not activated on the homepage, or it fires on other pages after consent. This is the correct architecture for an Art. 6(1)(a) tool.
Conclusion
wien.gv.at is not a case where trackers are hidden or the policy is unwritten. The policy is detailed, infrastructure is mostly proprietary, a Truendo CMP is present. The problem lies in one place: Siteimprove reaches the outside world before the consent system has time to act. 271 ms versus 902 ms — and this isn’t a technical glitch, but an architectural choice the city shields behind a disputed public-interest justification.
0debe245f468d0f370a99e254af8fae974204509b280bcf7ab0240ebffa1b540Where to file: Datenschutzbehörde (DSB) — file a complaint online →
To: Datenschutzbehörde (DSB) 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 wien.gv.at. 2. Circumstances I visited the website wien.gv.at and found indications that the processing of my personal data does not comply with the GDPR. The technical analysis published on gdpru.eu on 26 May 2026 (open methodology, reproducible measurements) documents the following indications: 1) Siteimprove Analytics loads 271 ms after the page opens — before the Truendo CMP has finished initializing and displaying the consent banner. There is no consent, yet the request has already gone out. 2) Buzzsprout loads audio 315 ms after the page opens — also before consent. By the site's own policy, embedded media requires Art. 6(1)(a). Full technical documentation is published at: https://gdpru.eu/en/audits/at-wien-gv-at/ 3. Provisions violated GDPR Art. 6(1)(a), TKG § 165; GDPR Art. 6(1)(a) 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]