Cookie Policy

Current setup

The site is static and uses local images, styles, scripts, and fonts. It does not load advertising pixels, Google Analytics, external web fonts, embedded social feeds, maps, videos, live chat, or payment widgets. Contact forms on Cloudflare Workers Static Assets prepare an email draft instead of storing a submission in a website database.

Scripted demo storage

The chatbot demonstration uses no chat cookies or saved transcript. Conversation text stays in page memory, not on a server. Only an explicit Use brief in project form action stores the brief in this tab's session storage under locriva-support-brief-v1. The project form reads and removes it once; clearing the demo or ending the tab session also removes it. The form still prepares an email draft rather than sending it automatically.

Hosting logs

Cloudflare Workers Static Assets and network providers may process IP addresses, request times, user-agent data, and security logs needed to deliver and protect the service. These provider operations are not used by Locriva for advertising or visitor profiling.

Why there is no cookie banner

The current site does not intentionally place non-essential cookies, so it does not show a consent banner. This position must be tested again whenever hosting, analytics, media, booking, chat, payment, or marketing tools change.

If tools are added later

If analytics, embedded media, remarketing, booking, live chat, or payment tools are added, Locriva will document the provider, purpose, data, duration, and recipients. Where consent is required, those tools must remain blocked until a visitor actively accepts them, and refusing must be as clear as accepting.

Optional storage choices

The site can store your explicitly saved analytics and marketing preferences in browser local storage under locriva-consent-v1, for up to 180 days. It does not save your enquiry text there. No optional analytics or advertising provider is currently connected. You can reject optional categories or withdraw your choice on the Privacy choices page.

Introducing a provider requires a new consent version, updated information and a review of access, retention, transfer safeguards and cookie cleanup. These controls are a technical foundation, not a legal-compliance guarantee.