Policy desk

Cookie Policy

This Cookie Policy explains the limited browser storage and preference behavior used by the BrassLedger static site.

What this site stores

The site uses browser localStorage rather than a custom server cookie system for several small pieces of interface state. The cart stores selected plan entries. A coupon key stores LEDGER10 when the user applies it. The cookie-notice choice stores whether the visitor accepted or declined the notice. These values support the static site's navigation and do not constitute a server-side customer account.

Why storage is used

Local storage lets the cart survive navigation between plan pages, cart.html, and checkout.html. It also prevents the notice from returning after a visitor records a preference. Without these values, a static site would need to rebuild the state every time a page changes.

Third-party content

The site loads Google Fonts for Rozha One and Work Sans. A browser may contact the font provider to retrieve those resources. The site does not include an advertising network or a third-party tracking script in this delivery.

Managing storage

Visitors can clear local website data through their browser settings. Clearing storage removes the local cart, coupon state, and notice preference. The site may then behave as if it is being visited for the first time. Browser privacy controls can also limit storage or external font loading, which may change presentation or functionality.

Cookies versus localStorage

The visible notice is called a cookie notice for familiarity, but this static implementation stores the choice in localStorage. localStorage is different from an HTTP cookie: it is scoped to the site's origin and is not automatically sent with every network request.

Production changes

If a future BrassLedger deployment adds authentication, analytics, billing, customer support, or other hosted services, the production privacy and cookie documentation should identify those services and the categories of storage they use. Consent requirements can vary by jurisdiction and by the purpose of a technology.

Contact

Company contact fields are currently blank. A live deployment should publish a privacy contact and keep this page synchronized with actual browser and third-party storage behavior.