Refund policy

Effective date: May 26, 2026 · Applies to paid products or subscriptions for Cutflux offered through cutflux.app and processed by Stripe (or a successor payment processor).

    Summary: Cutflux ordinarily does not refund completed charges. Paid access is consumed as instantaneous digital tooling (cloud FFmpeg minutes, captions infrastructure, entitlement flags unlocking browser features already delivered or immediately deliverable upon payment acknowledgment).
  

1. All sales final (default)

Except Section 5 (law-mandated), all fees are non-refundable. We do not refund because you dislike an edit aesthetic, misunderstood feature limitations, mismatched TikTok trending audio rules independently of our editor, intermittent browser GPU quirks outside our control, YouTube crawler blocks, misunderstood upload caps documented in UI/logs, misunderstood Cloud Run FFmpeg queue latency, captions timing drift attributable to mastering differences, misunderstood beat-detection stochasticity inherent to heuristic onset detection, misunderstood export resolution vs source resolution, misunderstood mobile vs desktop captions workflow copy, misunderstood login redirect cookie policies, misunderstood analytics opt-out ergonomics—or because you ceased using the Service after unlocking features.

2. Why

You purchase access to automation and computational capacity orchestrated remotely. Charges typically settle before or during consumption; reversal would grant unpaid usage asymmetrically disadvantaging metering against fraud. Chargebacks asserted solely to circumvent this policy remain subject to Stripe dispute evidence plus account enforcement under Terms of Service.

3. Trials, credits, cancellations

If a subscription or recurring plan includes introductory pricing, cancel before renewal per Stripe Customer Billing Portal instructions or contact paths we publish—or your card issuer’s subscription management tools—not via retroactive clawbacks disputing fulfilled months already provisioned absent fraud.

4. Technical failures attributable to Cutflux-controlled systems

If verifiable outages traceable narrowly to Operators’ backends (excluding user connectivity, malformed uploads, Stripe downtime, GCP regional incidents outside negotiated SLA horizons, AssemblyAI ingestion failures beyond API key rotation windows, user mis-specified FFmpeg flags at advanced surfaces) systematically prevent redemption of a SKU for forty-eight (48) uninterrupted hours starting from Stripe “paid” acknowledgment email timestamp after you escalate through contact channels surfaced from our landing/footer, Operators may—in sole discretion—issue credits usable only inside the Service equivalent to the withheld deliverable, still not cash refunds unless statutes force cash remedies.

5. When law requires cash remedies

Jurisdictions occasionally guarantee cooling-off withdrawals, deceptive-practice clawbacks for entirely undelivered digital goods billed yet never provisioned, or card-network mandated charge reversal categories. Sections 1–4 defer to clearer statutory rights only to extent they actually bind Operator legal personality and transaction fact pattern (non-lawyer characterization); nothing here waives nondisplacement rights.

6. How to escalate

Use contact channels reachable from our landing/footer (currently including official linked social profiles) with subject line referencing “Billing / No refund policy exception request,” attach Stripe receipt identifiers ch_.../cs_.../invoice links, succinct timeline, screenshots of errors if any—not raw legal threats without correlation data.