Skip to content
Code Recycle

Refund policy

Short version: if a listing claimed something that isn’t true, you get your money back. If it did what it said and you changed your mind, you don’t. Everything below is that line, drawn precisely.

What we refund, in full

The listing made a false claim

Every listing states what was verified — test counts, how many deliberate mutations the suite caught, which assurance gates passed. If any of that is wrong, that’s a refund. It’s a factual question, not a judgement call, and you don’t need to argue it.

It doesn't do what the description says

Not “it does less than I hoped” — it does not do the stated thing. Tell us what it says and what happened.

You never received it

Source is delivered as a private repository invite within 24 hours. If that didn’t arrive and we can’t fix it, you get your money back.

It shipped something that shouldn't be there

A live credential, a licence incompatible with what you were told, or an undisclosed install-time script. Refunded, and the listing comes down.

What we don't refund

Changing your mind after reading the source

You can’t un-see source code. This is the honest reason the policy is claim-based rather than no-questions-asked: an unconditional policy on source is an unconditional invitation to read it for free.

It works, but you wanted something else

Every listing states its limits, and several tell you to buy a different one — or nothing. Read those first; they’re there so this doesn’t happen.

You need it changed

That’s not a refund, it’s a customisation. Most listings offer paid changes with a firm quote up front.

The window

14 days from purchase for a claim-based refund. Longer if the problem is something we should have caught before listing it — a shipped credential has no deadline.

Email with the listing, the claim, and what happened. Refunds are processed to the original payment method.

If you're selling here

A refund is debited from your balance. You are notexposed to buyer’s remorse — that is the point of drawing the line at claims. You are exposed to overstating what you verified, which is entirely within your control.

So state claims narrowly and truthfully. “47 tests, 10 of 10 mutations caught” is a defensible sentence. “Production-ready” is not, and we’d rather you didn’t write it.

A pattern of upheld claim refunds affects your standing here and can delist you. A single one, handled well, does not.

Agents buying on someone's behalf

The same policy applies, and the machine-readable version is on each listing’s agent brief — the stated claims are exactly what a refund is measured against, so an agent can check compatibility before spending and cite a specific claim afterwards.

Payments are currently in test mode while the seller side opens up; nothing has been charged for real. This policy takes effect with live payments and is published now so it can be read before it matters.