Refund Policy

This policy is specific rather than diplomatic. Both lists are spelled out — the cases where money comes back and the cases where it does not. That is fairer to everyone: you know what you are buying before you pay, and neither side spends a week arguing about something that could have been read in advance.

1. The core rule

A digital product counts as delivered the moment the key or file is handed over. After delivery a refund is normally not possible.

The reason is mechanical rather than commercial: a key cannot be taken back and cannot be sold twice. By the time a dispute starts it is bound to an order and usually already activated. Refunding it would leave the buyer holding both the money and the goods.

This is the standard across the licence-key trade, not a rule we invented.

2. When a refund is considered

Three situations get a proper review, and money is returned when the facts check out:

Nothing was delivered. Payment cleared, no key arrived, and none can be issued — stock ran out, the seller never confirmed, something broke. If there is nothing to hand over, the payment is returned in full.

The wrong item was delivered. You paid for one variant — a subscription length, an edition, a platform — and received another. We try to swap it for the correct one first; if that is impossible, we refund.

The product does not match its description. A feature listed on the page does not exist, or a game listed as supported is not supported. This means a mismatch between the description and the product at the time of purchase, not a feature the developer removed afterwards — that case is section 3.

In all three, write in with your order number and the review starts immediately.

3. When a refund is not issued

A closed list, so there is no ambiguity:

1. The key was delivered and you changed your mind. There is no cooling-off return on a delivered digital item.
2. You bought the wrong thing by mistake. Every variant, term and platform is stated on the product page before checkout.
3. The software did not run on your setup. Incompatible hardware, an unsupported system version, a conflict with other software, missing prerequisites. Requirements are published before purchase and checking them is the buyer’s part of the deal.
4. You decline diagnostics. We troubleshoot, and for that we ask for logs, screenshots or a description of your system. A refund demanded instead of finding out what went wrong is declined.
5. The developer changed, paused or discontinued the product after purchase. Software of this kind lives that way: features get pulled, builds go on hold after a game or anti-cheat update. That risk sits with the buyer and is described in the Disclaimer.
6. A game account was banned. Neither the seller nor the build developer takes part in a publisher’s decisions. A ban is not a product defect.
7. A platform or service restricted access, including regional restrictions and marketplace decisions.
8. Signs of abuse: attempts to get the product free, reselling a key, or a chargeback filed after activation.

4. A paused product is not a faulty one

Worth its own section, because it is the most common misunderstanding. After a game or its protection updates, developers routinely pause a build and ship a fix a day or two later. During that pause the product does not run.

A pause is neither a defect nor grounds for a refund — it is the normal operating rhythm of this category of software. We try to pull listings from sale while a product is paused, though there can be a gap of a few hours between the game updating and the page coming down.

If a developer shuts a product down permanently while your subscription still has time left, write to us. Those cases are handled individually and the outcome depends on what the developer offers.

5. Partner listings

Some products are sold not by us but by partner sellers: the button on the page leads to the partner’s platform, and both payment and delivery happen there.

For those orders the seller decides refunds under their own rules and their platform’s. We are not a party to the transaction and never hold the money. What we do: point you to the right seller, help you phrase the claim so it gets handled, and remove a listing from the catalog if complaints keep coming.

Telling the two apart is easy — each product page states who fulfils it. If in doubt, ask support before paying, not after.

6. How to file a claim

1. Write to the support address on the Contacts page, by email or on Telegram.
2. Include your order number — without it the payment cannot be located.
3. Describe what happened and attach evidence: an error screenshot, logs, a screen recording. The more concrete the message, the faster the answer.
4. If the problem is technical, be ready to troubleshoot. A fair share of cases are solved in fifteen minutes with no refund needed at all.

Timing. A first reply usually arrives within a day. A final decision on a disputed case takes up to 10 working days — some cases require a query to the developer or the payment service, and the answer cannot arrive sooner than theirs.

Method. Money goes back the way it came, on the timetable of the payment service and your bank. We do not refund in cash, to a different wallet, or to a third party.

7. Chargebacks

Filing a chargeback after receiving a key is not a quality dispute; it is an attempt to keep both the product and the money. The result is the end of support and of any further service, and full disclosure of the order and delivery record to the payment service.

The ordinary route is faster and works better: write to us first.

8. Changes

The version published here is the one in force, with its date in the header. Orders already paid for are governed by the version in force when they were paid.