Cookie policy
Description of storage and measurement technologies found in the website code.
Necessary technologies and preferences
The code stores the optional choice in localStorage under sardiniakey_cookie_consent_v1; no expiry is configured. The footer Cookie preferences button reopens the panel. The choice is stored on the device and can be cleared through browser settings.
The consent panel opens automatically only on Host campaign landing pages when no choice is saved. It does not open automatically on other pages. This difference should be assessed against the Italian DPA Guidelines and is not changed by this patch.
Meta measurement
The code loads fbevents.js from connect.facebook.net and initialises Meta Pixel 2490022531506762 when an accepted choice exists and an event is requested. PageView is invoked on Host campaign landing pages with an accepted choice; Lead is invoked by the Host application form. PageView on other pages is not asserted.
Meta may set or read identifiers such as _fbp and _fbc. The reject/revoke code calls the revocation command and attempts to remove these identifiers at path /. Any expiry set by Meta and their actual presence in browsers have not been verified.
Choice and withdrawal
On campaign landing pages, the panel allows users to accept or reject measurement, and the footer allows preferences to be reopened. On rejection or withdrawal, code prevents subsequent events based on the preference and attempts to remove _fbp and _fbc accessible to the site.
Actual behaviour and a complete cookie/technology inventory must be checked in a browser for each route before final publication. No trackers were added by this change.
Provider and updates
Meta Platforms’ own information also applies to Meta processing. This notice may be updated following technical, operational, or legal changes.