Cookie notice — launch draft.

This notice intentionally avoids describing cookies or tracking that have not been verified in the production environment.

Current build status

This build does not intentionally activate analytics, advertising pixels, a consent manager, or a working contact form. Production hosting and future services may still use logs, cookies, local storage, or similar technologies, so the live stack must be inspected before publication.

[PRODUCTION SCAN AND DATA-STACK INVENTORY REQUIRED]

Technologies in scope

The final notice should cover cookies and comparable browser or device storage, including who sets each technology, its purpose, duration, and whether it is required for a requested feature.

[COOKIE, LOCAL-STORAGE, SESSION-STORAGE, PIXEL, AND SDK INVENTORY TO ADD]

Categories and purposes

If the production site uses essential, preference, measurement, personalization, advertising, or other categories, describe only the categories actually found and use terms that match the consent interface and vendor contracts.

[VERIFIED CATEGORIES, PURPOSES, PROVIDERS, AND DURATIONS REQUIRED]

Controls and consent

Determine whether visitors need a consent banner or preference center, which technologies must remain off before a choice, how a choice can be changed, and whether browser signals such as Global Privacy Control require a response.

[JURISDICTIONS, CONSENT LOGIC, PREFERENCE TOOL, AND SIGNAL HANDLING TO CONFIRM]

Browser settings

Visitors can often control storage through their browser, but final instructions should not imply that browser settings provide every legally required choice or that disabling storage will affect features unless that behavior has been tested.

[TESTED EFFECTS OF DISABLING STORAGE AND SUPPORT GUIDANCE TO ADD]

Contact and updates

Add a monitored contact method, effective date, and process for updating this notice when the production data stack changes.

[PRIVACY CONTACT, EFFECTIVE DATE, CHANGE REVIEW, AND OWNER REQUIRED]