ingenio-web.it

Context

www.ingenio-web.it is an Italian engineering-and-construction technical portal, published by the company IMREADY Srl. The capture shows 64 requests to 12 domains, and almost all the external ones are Google services. The publisher is correctly named as the data controller, and the Klaro consent-management system is installed on the site. The capture, like the whole series, was taken on a clean Edge browser with no VPN and no blocker. The case is interesting in that, against the backdrop of the commercial sites in the series, it stands out favourably in its consent mechanics — and the analysis is mainly about what is done right.

Who receives the data

Spotted here were: Google, KIProtect.

Was there a consent banner

There is a banner — the Klaro system. And, unlike most commercial sites in the series, it works to the point: the consent-state flag is by default in the «declined» position. This means that before the user’s explicit consent, data collection is limited — which is confirmed further on.

Done mostly right

This is the main observation and a plus for the site. Google’s analytics sends a measurement with the flag «consent declined» — that is, in anonymised mode, without saving identifiers and cookies. The AdSense advertising, although it loads, is served in non-personalised form under declined consent — that is, selected by the page content rather than by the visitor’s profile. Throughout the whole session not a single cookie was set. In other words, before consent the site behaves restrainedly: no identifying analytics, no personalised advertising. This is the direct opposite of those commercial sites in the series where trackers merged the visitor’s identifiers from the first second.

The recipients are not named in the main document

The only real catch is about the document. The main policy names the publisher as the controller, mentions profiling among the possible purposes and stipulates that data may be transferred abroad — but all of this in general formulations. Specific services are not named: neither Google’s advertising system and analytics, nor the embedded search, nor the consent tool itself. Most likely the detailed list is moved to a separate part of the cookie policy, which is not in the export, so I record this as incompleteness of what is available rather than proven concealment.

What cannot be claimed from the capture

A few honest caveats. On the non-personalised advertising mode I judge from the declined consent flag and the absence of cookies; the content of the advertising response itself is not visible in the capture. There is no recorded click on the banner — the «declined» state is the default value, and it did not change in this session. I did not export the separate cookie documentation. The capture covers the home page.

Conclusion

The stack here is almost entirely from Google — advertising, analytics, search, tags — but it is assembled mostly correctly. Before consent the flag is in the «declined» position: the analytics goes without cookies and without identifiers, the advertising is in non-personalised mode, not a single cookie is set. This is noticeably closer to a correct implementation than most commercial sites in the series. The only unclosed point is documentary: the main policy names neither Google nor the consent tool, limiting itself to general words about profiling and transfer abroad. The main takeaway for the reader: even on a site where almost everything external belongs to Google, one can behave restrainedly before consent — and here this is mostly done; the questions remain about the completeness of the document, not the behaviour.