How NIS2SelfCheck currently handles cookies, browser storage, and third-party frontend resources.
The NIS2SelfCheck frontend can load Google Analytics 4 after the visitor grants analytics consent. When enabled, this is used to measure visits, traffic sources, campaign performance, and self-check funnel events.
Google Analytics 4 is enabled on this deployment, but analytics measurement remains blocked until the visitor accepts analytics cookies or similar browser storage through the consent banner.
If the visitor accepts analytics, Google may receive pageview data, referrer information, campaign parameters such as UTM tags, broad device and browser metadata, approximate location, and custom funnel events from the self-check flow.
When analytics is enabled, the site stores the visitor's cookie-consent choice in browser storage so the banner does not need to be shown on every page load. This preference record is used only to remember the visitor's analytics choice.
The self-check pages use standard browser requests and client-side JavaScript to run the questionnaire, scan progress updates, and report flow. These technical operations are used to provide the requested service.
Some parts of the flow can involve third parties that may use their own technologies when their services are loaded.
This statement reflects the current product setup. If the analytics setup changes materially or if other non-essential technologies such as marketing tags, embedded videos, chat widgets, or A/B testing tools are added later, this statement will be updated accordingly and the required consent posture should be reviewed again.
You can manage cookies and site data through your browser settings. Blocking some third-party resources may affect how parts of the frontend render, such as hosted fonts or payment pages.