The website of the city of Rome (Roma Capitale). 272 requests, 23 domains. Two parallel Matomos, Google Analytics 4, a chatbot via Microsoft's infrastructure, Google translation, an accessibility widget and a video portal — an extensive technology stack, of which the policy names not a single tool, limiting itself to general navigation data and social-network plugins.
Request timeline
Declared versus actual
Detected trackers
- Matomo (/matomo/, idsite=1) — carries the visitor identifier
- Matomo (/matomo-apprc/, idsite=5) — carries the visitor identifier
- Google Analytics 4 (G-FWY4SWRLK5) — real hits without a consent flag
- Julia chatbot via Microsoft Bot Framework (europe.directline.botframework.com)
- Google Translate (translate.google.com, translate.googleapis.com)
- AccessiWay (acsbapp.com, embeds.accessiway.com) — accessibility widget
- Streamcloud (collector-ovp.streamcloud.it) — video portal
- Iubenda (accessibility widget)
Indicators of GDPR non-compliance
- Art. 13(1)(e) GDPR — the real stack is not declaredThe policy describes only general navigation data and, separately, social-network plugins (with the caveat that without active use they set no cookies). In reality, two Matomo instances (both with a visitor identifier), Google Analytics 4, a chatbot via Microsoft's infrastructure, Google Translate, the AccessiWay accessibility widget and a video portal on the Streamcloud platform work on the site. Not one of these tools is named in the policy.
- Art. 13(1)(f) GDPR — transfer to the USA without disclosureAmong the data recipients are Google, Microsoft and AccessiWay (American services). Google Analytics, meanwhile, sends real measurements without any consent-state flag. There is no section on the transfer of data outside the EU/EEA in the policy at all, although such a transfer does actually occur.
Context
www.comune.roma.it is the official website of the municipality of Rome, the capital commune Roma Capitale. An in-house-developed platform, with a self-made cookie bar. The capture shows 272 requests to 23 domains — including its own video portal with streaming video. Roma Capitale 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. The capital’s site carries an extensive technology stack: dual analytics, a chatbot, translation, accessibility, video. And almost none of this is described in the policy.
Who receives the data
Spotted here were: Google, Microsoft, AccessiWay, Streamcloud, Iubenda.
Was there a consent banner
Consent here is arranged in a peculiar way. Cookie management is handled by Roma Capitale’s in-house bar, which loads early, at +2721 ms, and with parameters that permit third-party components. And the Iubenda system, used on other sites as a consent banner, is connected here only for the accessibility widget — it has nothing to do with cookie management. There is no recorded «accepted/declined» event in the capture, and the analytics fires later without any sign that the bar held it back. It is telling that Google Analytics goes out without any consent-state flag at all — that is, it sends real measurements without checking against the user’s choice.
The third case of double Matomo in the series
Two different Matomo instances work in parallel on the site — on the same domain but in different paths, with different site identifiers. Both record the same page view almost synchronously, and both carry the visitor identifier. This is already the third such case after the medicines agency and the research council. It seems that the parallel installation of several independent counters — for different systems or contractors of one organisation — is a frequent phenomenon in large Italian government structures. But unlike the research council, where the counters worked without an identifier, here both assign the visitor a marker, so the «anonymity» of this statistics is conditional.
A chatbot that goes through Microsoft
The Julia chatbot deserves separate attention. Technically it works not on the city’s own infrastructure, but through Microsoft’s cloud platform. This means that the user’s dialogue with the bot passes through an American company’s service. On a city hall’s site, where a person may ask a question with personal details, this is significant — but neither the chatbot itself, nor still less whose infrastructure it works through, is mentioned in the policy.
The policy describes only the most general
The document limits itself to two subjects: the general navigation data that the site receives inevitably, and social-network plugins. It also contains a phrase precise in its own way — that the cookies are configured so as to set nothing on visiting a page; and this is even confirmed by the capture, where there is indeed not a single Set-Cookie. But beyond this narrow truth the document stays silent about everything that actually works: the two counters with a visitor identifier, Google Analytics, the chatbot on Microsoft’s infrastructure, the Google translator, the accessibility widget and the video portal. There is no section on the transfer of data outside the EEA at all, although the recipients are American.
What cannot be claimed from the capture
A few honest caveats. There is no recorded consent event in the capture, so on the operation of the in-house bar I judge from the load order, not from someone’s click; but the absence of a consent-state flag on Google Analytics is a fact from the requests themselves. The content of the dialogue with the chatbot I do not observe and do not claim that anything was entered into it — this is about the channel through which it passes. The visitor identifier of both counters is visible right in the parameters. The capture covers the public home page.
Conclusion
The website of Italy’s capital carries a large and heterogeneous technology stack — two counters with a visitor identifier, Google Analytics with no regard for consent, a chatbot via Microsoft’s infrastructure, translation from Google, an accessibility widget and a video portal. The policy, meanwhile, describes only the most general, inevitable navigation data and social-network plugins, naming not one of these tools and staying silent about the transfer of data across the ocean. The main takeaway for the reader: the larger the government structure, the longer its technology tail — and the more noticeable the gap between what the site actually does and the short paragraph with which it describes it.
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.
1bbecf4b6861d724f11aa891d9267d3591efb7b406a4fa23b965a2fe551014adWant 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) — comune.roma.it Кому: [укажите адрес компании — DPO / поддержка / юридический отдел] От: [Ваше имя], [контактный email] Прошу предоставить доступ к моим персональным данным, обрабатываемым в связи с использованием сайта comune.roma.it. 1. Категории данных и цели обработки (ст. 15(1)(a)-(c)) На основании независимого технического анализа сайта прошу подтвердить и подробно раскрыть следующие категории обработки: 1) Политика описывает только общие данные навигации и отдельно — плагины соцсетей (с оговоркой, что без активного использования они cookie не ставят). Реально же на сайте работают два экземпляра Matomo (оба с идентификатором посетителя), Google Analytics 4, чат-бот через инфраструктуру Microsoft, Google Translate, виджет доступности AccessiWay и видеопортал на платформе Streamcloud. Ни один из этих инструментов в политике не назван. 2) Среди получателей данных — Google, Microsoft и AccessiWay (американские сервисы). Google Analytics при этом отправляет реальные замеры без какого-либо флага состояния согласия. Раздела о передаче данных за пределы ЕС/ЕЭЗ в политике нет вовсе, хотя такая передача фактически происходит. 2. Получатели, сроки хранения и передача за пределы ЕЭЗ (ст. 15(1)(c)-(d), 46) Прошу также указать полный список третьих лиц-получателей, применимые сроки хранения по каждой категории и правовые основания передачи данных за пределы ЕЭЗ, если таковая происходит. Полный технический разбор с доказательствами (сохранённый сетевой журнал, контрольная сумма SHA-256) опубликован по адресу: https://gdpru.eu/en/audits/it-comune-roma-it/ 3. Автоматизированная обработка и профилирование (ст. 15(1)(h)) Прошу сообщить, применяется ли в отношении меня автоматизированное принятие решений или профилирование, и если да — раскрыть логику такой обработки. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Data access request (GDPR Art. 15) — comune.roma.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 comune.roma.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 describes only general navigation data and, separately, social-network plugins (with the caveat that without active use they set no cookies). In reality, two Matomo instances (both with a visitor identifier), Google Analytics 4, a chatbot via Microsoft's infrastructure, Google Translate, the AccessiWay accessibility widget and a video portal on the Streamcloud platform work on the site. Not one of these tools is named in the policy. 2) Among the data recipients are Google, Microsoft and AccessiWay (American services). Google Analytics, meanwhile, sends real measurements without any consent-state flag. There is no section on the transfer of data outside the EU/EEA in the policy at all, although such a transfer does actually occur. 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-comune-roma-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)
Тема: Жалоба на обработку персональных данных — comune.roma.it 1. Предмет жалобы Я подаю жалобу в отношении обработки моих персональных данных сайтом comune.roma.it. 2. Обстоятельства Я посетил сайт comune.roma.it и обнаружил признаки несоответствия обработки моих персональных данных требованиям GDPR. Технический разбор, опубликованный на gdpru.eu 15.06.2026 (открытая методология, воспроизводимые измерения), документирует следующие признаки: 1) Политика описывает только общие данные навигации и отдельно — плагины соцсетей (с оговоркой, что без активного использования они cookie не ставят). Реально же на сайте работают два экземпляра Matomo (оба с идентификатором посетителя), Google Analytics 4, чат-бот через инфраструктуру Microsoft, Google Translate, виджет доступности AccessiWay и видеопортал на платформе Streamcloud. Ни один из этих инструментов в политике не назван. 2) Среди получателей данных — Google, Microsoft и AccessiWay (американские сервисы). Google Analytics при этом отправляет реальные замеры без какого-либо флага состояния согласия. Раздела о передаче данных за пределы ЕС/ЕЭЗ в политике нет вовсе, хотя такая передача фактически происходит. Полная техническая документация опубликована по адресу: https://gdpru.eu/en/audits/it-comune-roma-it/ 3. Положения GDPR, соблюдение которых прошу проверить Art. 13(1)(e) GDPR — реальный стек не задекларирован; Art. 13(1)(f) GDPR — передача в США без раскрытия 4. Требование Прошу проверить изложенные обстоятельства и, если несоответствие подтвердится, принять меры, предусмотренные статьёй 58(2) GDPR. 5. Приложения Полная доказательная база — HAR-файл, контрольная сумма SHA-256 и цитата из политики конфиденциальности сайта, документирующая указанное противоречие — опубликована и проверяема по ссылке в пункте 2 выше. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Complaint regarding personal data processing — comune.roma.it 1. Subject of the complaint I am filing a complaint regarding the processing of my personal data by the website comune.roma.it. 2. Circumstances I visited the website comune.roma.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 describes only general navigation data and, separately, social-network plugins (with the caveat that without active use they set no cookies). In reality, two Matomo instances (both with a visitor identifier), Google Analytics 4, a chatbot via Microsoft's infrastructure, Google Translate, the AccessiWay accessibility widget and a video portal on the Streamcloud platform work on the site. Not one of these tools is named in the policy. 2) Among the data recipients are Google, Microsoft and AccessiWay (American services). Google Analytics, meanwhile, sends real measurements without any consent-state flag. There is no section on the transfer of data outside the EU/EEA in the policy at all, although such a transfer does actually occur. Full technical documentation is published at: https://gdpru.eu/en/audits/it-comune-roma-it/ 3. GDPR provisions I ask you to examine Art. 13(1)(e) GDPR — the real stack is not declared; Art. 13(1)(f) GDPR — transfer 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]