France's Ministry of the Interior — 53 requests, one external domain. The policy states that cookies are set only after consent and that data is not transferred outside the EU, without naming a specific audience-measurement tool. In the measurement, Cloudflare Web Analytics (beacon.min.js plus a RUM request) runs before consent; the load transmits the visitor's IP address to Cloudflare Inc — a US company not named in the policy.
Request timeline
Declared versus actual
Transfer timings
Cloudflare Web Analytics beacon.min.js. Cloudflare Inc, USA. Not named in the policy.
Detected trackers
- Cloudflare Web Analytics (static.cloudflareinsights.com)
Indicators of GDPR non-compliance
- GDPR Art. 13(1)(e) — disclosure of recipients and the toolThe policy mentions audience measurement in general terms ('mesurer sa fréquentation') and names no specific tool. In the measurement, Cloudflare Web Analytics is at work: beacon.min.js loads from static.cloudflareinsights.com at +219 ms, with RUM data sent via a POST request to /cdn-cgi/rum. The actual analytics service and its provider (Cloudflare Inc) are not disclosed in the policy.
- GDPR Art. 44 (Chapter V) + Art. 5(1)(a) — cross-border transfer and transparencyThe policy states directly: 'Ces données ne font pas l'objet d'un transfert en dehors du territoire de l'Union européenne.' Loading beacon.min.js from static.cloudflareinsights.com transmits the visitor's IP address to Cloudflare Inc — a US company — before consent. The absolute claim of no transfer outside the EU is contradicted by the actual data transfer to a recipient in the USA.
Context
interieur.gouv.fr is the official website of France’s Ministry of the Interior (Ministère de l’Intérieur), responsible for the police, gendarmerie, civil security, and elections. Controller: the ministry’s délégué à l’Information et à la communication. The privacy policy was supplied and checked against the version currently in effect on the site. Measurement: 53 requests, one external domain, captured on a clean browser.
Who receives data directly (before consent)
Cloudflare Inc (USA) — the visitor’s IP address, via loading Cloudflare’s analytics beacon.min.js.
Declared versus actual
The policy’s cookie section makes two explicit promises. First: cookies are set only if accepted (“Les cookies ne sont déposés que si vous les acceptez”). Second, in the data section: no transfer outside the territory of the European Union occurs (“Ces données ne font pas l’objet d’un transfert en dehors du territoire de l’Union européenne”). Audience measurement is mentioned in general terms — “mesurer sa fréquentation” — but the specific measurement tool is not named in the policy.
The measurement shows an unnamed tool at work. At +219 ms, beacon.min.js loads from the domain static.cloudflareinsights.com — this is Cloudflare Web Analytics, a service of Cloudflare Inc (USA). Real User Monitoring data is then sent via a POST request to /cdn-cgi/rum. The first promise, on cookies, is formally upheld: Cloudflare Web Analytics operates without cookies, and not a single cookie is set for the entire session. However, loading beacon.min.js itself transmits the visitor’s IP address to Cloudflare — a US company — which contradicts the second promise of no transfer outside the EU. Moreover, the analytics service actually in use is not named in the policy: it states only the general “mesurer sa fréquentation,” with no identification of the tool or its provider.
Timing relative to consent
Cloudflare’s analytics beacon loads at +219 ms, right at the start of the session, before any user choice. Since the service uses no cookies, the literal condition of “cookies only after consent” is not violated — but data transmission to an American recipient occurs regardless of consent.
What cannot be claimed from the measurement
Cloudflare Web Analytics uses no cookies, so there is no violation of the cookie condition in the measurement; the subject of the discrepancy is the non-disclosure of the actual tool and the claim of no transfer outside the EU. Cloudflare Inc is a US company; at the same time, Cloudflare’s infrastructure makes wide use of edge nodes within the EU, so the conclusion is drawn based on the recipient’s affiliation (an American company), not the physical location of the specific processing node. The full contents of the RUM request cannot be fully reconstructed from the lightweight capture. Server-side processing is not visible in a browser-based measurement.
Conclusion
The Ministry of the Interior’s policy promises that cookies are set only after consent and that data does not leave the EU, without naming the specific audience-measurement tool. In the measurement, Cloudflare Web Analytics is at work — a service of the American company Cloudflare Inc: its beacon loads before consent and transmits the visitor’s IP address to Cloudflare. The cookie condition is formally upheld, since the service is cookieless, but the actual tool is not disclosed in the policy, and the promise of no transfer outside the EU is contradicted by the data transfer to a US recipient. For the website of a core security-sector ministry, the non-disclosure of the actual analytics service, combined with the discrepancy from the no-transfer-outside-the-EU claim, indicates non-compliance with transparency requirements and cross-border transfer rules. Remedy: name the actual audience-measurement tool and its provider in the policy, bring the no-transfer-outside-the-EU claim into line with reality (or host the analytics on EU-based infrastructure with no American recipient involved), and include the service in the consent mechanism.
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.
0c782052c523f1bdc031bbbcf3d433fcfbe6beb8956c75f4c4fb0cca6146a45cWant 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) — interieur.gouv.fr Кому: [укажите адрес компании — DPO / поддержка / юридический отдел] От: [Ваше имя], [контактный email] Прошу предоставить доступ к моим персональным данным, обрабатываемым в связи с использованием сайта interieur.gouv.fr. 1. Категории данных и цели обработки (ст. 15(1)(a)-(c)) На основании независимого технического анализа сайта прошу подтвердить и подробно раскрыть следующие категории обработки: 1) Политика упоминает аудиторное измерение обобщённо («mesurer sa fréquentation») и не называет ни одного конкретного инструмента. В замере работает Cloudflare Web Analytics: beacon.min.js загружается с static.cloudflareinsights.com на +219 мс, данные RUM уходят POST-запросом на /cdn-cgi/rum. Фактический аналитический сервис и его провайдер (Cloudflare Inc) в политике не раскрыты. 2) Политика прямо заявляет: «Ces données ne font pas l'objet d'un transfert en dehors du territoire de l'Union européenne». Загрузка beacon.min.js с static.cloudflareinsights.com передаёт IP посетителя Cloudflare Inc — американской компании — до согласия. Абсолютное заявление об отсутствии передачи за пределы ЕС вступает в противоречие с фактической передачей данных получателю из США. 2. Получатели, сроки хранения и передача за пределы ЕЭЗ (ст. 15(1)(c)-(d), 46) Прошу также указать полный список третьих лиц-получателей, применимые сроки хранения по каждой категории и правовые основания передачи данных за пределы ЕЭЗ, если таковая происходит. Полный технический разбор с доказательствами (сохранённый сетевой журнал, контрольная сумма SHA-256) опубликован по адресу: https://gdpru.eu/en/audits/fr-interieur-gouv-fr/ 3. Автоматизированная обработка и профилирование (ст. 15(1)(h)) Прошу сообщить, применяется ли в отношении меня автоматизированное принятие решений или профилирование, и если да — раскрыть логику такой обработки. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Data access request (GDPR Art. 15) — interieur.gouv.fr
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 interieur.gouv.fr.
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 policy mentions audience measurement in general terms ('mesurer sa fréquentation') and names no specific tool. In the measurement, Cloudflare Web Analytics is at work: beacon.min.js loads from static.cloudflareinsights.com at +219 ms, with RUM data sent via a POST request to /cdn-cgi/rum. The actual analytics service and its provider (Cloudflare Inc) are not disclosed in the policy.
2) The policy states directly: 'Ces données ne font pas l'objet d'un transfert en dehors du territoire de l'Union européenne.' Loading beacon.min.js from static.cloudflareinsights.com transmits the visitor's IP address to Cloudflare Inc — a US company — before consent. The absolute claim of no transfer outside the EU is contradicted by the actual data transfer to a recipient in the USA.
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/fr-interieur-gouv-fr/
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: Commission nationale de l'informatique et des libertés (CNIL) — cnil.fr
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)
Тема: Жалоба на обработку персональных данных — interieur.gouv.fr 1. Предмет жалобы Я подаю жалобу в отношении обработки моих персональных данных сайтом interieur.gouv.fr. 2. Обстоятельства Я посетил сайт interieur.gouv.fr и обнаружил признаки несоответствия обработки моих персональных данных требованиям GDPR. Технический разбор, опубликованный на gdpru.eu 02.07.2026 (открытая методология, воспроизводимые измерения), документирует следующие признаки: 1) Политика упоминает аудиторное измерение обобщённо («mesurer sa fréquentation») и не называет ни одного конкретного инструмента. В замере работает Cloudflare Web Analytics: beacon.min.js загружается с static.cloudflareinsights.com на +219 мс, данные RUM уходят POST-запросом на /cdn-cgi/rum. Фактический аналитический сервис и его провайдер (Cloudflare Inc) в политике не раскрыты. 2) Политика прямо заявляет: «Ces données ne font pas l'objet d'un transfert en dehors du territoire de l'Union européenne». Загрузка beacon.min.js с static.cloudflareinsights.com передаёт IP посетителя Cloudflare Inc — американской компании — до согласия. Абсолютное заявление об отсутствии передачи за пределы ЕС вступает в противоречие с фактической передачей данных получателю из США. Полная техническая документация опубликована по адресу: https://gdpru.eu/en/audits/fr-interieur-gouv-fr/ 3. Положения GDPR, соблюдение которых прошу проверить GDPR Art. 13(1)(e) — раскрытие получателей и инструмента; GDPR Art. 44 (Chapter V) + Art. 5(1)(a) — трансграничная передача и прозрачность 4. Требование Прошу проверить изложенные обстоятельства и, если несоответствие подтвердится, принять меры, предусмотренные статьёй 58(2) GDPR. 5. Приложения Полная доказательная база — HAR-файл, контрольная сумма SHA-256 и цитата из политики конфиденциальности сайта, документирующая указанное противоречие — опубликована и проверяема по ссылке в пункте 2 выше. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Complaint regarding personal data processing — interieur.gouv.fr
1. Subject of the complaint
I am filing a complaint regarding the processing of my personal data by the website interieur.gouv.fr.
2. Circumstances
I visited the website interieur.gouv.fr and found indications that the processing of my personal data does not comply with the GDPR. The technical analysis published on gdpru.eu on 2 July 2026 (open methodology, reproducible measurements) documents the following indications:
1) The policy mentions audience measurement in general terms ('mesurer sa fréquentation') and names no specific tool. In the measurement, Cloudflare Web Analytics is at work: beacon.min.js loads from static.cloudflareinsights.com at +219 ms, with RUM data sent via a POST request to /cdn-cgi/rum. The actual analytics service and its provider (Cloudflare Inc) are not disclosed in the policy.
2) The policy states directly: 'Ces données ne font pas l'objet d'un transfert en dehors du territoire de l'Union européenne.' Loading beacon.min.js from static.cloudflareinsights.com transmits the visitor's IP address to Cloudflare Inc — a US company — before consent. The absolute claim of no transfer outside the EU is contradicted by the actual data transfer to a recipient in the USA.
Full technical documentation is published at: https://gdpru.eu/en/audits/fr-interieur-gouv-fr/
3. GDPR provisions I ask you to examine
GDPR Art. 13(1)(e) — disclosure of recipients and the tool; GDPR Art. 44 (Chapter V) + Art. 5(1)(a) — cross-border transfer and transparency
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]