Belgian Federal Public Service for the Interior — 27 requests, 6 domains. The CookieFirst consent manager correctly blocks Matomo before consent, but Google Fonts slips past it: it loads on page load, transmitting the visitor's IP address to Google (USA) before consent. Google Fonts is not named in the policy, despite the policy stating that no third-party cookies are placed.
Request timeline
Declared versus actual
Transfer timings
Google Fonts CSS. Google, USA. Not held back by the CMP.
Google font files. Google, USA.
Matomo held back by CookieFirst until consent. Correct.
Detected trackers
- Google Fonts (fonts.googleapis.com, fonts.gstatic.com)
- Matomo (matomo.ibz-dev.be) — blocked before consent
- CookieFirst (consent.cookiefirst.com) — CMP
Indicators of GDPR non-compliance
- GDPR Art. 13(1)(e) + Chapter V — disclosure of recipients and transferBefore consent, Google Fonts loads on page load (fonts.googleapis.com ×5 at +354 ms, fonts.gstatic.com at +488 ms), transmitting the visitor's IP address to Google (USA). A CookieFirst consent manager is present and correctly holds back Matomo (matomo.js returns with status 0 — blocked), but does not hold back Google Fonts. The cookie policy states that no third-party cookies are placed ('Aucun cookie de tierce partie'); Google Fonts indeed sets no cookie, but is a third-party recipient of the IP address from the USA and is not named in the policy.
- ePrivacy (Belgian implementation) — third-party resource before consentGoogle Fonts loads before the CookieFirst banner appears (+549 ms) and before any choice is made. Zero Set-Cookie headers for the entire session. The IP transfer to a third-party recipient in the USA occurs without consent and outside the mechanism, whereas the Matomo analytics tool is correctly held back by that same mechanism.
Context
ibz.be is the website of Belgium’s Federal Public Service for the Interior (SPF Intérieur / FOD Binnenlandse Zaken), responsible for the police, security, migration, identity documents, and elections. Controller: SPF Intérieur. The general privacy policy references a separate cookie policy, which was retrieved from the site. Measurement: 27 requests, 6 domains, captured on a clean browser.
Who receives data directly (before consent)
Google (USA) — the visitor’s IP address, via the Google Fonts load.
Declared versus actual
ibz.be’s cookie policy states plainly that no third-party cookies are placed when visiting the site (“Aucun cookie de tierce partie ne sera placé”). Analytics are described as Matomo-Cloud with data centers in Europe, installed only after consent. Management of the cookie table is assigned to CookieFirst.
The measurement largely confirms this — and shows that the consent mechanism works selectively. The Matomo analytics script (matomo.ibz-dev.be/matomo.js) returns with status 0 in the measurement: it is held back by CookieFirst until consent and effectively does not load. This is correct behavior, consistent with the policy.
However, Google Fonts slips past this mechanism. At +354 ms, before the consent banner appears (+549 ms), the Google Fonts CSS loads from fonts.googleapis.com, and the font files load from fonts.gstatic.com. Both requests transmit the visitor’s IP address to Google (USA). Google Fonts sets no cookie, so the policy’s literal statement about the absence of third-party cookies is not violated — but Google is a third-party recipient of data from the USA, receiving the IP address before consent, and this service is not named in the policy. The consent manager thus holds back the analytics tool but does not hold back the IP transfer to Google via the fonts.
Timing relative to consent
Google Fonts loads at +354 ms, the CookieFirst banner at +549 ms, and Matomo is blocked at +580 ms. In other words, the fonts reach Google before the banner is even ready, and before the blocking mechanism activates. No consent was given during the session (zero Set-Cookie).
What cannot be claimed from the measurement
The measurement covers the homepage. Matomo’s status 0 is interpreted as blocking by the consent manager before consent; Matomo’s behavior after consent is not observed in this session. Google may use edge nodes within the EU, so the conclusion is drawn based on the recipient’s affiliation (a US company), not the physical location of the node. Server-side processing is not visible in a browser-based measurement.
Conclusion
The Belgian Ministry of the Interior’s website correctly gates its analytics: Matomo (Matomo-Cloud, Europe) is held back by the CookieFirst consent manager until consent. But Google Fonts slips past this mechanism and transmits the visitor’s IP address to Google (USA) before consent; this service is not named in the policy, and the policy itself states that no third-party cookies are placed. For the website of a core security-sector ministry, transmitting the IP address to a third-party recipient in the USA before consent and outside the consent mechanism indicates non-compliance with the requirements for disclosure of recipients and cross-border transfer. The remedy is simple and does not affect the already-correct analytics setup: host the fonts locally on the proprietary domain — the one remaining leak would then disappear.
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.
360a09d63b4caa2686ce0a0b0c6306c678809e3a36919ccc71e59b052b50b20bWant 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) — ibz.be Кому: [укажите адрес компании — DPO / поддержка / юридический отдел] От: [Ваше имя], [контактный email] Прошу предоставить доступ к моим персональным данным, обрабатываемым в связи с использованием сайта ibz.be. 1. Категории данных и цели обработки (ст. 15(1)(a)-(c)) На основании независимого технического анализа сайта прошу подтвердить и подробно раскрыть следующие категории обработки: 1) На загрузке страницы до согласия загружается Google Fonts (fonts.googleapis.com ×5 на +354 мс, fonts.gstatic.com на +488 мс), передавая IP посетителя в Google (США). Consent-менеджер CookieFirst присутствует и корректно удерживает Matomo (matomo.js возвращается со статусом 0 — заблокирован), однако Google Fonts им не удерживается. Cookie-политика заявляет, что сторонние cookie не ставятся («Aucun cookie de tierce partie»); Google Fonts действительно не ставит cookie, но является сторонним получателем IP из США, и в политике не назван. 2) Загрузка Google Fonts происходит до появления баннера CookieFirst (+549 мс) и до какого-либо выбора. Set-Cookie за весь сеанс ноль. Передача IP стороннему получателю в США происходит без согласия и вне механизма, тогда как аналитический Matomo тем же механизмом корректно удержан. 2. Получатели, сроки хранения и передача за пределы ЕЭЗ (ст. 15(1)(c)-(d), 46) Прошу также указать полный список третьих лиц-получателей, применимые сроки хранения по каждой категории и правовые основания передачи данных за пределы ЕЭЗ, если таковая происходит. Полный технический разбор с доказательствами (сохранённый сетевой журнал, контрольная сумма SHA-256) опубликован по адресу: https://gdpru.eu/en/audits/be-ibz-be/ 3. Автоматизированная обработка и профилирование (ст. 15(1)(h)) Прошу сообщить, применяется ли в отношении меня автоматизированное принятие решений или профилирование, и если да — раскрыть логику такой обработки. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Data access request (GDPR Art. 15) — ibz.be
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 ibz.be.
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) Before consent, Google Fonts loads on page load (fonts.googleapis.com ×5 at +354 ms, fonts.gstatic.com at +488 ms), transmitting the visitor's IP address to Google (USA). A CookieFirst consent manager is present and correctly holds back Matomo (matomo.js returns with status 0 — blocked), but does not hold back Google Fonts. The cookie policy states that no third-party cookies are placed ('Aucun cookie de tierce partie'); Google Fonts indeed sets no cookie, but is a third-party recipient of the IP address from the USA and is not named in the policy.
2) Google Fonts loads before the CookieFirst banner appears (+549 ms) and before any choice is made. Zero Set-Cookie headers for the entire session. The IP transfer to a third-party recipient in the USA occurs without consent and outside the mechanism, whereas the Matomo analytics tool is correctly held back by that same mechanism.
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/be-ibz-be/
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: Autorité de protection des données (APD) — 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)
Тема: Жалоба на обработку персональных данных — ibz.be 1. Предмет жалобы Я подаю жалобу в отношении обработки моих персональных данных сайтом ibz.be. 2. Обстоятельства Я посетил сайт ibz.be и обнаружил признаки несоответствия обработки моих персональных данных требованиям GDPR. Технический разбор, опубликованный на gdpru.eu 26.05.2026 (открытая методология, воспроизводимые измерения), документирует следующие признаки: 1) На загрузке страницы до согласия загружается Google Fonts (fonts.googleapis.com ×5 на +354 мс, fonts.gstatic.com на +488 мс), передавая IP посетителя в Google (США). Consent-менеджер CookieFirst присутствует и корректно удерживает Matomo (matomo.js возвращается со статусом 0 — заблокирован), однако Google Fonts им не удерживается. Cookie-политика заявляет, что сторонние cookie не ставятся («Aucun cookie de tierce partie»); Google Fonts действительно не ставит cookie, но является сторонним получателем IP из США, и в политике не назван. 2) Загрузка Google Fonts происходит до появления баннера CookieFirst (+549 мс) и до какого-либо выбора. Set-Cookie за весь сеанс ноль. Передача IP стороннему получателю в США происходит без согласия и вне механизма, тогда как аналитический Matomo тем же механизмом корректно удержан. Полная техническая документация опубликована по адресу: https://gdpru.eu/en/audits/be-ibz-be/ 3. Положения GDPR, соблюдение которых прошу проверить GDPR Art. 13(1)(e) + Chapter V — раскрытие получателей и передача; ePrivacy (бельгийская имплементация) — сторонний ресурс до согласия 4. Требование Прошу проверить изложенные обстоятельства и, если несоответствие подтвердится, принять меры, предусмотренные статьёй 58(2) GDPR. 5. Приложения Полная доказательная база — HAR-файл, контрольная сумма SHA-256 и цитата из политики конфиденциальности сайта, документирующая указанное противоречие — опубликована и проверяема по ссылке в пункте 2 выше. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Complaint regarding personal data processing — ibz.be
1. Subject of the complaint
I am filing a complaint regarding the processing of my personal data by the website ibz.be.
2. Circumstances
I visited the website ibz.be 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) Before consent, Google Fonts loads on page load (fonts.googleapis.com ×5 at +354 ms, fonts.gstatic.com at +488 ms), transmitting the visitor's IP address to Google (USA). A CookieFirst consent manager is present and correctly holds back Matomo (matomo.js returns with status 0 — blocked), but does not hold back Google Fonts. The cookie policy states that no third-party cookies are placed ('Aucun cookie de tierce partie'); Google Fonts indeed sets no cookie, but is a third-party recipient of the IP address from the USA and is not named in the policy.
2) Google Fonts loads before the CookieFirst banner appears (+549 ms) and before any choice is made. Zero Set-Cookie headers for the entire session. The IP transfer to a third-party recipient in the USA occurs without consent and outside the mechanism, whereas the Matomo analytics tool is correctly held back by that same mechanism.
Full technical documentation is published at: https://gdpru.eu/en/audits/be-ibz-be/
3. GDPR provisions I ask you to examine
GDPR Art. 13(1)(e) + Chapter V — disclosure of recipients and transfer; ePrivacy (Belgian implementation) — third-party resource before consent
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]