Last updated: June 2021

The store page is carefully drafted to outline what an asset does, and does not. If applicable, a more extensive “compatibility” page is linked. Please read this before purchase to avoid any unwelcome surprises. If you’re uncertain about any asset’s workings, or have questions before purchasing, please do not hesitate to reach out. I will do the best to my abilities to answer your questions.

This policy attempts to clarify the Asset Store EULA‘s legal jargon and specifies the practical cases that it does, or does not cover. However, it does not add refund conditions that aren’t already covered by it.

All Asset Store sales are final as per the EULA section 2.2.9, which is agreed upon at checkout. Digital purchases cannot be returned once downloaded, hence it’s required to agree to waive the right to a refund. Clicking the “Download” button finalizes this agreement.

This because it is impossible to ensure the package files are deleted after a refund is issued (no DRM system). Keeping both my work and its monetary value is not a fair trade. Therefore, some conditions must be met in order to avoid abuse or supporting impulsive purchases:

Conditions that justify a refund:

- You have not yet downloaded the asset (verified through invoice number). No further reason required.
- Accidental purchase, or on wrong account (only valid if not yet downloaded).
- The asset was removed from the store within 4 weeks of purchasing.
- The asset fails to work as advertised, or there is a vital incompatibility with existing systems (within the confines of the supported platforms, capabilities and versions) . And cannot be resolved in a future update or a hotfix.

Requests are declined if:

-The invoice date is passed 14 days.
-You appear to not have read, misread or misunderstood the store page description, or otherwise failed to inform yourself through the linked online documentation. This includes details such as:
    -Minimum/maximum compatible or supported Unity versions
    -Compatible and/or supported platforms
    -Scriptable Render Pipeline compatibility (including the standard/built-in RP)
    -Listed features and limitations (sometimes expanded on in the “Technical details” section)
    -Required asset dependencies (in the case of extensions/add-ons)
-The asset is claimed to no longer be used.
-The package in question went on sale, shortly after a full-price purchase was made.

If you find you are in accordance with these conditions, please get in touch with the basis of your request.

Contact: info@skrilstudio.com