Skip to content
USD
English

Fair review for first-party digital products

How HyperDAF reviews refund requests

This policy explains when a refund request may be reviewed, the information required, how digital access affects eligibility and what happens after a decision.

Policy ownerHyperDAFFirst-party developer, publisher, seller and support provider for HyperDAF products
Submit refund request

Our refund-review commitments

HyperDAF reviews requests against the published product description, actual delivery state, available technical evidence, payment records and applicable consumer law.

Clear request path

Customers can submit an order-linked request through the published HyperDAF contact route.

Evidence-based review

Technical and billing facts are reviewed before a decision instead of relying on unsupported assumptions.

Rights preserved

Nothing in this policy removes rights or remedies that cannot lawfully be excluded.

Presentation is not payment authority

This page explains policy and request guidance. HyperDAF Engine remains the sole owner of order, payment, refund, entitlement and audit state.

When a request may qualify for review

A request is reviewed individually. Meeting a listed circumstance does not guarantee approval, and mandatory legal rights always take priority over a configured policy window.

Standard voluntary request window14 days from purchase date

Mandatory legal rights may apply outside this configured window.

Material technical defect

The product has a reproducible material defect that prevents its documented core function and HyperDAF cannot provide a reasonable correction or workaround.

Materially not as described

The delivered product materially differs from the published description or included files at the time of purchase.

Duplicate payment

The same order was charged more than once and the duplicate amount is confirmed in HyperDAF payment records.

Unauthorized payment

A payment is credibly reported as unauthorized and the customer cooperates with identity, account and payment-provider verification.

Delivery failure

HyperDAF cannot provide the purchased download, licence or service access within a reasonable resolution period after confirmed payment.

Billing error

The charged amount does not match the authoritative order total because of a confirmed HyperDAF billing or calculation error.

Reasonable resolution opportunity

HyperDAF may ask for reasonable diagnostic evidence and an opportunity to resolve a correctable product issue before deciding the request.

Requests that normally do not qualify

The following circumstances normally do not qualify for a voluntary refund unless required by applicable law or a separate written HyperDAF commitment.

Change of mind

A change of preference after files, licence keys or service access have been delivered or used.

Published compatibility ignored

The environment does not meet the compatibility, version, hosting or dependency requirements published before purchase.

Third-party conflict

The issue is caused by unsupported third-party code, custom modifications, hosting restrictions or external services outside HyperDAF control.

Misuse or prohibited modification

The product was misused, redistributed, reverse engineered, altered outside documented extension points or used in breach of its licence.

Customization expectations

The request is based on customization, integration, migration or implementation work that was not included in the purchased product or service.

Consumed services

Support time, setup work, usage-based service, subscription access or other service value has already been materially consumed.

Expired voluntary window

The request is submitted outside the configured voluntary review window and no mandatory legal right or written exception applies.

Fraud or policy abuse

The request includes false evidence, account manipulation, repeated download-and-refund behavior, payment abuse or another credible fraud indicator.

How digital products and services are treated

Digital files, licence credentials and service access can be delivered immediately and cannot be physically returned. Review therefore considers access, use, defect evidence and available remedies.

Downloadable products

Download activity may be considered during review. A download does not remove mandatory rights, but it may affect voluntary change-of-mind eligibility.

Licence keys

Approved refunds may require the related licence to be revoked or disabled. Continued use after a refund is not permitted.

Updates and renewals

Renewal requests are reviewed against the renewal notice, billing record, access already provided and applicable cancellation rights.

Bundles

Bundle review considers the complete purchase, products already accessed and whether a partial remedy can fairly resolve the issue.

Templates and design files

Differences caused by customer content, fonts, software versions or customization choices are not product defects when the published requirements are met.

SaaS access

SaaS review considers service availability, usage, consumed capacity, billing period and whether the issue was resolved within a reasonable period.

Recurring subscriptions

Cancellation normally stops future renewal and does not automatically refund an active period already started, except where law or a written offer requires otherwise.

Support and services

Completed support, setup or professional-service work is reviewed according to the agreed scope, work delivered and any written service commitment.

Technical resolution before a decision

When a reported issue appears correctable, HyperDAF may request a reasonable opportunity to reproduce it, confirm the supported environment and provide a fix, update or practical workaround.

  1. 1

    Confirm the environment

    Verify the product version, WordPress or software version, PHP or runtime version, hosting limits and published dependencies.

  2. 2

    Reproduce the issue

    Provide clear steps, safe error text and relevant screenshots or logs without sharing passwords, secret keys or private customer data.

  3. 3

    Apply the supported remedy

    Test the provided correction, update, configuration guidance or workaround within a reasonable period and report the result.

Resolution timing

Resolution time depends on issue complexity, available evidence, customer response time and whether third-party systems are involved.

How to submit a refund request

Submit one clear request through the official route and include enough information to identify the order, product and reported issue. A request does not guarantee approval.

Order reference

Provide the HyperDAF order number, receipt reference and purchase email address.

Product details

Identify the product, licence or subscription, purchased plan and version in use.

Issue evidence

Describe the issue, expected result, actual result, reproduction steps and safe supporting screenshots or logs.

Technical environment

Include relevant WordPress, PHP, browser, operating-system, hosting and dependency versions.

Protect sensitive information

Never send passwords, private keys, full payment-card numbers, authentication cookies or unrelated personal data.

Submit refund request

HyperDAF may acknowledge receipt and request missing information before substantive review begins.

Decision timing depends on request completeness, technical investigation, fraud checks and payment-provider processes.

The decision may approve, partially approve, decline or request additional resolution steps. The outcome is sent through the verified contact route.
Submit refund requestUse the purchase email address where possible so the order can be verified securely.

What happens after approval

An approved outcome is recorded and processed through the applicable HyperDAF payment and order workflow. The policy page itself does not approve or execute refunds.

Original payment method

Approved money refunds are normally returned to the original payment method where supported. Offline payment methods may require verified operational instructions.

Processing time

After HyperDAF submits an approved refund, the payment provider or financial institution controls when the credit appears.

Partial refunds

A partial refund may be used when only part of a bundle, service period, fee or delivered value is affected and the customer accepts the resolution.

Credit or replacement

Where lawful and agreed, HyperDAF may offer a replacement, extension or account credit instead of a money refund.

Taxes, currency and fees

Tax, currency conversion and third-party fees are handled according to the original transaction, provider rules and applicable law.

Chargebacks and disputes

A chargeback or payment dispute is handled through the payment provider and may pause the direct refund review while the same transaction is under formal dispute.

Statutory rights are not limited

Nothing in this policy excludes, restricts or replaces rights, remedies, guarantees, withdrawal rights or refund obligations that apply under mandatory law. Where this policy conflicts with such law, the mandatory rule controls.

Changes to this policy

HyperDAF may update this policy to reflect product, legal, payment-provider or operational changes. The effective and last-reviewed dates should be updated, and material changes should not be applied retroactively where prohibited.

Questions or refund requests

Contact HyperDAF through the official request route for order-linked refund review or questions about this policy. Include the order reference, but never send passwords, private keys or full payment-card details.

Refund contact emaildev.hayatkhan@gmail.com
Response handling

Refund-policy and order enquiries are routed to the appropriate HyperDAF contact for verification and review.

Submit refund request