Skip to main content
InBrief / templates

Refund Policy

In effect from 9 August 2026Version 1.0

The short version: purchases are final. There is no trial period and no money-back window, and this page says so rather than implying otherwise — but there are things you are owed regardless, and they are set out below.

1. The position

What is sold is source code, and it is delivered immediately and in full. Once repository access has been granted, the purchase is final and no refund is offered.

The reason is not a preference. Code cannot be handed back: once it has been cloned it has been received, and there is no way to verify that it was deleted. A refund at that point is simply a free copy, which is why the position is stated before you pay and confirmed by you at checkout.

Access is granted the moment you open your claim link and enter a GitHub username, which is usually minutes after paying. If you have paid but have not yet claimed, write to us before you claim — while nothing has been handed over there is something to discuss, and after it has been, there is not.

2. Look properly first

Because this is the policy, everything needed to judge the product is published before purchase rather than after: a live demo running the real thing on the real stack, the complete feature list, the running costs, what you need in place, and the exact scope of the Business + Setup service including what it does not cover.

Questions before buying are answered, and they are answered faster than a dispute is. Ask.

3. If delivery fails, you are owed

This is an obligation, not goodwill. You paid for repository access. If you never receive it, you get the product or your money back — your choice — and no policy on this page limits that.

It applies when access was never granted and cannot be — for example the invitation cannot be issued, or a fault at our end means your order was never delivered at all.

It does not apply when the code arrived and you decided you did not want it. Nor does it apply to problems on your side of the line — your hosting, your domain, your GitHub account, or a deployment you chose not to complete. Those are covered by support, not by a refund.

4. Duplicate and accidental charges

If you were charged twice for the same thing, or a payment went through that you did not intend to make, the extra charge is refunded. You paid once for one licence and that is all you owe.

Tell us and it is dealt with. Bringing it to us is faster than raising it with your bank, and it does not put your access at risk in the meantime.

5. Chargebacks

A chargeback reverses the payment, and repository access is revoked when that happens. This is automatic and it is not a punishment: a reversed payment with the code still attached is a copy nobody paid for.

The licence ends with the payment that bought it, and you must stop using the template.

If something has gone wrong, email first. A message is answered in hours; a chargeback takes weeks, costs both sides, and cuts off the access while it runs.

6. Your statutory rights stand

Nothing on this page removes, limits or waives a right that consumer-protection law gives you. Where such a right applies to your purchase, it applies whatever this policy says, and this policy is read subject to it rather than the other way round.

Some consumer regimes give a period in which a digital purchase can be cancelled, and the same regimes generally allow that period to end early when the buyer asks for the content to be supplied immediately and acknowledges the consequence. The confirmation you tick at checkout records exactly that, and the version you accepted and the moment you accepted it are stored on your order.

Where a right cannot be given up under the law that applies to you, it is not given up. If you believe you hold such a right, say so and it will be looked at on its merits rather than refused by reference to this page.

7. How to raise something

Email hello@inbrief.sh from the address you bought with, and quote the order reference from your order page. Say what happened; a refusal will always come with a reason, and so will an agreement.

Where a refund is due, it is issued through Paddle, who took the payment as merchant of record, and it goes back to the payment method you used. How quickly it appears is then a matter for your bank or card issuer.

8. Changes to this policy

This policy carries a version and an effective date, shown at the top of the page. The version recorded against your order when you paid is the one that governs your purchase; a later edit cannot be applied backwards to it.

Terms of ServiceLicence