How this works

Buying

Checkout runs on Polar, who are the merchant of record. That means Polar is the seller on the receipt, and they handle sales tax, VAT and GST for your country. You do not need an account here, and there is nothing to sign up for.

You pay once. There is no subscription on any product, and nothing expires. If a product is finished, charging rent for it would be charging for nothing.

Getting your files

Everything is delivered through Polar's customer portal. After paying you get an email with a link, and you can return to it any time by signing in with the address you paid with - Polar emails you a one-time code, so there is no password to keep.

Depending on the product, one or more of these will be waiting:

What	How it reaches you
Files	Download directly from the portal, as many times as you like. Every product has these.
Repository access	An invite to a private GitHub repository, sent to the GitHub account you connect at checkout. Products with this show Repository Sync Provided: Yes.
Licence key	Shown in the portal, for self-hosted software that validates one. Activates on up to three machines and can be rotated if one is retired.

Updates

Buying does not buy you future versions. Your licence to the version you bought does not expire, which is what "buy once, keep it forever" means. It is not a commitment to ongoing development, and the terms say so plainly.

In practice I do ship updates, because these are tools I use myself and a defect in one is my problem too. When an update goes out you get it at no extra cost. What I am not doing is pretending a small digital tool comes with a lifetime software-development contract.

How updates arrive depends on the product. If it has repository access, git pull and you are current, and the repository is the living version. If it is files only, the portal holds the latest build, so re-download whenever you want it.

Keep your own copy of anything you download. Third-party dependencies change, and download infrastructure is not promised to exist forever.

Licensing

The summary is below. The terms are the binding version, and they win wherever this page is looser.

• Use it commercially. Client work, internal tools, products you sell, published articles. No per-seat fee and no separate commercial tier.
• Modify it. These are meant to be taken apart. Fork the design system, rewrite the prompts, strip the parts you do not need.
• Share it inside your organisation. One purchase covers your team.
• Do not resell it as a product of its own, or redistribute it publicly. Building something on top and selling that is fine. Repackaging the thing itself is not.

Working with the knowledge bases

The knowledge bases are folders of markdown, deliberately. No framework, no runtime, no dependencies. Point an agent, an editor or a retrieval system at the folder and it works.

Two files do the heavy lifting:

• CLAUDE.md carries instructions for agents that read it - how to navigate the base, how to cite from it, and how to extend it without breaking its consistency.
• setup.md is the one file you edit. Your platforms, your taxonomy, your attribution windows, your metric owners. Everything else reads from it, so the base describes your business rather than a generic one.

Every entry opens with a single sentence stating what the thing is, and that sentence also appears in the table of contents. That is what lets an agent decide what is worth opening without opening it, which keeps a retrieval step cheap instead of forcing a full-context dump.

Refunds

Ask and you get one. Use the contact route in your purchases, which reaches me directly.

Digital goods are awkward to return, so there is no clever policy here: if a product was not what you expected, that is worth more to me as feedback than the sale was. Polar processes the refund back to your original payment method.

The full refund policy covers how it is processed and how Australian Consumer Law sits alongside it.

Support

These are products, not a service, so there is no SLA. In practice: if something is broken, tell me and I will fix it, because a defect in something I use myself is my problem too.

If you want something specific built, ask. That is a different conversation and sometimes an interesting one.