Buyer support
If you have issues, open a support ticket with all details first.
We first try to solve technical problems together.
Digital deliveries may have limited refund eligibility depending on the case.
01
02
03
04
Before review
Reviewed
Often excluded
1Open a support ticket with order and issue details.
2Joint technical review and attempt to resolve.
3Decision about fix, replacement, credit or refund.
Refund policy
This policy explains how we handle refunds, technical issues and support cases for digital products and custom work.
Digital product principle
Digital products are usually provided or unlocked immediately after purchase. Because of that, a refund after access, download or usage is not automatic. We review each case fairly, especially when there is a reproducible technical issue not caused by incorrect installation, third-party changes or an incompatible server environment.
When support comes first
For installation issues, configuration questions, framework conflicts or errors, we first try to resolve the issue together. We need a clear description, logs, product version, framework, server artifacts and reproduction steps.
Possible refund reasons
A refund may be reviewed if a product permanently fails in the correct environment, an advertised core feature is missing, or a duplicate purchase is clearly proven. A change of mind, missing server requirements or third-party modifications are usually not sufficient.
Custom work
For custom projects, refunds depend on project status, work already completed, agreed scope and acceptance. Development time, concept work, designs or integrations already delivered may not always be fully refundable.
Create a ticket with order ID, product, logs and reproduction steps.
Technical defects, duplicate purchases or missing advertised core features.
Change of mind, missing server requirements, third-party changes or rule violations.