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.
Request timeline
Declared versus actual
Transfer timings
Privacy Center CMP TCF 2.0
Semantiq — semantic targeting
Clickstream batch — data before consent
gdpr=1&gdpr_consent=CQk0NkAQ...
Detected trackers
- Adition (imagesrv.adition.com, ad13.adfarm1.adition.com) — ad network
- DoubleClick (ad.doubleclick.net) — impression tracking
- IAS / Integral Ad Science (adsafeprotected.com) — brand safety
- adnz.co / Semantiq — semantic targeting
- Privacy Center CMP (sdk.privacy-center.org)
- Matomo (app-analytics.orf.at) — self-hosted
- createjs.com CDN
Indicators of GDPR non-compliance
- GDPR Art. 6(1), Art. 5(1)(a)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.
- GDPR Art. 7 — TCF 2.0Adition 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.
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.
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.
3b14c21b783aea4d807007a73e6bbb185ebecc2687eb4095a338a8e4b1241b46Want a response from the company about this audit? → Open the tool
Fill in once — it will be inserted into every letter below:
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.
RIA DigiDoc — phone · Smart-ID / Mobile-ID
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) — orf.at Кому: [укажите адрес компании — DPO / поддержка / юридический отдел] От: [Ваше имя], [контактный email] Прошу предоставить доступ к моим персональным данным, обрабатываемым в связи с использованием сайта orf.at. 1. Категории данных и цели обработки (ст. 15(1)(a)-(c)) На основании независимого технического анализа сайта прошу подтвердить и подробно раскрыть следующие категории обработки: 1) adnz.co/semantiq (+1344 мс) загружается одновременно с Privacy Center CMP (+1344 мс) — до получения согласия. adnz.co clickstream collector отправляет данные на +2534 мс. Рекламная инфраструктура (Adition +2093 мс) загружается до готовности баннера. 2) Adition запросы содержат TCF consent string (gdpr=1&gdpr_consent=CQk0NkAQ...) — согласие передаётся. Но adnz.co семантический скрипт активируется до баннера. DoubleClick trackimp (+3406 мс) загружается после согласия. 2. Получатели, сроки хранения и передача за пределы ЕЭЗ (ст. 15(1)(c)-(d), 46) Прошу также указать полный список третьих лиц-получателей, применимые сроки хранения по каждой категории и правовые основания передачи данных за пределы ЕЭЗ, если таковая происходит. Полный технический разбор с доказательствами (сохранённый сетевой журнал, контрольная сумма SHA-256) опубликован по адресу: https://gdpru.eu/en/audits/at-orf-at/ 3. Автоматизированная обработка и профилирование (ст. 15(1)(h)) Прошу сообщить, применяется ли в отношении меня автоматизированное принятие решений или профилирование, и если да — раскрыть логику такой обработки. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Data access request (GDPR Art. 15) — orf.at 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 orf.at. 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) 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. 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/at-orf-at/ 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]
RIA DigiDoc — phone · Smart-ID / Mobile-ID
Where to file: Datenschutzbehörde (DSB) — file a complaint online →
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)
Тема: Жалоба на обработку персональных данных — orf.at 1. Предмет жалобы Я подаю жалобу в отношении обработки моих персональных данных сайтом orf.at. 2. Обстоятельства Я посетил сайт orf.at и обнаружил признаки несоответствия обработки моих персональных данных требованиям GDPR. Технический разбор, опубликованный на gdpru.eu 26.05.2026 (открытая методология, воспроизводимые измерения), документирует следующие признаки: 1) adnz.co/semantiq (+1344 мс) загружается одновременно с Privacy Center CMP (+1344 мс) — до получения согласия. adnz.co clickstream collector отправляет данные на +2534 мс. Рекламная инфраструктура (Adition +2093 мс) загружается до готовности баннера. 2) Adition запросы содержат TCF consent string (gdpr=1&gdpr_consent=CQk0NkAQ...) — согласие передаётся. Но adnz.co семантический скрипт активируется до баннера. DoubleClick trackimp (+3406 мс) загружается после согласия. Полная техническая документация опубликована по адресу: https://gdpru.eu/en/audits/at-orf-at/ 3. Положения GDPR, соблюдение которых прошу проверить GDPR Art. 6(1), Art. 5(1)(a); GDPR Art. 7 — TCF 2.0 4. Требование Прошу проверить изложенные обстоятельства и, если несоответствие подтвердится, принять меры, предусмотренные статьёй 58(2) GDPR. 5. Приложения Полная доказательная база — HAR-файл, контрольная сумма SHA-256 и цитата из политики конфиденциальности сайта, документирующая указанное противоречие — опубликована и проверяема по ссылке в пункте 2 выше. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Complaint regarding personal data processing — orf.at 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. GDPR provisions I ask you to examine GDPR Art. 6(1), Art. 5(1)(a); GDPR Art. 7 — TCF 2.0 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]