Cookie Policy

What the supplied code does

These files do not set cookies through JavaScript and include no analytics, advertising, external scripts, remote fonts or embedded third-party content. The only programmed storage is a closing preference in localStorage. Unlike cookies, localStorage remains in the browser and is not automatically attached to HTTP requests.

Key and contents

The key lixtyn_notice_v1 stores an object containing closed: true and expires, an expiry timestamp in milliseconds. It is written only when you select “Close notice”. It contains no name, email, form text or tracking identifier. This code does not send it to a server.

Duration and expiry

The preference is treated as valid for 180 days after closing. localStorage does not expire entries automatically: when a page next loads, the code checks the timestamp and removes an expired entry. If you do not return, the entry may remain until you remove it. If your browser blocks storage, closing still works for the current page, but the notice can reappear on another visit.

Removing the preference

Select “Show cookie notice” in the footer to remove the key and reopen the notice. You can also clear site data for lixtyn.pro in your browser privacy settings. Storage belongs to the browser and origin where you open the pages; it is not shared across devices. Removing it does not prevent reading the site or preparing an email.

Form fields and live hosting

The form uses its fields to prepare a mailto link and does not save them in localStorage. See the Privacy Policy for how email enquiries work.

This policy describes the supplied files. Hosting, a CDN or Cloudflare may introduce cookies, technical logs or scripts after publication. A ZIP check does not establish what the live site uses. Any added tools need a live-site check, an updated policy and appropriate consent controls.