Cookie Policy — Working Draft

Working draft — details awaiting confirmation. This page is published to make the current position transparent. The outstanding business particulars and policy decisions are identified below; this draft does not represent a completed legal or compliance review.

About this working draft

Cookies and similar technologies can store information on a device or access information already stored there. Their purpose can include delivering a requested function, signing in, keeping a service secure, remembering a choice or measuring activity.

This draft is not a completed cookie inventory. Exact cookie or storage names, providers, durations and visitor-specific behaviour remain under review. No complete “cookie-free” or consent-compliance claim is made.

Current features and review status

Account and sign-in functions: the website uses WordPress administration. Authentication functions for signed-in administrators are separate from ordinary public browsing. Their actual storage names and lifetimes must be verified without exposing session values.
Enquiry security: honeypot and token-based spam protection are enabled for forms. Form analytics and IP logging are disabled. The storage behaviour of form protection and any hosting security layer still needs to be mapped.
Performance: page caching and browser caching support delivery of website resources. Caching does not, by itself, establish which cookies or similar storage are used. Any related visitor storage must be assessed in the inventory.
Optional integrations: no analytics or advertising account was connected during this project work. A wider review of existing code, hosting and third-party behaviour is still needed before treating that observation as a complete visitor inventory.

Consent and other applicable conditions

Whether storage needs consent or can rely on an exception depends on its actual purpose, operation and applicable rules. A feature should not be labelled essential simply because it is useful to the business.

Before adding or enabling an optional technology, its purpose, provider, data use and control requirements should be reviewed. Where consent is required, the technology needs to wait for a valid choice, and users need an accessible way to change that choice. Some exceptions can carry their own information and objection requirements.

Items still to be confirmed

The signed-out visitor inventory, including the first visit and form interactions.
The names, providers, purposes and durations of any cookies, local storage or comparable technologies.
Storage or logging introduced by hosting, security, embedded content or other third parties.
Which applicable requirements or exceptions govern each item, and whether a consent or objection mechanism is needed.
The operator details and final contact arrangements identified in the Privacy Policy.

Browser controls

Your browser provides controls for reviewing, blocking and deleting stored site data. Blocking storage needed for a requested feature can affect that feature, such as signing in. Browser controls do not replace any website-specific choice that applicable rules require.

This draft does not claim that a complete site-wide cookie preference centre has already been configured. Its design and descriptions should follow the verified inventory.

Changes to website technology

The inventory and this policy should be reviewed when analytics, advertising, chat, embedded media, form protection, caching, hosting or other integrations change. Relevant privacy information and user controls should be updated alongside the feature.

Related information

For a question about this page, use our Contact Us page or the website’s listed address, contact@nexlifty.com.