The website of Italy's Ministry of Justice. 35 requests, 3 domains. The Web Analytics Italia government analytics is named in the policy and correctly described; YouTube is declared in privacy mode and with consent. The session-recording module that appeared on other government sites is not here. The declared matches the fact.
Request timeline
Declared versus actual
Detected trackers
- Web Analytics Italia / Matomo (ingestion.webanalytics.italia.it) — carries the visitor identifier, named in the policy
- YouTube in privacy mode (youtube-nocookie.com) — declared, with consent; did not activate in this session
Context
giustizia.it is the website of Italy’s Ministry of Justice. It is built on the standard government theme. The capture shows 35 requests to three domains: the site itself, the ministry’s own news portal and the national analytics platform. The ministry itself is correctly named as the data controller. The capture, like the whole series, was taken on a clean Edge browser with no VPN and no blocker. This is a clean result — and, pleasingly, exemplary in exactly those details where other sites in the series erred.
Who receives the data
Spotted here was: Web Analytics Italia (government-run, Italy). There are no third-party commercial recipients in this session.
Was there a consent banner
There is a cookie notice on the site. Government anonymous analytics is equated to technical means and requires no consent, so its firing is not in itself a violation. The embedded video, if it occurs on other pages, is declared in privacy mode and with consent. I will only note that the analytics measurement carries the visitor identifier, so the «anonymity» here, as on other government sites, comes with a slight caveat.
The declared matches the fact
The main merit of this site is the accuracy of the document. The policy names the Web Analytics Italia government analytics directly and correctly describes how it works. YouTube is described separately and carefully: it is stated that the video is embedded via the privacy domain youtube-nocookie.com and that consent is requested for third-party cookies. In the capture without consent the video did not activate. And, importantly, there is no session-recording module here — the very one that appeared in the series on the sites of the tax authority, the cybersecurity agency and even the government. The declared and the observed coincide.
Done right where others erred
The contrast is worth emphasising. The embedded video here is set up exactly as it should be: privacy mode plus consent. And this is precisely what the Court of Cassation — an institution of the same judicial system — did wrong, placing a regular YouTube embedding without a mention in the policy. And the session recording replicated across a number of government platforms is also absent here. That is, the ministry got right exactly the details on which others stumbled.
What cannot be claimed from the capture
A few honest caveats. The behaviour of the embedded video after consent I do not observe — in this session it did not launch; but in the document it is declared in privacy mode, which in itself is the right choice. On the IP masking in the analytics I judge from its default configuration; the visitor identifier, meanwhile, is visible in the capture. The analytics is government-run, so the question of the servers’ geography does not arise. The capture covers the home page.
Conclusion
A clean and exemplary result. The only analytics service is named and correctly described, the embedded video is set up in privacy mode and behind consent, there is no hidden session-recording module, nothing leaves the country. Against the backdrop of the related site of the same judicial system, where the video was connected in the regular way and without a mention, here one can see how the same tasks are solved correctly. The main takeaway for the reader: this is how a tidy government site should look — the declared tools are named, privacy modes are chosen where they exist, and reality does not diverge from the document.
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.
8f0e28f2e1a378b05fbec58a15daf71ea270c77a7a601885a0f5543ccdce3334Want 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) — giustizia.it Кому: [укажите адрес компании — DPO / поддержка / юридический отдел] От: [Ваше имя], [контактный email] Прошу предоставить доступ к моим персональным данным, обрабатываемым в связи с использованием сайта giustizia.it. 1. Категории данных и цели обработки (ст. 15(1)(a)-(c)) Прошу предоставить информацию по всем категориям, целям и получателям обработки моих данных на этом сайте — независимо от того, выявлены ли на сегодняшний день какие-либо несоответствия. 2. Получатели, сроки хранения и передача за пределы ЕЭЗ (ст. 15(1)(c)-(d), 46) Прошу также указать полный список третьих лиц-получателей, применимые сроки хранения по каждой категории и правовые основания передачи данных за пределы ЕЭЗ, если таковая происходит. Полный технический разбор с доказательствами (сохранённый сетевой журнал, контрольная сумма SHA-256) опубликован по адресу: https://gdpru.eu/en/audits/it-giustizia-it/ 3. Автоматизированная обработка и профилирование (ст. 15(1)(h)) Прошу сообщить, применяется ли в отношении меня автоматизированное принятие решений или профилирование, и если да — раскрыть логику такой обработки. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Data access request (GDPR Art. 15) — giustizia.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 giustizia.it. 1. Categories of data and purposes of processing (Art. 15(1)(a)-(c)) I request information on all categories, purposes, and recipients of my data processed on this site — regardless of whether any non-compliance has been identified to date. 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-giustizia-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]