Cookie Policy

No optional analytics or advertising tags are enabled by the website's integration configuration. There are no active customer payment or third-party embedded product services. A banner claiming that those technologies are in use would be misleading, so no such banner is displayed.

The site uses application scripts for navigation and interactive controls, and JSON-LD text for structured page information. It requests typefaces from Google Fonts. A font request is a third-party connection, not evidence that an analytics cookie exists; associated privacy and device-access behaviour still requires review.

The enquiry form does not save its field contents in cookies, local storage or session storage. A preference record named umbrella-it-consent-v1 is created in local storage only when you save technology preferences. It records the preference version, save time and optional category choices; it does not include enquiry details. Its purpose is to remember your choice, subject to legal approval of the eventual retention and permission design.

The Lovable editor preview can use managed authentication storage and an editor message bridge. This is distinct from the ordinary visitor enquiry experience. Hosting-issued cookies or scripts must be inventoried in the final production environment before approval; this draft does not invent their names or describe editor storage as visitor tracking.

Technologies necessary to deliver a requested service are assessed separately from optional analytics, advertising and embedded services. Optional categories are off by default. Current integrations in those categories remain disabled regardless of any saved preference.

Under current UK rules, some uses may qualify for specific exceptions if all conditions are met. We do not assume that an analytics tool is exempt merely because it is described as statistical. Required information, a simple means of objection where applicable, and any consent requirements need professional assessment before activation.

Use Technology preferences below or in the footer to review and change your choices. Currently inactive categories cannot be enabled through these controls. If optional services are authorised later, consent must be obtained before uses requiring it; declining must be as straightforward as accepting. Browser settings can also control storage, but removing it may remove a saved preference.

Future Google integrations must use one approved installation path and consent-aware controls. Compatibility preparations do not send information to Google or activate a tag. The legality of the final permission or exception model must be reviewed before tracking begins.