Digital Products

Returns & refunds, for digital orders.

Everything we sell is delivered instantly — a download, a licence, or account access. Because digital assets can't be physically returned, this page explains how we handle concerns, what information we need from you, and how the resolution process works at DarkDev Labs.

Updated: October 23, 2026 48-hour reporting window Verified buyers protected
Reporting Window 48 hours From delivery timestamp
First Step Support & troubleshooting Every case starts here
What We Need Evidence & cooperation Order ID, environment, records
Refund Time 7–14 business days After formal approval

Our commitment to digital buyers

Every product sold on DarkDev Labs is a digital asset — a downloadable file, an activation key, a licence, or access to software. Because digital products are delivered instantly and cannot be physically returned, our returns and refunds programme is built around resolution rather than traditional exchange.

We stand behind everything we sell. When something genuinely isn't working the way it should, we are committed to making it right — through technical support first, and where that path cannot resolve the issue, through the structured process described below.

How digital delivery works

Understanding the delivery model helps clarify how this policy applies to your purchase.

  • All products are delivered electronically — through a secure download link, a licence key, an API credential, or account-based access.
  • Delivery is typically instant but may take up to 24 hours in rare cases where our system needs manual review of the order.
  • Every download link is unique to your account and is logged by our system for security purposes.
  • Once a download has been initiated or a licence key has been revealed on your dashboard, the digital asset is considered consumed.
  • Licence keys are single-use or account-bound and cannot be transferred, resold, or re-issued to another account.

These characteristics are what make our products instantly useful — and also why the eligibility rules below are structured the way they are.

Reporting window

Any concern about a digital order must be reported within 48 hours of the delivery timestamp recorded by our system. This window is measured from the moment the download link or licence key was first made available in your account, not from the moment you personally chose to open it.

  • The delivery timestamp is logged automatically and is available in your account dashboard under Order History.
  • Reports must be submitted in writing through our official support channel before 11:59 PM on the 48th hour in your local timezone.
  • Weekends and public holidays do not extend the reporting window.
  • Reports submitted after this window cannot be reviewed under this programme.
  • Only one reporting window applies per order — a fresh window does not open after a support conversation has started.

Genuine delivery issues we investigate

Where a digital product does not perform the core function described on its product page, we investigate the case in full. The following are examples of the kind of situations we look into:

  • Non-delivery — the download link or licence key did not reach your account, and our delivery logs confirm this on our side after review.
  • Corrupted or inaccessible file — the delivered package fails to extract or open, and the issue persists across at least two different devices or browsers on your side.
  • Licence key does not activate — the key is rejected by the official activation service, and the rejection is reproducible when tested by our team.
  • Materially different from description — the delivered product is substantially different from the core functionality described on its product page in a way that was not disclosed.
  • Duplicate purchase — the same product was accidentally purchased twice within the same account in a single session, and neither copy has been downloaded or activated.

Each of these situations is assessed individually. Reporting an issue does not automatically mean it qualifies — every claim is verified against our delivery logs, activation records, and any evidence you provide.

Conditions for a claim to be considered

For a claim to be reviewed under this programme, the following conditions must all be satisfied. This list exists to keep the process fair for every customer and to prevent abuse of the refund system.

  • The order must have been placed under your own registered account.
  • The claim must be submitted within the reporting window described above.
  • Full cooperation with our technical support team is required — including attempting any troubleshooting steps they provide.
  • You must provide the information requested by support, which may include: order number, environment details (operating system, browser or device), error messages, screenshots, and, where relevant, a short screen recording demonstrating the issue.
  • The issue must be reproducible — that is, our team must be able to observe the same behaviour when testing under comparable conditions.
  • The product must not have been modified, patched, reverse-engineered, or redistributed by you or any third party on your behalf.
  • The licence key must not have been activated, transferred, or shared with anyone outside your own account.
  • The claim must not have been previously resolved through our support process for the same order.
  • The order must not be part of a bulk purchase intended for resale.
  • The account must not have an outstanding chargeback or unresolved payment dispute against any previous order.

Where any of these conditions cannot be met, our support team will still do their best to help you get the product working — this is always the first priority.

Technical support comes first

In nearly every case, an issue that seems like a delivery problem can be resolved through a short technical conversation. Our support team's first objective is to make your purchase work for you.

  • All support is handled through written communication so that both sides have a clear record of what was tried.
  • We may ask for environment details, step-by-step reproduction, or a short screen recording — this is standard practice and helps us diagnose the issue quickly.
  • Response times vary based on complexity, but we aim to reply within 1–2 business days.
  • Resolution through support — whether that is a working fix, an updated build, or a reissued key — is always the preferred outcome.
  • Where a technical resolution is provided and works correctly, the delivery obligation is considered fulfilled.

Support engagement is a required step in the process. A claim can only move forward to formal review once both sides have made a documented effort to resolve the issue through troubleshooting.

How each claim is assessed

Once a claim has been raised, our team undertakes a structured assessment. This ensures decisions are consistent, documented, and fair across every order.

  • Our team reviews the delivery log, download history, activation history, and any support conversation already on record.
  • Where possible, the issue is reproduced in a controlled environment using the same software, licence, and comparable setup.
  • The assessment considers the effort already made by both sides during the support phase.
  • In borderline cases, we may offer partial accommodation — such as a reissued licence, an alternative product of equal value, or store credit — rather than a monetary refund.
  • Assessment typically takes 5–10 business days from the moment all requested information has been provided.
  • Every outcome is communicated in writing with a clear reason for the decision reached.

The goal of this assessment is always the same: to arrive at a resolution that is fair and honest given the facts of the specific case.

Circumstances outside the programme

