The guarantee

If jCodeMunch doesn’t pay for itself, you don’t pay for jCodeMunch.

Here is what that means.

Try it for 30 days. If it didn’t earn its keep, ask for your money back.

You have 30 days from the day you buy. Use it on your real work, with the anonymous savings telemetry left on. If it hasn’t paid for itself by then, email me and I’ll refund what you paid.

You don’t have to prove anything. You decide whether it paid for itself. I’ll ask what happened, because I’d like to fix it, and your refund doesn’t depend on the answer.

Why telemetry has to be on

I can’t fix what I can’t see. The telemetry is how I find out whether the tools were being used on your machine and what they reckoned they saved.

It is on by default, and it sends three things: a random anonymous ID, and two running counts of tokens saved. No code, no file paths, no repo names, nothing about you. The full disclosure is here.

You can switch it off any time with share_savings: false in config.jsonc, or JCODEMUNCH_SHARE_SAVINGS=0. The product works the same without it. The guarantee covers installs that ran with it on.

Those counts are the tools’ own estimate. They are not your bill, and I won’t use them to argue you out of a refund.

One email

Write to j@gravelle.us from the address you bought with, inside the 30 days. Include the anon_id from ~/.code-index/_savings.json so I can find your counts.

The money goes back to the payment method you used. Stripe says refunds take 5 to 10 days to appear on a statement. Your licence key is switched off when the refund goes out.

Personal and non-commercial use was free before you bought, and it stays free after.

Every licence bought on this site

Builder, Studio and Platform, bundles and single-tool licences alike, for jCodeMunch, jDocMunch and jDataMunch.

These terms apply to purchases from 13 October 2026. If you bought before that, you bought under the one sentence at the top of this page, and it still stands. Email me.

Small repositories

If your agent can find what it needs with its built-in search in a couple of steps, an index adds work where it was meant to remove it. The benefit grows with the size of the codebase, and with how often the agent opens a whole file to read one part of it.

Not sure which side of that you’re on? Count before you buy: What’s actually filling your Claude Code session?

J. Gravelle, Member
jMunch LLC