Anp.nl is the website of the Dutch national news agency. Homepage scan: 51 requests, 16 domains. The site has its own consent banner, but in practice it does not hold trackers back. Before the user's choice, the Facebook pixel sends a pageview event to Meta, Google Analytics runs in two generations at once — legacy and current, a third-party identification and attribution service contacts its own servers, and a video platform collects player statistics. Consent mode for Google is not configured. In other words, the banner is present, but the advertising pixel, analytics, and identification fire before the choice, and three of these recipients aren't even named in the policy.
Request timeline
Declared versus actual
Detected trackers
- Facebook / Meta Pixel
- Google Analytics (Universal + GA4)
- Bending Spoons (identification/attribution)
- Vimeo (player analytics)
Indicators of GDPR non-compliance
- Art. 6(1)(a) GDPR and art. 11.7a Telecommunicatiewet — advertising pixel and analytics fire before consent despite the bannerThe site has its own consent banner, but in practice it does not hold trackers back. A whole set of services fires before any user choice. The Facebook pixel sends a pageview event to Meta. Google Analytics runs in two generations at once — the legacy version and the current one — and sends its own requests. A third-party identification and attribution service sends a request to its own servers. The video platform collects player statistics. Consent mode for Google Analytics is not configured — requests go out without a consent signal. In other words, the banner exists, but the advertising pixel, analytics, and identification fire before the user's choice, as if it weren't there at all. All of these services are non-technical purposes requiring consent.
- Art. 13 GDPR — the Facebook pixel, video-platform analytics, and third-party identification are not disclosed in the policyThe policy names only Google Analytics. However, the Facebook pixel transmitting the visit to Meta, the video-platform analytics, and the third-party identification and attribution service are not mentioned in the policy. In other words, three data recipients, including a social-network advertising pixel, are undisclosed in the listing.
Context
www.anp.nl is the website of the Dutch national news agency (Algemeen Nederlands Persbureau): a news feed, photo bank, and services for editorial teams. The data controller is ANP. The site is informational, with an extension into media services.
Scan: 51 requests to 16 domains, homepage, captured in a clean Edge browser without a VPN or ad blocker. The site has its own consent banner. For a news agency, the technical stack is heavily loaded with trackers.
Who receives the data
Observed here: Meta, Google, Bending Spoons, Vimeo.
Meta receives a pageview event via the Facebook pixel. Google is present with analytics from two generations at once. A third-party identification and attribution service sends a request to its own servers. A video platform collects player statistics. In other words, the fact of the visit goes out to several third-party services at once.
Was there a consent banner
Yes, the site has its own consent banner. But in practice it does not hold trackers back: the advertising pixel, analytics, and identification fire before the user’s choice. Consent mode for Google Analytics, moreover, is not configured — its requests go out with no consent signal at all.
In other words, the consent mechanism is present but doesn’t do its job.
What fires before consent
Before the user’s choice, the following fire:
- the Facebook pixel — a pageview event to Meta;
- Google Analytics — two generations, including the legacy one;
- a third-party identification and attribution service;
- video-player analytics.
All of these services are non-technical purposes requiring consent. It’s worth separately noting that one generation of Google Analytics has long been discontinued, yet continues running on this site.
Undisclosed recipients
A separate point. The policy names only Google Analytics. The Facebook pixel transmitting the visit to Meta, the video-platform analytics, and the third-party identification and attribution service are not mentioned in the policy. In other words, three data recipients, including a social-network advertising pixel, are undisclosed in the listing.
Conclusion
Anp.nl is a case where the consent mechanism exists but doesn’t work. The news agency’s site has a banner, yet the Facebook pixel, two generations of Google Analytics, third-party identification, and video-player analytics all fire before the user’s choice, and consent mode for Google is not configured. On top of that, three of these recipients aren’t named in the policy. The key takeaway for the reader: having a banner means nothing by itself if it doesn’t actually hold trackers back until consent, and if the recipient list is missing half of the services actually in use. It would be enough to configure blocking and consent mode so that the pixel and analytics wait for the user’s choice, to complete the recipient list, and to remove the legacy analytics.
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.
d17b505addf51e1dfab21fd57b8fb7e16576461b43cd74ccc9904da1eaa0b4c8Want 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) — anp.nl Кому: [укажите адрес компании — DPO / поддержка / юридический отдел] От: [Ваше имя], [контактный email] Прошу предоставить доступ к моим персональным данным, обрабатываемым в связи с использованием сайта anp.nl. 1. Категории данных и цели обработки (ст. 15(1)(a)-(c)) На основании независимого технического анализа сайта прошу подтвердить и подробно раскрыть следующие категории обработки: 1) На сайте установлен собственный баннер согласия, но фактически он не удерживает трекеры. До какого-либо выбора пользователя отрабатывает целый набор сервисов. Пиксель Facebook отправляет в Meta событие просмотра страницы. Аналитика Google работает сразу в двух поколениях — устаревшем и текущем — и отправляет свои обращения. Сторонний сервис идентификации и атрибуции отправляет запрос на свои серверы. Видеоплатформа собирает статистику плеера. Режим согласия для аналитики Google при этом не настроен — обращения уходят без сигнала согласия. То есть баннер на сайте есть, но рекламный пиксель, аналитика и идентификация срабатывают раньше выбора, как будто его нет. Все эти сервисы — нетехнические цели, требующие согласия. 2) Политика называет только аналитику Google. Однако пиксель Facebook, передающий визит в Meta, аналитика видеоплатформы и сторонний сервис идентификации и атрибуции в политике не упомянуты. То есть три получателя данных, включая рекламный пиксель соцсети, в перечне не раскрыты. 2. Получатели, сроки хранения и передача за пределы ЕЭЗ (ст. 15(1)(c)-(d), 46) Прошу также указать полный список третьих лиц-получателей, применимые сроки хранения по каждой категории и правовые основания передачи данных за пределы ЕЭЗ, если таковая происходит. Полный технический разбор с доказательствами (сохранённый сетевой журнал, контрольная сумма SHA-256) опубликован по адресу: https://gdpru.eu/en/audits/nl-anp-nl/ 3. Автоматизированная обработка и профилирование (ст. 15(1)(h)) Прошу сообщить, применяется ли в отношении меня автоматизированное принятие решений или профилирование, и если да — раскрыть логику такой обработки. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Data access request (GDPR Art. 15) — anp.nl 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 anp.nl. 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) The site has its own consent banner, but in practice it does not hold trackers back. A whole set of services fires before any user choice. The Facebook pixel sends a pageview event to Meta. Google Analytics runs in two generations at once — the legacy version and the current one — and sends its own requests. A third-party identification and attribution service sends a request to its own servers. The video platform collects player statistics. Consent mode for Google Analytics is not configured — requests go out without a consent signal. In other words, the banner exists, but the advertising pixel, analytics, and identification fire before the user's choice, as if it weren't there at all. All of these services are non-technical purposes requiring consent. 2) The policy names only Google Analytics. However, the Facebook pixel transmitting the visit to Meta, the video-platform analytics, and the third-party identification and attribution service are not mentioned in the policy. In other words, three data recipients, including a social-network advertising pixel, are undisclosed in the listing. 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/nl-anp-nl/ 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: Dutch Data Protection Authority (AP) — autoriteitpersoonsgegevens.nl
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)
Тема: Жалоба на обработку персональных данных — anp.nl 1. Предмет жалобы Я подаю жалобу в отношении обработки моих персональных данных сайтом anp.nl. 2. Обстоятельства Я посетил сайт anp.nl и обнаружил признаки несоответствия обработки моих персональных данных требованиям GDPR. Технический разбор, опубликованный на gdpru.eu 16.06.2026 (открытая методология, воспроизводимые измерения), документирует следующие признаки: 1) На сайте установлен собственный баннер согласия, но фактически он не удерживает трекеры. До какого-либо выбора пользователя отрабатывает целый набор сервисов. Пиксель Facebook отправляет в Meta событие просмотра страницы. Аналитика Google работает сразу в двух поколениях — устаревшем и текущем — и отправляет свои обращения. Сторонний сервис идентификации и атрибуции отправляет запрос на свои серверы. Видеоплатформа собирает статистику плеера. Режим согласия для аналитики Google при этом не настроен — обращения уходят без сигнала согласия. То есть баннер на сайте есть, но рекламный пиксель, аналитика и идентификация срабатывают раньше выбора, как будто его нет. Все эти сервисы — нетехнические цели, требующие согласия. 2) Политика называет только аналитику Google. Однако пиксель Facebook, передающий визит в Meta, аналитика видеоплатформы и сторонний сервис идентификации и атрибуции в политике не упомянуты. То есть три получателя данных, включая рекламный пиксель соцсети, в перечне не раскрыты. Полная техническая документация опубликована по адресу: https://gdpru.eu/en/audits/nl-anp-nl/ 3. Положения GDPR, соблюдение которых прошу проверить Art. 6(1)(a) GDPR и ст. 11.7a Telecommunicatiewet — рекламный пиксель и аналитика срабатывают до согласия вопреки баннеру; Art. 13 GDPR — пиксель Facebook, аналитика видеоплатформы и сторонняя идентификация в политике не названы 4. Требование Прошу проверить изложенные обстоятельства и, если несоответствие подтвердится, принять меры, предусмотренные статьёй 58(2) GDPR. 5. Приложения Полная доказательная база — HAR-файл, контрольная сумма SHA-256 и цитата из политики конфиденциальности сайта, документирующая указанное противоречие — опубликована и проверяема по ссылке в пункте 2 выше. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Complaint regarding personal data processing — anp.nl 1. Subject of the complaint I am filing a complaint regarding the processing of my personal data by the website anp.nl. 2. Circumstances I visited the website anp.nl and found indications that the processing of my personal data does not comply with the GDPR. The technical analysis published on gdpru.eu on 16 June 2026 (open methodology, reproducible measurements) documents the following indications: 1) The site has its own consent banner, but in practice it does not hold trackers back. A whole set of services fires before any user choice. The Facebook pixel sends a pageview event to Meta. Google Analytics runs in two generations at once — the legacy version and the current one — and sends its own requests. A third-party identification and attribution service sends a request to its own servers. The video platform collects player statistics. Consent mode for Google Analytics is not configured — requests go out without a consent signal. In other words, the banner exists, but the advertising pixel, analytics, and identification fire before the user's choice, as if it weren't there at all. All of these services are non-technical purposes requiring consent. 2) The policy names only Google Analytics. However, the Facebook pixel transmitting the visit to Meta, the video-platform analytics, and the third-party identification and attribution service are not mentioned in the policy. In other words, three data recipients, including a social-network advertising pixel, are undisclosed in the listing. Full technical documentation is published at: https://gdpru.eu/en/audits/nl-anp-nl/ 3. GDPR provisions I ask you to examine Art. 6(1)(a) GDPR and art. 11.7a Telecommunicatiewet — advertising pixel and analytics fire before consent despite the banner; Art. 13 GDPR — the Facebook pixel, video-platform analytics, and third-party identification are not disclosed in the policy 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]