Terms of Service

Last updated: October 13, 2026

Triage is operated by Chodeberg, a sole proprietorship based in the United States ("Chodeberg", "we", "us"). Contact: help@support.chodeberg.com.

By creating an account or using Triage, you agree to these terms.

1. What Triage is

Triage by Chodeberg ("Triage") builds sandboxed environments from a software vendor's repository. It lets that vendor's customers report bugs into those environments, replays reported steps on clean machines, and gives the vendor verified reports and view-only live links.

There are two kinds of user:

Vendors connect a repository, pay for usage, and receive reports.
Reporters submit bugs to a vendor through the vendor's Triage intake (usually an MCP server added to their AI assistant). Reporters never pay.

2. Accounts

You need an account to use Triage. Everyone signs in with GitHub: vendors to the console, and reporters through a vendor's Triage intake. You're responsible for activity on your account and for keeping its access secure. You must be old enough to form a binding contract where you live. If you sign up for an organisation, you confirm you have authority to bind it.

3. Vendor responsibilities

By connecting a repository you confirm that:

you have the right to let us fetch, build and run that code, and to store snapshots of it, for the purposes in §5;
the code doesn't contain material you aren't allowed to share with a service provider;
you will not configure Triage to run malware, attack third parties, mine cryptocurrency, or bypass our limits.

You control who can report to you, your monthly spending cap and per-reporter quotas. You are responsible for how you use reports and the evidence in them.

4. Reporter responsibilities

When you submit a bug you agree:

not to submit illegal content, malware, other people's personal data, or secrets (API keys, passwords, tokens);
not to try to escape the sandbox, abuse the vendor's budget, or harass the vendor or others.

What you submit goes to the vendor you reported to, and to us as their service provider. Our software redacts likely secrets, but it can't catch everything. Don't paste anything you wouldn't send to the vendor.

5. What we do with vendor code

We fetch your code at the tagged commits you choose, using a read-only GitHub App. We never push to your repository.
We build an environment for each tag. We store a snapshot of the tagged source in Cloudflare Artifacts and a container image in Cloudflare's registry, so reports can be replayed and their root cause located.
We use your code only to provide Triage to you. We don't sell it, publish it, or use it to train AI models.
We delete an environment's snapshots when it's retired. If you uninstall the GitHub App, or the repository becomes private to us or is transferred, we delete everything for that repository within 7 days. Open reports keep their README and evidence but stop replaying.

6. Sandboxes and acceptable use

Triage sessions run in isolated, short-lived containers with no internet access by default, and with CPU, memory and time limits. We may stop, suspend or delete any session, environment or account that we reasonably believe breaks these terms or puts other users or our infrastructure at risk.

7. Credits, pricing and payment

Triage is paid for with credits. One credit is US$0.01 of value. Builds, live sessions and verification replays use credits at the hourly rates on the pricing page, for example 57 credits per hour on the standard 4 vCPU desktop. Rates may change with notice, and a change applies only to usage after it takes effect.
Credits are bought in packs (US$100, US$250, US$500 or US$1,000) or as a custom amount from US$100 to US$10,000, through Paddle, our merchant of record. Paddle is the seller of record, handles tax and payment, and its buyer terms also apply to the purchase. Paddle's fee comes out of the amount you pay. The credits you receive are shown before you pay and on your receipt.
Purchased credits don't expire. The free monthly grant (currently 100 credits) is used before purchased credits, and any unused part lapses at the end of the month.
Credits are reserved before a build or session starts and settled for what was actually used. Unused reservations are released.
Credits have no cash value and can't be transferred between accounts.

8. Refunds

You can ask for a refund of the unused credits from a purchase within 14 days of that purchase. We refund the unused share of what you paid for that purchase, through Paddle, to your original payment method.
Credits that have already been spent, and the free monthly grant, aren't refundable.
After 14 days, purchases are final, except where the law where you live gives you more rights.
To ask for a refund, email help@support.chodeberg.com from your account's email address with the date of the purchase, or reply to your Paddle receipt. We answer within 5 business days. Once a refund is approved, your bank may take a few more days to show it.
A refunded or charged-back payment removes the credits it bought. If some of those credits were already spent, the shortfall is recorded against your account.

The same policy is on its own page: Refund policy.

9. Reports, links and confidentiality

Reports are private to the vendor by default. View-only live links are capability links: anyone holding one can watch that session until it expires or is stopped, so share them with care. We treat report content as the vendor's confidential information.

10. Availability and changes

Triage depends on third-party infrastructure (Cloudflare, GitHub, Paddle), and some of it is in beta. We work to keep Triage available but don't guarantee uninterrupted service. We may change or discontinue features. For a material change that reduces what you've paid for, we'll give at least 30 days' notice. We'll post changes to these terms here and email account holders about material ones.

11. Intellectual property

You keep all rights to your code, reports and content. You grant us a limited licence to host, process and display them only to run Triage for you and the reporters you allow. We keep all rights to Triage itself.

12. Disclaimers and liability

Triage is provided "as is". A verified report means the bug reproduced in our environment; it doesn't guarantee the same behaviour on every machine. To the extent the law allows, our total liability for any claim is limited to the amount you paid us in the 12 months before the claim, and we're not liable for indirect or consequential losses. Some places don't allow these limits; where that's the case, they apply only as far as the law permits.

13. Ending your account

You can stop using Triage and delete your account at any time. We may end or suspend accounts that break these terms. On deletion, we delete your environments and snapshots as described in §5, and keep only what we must retain by law (for example payment records). Unused purchased credits on a deleted account are refundable only within the 14 days in §8.

14. Security reports

Please report security issues to security@support.chodeberg.com. Don't test against other users' data.

15. Governing law and contact

These terms are governed by the laws of the United States, without regard to conflict-of-law rules. Questions about these terms: help@support.chodeberg.com.