Cookie policy

STRUCTURE ONLY - NOT LEGAL TEXT. DO NOT PUBLISH.

The cookie policy must reflect the cookies actually set by the finished website, which cannot be known until the build, analytics, payment providers and any embedded media are in place. It must then be approved locally.

Sections each market must complete

What cookies are, in plain language.

A current inventory of the cookies used, grouped by purpose: strictly necessary, functional, analytics and marketing. Each entry needs the name, the provider, the purpose and the retention period.

Which cookies are set only after consent, and which are exempt.

How to give, change or withdraw consent, including a link that reopens the consent settings.

How to control cookies through the browser.

Any third-party cookies set by embedded content such as video, maps or donation forms.

The date the inventory was last reviewed.

Dependencies

Site Settings contains a cookieConsentEnabled toggle and a Google Tag Manager container field. The cookie inventory must match whatever those actually load in each market, and it must be re-checked whenever a tag is added.