Core cookies keep things working.
Security and sign-in may need them.
Draft cookie policy · version 0.1
Cookies,explained plainly.
What the site may remember, what is necessary, and how optional choices will stay under your control.
The 60-second version
Four things worth remembering.
The production list will be finalised with the consent setup.
Optional means optional.
No consent, no non-essential cookie.
You can change your mind.
Controls should remain easy to reach.
The list matches reality.
The final table will follow the live site.
What cookies are
Cookies are small pieces of information stored by a site or browser to remember useful details.
Similar technology can include local storage, pixels or identifiers. The final policy will describe what the production site actually uses.
Necessary cookies
These support core functions such as security, network management and sign-in.
SecuritySessionPreferences
Because the service cannot work reliably without them, necessary cookies do not normally depend on optional consent.
Optional cookies
Optional tools may help understand performance or improve communications.
MeasurementUnderstand aggregate site performance.
CommunicationMeasure requested campaigns or updates.
The final policy will list each optional purpose and provider. Until consent is given, those tools should remain inactive.
The cookie list
The production version will name each cookie, provider, purpose and duration.
| Category | Purpose | Duration |
|---|---|---|
| Necessary | Secure session | Session |
| Preference | Remember choice | 6 months |
These sample rows are intentionally generic and must be replaced after the production consent and analytics setup is confirmed.
Your controls
You should be able to accept, reject or revisit optional choices without friction.
1 · ChooseAt first visit
2 · ReviewAny time
3 · ChangeWithout penalty
Browser controls can also delete or block cookies, although blocking necessary technology may affect how the service works.
Third-party services
Some providers may set or read information when their service is used.
No mystery providers
If another company receives cookie data, the production list should make that relationship visible.
The final policy will link to relevant provider information and distinguish first-party tools from third-party tools.
Changes to this list
The policy should change when the technology changes—not months later.
Material additions will be dated and, where required, presented for a fresh choice.
Questions and contact
Ask if a cookie or provider is unclear.
We will replace this draft with reviewed contact and complaint information before publication.