Cookies Policy

Starlet may use cookies and similar browser storage technologies to support basic website functionality. This static demo uses local browser storage to remember whether a visitor selected Accept or Decline on the cookie banner. No server-side cookie database is included in the downloadable project.

Essential storage helps the interface remember basic preferences and operate consistently. A production deployment may add analytics, conversion measurement, fraud prevention, or embedded services, but those technologies should be disclosed before use and configured in accordance with applicable privacy law. Non-essential tracking should not be silently added to this static project.

Visitors can generally clear cookies and local storage through their browser settings. Clearing the stored cookie choice may cause the banner to appear again. Browser privacy modes, content blockers, and device settings may change how storage behaves.

If a production Starlet deployment uses Stripe, analytics, customer-support tools, or other third-party services, the operator should list those providers, describe their purposes, and link to their applicable policies. The static demo does not itself transmit payment details, uploaded photos, or support forms to a server.

This policy should be reviewed whenever vendors, analytics tools, domains, consent mechanisms, or storage technologies change. The company contact fields are intentionally blank in this demo and should be replaced with the actual privacy contact before launch. Nothing in this policy removes rights granted by applicable privacy or consumer-protection law.

For a production site, the consent banner should accurately reflect the actual technologies loaded on each page and should not describe storage that the deployment does not use. Consent choices should be respected by analytics and marketing scripts, and the privacy notice should explain how visitors can exercise applicable rights.

Visitors should also review their browser controls for blocking third-party content, clearing stored preferences, and limiting cross-site tracking. If the production service changes its consent mechanism, the banner, policy, and actual technical behavior should be updated together so that the published notice remains an accurate description of the site.