Legal

Cookie Policy

This Cookie Policy describes the limited browser storage behavior represented by the Tidecasters static storefront. It should be updated whenever production analytics, advertising tags, payment widgets, or other third-party technologies are added. Current behavior. The site uses browser local storage for two small purposes: remembering whether a visitor selected Accept or Decline on the cookie banner, and keeping a local shopping cart for the static checkout demonstration. These values remain in the visitor's browser and are not sent to a Tidecasters backend by the demonstration code. Cookie banner. The banner presents Accept and Decline controls. Accept stores an acceptance choice; Decline stores a decline choice. The banner is then hidden on subsequent visits in the same browser context. Because the site is static, this preference mechanism is intentionally simple and does not constitute a full consent-management platform. Third-party resources. The stylesheet imports Google Fonts for Fredoka and Nunito. A production operator should evaluate whether the chosen font-loading method is appropriate for its privacy obligations and may choose to self-host fonts. If analytics, advertising, chat, payment, or embedded media vendors are added, their cookies and local-storage technologies should be included in an updated inventory and disclosed according to applicable law. No advertising tracker is required by the storefront. Tidecasters hosts your shows but never promises audience growth, and the site should not add tracking technologies that imply a guarantee or sell listening data. Managing storage. Visitors can clear local storage through their browser settings. Clearing storage may reset the cart and cookie preference. Browser privacy controls, content blockers, and private browsing modes may also change how storage behaves. Production changes. Before launch, the operator should inventory cookies and similar technologies by name, provider, purpose, category, duration, and data recipient. Consent requirements vary by jurisdiction and by the purpose of the technology. Necessary functionality may be treated differently from analytics or advertising, but the exact legal treatment should be reviewed for the deployment's target audience. Payment widgets. The static checkout intentionally does not collect card details. A live Stripe checkout may introduce provider-controlled technologies or redirect flows. The final cookie and privacy disclosures should reflect the exact Stripe integration used. Contact. The COMPANY object in plans.js is the single source for company contact fields. If those fields are blank, the site omits them rather than rendering fabricated contact information. This policy is a practical starting point for the static demonstration, not jurisdiction-specific legal advice. Review it before adding analytics, advertising, payment embeds, or other third-party services.