Policy draft
Cookie policy
This draft records the current cookie posture and the decisions still required before production analytics or optional services are enabled.
01
Strictly necessary storage
The editorial CMS may use authentication and security cookies for authorised administrators. Public infrastructure may use necessary security or load-management storage depending on deployment configuration.
02
Optional analytics
Analytics is disabled by default and cannot load solely because a container ID is present. When configured, the site asks for an explicit choice before requesting Google Tag Manager, stores that choice locally, and lets visitors reopen Privacy settings to withdraw consent.
Analytics events are limited to bounded publication interactions and do not include newsletter email addresses or free-text form values. Advertising and monetisation remain separately disabled by default.
03
Cookie controls
The current analytics preference is stored under a versioned local-storage key. A future provider's cookie durations, provider identity, consent categories, regional behavior, and retention terms still require legal and technical approval before analytics is enabled in production.