Cookie Policy
WHAT COOKIES AND SIMILAR TECHNOLOGIES ARE
Cookies are small pieces of information stored by a browser that may be sent back to a website with later requests. Other technologies, such as local storage, keep information in the browser for scripts to read. Different rules and lifetimes can apply to each technology.
Local storage does not automatically send its contents with every request, but website scripts may read it and may transmit information. The use of local storage instead of a cookie does not, by itself, remove applicable privacy or consent requirements.
PREVIOUS-VISIT DISPLAY
The supplied LABSZPHC header code uses a local-storage value to display the previous visit recorded in the same browser storage area. It is not a complete account of visits across different browsers or devices.
Clearing this value resets the browser’s previous-visit reference. It does not delete server-side authentication records or enquiry messages. If the script remains enabled, it may create the value again on a later visit.
OTHER STORAGE — INVENTORY TO COMPLETE
[EDITOR: Replace this section with a verified inventory of technologies actually used on the live website. For each item, list its exact name, provider/domain, purpose, technology, duration, category, activation conditions and applicable choice mechanism. Remove services that are not used.]
- WordPress and security: check public visits separately from administrator login, forms and any comment functionality that is enabled.
- Contact-form protection: check whether Cloudflare Turnstile is deployed and which storage or device-access operations occur with the actual configuration. Do not assume all Cloudflare services use the same cookies.
- Language selection: check the active translation implementation, saved preferences and third-party requests.
- Embedded content: check externally hosted video, maps, social widgets and other embeds, if present.
- Analytics or advertising: confirm whether any are installed and active. Their use or absence has not been verified for this draft.
- Preference management: identify the storage used by any actual consent manager, including its retention period.
CONSENT AND OTHER PERMITTED USES
Whether a technology requires consent depends on its purpose and the rules that apply. Where prior consent is required, the technology must remain inactive until that consent is given. Any reliance on an exception must meet its conditions, including information or objection requirements where applicable.
Reading this policy, scrolling a page or accepting general website Terms is not, by itself, consent to optional tracking. A label such as “functional” or “security” does not automatically establish that every use is exempt.
[BEFORE PUBLICATION: Explain the actual controls for accepting, rejecting and changing choices, and for objecting where an applicable exception requires it. Add a working way to reopen those controls. Verify that rejection and withdrawal stop the relevant future storage/access operations. Do not add a decorative or non-working “Cookie Settings” button.]
MANAGING BROWSER STORAGE
Your browser’s privacy or site-data settings can generally be used to inspect, block or remove cookies and other stored website data. The available controls depend on the browser. Clearing only cookies may not clear local storage; check the site-data options as well.
Blocking or clearing storage may reset preferences, sign you out, or affect features that depend on it. Choices can differ between browsers and devices. Browser settings are an additional control, not a substitute for the website obtaining consent where required.
THIRD-PARTY CONTENT AND SERVICES
Where third-party services are actually used, the final inventory should identify them and explain when they load. Their privacy notices provide further information, but do not replace our responsibility to explain our own use of their technology.
[ADD VERIFIED PROVIDER INFORMATION AND POLICY LINKS ONLY FOR SERVICES USED. Confirm any third-party processing and international-transfer information against the final Privacy Policy.]
SERVER RECORDS ARE DIFFERENT
Cookies and local storage are not the same as records retained on a server. Removing browser data does not automatically delete product-code query history, security logs, emails or backups. Refer to the Privacy Policy for the purposes, retention and rights relating to those records.
Do not assume that a code has never been checked simply because a visit indicator resets or a public verification result shows no history.
UPDATES AND CONTACT
This policy should be updated when the website’s storage technologies or their purposes change. Where new consent or notice is required, updating the text alone is not sufficient.
For questions about cookies or browser storage, contact the privacy email above. For broader information about personal-data handling, see our Privacy Policy.
[LINK TO THE FINALISED PRIVACY POLICY AND COMPLETE THE CONTACT DETAILS BEFORE PUBLICATION.]