App/Item is "not as described"

An App/Item is "not as described" if it is materially different from the App/Item description or preview when it comes to its features and functionality of App/Items. If it turns out the App/Item is "not as described" we are obligated to refund the buyer of that App/Item.

App/Item doesn't work the way it should

If an App/Item doesn't work the way it should and can't easily be fixed we are obligated to refund the buyer of the App/Item. This includes situations where App/Item has a problem that would have stopped a buyer from buying it if they'd known about the problem in the first place. If the App/Item can be fixed, then we do so promptly by updating our App/Item otherwise we are obligated to refund the buyer of that App/Item.

App/Item has a security vulnerability

If an App/Item contains a security vulnerability and can't easily be fixed we are obligated to refund the buyer of the App/Item. If the App/Item can be fixed, then we do so promptly by updating our App/Item. If our App/Item contains a security vulnerability that is not patched in an appropriate timeframe then we are obligated to refund the buyer of that App/Item.

App/Item support is promised but not provided

If we promise our the buyer App/Item support and we do not provide that support in accordance with the App/Item support policy we are obligated to refund the buyer who have purchased support.

App/Item support extension not used

If a buyer purchases an App/Item support extension and requests a refund of that extension before their existing App/Item support expires we are obligated to refund the buyer who have purchased that App/Item support extension.

No refund scenario

If our App/Item is materially similar to the description and preview and works the way it should, there is generally no obligation to provide a refund in situations like the following:

• Buyer doesn't want it after they've downloaded it;
• The App/Item did not meet the their expectations;
• Buyer is not satisfied with the current feature availability of the product;
• Buyer simply change their mind;
• Buyer bought an App/Item by mistake;
• Buyer do not have sufficient expertise to use the App/Item;
• Buyer ask for goodwill;
• Buyer can no longer access the App/Item because it has been removed;
• Problems originated from the API providing organization;
• No refund will be provided after 30 days from the purchase of a App/Item.

Force Refund

We hold the authority to refund buyer purchase by force without any request from buyer end. Force refund will stop software access as well as support access by denying purchase code with immediate action.

Refund Request

If a buyer eligible to get a refund then he/she must create a refund request for the particular product.