Cookie notice draft.
This page explains the basic cookie categories a final deployment may use.
The site may use essential cookies for page behavior, performance cookies for anonymous analytics, and preference cookies if you later add saved settings or a consent banner. If you keep the site simple, the cookie footprint can stay small.
Cookie categories
Essential cookies support basic site behaviour. Preference cookies remember a choice when such a feature exists. Measurement cookies help a publisher understand which pages are useful when analytics is enabled. Advertising cookies should not be introduced without a clear business purpose and an appropriate notice or consent process.
The actual cookie list should be reviewed whenever analytics, video embeds, advertising, or third-party forms are added.
Keeping the notice accurate
A cookie notice is only useful when it matches the services running on the site. The publication should review it after theme, analytics, advertising, consent, or form changes and remove descriptions for tools that are no longer active.
Reviewing consent and settings
Where consent is required, visitors should be able to understand the purpose before accepting a non-essential cookie and should not be forced to provide more information than the site needs. A refusal or withdrawal path should be as clear as the acceptance path.
Technical changes should trigger a review of the notice, consent records, third-party scripts, and any privacy documentation.
What visitors should be told
A useful notice names the service, explains its purpose, identifies whether it is essential or optional, and states how a visitor can change the choice later. The notice should use ordinary language rather than hiding the practical effect in technical terms.
Cookie descriptions should never promise that a service is inactive when its script is still present. The site owner should test the actual browser storage and network requests after each major change.