The website of Federcostruzioni — the federation of industry associations of Italy's construction sector (WordPress). 130 requests, 8 domains. The policy categorically excludes any tracking methods except session cookies — but on the home page the AddToAny social-network widget, regular YouTube and Google Fonts are active, transmitting the IP to the USA.
Request timeline
Declared versus actual
Detected trackers
- AddToAny (static.addtoany.com) — social-network widget with tracking
- YouTube in regular mode ([www.youtube.com](https://www.youtube.com), i.ytimg.com) — transmits the IP to Google, USA
- Google Fonts (fonts.googleapis.com, fonts.gstatic.com) — transmit the IP to Google, USA
- Font Awesome from BootstrapCDN
Indicators of GDPR non-compliance
- Art. 5(1)(a) and Art. 13(1)(e) GDPR — a categorical «no tracking» against the factThe policy explicitly and without reservation states: no profiling cookies are used and no other tracking methods are applied — only strictly necessary session cookies. This is directly refuted by the capture: on the home page the AddToAny social-network widget, embedded YouTube videos in regular mode and Google Fonts are active. All of them reach out to third-party servers, transmitting the visitor's IP address. This is not a gap in the list, but a contradiction of the document's very assertion.
- Art. 13(1)(f) GDPR — transmission of the IP to the USA without disclosureThe regular embedding mode of YouTube and the Google fonts transmit the visitor's IP to Google (USA); AddToAny is also an American service. There is no section on the transfer of data outside the EU in the policy. The consent plugin is installed on the site, but it holds back none of these services — they load independently of it.
Context
www.federcostruzioni.it is the website of Federcostruzioni, the federation of industry associations of Italy’s construction sector, uniting large sectoral bodies. It is built on WordPress. The capture shows 130 requests to eight domains. The federation itself is correctly named as the data controller, and the policy, unlike some sites in the series, relies on the regulation in force. The capture, like the whole series, was taken on a clean Edge browser with no VPN and no blocker. The case is interesting not for the volume of tracking — it is modest — but for the fact that the document here does not stay silent, but explicitly asserts the opposite of reality.
Who receives the data
Spotted here were: AddToAny, Google.
Was there a consent banner
The consent plugin is installed on the site — its code loads at the start of the visit. But it does not perform its task: the social-network widget, the Google fonts and the embedded videos load independently of it, without waiting for any user choice. That is, the banner is present formally, while the trackers do not depend on it.
The categorical «no tracking» — against the fact
Here is the main thing. Most sites in the series sin by omission — they do not name the tools used. This one goes further and states directly: there are no profiling cookies, and no other tracking methods are used, only strictly necessary session cookies. The capture refutes this in three places at once. On the home page the AddToAny social-network widget works, which by its nature collects data about visitors. YouTube videos are embedded. Google fonts are loaded. All three reach out to others’ servers and transmit the visitor’s IP address to them. This is not a gap in the list — it is a contradiction of the very text that assures there is nothing of the kind.
Where the data goes — to Google, USA
Of the three third-party services, two are Google: the embedded YouTube and the fonts. And the video is connected in regular mode rather than privacy mode, so the very loading of the player already reaches Google and takes the IP to the USA. The fonts are the same story: the site keeps some of them self-hosted, but some are still pulled from Google’s servers. AddToAny is also an American service. There is no section on the transfer of data outside the EU in the policy at all. All this is fixed in the standard way: privacy mode for the video and moving the fonts to one’s own server, all the more so since some of them are already there.
What cannot be claimed from the capture
A few honest caveats. The data collection by the AddToAny widget is its known business model, not a conclusion from the capture itself; in the capture I see the fact of its loading and the requests to its servers. With the embedded video the heavier requests to Google occur on playback, but loading the player in regular mode already transmits the IP. The contents of the cookies are not directly visible in the lightweight export. The capture covers the home page.
Conclusion
The volume of tracking here is small, but the problem is not in it, but in the document’s categorical nature. The policy explicitly asserts that no tracking methods except session cookies are used — while the home page itself refutes this three times over: the social-network widget, regular YouTube and Google fonts, all quietly reaching out to others’ servers, mostly to Google in the USA, and the installed consent plugin holds back none of them. The main takeaway for the reader: it is one thing to forget to mention a tool, and quite another to write outright «we do not have this» when it is there; here it is exactly the second case, and it is fixed in a couple of technical moves.
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.
dc478acb00b4abf485aedd4bf779a77114e67b31e6a829d2ce1ad1ff22b5e9e9Want 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) — federcostruzioni.it Кому: [укажите адрес компании — DPO / поддержка / юридический отдел] От: [Ваше имя], [контактный email] Прошу предоставить доступ к моим персональным данным, обрабатываемым в связи с использованием сайта federcostruzioni.it. 1. Категории данных и цели обработки (ст. 15(1)(a)-(c)) На основании независимого технического анализа сайта прошу подтвердить и подробно раскрыть следующие категории обработки: 1) Политика прямо и без оговорок заявляет: cookie для профилирования не используются и никакие другие методы трекинга не применяются — только строго необходимые сессионные cookie. Это прямо опровергается замером: на главной странице активны виджет соцсетей AddToAny, встроенные видео YouTube в обычном режиме и шрифты Google Fonts. Все они обращаются к серверам третьих сторон, передавая IP-адрес посетителя. Это не пробел в перечне, а противоречие самому утверждению документа. 2) Обычный режим встраивания YouTube и шрифты Google передают IP посетителя в Google (США), AddToAny — также американский сервис. Раздела о передаче данных за пределы ЕС в политике нет. Плагин согласия на сайте установлен, но ни один из этих сервисов он не задерживает — они грузятся независимо от него. 2. Получатели, сроки хранения и передача за пределы ЕЭЗ (ст. 15(1)(c)-(d), 46) Прошу также указать полный список третьих лиц-получателей, применимые сроки хранения по каждой категории и правовые основания передачи данных за пределы ЕЭЗ, если таковая происходит. Полный технический разбор с доказательствами (сохранённый сетевой журнал, контрольная сумма SHA-256) опубликован по адресу: https://gdpru.eu/en/audits/it-federcostruzioni-it/ 3. Автоматизированная обработка и профилирование (ст. 15(1)(h)) Прошу сообщить, применяется ли в отношении меня автоматизированное принятие решений или профилирование, и если да — раскрыть логику такой обработки. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Data access request (GDPR Art. 15) — federcostruzioni.it 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 federcostruzioni.it. 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 explicitly and without reservation states: no profiling cookies are used and no other tracking methods are applied — only strictly necessary session cookies. This is directly refuted by the capture: on the home page the AddToAny social-network widget, embedded YouTube videos in regular mode and Google Fonts are active. All of them reach out to third-party servers, transmitting the visitor's IP address. This is not a gap in the list, but a contradiction of the document's very assertion. 2) The regular embedding mode of YouTube and the Google fonts transmit the visitor's IP to Google (USA); AddToAny is also an American service. There is no section on the transfer of data outside the EU in the policy. The consent plugin is installed on the site, but it holds back none of these services — they load independently of it. 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/it-federcostruzioni-it/ 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: Italian Data Protection Authority (Garante) — garanteprivacy.it
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)
Тема: Жалоба на обработку персональных данных — federcostruzioni.it 1. Предмет жалобы Я подаю жалобу в отношении обработки моих персональных данных сайтом federcostruzioni.it. 2. Обстоятельства Я посетил сайт federcostruzioni.it и обнаружил признаки несоответствия обработки моих персональных данных требованиям GDPR. Технический разбор, опубликованный на gdpru.eu 15.06.2026 (открытая методология, воспроизводимые измерения), документирует следующие признаки: 1) Политика прямо и без оговорок заявляет: cookie для профилирования не используются и никакие другие методы трекинга не применяются — только строго необходимые сессионные cookie. Это прямо опровергается замером: на главной странице активны виджет соцсетей AddToAny, встроенные видео YouTube в обычном режиме и шрифты Google Fonts. Все они обращаются к серверам третьих сторон, передавая IP-адрес посетителя. Это не пробел в перечне, а противоречие самому утверждению документа. 2) Обычный режим встраивания YouTube и шрифты Google передают IP посетителя в Google (США), AddToAny — также американский сервис. Раздела о передаче данных за пределы ЕС в политике нет. Плагин согласия на сайте установлен, но ни один из этих сервисов он не задерживает — они грузятся независимо от него. Полная техническая документация опубликована по адресу: https://gdpru.eu/en/audits/it-federcostruzioni-it/ 3. Положения GDPR, соблюдение которых прошу проверить Art. 5(1)(a) и Art. 13(1)(e) GDPR — категоричное «трекинга нет» против факта; Art. 13(1)(f) GDPR — передача IP в США без раскрытия 4. Требование Прошу проверить изложенные обстоятельства и, если несоответствие подтвердится, принять меры, предусмотренные статьёй 58(2) GDPR. 5. Приложения Полная доказательная база — HAR-файл, контрольная сумма SHA-256 и цитата из политики конфиденциальности сайта, документирующая указанное противоречие — опубликована и проверяема по ссылке в пункте 2 выше. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Complaint regarding personal data processing — federcostruzioni.it 1. Subject of the complaint I am filing a complaint regarding the processing of my personal data by the website federcostruzioni.it. 2. Circumstances I visited the website federcostruzioni.it and found indications that the processing of my personal data does not comply with the GDPR. The technical analysis published on gdpru.eu on 15 June 2026 (open methodology, reproducible measurements) documents the following indications: 1) The policy explicitly and without reservation states: no profiling cookies are used and no other tracking methods are applied — only strictly necessary session cookies. This is directly refuted by the capture: on the home page the AddToAny social-network widget, embedded YouTube videos in regular mode and Google Fonts are active. All of them reach out to third-party servers, transmitting the visitor's IP address. This is not a gap in the list, but a contradiction of the document's very assertion. 2) The regular embedding mode of YouTube and the Google fonts transmit the visitor's IP to Google (USA); AddToAny is also an American service. There is no section on the transfer of data outside the EU in the policy. The consent plugin is installed on the site, but it holds back none of these services — they load independently of it. Full technical documentation is published at: https://gdpru.eu/en/audits/it-federcostruzioni-it/ 3. GDPR provisions I ask you to examine Art. 5(1)(a) and Art. 13(1)(e) GDPR — a categorical «no tracking» against the fact; Art. 13(1)(f) GDPR — transmission of the IP to the USA without disclosure 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]