Fair Use Policy

1. The short version

Plan limits on RepoWarden — repository counts, dependency-update PRs per month, CI fix attempts, test generations, scan rate — exist so the service stays fast, reliable, and affordable for everyone. They are real numbers, but they are not booby-trapped: occasional bursts above them are fine. Sustained or deliberately abusive overuse is not.

If your usage looks like a problem, we'll email you before doing anything else. Honest customers will never be surprised.

2. What counts as fair use

Using RepoWarden as designed: connecting repositories you control, receiving dependency-update PRs, having the runner attempt CI fixes, and generating tests. Triggering scans manually within the displayed cadence. Using the chat / @repowarden commands on PRs we opened. Connecting your team to its own repositories.

3. What counts as abuse

Examples (not an exhaustive list):

• Scripted requests or automation that bypass our rate limits or our UI to trigger scans, PRs, or CI fixes faster than the plan allows.
• Connecting repositories you do not own or have written permission to modify.
• Splitting a single team across multiple Free or Starter accounts to avoid plan limits.
• Using RepoWarden to attack, scan, or modify infrastructure outside of repositories you control (we are a maintenance tool, not an offensive security tool).
• Sustained usage exceeding plan limits by more than 50% for two or more consecutive billing periods on a Free, Starter, or Pro plan.
• Reverse-engineering, scraping, or republishing the service.

4. What we do if usage looks like a problem

In order, escalating only when needed:

1. We contact you — an email to the workspace owner with the specifics, and a chance to either fix it or move to a tier that fits.
2. We may throttle — slowing scans, deferring PRs, or pausing CI-fix attempts until we've talked.
3. We may suspend — only after at least one warning, and only if usage is actively harming the service or other customers.

We do not silently degrade performance, hide your data, or terminate accounts without notice. If we ever need to suspend, we'll explain why and how to resolve it.

5. Checking your usage

Every workspace has a Usage page showing your current numbers against your plan caps. We update it in near real-time. If anything looks off, email hello@repowarden.dev before assuming it's a bug.

6. Burst tolerance

We allow short-term overage of up to 50% on individual plan caps in a given month, automatically and silently, when there's a clear legitimate reason — for example, a one-off CVE wave, an EoL upgrade that triggers many PRs at once, or a bulk repo onboarding. We don't charge for this. We do count it for the purposes of identifying accounts where overage is the norm rather than the exception.

7. Enterprise customers

If you're on an Enterprise contract, your contract supersedes this policy. Limits and remedies are whatever's in your signed agreement.

8. Updates

We may revise this policy. If we tighten it materially, we'll email workspace owners at least 30 days before the change takes effect.

9. Contact

Questions, edge cases, or "is this OK?" → email hello@repowarden.dev. The policy is operated by Turbo Technologies Ltd, registered in England and Wales (company number 13124266), trading as RepoWarden.