Back to products
DIZZYSCRIPTS POLICY

Refund Policy

Refund expectations for Envato, Codester, Paddle, Gumroad, and direct digital software purchases.

Effective 24 Jun 2026 Version 2.0 Updated 25 Jun 2026

Digital product refunds

DizzyScripts products are digital software files, documentation, and support services. Refund eligibility depends on the purchase channel, the provider rules that applied at checkout, and the facts of the request.

Marketplace purchases

If you purchased through Envato, CodeCanyon, or Codester, refund requests must follow the marketplace rules and may need to be submitted through that marketplace. The support website may verify your purchase or license code and help investigate technical issues, but it does not replace marketplace refund handling.

Paddle purchases

If Paddle checkout is enabled and used, refund or payment questions should include the Paddle order email, product name, and order reference. Paddle may process payment methods, tax, receipts, refunds, disputes, and chargebacks under its own checkout flow.

Gumroad purchases

If Gumroad checkout is enabled and used, refund or delivery questions should include the Gumroad receipt email, product name, and receipt reference. Gumroad provider rules may apply.

Before requesting a refund

Please review the product page, demo, documentation, system requirements, license policy, and support policy before purchase. If a technical issue occurs, open one focused support ticket with the exact steps, screenshots, server details, PHP version, error logs, product version, and purchase reference.

When a refund may be considered

A refund may be considered when a product cannot be delivered, a duplicate charge is confirmed, the wrong direct product mapping was used, a verified critical issue prevents normal use and cannot be resolved, or the payment provider requires a refund under its rules.

Usually non-refundable

Refunds are generally not offered for change of mind after download, unsupported hosting or PHP environments, custom feature requests, third-party conflicts outside the product scope, failure to read listed requirements, or requests made after significant use of the digital files.