Add Refunds clause to Terms of Service - #1545
Merged
Merged
Conversation
Payments for completed and accepted work are non-refundable, with the usual carve-outs: this doesn't override rights granted by applicable law, and fraudulent, duplicate, or undelivered transactions can still be refunded after review. Inserted as clause 6, next to the existing Disputes clause, renumbering the clauses that follow. Updated the English translation catalogs (generated/result) to match; frontend/src/translations/*/br.json were intentionally left untouched since translating contract language needs review by someone who can vouch for the Portuguese wording, not a best-guess translation.
alexanmtz
added a commit
that referenced
this pull request
Sep 6, 2026
… regression (#1546) * Link the refund policy from disputes-and-refunds.md Adds a short "Our refund policy" section stating the general rule (completed/accepted work is non-refundable, with the usual fraud/duplicate/undelivered carve-outs) and points to the Refunds clause now in the Terms of Service (#1545), so the practical debit/credit mechanics on this page sit next to the policy they implement. There's no direct URL for the Terms of Service in the app today — it opens as an in-page dialog from the site footer's "Legal" menu rather than living at its own route — so the link points to gitpay.me with that noted, instead of a fabricated deep link. * Actually stop tracking _site/ this time The previous attempt at this (in #1543) added .gitignore's _site/ entry but the removal itself got reverted by an in-progress `git reset` while splitting that PR into commits, so the merge ended up re-committing _site/ anyway — with my local validation build's output baked in (Jekyll v3.10.0, localhost:4000 canonical URLs), which is worse than the original stale copy it was meant to replace. This time: a plain `git rm -r --cached _site`, committed immediately, nothing in between to undo it. Verified the diff below is 202 pure deletions with no other changes. --------- Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a Refunds clause to the in-app Terms of Service (
terms-of-service.tsx), per request:Inserted verbatim as clause 6, placed right after the existing "5. Disputes" clause since the two are closely related, renumbering the clauses that follow (Intellectual Property → 7, Termination → 8, Limitation of Liability → 9, Governing Law → 10, Changes → 11). Also bumped the "Updated" date shown on the page.
A companion docs change adds a link to this policy from
docs.gitpay.me's disputes-and-refunds page (separate PR against thegh-pagesbranch, coming next).Changes
frontend/src/components/design-library/molecules/content/terms/terms-of-service/terms-of-service.tsx— new clause 6, renumbered clauses 7–11, updated date.frontend/src/translations/generated/en.json,frontend/src/translations/result/en.json— updatedterms-of-service.contentandterms-of-service.dateto match, so the live English UI (which reads from these compiled catalogs, not just the component'sdefaultMessage) actually reflects the change.Needs human confirmation / follow-up
frontend/src/translations/{generated,result}/br.jsonstill have the old 10-clause text. I didn't attempt a Portuguese translation of new contract language without someone able to verify the legal wording — this needs a reviewed translation before the two languages match again.Validation
🤖 Generated with Claude Code
https://claude.ai/code/session_01PtCXQDsoFovaYbCxvdjua2
Generated by Claude Code