Cookie & Local Storage Policy
1. This static site uses browser localStorage for small pieces of functional state: the demo cart, cookie-choice preference, and checkout state
This static site uses browser localStorage for small pieces of functional state: the demo cart, cookie-choice preference, and checkout state. The site does not require a server-side cookie for the basic storefront flow.
2. The preference banner offers Accept and Decline controls
The preference banner offers Accept and Decline controls. The selected choice is stored locally in the browser. Clearing site data removes that preference and any cart stored by this project.
3. A production service may use cookies or similar technologies for authentication, security, analytics, preferences, and payment flows
A production service may use cookies or similar technologies for authentication, security, analytics, preferences, and payment flows. Such technologies should be disclosed according to the jurisdictions and services involved.
4. Because this build has no backend, it does not use localStorage as a substitute for secure account storage
Because this build has no backend, it does not use localStorage as a substitute for secure account storage. Do not place passwords, payment card data, or other sensitive secrets into the demo cart.
5. Third-party resources such as Google Fonts may make network requests when a visitor loads the site
Third-party resources such as Google Fonts may make network requests when a visitor loads the site. If a deployment requires stricter privacy or offline behavior, fonts can be self-hosted and the external font links removed.
6. Questions about this policy can be raised through the Contact page
Questions about this policy can be raised through the Contact page. The company contact fields remain blank until the owner supplies them.
Last updated: September 21, 2026.
Additional guidance
Visitors who prefer not to retain local state can clear site data in their browser. Because localStorage is device-specific, a different browser or private window may show a fresh cart and preference state. The static site does not treat the cookie banner as consent for unrelated tracking. If analytics or advertising tools are added, their collection and consent behavior should be disclosed separately. A deployment can also remove Google Fonts and serve self-hosted fonts if reducing third-party requests is important. These choices should be documented before a production launch.