RU EN
www.
Technical audit · 2026-05-26

orf.at

Österreichischer Rundfunk — Austrian Public Broadcasting
AT

Policy changed — see what exactly · 2026-08-14 →

Austrian public television — 85 requests, 22 domains. A Privacy Center CMP with TCF 2.0 — consent is passed to Adition and DoubleClick. Self-hosted Matomo on app-analytics.orf.at. adnz.co semantic targeting loads before the banner.

Timeline of the leak

+917 ms · on load
Matomo (app-analytics.orf.at) — ORF's self-hosted analytics.
+1344 ms · banner
Privacy Center CMP (sdk.privacy-center.org) — TCF 2.0 banner.
+1344 ms · before consent
adnz.co/semantiq — semantic targeting. Loads simultaneously with the banner.
+2093 ms · before consent
Adition (imagesrv.adition.com/js/aut.js) — advertising infrastructure.
+2534 ms · before consent
api.adnz.co clickstream batch — data goes out before consent.
+2884 ms · with consent
Adition request with gdpr=1&gdpr_consent=CQk0NkAQ... — TCF consent string transmitted.
+3406 ms · with consent
DoubleClick trackimp — ad impression tracking.
+3602 ms
createjs.com CDN — ad banner (Flash-legacy library).

Declared versus actual

+ adnz.co / Semantiq (before consent) — не заявлен
+ createjs.com CDN — не заявлен
+ IAS AdSafeProtected — не заявлен

Transfer timings

+1344 ms sdk.privacy-center.org

Privacy Center CMP TCF 2.0

+1344 ms adnz.co

Semantiq — semantic targeting

+2534 ms api.adnz.co

Clickstream batch — data before consent

+2884 ms ad13.adfarm1.adition.com

gdpr=1&gdpr_consent=CQk0NkAQ...

Detected trackers

Indicators of GDPR non-compliance

Context

ORF (Österreichischer Rundfunk) is Austria’s public broadcaster, the country’s largest media operator. Funded by the GIS license fee and advertising. The orf.at site is Austria’s leading news portal. HAR: 85 requests, 22 domains.

Privacy Center CMP — TCF 2.0 implemented

ORF uses the Privacy Center CMP (sdk.privacy-center.org) with TCF 2.0. Requests to Adition carry a real TCF consent string: gdpr=1&gdpr_consent=CQk0NkAQk0NkAAHABBENCgFgA.... This means consent is correctly passed to advertising partners via the IAB TCF mechanism. DoubleClick trackimp loads only after consent is obtained.

Self-hosted Matomo — the right choice

app-analytics.orf.at/matomo.js (+917 ms) — Matomo on ORF’s own subdomain. Analytics stays within ORF’s infrastructure. The same approach as AGES and EBA.

adnz.co — before the banner

adnz.co/semantiq/semantiq.js (+1344 ms) loads at the same time as the CMP banner — i.e., before consent is obtained. Semantiq is an ad semantic-targeting system (it analyzes page content to select ads without cookies). At +2534 ms api.adnz.co sends clickstream data as a batch request. Cookieless semantic targeting sits in a legal grey zone under GDPR — it doesn’t identify the user directly, but it does analyze behavior.

Adition — an advertising network

Adition (now part of Virtual Minds / Ströer) is a German advertising platform. ORF uses it as its primary ad network. is.orf-player.at — ORF’s own domain for the video player, loads ad banners from Adition through a proprietary proxy.

createjs.com — Flash legacy

code.createjs.com/1.0.0/createjs.min.js (+3602 ms) — CDN for the CreateJS library (Adobe), originally created for migrating Flash content to HTML5. Used to render an ad banner. A public Adobe CDN, with data going to the USA.

Conclusion

ORF has implemented TCF 2.0 more correctly than many commercial sites in the series: the consent string is genuinely passed to Adition and DoubleClick, and Matomo is self-hosted. The main issue is that adnz.co Semantiq loads before consent and sends clickstream data. createjs.com is an external ad CDN not mentioned in the policy.

Evidence
Original (audit)
HAR file: at/orf-at-2026-05-26.har
SHA-256: 3b14c21b783aea4d807007a73e6bbb185ebecc2687eb4095a338a8e4b1241b46
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: 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 orf.at.

2. Circumstances
I visited the website orf.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) adnz.co/semantiq (+1344 ms) loads at the same time as the Privacy Center CMP (+1344 ms) — before consent is obtained. The adnz.co clickstream collector sends data at +2534 ms. The advertising infrastructure (Adition +2093 ms) loads before the banner is ready.

2) Adition requests carry a TCF consent string (gdpr=1&gdpr_consent=CQk0NkAQ...) — consent is transmitted. But the adnz.co semantic script activates before the banner. DoubleClick trackimp (+3406 ms) loads after consent.

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

3. Provisions violated
GDPR Art. 6(1), Art. 5(1)(a); GDPR Art. 7 — TCF 2.0

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]