Terms of service
Gitback.us is a feedback, roadmap, changelog and FAQ portal for a GitHub repository. These terms are the agreement between you and us about using it.
They are written to be read. Where a clause restates a rule the product is actually built on, it says which one, so you can check the claim against docs/product/business-rules.md rather than take it on trust.
Last updated 18 September 2026.
What Gitback is
You give Gitback the URL of a GitHub repository — the Source Repo — and it renders a Board: a public-facing portal with Feedback, Roadmap, Changelog and FAQ modules over that repository's own Discussions, Issues, Releases and labels. It is a view of your repository and a way to write back into it. It is not a place your users' contributions are kept instead.
Anyone can open a Board for a public repository without an account. Claiming a Board — becoming the Client who can curate it — requires signing in with GitHub from an account with write access to that repository. GitHub is the only identity Gitback accepts (BR-012).
Your content stays yours
Every idea, comment and vote made through a Board is created as a real GitHub object in the maintainer's own repository, by the account that made it, and we keep no copy of it — your feedback lives in your GitHub, not our database (BR-013). We claim no ownership of it and no licence to it beyond what we need to display it back to you on the Board you asked us to render.
Because the content is in your repository, it is governed by your repository's licence and by your agreement with GitHub, not by this one. That also means we cannot edit or delete it for you: those are GitHub actions, taken with your GitHub account.
The promise above is a claim about content, not about all state. We do hold operational state — a read cache, claim state, a takedown blocklist and billing entitlement — and the privacy page enumerates all of it.
What we write into your repository
Before the first time Gitback writes anything into a Source Repo, it shows you exactly what will be created and asks you to confirm (BR-029). That footprint is a .gitback/ directory of plain markdown and a few namespaced labels — nothing that needs a runtime of ours to make sense of.
Declining is a supported answer, not an error (BR-030). A Board that runs without a footprint still does most of its job; roadmap status and board configuration move into our own store, and the FAQ module switches off rather than quietly relocating your content into our database (BR-031). You can withdraw consent later, which stops our future writes. It never deletes what is already there, because those files and labels are yours.
Boards, claiming and takedown
A public repository can be given a Board by anyone, including someone who does not own it. If you own the repository and do not want the Board, you can take it down, and the takedown is permanent: the repository cannot be re-boarded by anyone re-typing the URL, and only a Claim from an account with write access reopens it (BR-015).
A private repository's Board is private by default and shows nothing until its Client explicitly turns exposure on (BR-011). Paying for a plan does not publish anything.
Plans and payment
Boards for public, open-source repositories are free. A Board for a private repository needs a signed-in GitHub account on a paid plan (BR-033). Current prices and what each plan includes are on the pricing page, which is the authority — prices are configuration here, not constants, and will change as we learn (BR-021).
Paid plans are billed in advance through Stripe, who handle your card details; we never see them. You can cancel at any time and the plan runs to the end of the period you have paid for. We do not refund part-used periods as a rule, but if Gitback did not do what you paid for, write to us and we will sort it out.
If a payment fails or a plan lapses, a private repository's Board stops being served. Nothing in your repository is touched.
If you leave
If you stop paying, unclaim your Board, or Gitback disappears entirely, everything under .gitback/ and every label we created stays in your repository and keeps working (BR-032). They are plain markdown and native GitHub labels; reading them needs nothing of ours. That is the strongest form of the promise, and we consider ourselves bound by it: we will never write anything into a Source Repo that is meaningless without our product.
Using it reasonably
We ask a few things of you. Do not use Gitback to:
- post unlawful content, or content that infringes someone else's rights;
- harass anyone, on a Board or through the repository behind it;
- impersonate a repository's maintainer, or present a Board you do not own as officially theirs;
- work around the entitlement checks, or scrape the service in a way that degrades it for other people;
- attempt to reach repositories or accounts your GitHub credentials do not already give you.
We can suspend a Board or an account that does these things. Where we do, we will say why.
Availability, warranties and liability
Gitback depends on GitHub. When GitHub's API is unavailable or rate-limits us, parts of a Board will be too. We aim to keep the service running and do not promise that it always will be; it is provided as it is, without warranties beyond those the law gives you and does not let us exclude.
To the extent the law allows, we are not liable for indirect or consequential loss, and our total liability to you for any claim is limited to what you paid us in the twelve months before it arose. Nothing here limits liability for death, personal injury, or fraud.
Changes to these terms
We may change these terms. When a change is material, we will tell Clients with an account before it takes effect, and the date at the top of this page always says when the wording last moved. Continuing to use Gitback after a change means you accept it; if you do not, cancel, and everything in your repository stays where it is.
Contact
Gitback.us is a coduo.co product. Questions about these terms, takedowns, or anything else go to hello@coduo.co.