Refund draft for review
Fair refund wording without promising impossible recovery results.
This launch-day candidate wording is for local review only. Final wording must match the actual payment provider, product delivery route, UK consumer rules, and professional legal advice before publication.
Principle
Help first, then review fairly
If software does not work as reasonably described for a supported use case, the customer should contact support with order details and a non-sensitive description of the issue. High Caliber should try to help first, then review refund options where appropriate.
- Recovery tools cannot guarantee that every file, record, message, photo, branch, note, or unsupported item will be recoverable.
- Known unsupported cases should be explained before purchase wherever practical.
- Customers should keep backups and should not overwrite original data while testing exports.
- Refund handling must follow the final commerce-provider route and applicable consumer rights.
Compatibility
Reduce bad purchases before payment
Product pages should offer clear supported/unsupported case wording, demos, screenshots, compatibility guidance, or pre-purchase questions where that helps a customer decide safely.
Where a product has a preview, trial, sample report, or compatibility-check route, the refund policy should refer customers to that route before purchase.
Cancellations
Subscriptions and paid extras must match the real setup
If optional paid modules, subscriptions, renewals, or upgrade entitlements are added later, cancellation wording must match the actual provider setup, entitlement rules, customer account route, and final legal review. No subscription, billing, or entitlement system is connected in this local scaffold.