CURRENT STORAGE INVENTORY
Cookie Policy
This policy records the current static-build behavior. It must be updated before any analytics, advertising, embedded media, chat, payment, A/B testing or other storage technology is enabled.
1. Current inventory
| Category | Provider | Current status | Consent |
|---|---|---|---|
| Necessary cookies | None identified by the static site | Not set by project code | Not applicable |
| Analytics | None | Disabled | Required before activation where applicable |
| Advertising / social pixels | None | Disabled | Required before activation where applicable |
| Embedded third parties | None | Disabled | Assess before activation |
2. Consent and withdrawal
Because the current build does not set non-essential storage, it does not show a consent banner or a preference control. If non-essential storage is introduced, the implementation must provide an equally visible reject, settings and accept choice where required; keep optional technologies off before the relevant choice; record only the necessary consent state; and provide an immediate way to withdraw or change preferences.
3. Regional rules
Cookie and tracking rules differ by jurisdiction. EEA and UK deployment requires a review of the applicable cookie and privacy rules before optional storage is activated. United States requirements can vary by state and by the data or sharing involved. Each target market must be reviewed before technology is enabled for residents there.
4. Future changes
Before adding any tag, the operator must update the inventory with provider, purpose, categories of data, lifetime, recipient, activation condition and consent dependency. A tracker is not approved merely because a generic banner exists.