Refund Policy
Refunds should not become another dashboard to babysit. The policy below separates portal credits, custom work, routed handoffs, failures, and disputes.
Any paid work, credit use, supplier routing, or consulting engagement is governed by the written terms shown at purchase or in the signed work agreement.
If a Bluewizarding page does not process checkout directly, the payment and refund terms live in the portal, invoice, statement of work, or supplier-routing agreement that created the charge.
Portal credit-pack refund requests must be made within 14 calendar days of purchase unless the purchase terms say otherwise. Requests after that window are not eligible under the standard credit policy.
If portal credits remain active, the portal purchase terms control the final refund window, eligible pack types, and support path.
A credit-pack refund is available only when fewer than 10% of the purchased credits have been used, unless the purchase terms say otherwise. A buyer who uses more than that threshold is outside the standard credit refund path.
Failed generations should return consumed credits automatically when the portal mechanism supports it, and those returned credits should not count against the usage threshold.
Approved portal-credit refunds should go back to the original payment method. Bluewizarding targets processing within 2 business days after approval, with bank or card timing depending on the issuer.
Bluewizarding should not promise gift cards, store credit, alternative payout methods, or partial credit-pack refunds unless the active purchase terms say so.
The standard credit-pack policy does not offer partial refunds. If a credit pack is eligible, the refund path is for the full pack purchase price.
Custom consulting, research, simulation, or technical work is different. Those outcomes depend on the written scope, milestone state, delivery status, and accepted change requests.
If a portal generation fails because of a technical error, the safer product rule is to restore the consumed credits without making the user ask. The refund page should stay clear about that distinction.
Question refinement, supplier routing, and public profile previews do not create a paid generation unless the checkout and account terms explicitly say so.
Payment disputes or chargebacks may freeze account access while the payment processor reviews the case.
The recommended path is still direct contact first, because support can usually inspect account, receipt, and generation details faster than a formal dispute cycle.
Referral, routing, residual, or supplier-introduction compensation may follow a separate agreement. Buyer and supplier obligations should be checked before any routed handoff is treated as billable.
A routed handoff should not be treated as a refundable portal-credit purchase unless the purchase terms explicitly connect those systems.
Use the public contact page with the account, purchase date, work agreement, portal receipt, and the outcome you expected. Include what happened instead.
For portal credits, include the account email and purchase date. For consulting or custom work, include the written agreement, milestone, invoice, or accepted scope.
Use the public business contact for portal-credit, billing, consulting, or routed-handoff questions.
Open the contact page