Policy changed — see what exactly · 2026-10-02 →
France's national health insurance — 42 requests, 7 domains. Piano Analytics audience measurement correctly operates in OPT-OUT mode. But Google Campaign Manager / DoubleClick sends a page_view carrying the medical page's URL to Google's advertising infrastructure with no consent given — advertising does not qualify for the consent exemption.
Request timeline
Declared versus actual
Transfer timings
GTM-53ZCDGR — the container. Google, USA.
Piano Analytics, idclient=OPT-OUT. Correctly exempt from consent.
Campaign Manager / DoubleClick DC-15137949, page_view carrying the page URL. Google, USA.
Detected trackers
- Google Tag Manager (www.googletagmanager.com, GTM-53ZCDGR)
- Google Campaign Manager / DoubleClick (DC-15137949, pagead2.googlesyndication.com)
- AT Internet / Piano Analytics (tag.aticdn.net, logs1412.xiti.com) — with OPT-OUT
- jsDelivr CDN (cdn.jsdelivr.net)
Indicators of GDPR non-compliance
- ePrivacy / Art. 82 Loi Informatique et Libertés + GDPR Art. 6(1)Google Campaign Manager / DoubleClick (the GTM-53ZCDGR container activates gtag DC-15137949) sends a request to pagead2.googlesyndication.com/ccm/collect with a page_view event at +648 ms. Session state: no consent — Xiti transmits idclient=OPT-OUT, zero Set-Cookie for the entire session. Despite this, Google's advertising tracker fires. By the policy's own wording, Campaign Manager serves to 'mesurer l'efficacité de nos campagnes' — this is advertising measurement, which does not qualify for the consent exemption reserved for audience-measurement tools alone (Piano Analytics).
- GDPR Art. 9 (context) / Art. 5(1)(a)The dl parameter of the ccm/collect request carries the full URL of the page being viewed — a section on the childbirth benefit on the health insurance portal. Information about which medical topic the visitor is reading goes to Google's advertising infrastructure before any consent.
Context
ameli.fr is the official portal of Assurance Maladie, France’s national compulsory health insurance system. Through it, insured persons manage reimbursements, sick leave, medical appointments, and benefits. Controller: l’Assurance Maladie. The privacy policy is extensive (roughly 64,000 characters) and detailed. Measurement: 42 requests, 7 domains, captured on a clean browser, on an actualités page about the new-parent benefit.
Who receives data directly
Google LLC (USA) — a page_view event carrying the full URL of the medical page being viewed, via Campaign Manager / DoubleClick, with no consent given.
Declared versus actual
ameli’s policy discloses data recipients in detail and, unlike a number of other government sites, honestly names its American sub-processors: Doubleclick (Google) and Campaign Manager are named directly, and the transfer to the USA is stated with its legal basis (an adequacy decision). Piano Analytics is declared as an audience-measurement tool exempt from consent, with an accessible “Refuser” button. The measurement confirms this: the Xiti/Piano beacon goes out carrying idclient=OPT-OUT, and no cookies are set. On this front, the policy matches the facts.
The discrepancy lies in the legal category assigned to Campaign Manager. Under French law, the consent exemption applies only to audience measurement meeting CNIL’s conditions. Campaign Manager / DoubleClick, by the policy’s own wording, serves to measure the effectiveness of advertising campaigns — this is advertising processing, requiring prior (opt-in) consent. In the measurement, the session state is unambiguously “no consent”: Xiti in OPT-OUT, zero cookies. Despite this, at +648 ms a request to pagead2.googlesyndication.com/ccm/collect carrying a page_view event goes out to Google. The advertising tracker is not held back by the opt-out state.
What is transmitted
The dl parameter of the ccm/collect request carries the full address of the page being viewed — a section on the childbirth benefit. In other words, what is transmitted to Google’s advertising infrastructure is not merely the fact of a visit to ameli.fr, but the specific medical topic the visitor is interested in — on the national health insurance portal, before any consent.
What cannot be claimed from the measurement
The measurement covers a single page in the actualités section. The transfer to the USA itself is disclosed by the policy, backed by an adequacy decision — the subject of the non-compliance is not the fact of the transfer, but the advertising tracker firing with no consent. The conclusion that Campaign Manager belongs to the advertising category rests on the policy’s own explicit wording (“efficacité de nos campagnes”) and on the technical nature of the domain pagead2.googlesyndication.com. Behavior following an “Accepter” click is not observed in this session; what is recorded here is specifically the opt-out/no-consent state.
Conclusion
ameli.fr has built the audience-measurement side correctly: Piano Analytics runs in OPT-OUT mode, no cookies are written, and opting out is available. The policy is transparent in disclosing recipients and the transfer to the USA. But the advertising layer ignores this opt-out state: Google Campaign Manager / DoubleClick, via the GTM container, sends a page_view carrying the medical page’s URL to Google’s infrastructure even though there is no consent, and advertising does not qualify for the consent exemption. For a compulsory health insurance portal, transmitting the topic of the medical page being read to an advertising system before consent indicates non-compliance with the requirements on legal basis and prior consent for advertising trackers. Remedy: gate Campaign Manager’s activation on the outcome of the consent module’s choice, the same way this has already been done for the audience-measurement layer.
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.
f0978babf21b2ae4dd39fe8c22bedaa2859233c8d6ed4ad47571c16b11006d3dWant 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) — ameli.fr Кому: [укажите адрес компании — DPO / поддержка / юридический отдел] От: [Ваше имя], [контактный email] Прошу предоставить доступ к моим персональным данным, обрабатываемым в связи с использованием сайта ameli.fr. 1. Категории данных и цели обработки (ст. 15(1)(a)-(c)) На основании независимого технического анализа сайта прошу подтвердить и подробно раскрыть следующие категории обработки: 1) Google Campaign Manager / DoubleClick (контейнер GTM-53ZCDGR активирует gtag DC-15137949) отправляет запрос pagead2.googlesyndication.com/ccm/collect с событием page_view на +648 мс. Состояние сеанса — без согласия: Xiti передаёт idclient=OPT-OUT, Set-Cookie за весь сеанс ноль. Несмотря на это, рекламный трекер Google срабатывает. Campaign Manager по собственной формулировке политики служит для «mesurer l'efficacité de nos campagnes» — это рекламное измерение, которое не подпадает под освобождение от согласия, предусмотренное только для аудиторных инструментов (Piano Analytics). 2) В параметре dl запроса ccm/collect передаётся полный URL просматриваемой страницы — раздел о пособии по рождению ребёнка на портале медицинского страхования. Информация о том, какую медицинскую тему читает посетитель, уходит в рекламную инфраструктуру Google до какого-либо согласия. 2. Получатели, сроки хранения и передача за пределы ЕЭЗ (ст. 15(1)(c)-(d), 46) Прошу также указать полный список третьих лиц-получателей, применимые сроки хранения по каждой категории и правовые основания передачи данных за пределы ЕЭЗ, если таковая происходит. Полный технический разбор с доказательствами (сохранённый сетевой журнал, контрольная сумма SHA-256) опубликован по адресу: https://gdpru.eu/en/audits/fr-ameli-fr/ 3. Автоматизированная обработка и профилирование (ст. 15(1)(h)) Прошу сообщить, применяется ли в отношении меня автоматизированное принятие решений или профилирование, и если да — раскрыть логику такой обработки. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Data access request (GDPR Art. 15) — ameli.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 ameli.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) Google Campaign Manager / DoubleClick (the GTM-53ZCDGR container activates gtag DC-15137949) sends a request to pagead2.googlesyndication.com/ccm/collect with a page_view event at +648 ms. Session state: no consent — Xiti transmits idclient=OPT-OUT, zero Set-Cookie for the entire session. Despite this, Google's advertising tracker fires. By the policy's own wording, Campaign Manager serves to 'mesurer l'efficacité de nos campagnes' — this is advertising measurement, which does not qualify for the consent exemption reserved for audience-measurement tools alone (Piano Analytics). 2) The dl parameter of the ccm/collect request carries the full URL of the page being viewed — a section on the childbirth benefit on the health insurance portal. Information about which medical topic the visitor is reading goes to Google's advertising infrastructure before any 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/fr-ameli-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)
Тема: Жалоба на обработку персональных данных — ameli.fr 1. Предмет жалобы Я подаю жалобу в отношении обработки моих персональных данных сайтом ameli.fr. 2. Обстоятельства Я посетил сайт ameli.fr и обнаружил признаки несоответствия обработки моих персональных данных требованиям GDPR. Технический разбор, опубликованный на gdpru.eu 02.07.2026 (открытая методология, воспроизводимые измерения), документирует следующие признаки: 1) Google Campaign Manager / DoubleClick (контейнер GTM-53ZCDGR активирует gtag DC-15137949) отправляет запрос pagead2.googlesyndication.com/ccm/collect с событием page_view на +648 мс. Состояние сеанса — без согласия: Xiti передаёт idclient=OPT-OUT, Set-Cookie за весь сеанс ноль. Несмотря на это, рекламный трекер Google срабатывает. Campaign Manager по собственной формулировке политики служит для «mesurer l'efficacité de nos campagnes» — это рекламное измерение, которое не подпадает под освобождение от согласия, предусмотренное только для аудиторных инструментов (Piano Analytics). 2) В параметре dl запроса ccm/collect передаётся полный URL просматриваемой страницы — раздел о пособии по рождению ребёнка на портале медицинского страхования. Информация о том, какую медицинскую тему читает посетитель, уходит в рекламную инфраструктуру Google до какого-либо согласия. Полная техническая документация опубликована по адресу: https://gdpru.eu/en/audits/fr-ameli-fr/ 3. Положения GDPR, соблюдение которых прошу проверить ePrivacy / Art. 82 Loi Informatique et Libertés + GDPR Art. 6(1); GDPR Art. 9 (контекст) / Art. 5(1)(a) 4. Требование Прошу проверить изложенные обстоятельства и, если несоответствие подтвердится, принять меры, предусмотренные статьёй 58(2) GDPR. 5. Приложения Полная доказательная база — HAR-файл, контрольная сумма SHA-256 и цитата из политики конфиденциальности сайта, документирующая указанное противоречие — опубликована и проверяема по ссылке в пункте 2 выше. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Complaint regarding personal data processing — ameli.fr 1. Subject of the complaint I am filing a complaint regarding the processing of my personal data by the website ameli.fr. 2. Circumstances I visited the website ameli.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) Google Campaign Manager / DoubleClick (the GTM-53ZCDGR container activates gtag DC-15137949) sends a request to pagead2.googlesyndication.com/ccm/collect with a page_view event at +648 ms. Session state: no consent — Xiti transmits idclient=OPT-OUT, zero Set-Cookie for the entire session. Despite this, Google's advertising tracker fires. By the policy's own wording, Campaign Manager serves to 'mesurer l'efficacité de nos campagnes' — this is advertising measurement, which does not qualify for the consent exemption reserved for audience-measurement tools alone (Piano Analytics). 2) The dl parameter of the ccm/collect request carries the full URL of the page being viewed — a section on the childbirth benefit on the health insurance portal. Information about which medical topic the visitor is reading goes to Google's advertising infrastructure before any consent. Full technical documentation is published at: https://gdpru.eu/en/audits/fr-ameli-fr/ 3. GDPR provisions I ask you to examine ePrivacy / Art. 82 Loi Informatique et Libertés + GDPR Art. 6(1); GDPR Art. 9 (context) / Art. 5(1)(a) 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]