Legal

Refund Policy

This Refund Policy explains the refund language represented by the Tidecasters storefront. It is intended to be clear about the relationship between a 14-day trial, monthly renewal, and refund requests. Trial period. Each Tidecasters plan includes a 14-day trial. The trial is intended to let a customer evaluate the plan before the first paid monthly period. If a customer cancels during the trial and before conversion, the first paid renewal is avoided. A production billing system should show the trial end date clearly. Monthly renewal. After the trial, a monthly subscription renews automatically at the then-current monthly price unless cancelled before renewal. Customers are responsible for reviewing their renewal date and cancellation status. A production account page should provide an obvious cancellation mechanism. Refund requests. Refunds are handled according to the circumstances of the request and applicable law. A production operator may consider duplicate charges, technical billing errors, unauthorized transactions, and other documented situations. Nothing in this policy limits rights that cannot legally be waived. No audience-performance refunds. Tidecasters hosts your shows but never promises audience growth. Changes in download counts, listener numbers, rankings, sponsorship revenue, advertising demand, or discovery do not by themselves establish a refund entitlement. Testimonials and product analytics describe experiences or measurements; they are not performance guarantees. Service issues. If a material service problem prevents the customer from using an included feature, the customer should document the issue and contact the service through the published support route. A production service may offer troubleshooting, service credits, or refunds where appropriate. Payment processor. The intended production processor is Stripe. The static storefront does not collect card details. If a live charge is disputed, the customer may have rights and procedures available through the card issuer or payment processor in addition to the service's own support route. How to request. A production implementation should provide the account email, transaction identifier, plan name, relevant dates, and a short explanation of the request. Do not send full card numbers through ordinary contact forms. Cancellation versus refund. Cancelling a subscription prevents future renewals when completed before the applicable renewal point; it does not automatically create a refund for a prior paid month. Refund eligibility is a separate question governed by this policy and applicable law. This policy is designed for the static Tidecasters demonstration. Before commercial launch, the operator should replace the generic process with the actual legal entity, refund windows, regional requirements, and support contact.