Legal

Privacy Policy

This Privacy Policy describes the information practices represented by the Tidecasters static storefront. It is written as a launch-ready starting point rather than legal advice and should be reviewed for the jurisdiction, vendors, and data flows of any production deployment. Information you provide. The storefront may display forms for a name, email address, and message. In this static demonstration those forms do not transmit information to a backend. If a production service activates these forms, it should collect only the information reasonably needed to respond, provide an account, deliver activation information, process billing, and support the service. Billing information. The static site does not collect payment-card details. A production checkout is intended to use Stripe. Payment information would be handled according to the processor's applicable documentation and privacy terms, with Tidecasters receiving the information needed to identify the transaction and manage the subscription. Podcast information. A production hosting service may process show titles, episode files, RSS information, artwork, descriptions, and related metadata so that it can store and distribute the show. Creators retain ownership of their content subject to the service rights necessary to operate hosting and delivery. Listening data. Tidecasters does not sell listening data. Analytics may be used to provide the features described by a customer's plan, such as episode performance or listener geography. Any production analytics system should document its sources, retention periods, aggregation practices, and lawful basis. Cookies. The current storefront uses local browser storage to remember the user's cookie preference and shopping cart. A production deployment should inventory every cookie, local-storage item, analytics script, and third-party resource, then disclose them accurately. Retention and security. A production operator should establish retention periods based on the data type and operational need, and should use reasonable administrative, technical, and organizational safeguards. No internet service can promise absolute security. Your choices. Depending on jurisdiction, users may have rights to access, correct, delete, restrict, or export certain personal information. A production service should provide an appropriate request mechanism and verify identity before disclosing account data. Children. The service is not designed to knowingly collect information from children where prohibited by applicable law. Contact. The COMPANY object in plans.js is the single source for company contact fields. Blank contact fields are intentionally omitted from rendered company cards. This policy is a static-site template and should be updated with the actual controller identity, jurisdictions, vendors, retention periods, and contact process before launch.