Current design-stage status
This static mockup does not establish what cookies, browser storage, pixels, embedded media, or scripts the published site will use. Run a clean-browser scan of the production domain, including every route and third-party embed, before finalizing this notice.
Technology inventory
For every technology, record provider/name, purpose, category, data collected, duration, domain/scope, sharing/recipient, and whether it runs before a choice. Distinguish strictly necessary operation from analytics, personalization, and advertising only when those categories are actually present.
Notice, consent, and preference controls
Counsel and the privacy lead must determine jurisdiction-specific notice and consent requirements. If optional storage requires consent, prevent it from firing before valid choice, make refusal as usable as acceptance, store and honor preferences for the required duration, and offer an accessible way to change or withdraw the choice.
Third-party content and changes
Review video, maps, fonts, analytics, tag managers, and other embeds for calls made before consent, third-party cookies, and cross-border disclosure. Re-scan after deploy or vendor changes and keep this notice synchronized with the actual inventory.
Browser controls and contact
Browser controls may also limit local storage, but do not substitute them for any required site-level choice. Add the verified privacy contact and an update/effective date once assigned.