legal: add a Refunds and Cancellation section to the terms

[chaitanyagiri]

What this does

docs/terms.html mentioned refunds in exactly one place: a clause inside 08 Donations saying a donation is a gift and is not refundable. There was nothing about paid licences at all, and Pro has been on sale for weeks.

This adds 09 Refunds and cancellation and moves the money language out of Donations so it is not the only place a payment is discussed.

The new section says

1. All payments are final and we do not give refunds. Purchases, donations, unused time.
2. In most cases there is nothing to cancel, because Pro is a one time payment for a fixed term, not a subscription. No card kept, nothing renews, the free app keeps working when the term ends. This is genuinely good news for the buyer and it does most of the work of sounding reasonable.
3. Where a plan is charged on a recurring basis, it stops from the account. Stopping prevents future charges and does not refund past ones. Written without naming a specific plan.
4. One discretion line: we may still refund at our sole discretion, and doing it once creates no right to it. This is what lets us refund someone we want to refund without contradicting our own terms.
5. A short carve out for mandatory consumer law. A clause that claims to remove rights the law gives is the clause that gets struck down whole, which would take the rest of the section with it.

Other changes in the file

• The short version box gains one sentence on money, so a person who reads only the summary knows payments are final before they pay rather than after. Good news first: one time term, nothing renews, nothing to cancel.
• 07 Paid services gains a paragraph on Pro: sold at harnessmd.com, one time payment for a fixed term, not a subscription, Razorpay, and that the harnessmd.com terms govern the purchase itself. Without this the page never says we sell Pro, so the new refunds section would be about a product the document does not describe.
• 08 Donations keeps the gift language and now points at the new section instead of carrying the policy alone.
• Sections 09 to 14 renumber to 10 to 15. Table of contents updated. Last updated date becomes 16 September 2026. The effective date is unchanged.
• No other legal page is touched and no version number is touched.

Flagged, needs a decision, deliberately not fixed here

1. There are now two different Terms of Service live. harnessmd.com/terms serves a full, newer document, effective 12 September 2026, from Chaitanya Information Technologies, with its own section 7 Paid plans and section 8 Refunds. It states that it applies to munderdiffl.in as well. This page still says the terms are from an individual developer and that "there is no company". Both are published. Which one governs a Pro purchase is a real question and it needs answering by a person, not by a patch. The wording added here was matched to the harnessmd text on purpose so the two do not contradict each other in the meantime.
2. Support address. The new section sends billing problems to support@harnessmd.com, which is the address already published on harnessmd.com. The Contact section of this page still uses the personal Gmail address. Changing a published contact address is a separate decision, so it is not in this diff.
3. harnessmd.com has no page at a refunds URL. Its refund terms live inside /terms section 8. /refunds, /refund and /cancellation all 404. Razorpay's checklist expects a distinct, linked Refund and Cancellation policy. That is a different repo and a deploy, so it is not in this PR.

None of the text here is legal advice. It is policy wording written to match the product.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UkBAGTNhQsCrhyBFcnG9AS

[github-actions]

🚫 This PR is missing its before/after evidence

Every pull request here has to show its work. Screenshots or a short screen recording, before the change and after it.

• Before — no image or video under that heading
• After — no image or video under that heading

How to fix it: edit the description, keep the ### Before and ### After headings from the template, and drag an image or video under each. GitHub uploads it inline. This check re-runs the moment you save.

A bug fix with no visible surface still needs it: show the failing behaviour, then the same steps passing. A terminal recording is fine.

Genuinely nothing to show — a CI tweak, a typo, a dependency bump? A maintainer can apply the no-visual-change label. Please don't ask unless it truly has no observable effect.

📖 CONTRIBUTING.md → Evidence is mandatory