Certain situations fall outside the scope of this programme because they do not represent a delivery or product failure. We list them here so you can make an informed decision before purchase.

  • Change of mind after the digital asset has been downloaded, accessed, or activated.
  • Purchase made by mistake on the wrong product, wrong tier, wrong duration, or wrong account, after delivery has occurred.
  • Product no longer needed due to a change in personal or business plans.
  • Incompatibility with software, hardware, or environment that is outside the officially listed system requirements on the product page.
  • Missing features that were never advertised or promised on the product page.
  • Issues caused by third-party tools, modifications, plugins, or setups that are not officially supported.
  • Subjective expectations about design, aesthetics, or performance that differ from the documented specifications.
  • Failure by the customer to read the documentation, installation guide, or system requirements before purchase.

We share these boundaries openly so that buyers can make informed decisions. Every product page lists detailed specifications and system requirements — we recommend reading them carefully before checkout.

Categories delivered as-is

Because of the way certain digital products are manufactured, distributed, or licensed, some categories are delivered as-is. These are clearly marked on the product page at checkout.

  • Licence keys and activation codes — once revealed in your dashboard, they cannot be un-issued by the vendor.
  • Downloadable digital files — software packages, templates, scripts, and assets — once the download has begun.
  • Subscription-based access — including monthly, annual, and lifetime subscription products.
  • Bundles — where any single item within the bundle has been accessed or activated.
  • Custom or made-to-order digital work — anything produced to your specifications once production has started.
  • Products on promotional campaigns — where the campaign terms explicitly state a modified policy.
  • Educational content — courses, lessons, and guided material once streaming or download access has been granted.

This list is provided for transparency. If you are unsure whether a specific product falls into one of these categories, our team will gladly clarify before you place the order.

Steps to raise a claim

To keep the process organised and traceable, please follow the steps below in order. Claims that skip a step cannot be reviewed in the standard queue.

  1. Contact support Email our support team with your order number, the product name, a description of the issue, and any error messages, screenshots, or a short screen recording that demonstrates the problem.
  2. Troubleshooting phase Our team will guide you through standard diagnostics — environment checks, reinstall steps, alternative download mirrors, and licence verification. Please try each step they suggest and reply with your observations.
  3. Formal claim (if needed) If troubleshooting does not resolve the issue, our team will open a formal claim under this programme. You will receive a case reference number for future correspondence.
  4. Assessment Our returns team reviews the delivery logs, activation records, and the entire support conversation. Additional information may be requested during this stage.
  5. Decision A written decision is issued within 5–10 business days of receiving all required information. The decision includes the outcome and the reasoning behind it.
  6. Resolution Where the claim is approved, the resolution is carried out using the method described in the resolutions section below. Where it is not approved, our support team remains available to help in any other way we can.

Possible resolutions

Depending on the nature of the issue and the assessment outcome, one of the following resolutions may be offered. Each resolution is chosen to match the specific facts of the case.

  • Reissued licence or download link — when the original delivery failed for a technical reason on our side.
  • Alternative build or version — where a newer or corrected build of the same product resolves the issue.
  • Alternative product of equal value — when the specific product is no longer viable for your use case but another product in our catalogue may be.
  • Store credit — issued to your account for use on any future purchase.
  • Partial monetary refund — where the assessment determines that a portion of the purchase value should be returned, based on the nature of the issue.
  • Full monetary refund — issued where the assessment confirms a complete failure of the delivery obligation as described in this policy.

Every resolution is documented in writing with the reasoning behind it, so you always understand how the outcome was reached.

Refund method & timeline

Where a monetary refund is issued, it is processed back to the original payment method used at checkout. Where the original method is no longer available, our team will coordinate an alternative with you in writing.

  • Refunds are initiated within 7–14 business days after a claim has been formally approved.
  • The time for the funds to appear in your account depends on the payment provider or bank — this is outside our direct control.
  • Where the order was paid in cryptocurrency, refunds are issued in the same currency at the market rate on the day of processing. Because of market movement between the original payment and the refund, the received amount may differ from the original payment value.
  • Blockchain network fees associated with the refund transaction are deducted from the refunded amount.
  • Promotional discounts, coupon codes, and gift cards applied at purchase are recalculated when the refund is processed — the refund reflects the discounted price actually paid.
  • Payment processing fees charged by third-party gateways are not included in the refunded amount.
  • Refunds are always returned to the same currency and wallet or card that was used for the original payment; we cannot issue refunds to a different recipient.

Duplicate orders

Accidental duplicate orders happen — usually because of a double-click at checkout or a browser refresh during payment. We handle these cases with care.

  • To qualify as a duplicate, both orders must have been placed under the same account, within the same session, for the same product.
  • Neither copy may have been downloaded, viewed, or activated.
  • The duplicate claim must be raised within the 48-hour reporting window.
  • Once verified, the duplicate charge is resolved through the standard refund process.
  • Where both copies have already been delivered and accessed, the duplicate cannot be treated as an accidental order — both copies remain licensed to your account.

Payment disputes

We encourage you to reach out to our support team before opening a payment dispute with your bank, card provider, or crypto gateway. In our experience, almost every concern can be resolved directly — usually faster and with a better outcome for you.

  • When a payment dispute is opened while a support conversation is already in progress, the case is transferred to a specialised review queue.
  • During an active payment dispute, all other resolution options under this programme are temporarily paused until the dispute is closed.
  • Accounts with unresolved payment disputes may be limited from placing new orders until the matter is settled.
  • Once the dispute is resolved, we are glad to continue working with you under the standard process described on this page.

Need help with a digital order?

Our support team reviews every request individually. Reach out with your order number and details, and we'll walk you through the process step by step.

Back to top
Added to cart