Draft · not in force
Refund policy
Position in plain language
There will be a refund process. It is deliberately not the centre of our pitch: we would rather persuade you with a published validation record and an honest account of what the software does not do than with a promise to undo the purchase. Both things can be true — a refund route exists, and it is not the reason to buy.
1. Who processes a refund
Purchases are expected to be made through a merchant of record, which is the seller for the transaction. A refund is therefore processed by that merchant, to the original payment method.
[OWNER TO FINALIZE] The merchant of record's name, its refund terms, and the link to its policy.
2. Statutory withdrawal rights
Digital purchases in some jurisdictions carry a statutory right of withdrawal, which can be affected by consenting to immediate access to the download at checkout. The checkout flow will make that consent explicit rather than burying it.
[OWNER TO FINALIZE] The exact wording of the consent, and how withdrawal is handled where it has not been given.
3. Discretionary refunds
Beyond any statutory right, the intent is to refund in good faith where the software does not do what this website says it does, or where it will not run on a supported system and the problem cannot be resolved.
[OWNER TO FINALIZE] The window in days, the conditions, and whether any circumstances are excluded.
4. What happens to the licence key
A refunded licence key is added to the public revocation list that the application downloads, and stops activating. This is stated here rather than discovered later.
5. Before you ask for a refund
If something is wrong, email [email protected] first. The software is made by one person, who would rather fix the problem than process the refund — but will process the refund.
[OWNER TO FINALIZE] Target response time and the exact steps for making a request.
6. Chargebacks
[OWNER TO FINALIZE] How disputed charges are handled, and their effect on the licence.