At a Glance
- Optional Google Analytics is disabled
- Sign-in needs essential browser storage
- Clearing storage can remove checkout drafts
This summary does not replace the complete policy below.
1. What Browser Storage Means
Cookies are small values a site stores in your browser and can receive with later requests. Local storage, session storage, and IndexedDB are related browser technologies used by the application and its authentication provider. This policy covers those technologies, not only traditional cookies. The Privacy Policy explains related personal-data handling.
2. Storage Used by This Release
- Marketing sign-in session: the first-party __ba_session cookie (or a configured equivalent) lets the marketing site recognize a signed-in account. The current server configuration sets a five-day lifetime. In hosted production it is HttpOnly and Secure. Signing out requests its removal; browser settings can also remove it.
- Firebase authentication: Firebase stores authentication state and refresh information in browser-managed storage, such as IndexedDB or local storage, to maintain account access. Persistence depends on the sign-in context and browser. Support-preview sessions use session-scoped persistence. Logging out ends the application session.
- Requested preferences: the theme key stores the light/dark appearance choice, and tab-scoped advisor settings can store whether order amounts are hidden. These support the interface choices you use, not advertising profiles.
- Application state: lastVisitTimestamp records a library visit in local storage. beatadvisor.checkout and request-draft entries in session storage retain checkout retry identity, selections, and typed instructions so a return from Stripe can restore the current purchase. Local storage persists until removed; session storage normally lasts for the tab session, but browser session restoration can preserve it.
- Provider contexts: Google sign-in and Stripe’s hosted checkout/onboarding can use their own cookies or storage for authentication, payment security, fraud prevention, and provider functionality. Their current inventories and lifetimes are governed by their own notices rather than a fixed list controlled by BeatAdvisor.
3. Optional Analytics and Advertising
This release does not initialize Google/Firebase Analytics even if a measurement ID is configured. No advertising pixel or optional analytics consent banner is included. We will not enable optional tracking merely because you continue browsing or accept service terms; any required prior consent and a usable withdrawal mechanism must be implemented first.
Disabling analytics in this release does not automatically delete cookies left by an earlier release or by another website. A browser’s Global Privacy Control or Do Not Track setting does not disable essential authentication or payment processing. Where an opt-out signal creates a legal obligation, it must be honored; this release has no advertising sale/share feature to toggle.
4. Your Controls
You can inspect, block, or delete cookies and site data through your browser settings and sign out when using a shared device. Blocking essential authentication or payment storage may prevent login or checkout. Clearing site data can discard local preferences and unsent request drafts, but does not cancel an order or erase server-side records.
Use the site’s account and order controls, or contact support, for cancellation and data requests. For provider-specific storage, review Google’s and Stripe’s current notices. Questions about BeatAdvisor storage can be sent to support@beatadvisor.com.
Questions About This Policy?
Include your order number when relevant. Never email passwords or full card details.
support@beatadvisor.com