Refund Policy
A review path for digital OumsAI purchases.
OumsAI products are digital WordPress and WooCommerce tools. This policy explains when refund requests can be reviewed, what information helps support evaluate a request, and how renewals, cancellations, and plan changes are handled.
Digital productNo physical return is required for review.
Support firstTechnical issues need clear context and reproduction steps.
Fair reviewEligibility depends on purchase, license, and support records.
Refund summary
How refund reviews are handled.
14-day review window
First-time purchase refund requests should usually be submitted within 14 days unless checkout terms say otherwise.
Evidence helps
Order number, purchase email, site URL, license status, screenshots, logs, and steps to reproduce speed up review.
Renewals differ
Canceling a subscription prevents future renewals but does not automatically refund past charges.
Plan fixes first
If you bought the wrong plan, support may be able to correct the plan without a cancel-and-repurchase loop.
This summary is for readability. The full policy below explains the controlling details.
Last updated: May 22, 2026
1. Digital product policy
OumsAI products are digital WordPress and WooCommerce plugin products. Because there is no physical item to return, refund requests are reviewed through account, license, activation, and support records.
2. Refund review window
Unless a checkout page, order form, or special offer states different terms, first-time purchase refund requests should be submitted within 14 days of purchase. Submitting a request does not guarantee approval, but it starts the review process.
3. Cases that may qualify
A refund may be considered when the product cannot be activated after support review, a confirmed technical issue prevents core use of the purchased product, the same customer accidentally made a duplicate purchase, or the product materially does not match the purchase description.
For technical issues, OumsAI may ask for reasonable troubleshooting details before approving a refund, including site URL, WordPress and WooCommerce versions, screenshots, logs, and steps to reproduce.
4. Cases that usually do not qualify
Refunds are usually not approved for change of mind after activation, failure to read product requirements, conflicts caused by unsupported custom code, requests outside the review window, license sharing, account abuse, completed renewal periods, or issues caused by third-party services outside OumsAI control.
5. Renewals and cancellations
Canceling a subscription prevents future renewals when processed correctly, but it does not automatically refund past charges. Renewal refund requests may be reviewed when submitted promptly and when the renewed license has not been actively used after renewal.
6. How to request a refund
Contact support with the purchase email, order number, site URL, license status, reason for the request, and any troubleshooting evidence. If the issue is technical, describe the expected result, actual result, and steps to reproduce the issue.
Do not send passwords, full payment card details, private keys, or unnecessary customer personal data in a refund request.
7. Review and timing
Approved refunds are returned through the original payment method when possible. Payment providers and banks may take additional time to show the refund after it is processed.
8. Chargebacks and disputes
If you open a payment dispute before contacting support, account access, license status, or support handling may be paused while the dispute is reviewed by the payment provider.
9. Plan changes
If you purchased the wrong plan, contact support before opening a refund request. In many cases, a plan correction, upgrade, downgrade, or account adjustment is cleaner than canceling and repurchasing.
10. Contact
For refund questions, use the support page and include the account details needed to identify the purchase.
Refund request
Start with support so the issue is understood.
The fastest review includes the order number, purchase email, site URL, license status, and the exact reason for the request.