Plain English mostlyBack to homeRG-LEGALTERMS

Terms of Service.

Last updated · May 19, 2026

§ 01

Who we are

RunGuard is operated by Robion Systems BV, a private limited liability company incorporated in the Netherlands. These Terms apply to your access to and use of RunGuard, including the dashboard, API, SDKs, documentation, GitHub App, and related services.

In these Terms, "RunGuard," "we," "our," and "us" mean Robion Systems BV. "You" means the person or organization using the Service. If you use RunGuard for an organization, you confirm that you are authorized to accept these Terms on that organization's behalf.

§ 02

Acceptance of terms

By creating an account, installing the RunGuard GitHub App, using an SDK, sending data to the API, or otherwise using the Service, you agree to these Terms. If you do not agree, do not use the Service.

If you have a separate signed agreement or order form with Robion Systems BV for RunGuard, that agreement controls where it conflicts with these Terms.

§ 03

Description of service

RunGuard is a control plane for production reliability. We ingest production runtime errors from your application, classify and group them, apply your safety policy, build a review-grade Markdown crash packet, and dispatch the incident to an AI executor of your choice. The actual fix work runs on your own GitHub, AI, CI, or local-agent infrastructure, using accounts, seats, keys, runners, and provider limits that you control.

RunGuard provides orchestration, safety policy, crash-packet generation, dispatch routing, dashboard workflows, and status tracking. RunGuard does not guarantee that every error will be detected, that every incident will be routed, or that any proposed fix will be correct, secure, or suitable for production.

Features described as beta, preview, experimental, planned, or on the roadmap may change, pause, or never ship. We may add, remove, or change executor integrations as the Service evolves.

§ 04

Accounts and access

4.1 Account creation

To use RunGuard, you must authenticate via GitHub OAuth. You are responsible for maintaining the security of your GitHub account, RunGuard account, API keys, repository settings, and any activity that occurs under credentials or installations you control.

4.2 Business use

RunGuard is primarily intended for businesses, software teams, and professional users. You must be at least 18 years old and legally able to enter into these Terms. If mandatory consumer-protection rules apply to you, nothing in these Terms limits rights that cannot legally be waived.

4.3 Repository access

By installing the RunGuard GitHub App on a repository, you grant us permission to:

  • Read minimum repository metadata for routing context, including owner, name, repository ID, and default branch
  • File labeled GitHub Issues containing the crash packet (when an Issue-based executor is selected)
  • Receive signed webhook events for Issues and pull requests to track the lifecycle of each incident
  • Track external links produced by your chosen executor (Issue or PR URLs)

RunGuard does not clone your repository as part of routine operation and does not modify your source code directly. Any pull request you receive is opened by your chosen executor or by a user acting in your repository, using permissions you grant separately.

§ 05

Your responsibilities

You are responsible for deciding which repositories to connect, what data to send, which executors to enable, which protected paths to configure, and whether to review, modify, merge, deploy, or reject any proposed fix.

You must not send RunGuard end-user personal data, payment data, health data, government identifiers, secrets, authentication tokens, or other sensitive data unless we have expressly agreed to that in writing. RunGuard is designed for technical incident context, not for storing sensitive user records.

You are responsible for your compliance with laws, regulations, customer commitments, open-source licenses, internal policies, and third-party provider terms that apply to your use of RunGuard.

§ 06

Acceptable use

6.1 You agree not to:

  • Use the Service for any illegal purpose or in violation of any laws
  • Attempt to gain unauthorized access to the Service or related systems
  • Probe, scan, load test, or attack the Service except as authorized in writing
  • Interfere with or disrupt the Service, queues, or workers
  • Bypass plan limits, rate limits, authentication, authorization, or security controls
  • Use the Service to develop, benchmark, or operate a competing product using non-public RunGuard functionality
  • Reverse engineer, decompile, or disassemble the Service, except to the extent applicable law permits this despite the restriction
  • Remove or obscure proprietary notices from the Service
§ 07

Data and privacy

7.1 Data we collect

  • Error signatures, stack traces, and minimal request context
  • Repository identifiers such as owner, name, branch, and GitHub repository ID
  • GitHub account information from the OAuth scope you consent to
  • Usage, billing, support, and security information needed to run the Service

7.2 Data usage

We use collected data solely for incident classification, packet construction, dispatch routing, quota enforcement, security, support, billing, analytics, and Service operation. We do not sell your data to third parties.

7.3 Privacy policy

Our Privacy Policy explains how we collect, use, store, and protect personal data. If these Terms and the Privacy Policy conflict, these Terms control for contractual matters and the Privacy Policy controls for privacy matters.

7.4 Data security

All data is encrypted at rest and in transit. Secrets matching common patterns (GitHub tokens, OpenAI/Anthropic keys, Bearer headers, environment-variable assignments) are redacted at ingest before storage, but no automated redaction is perfect. You remain responsible for avoiding unnecessary sensitive data in payloads sent to RunGuard.

§ 08

Safety policy and protected paths

RunGuard implements a default safety policy for sensitive code paths including authentication, authorization, billing, payments, and database migrations. You can customize protected paths from the Settings page. Protected paths are enforced before an incident is dispatched to an executor, but they are a guardrail rather than a substitute for engineering review, code review, CI, testing, access controls, or deployment controls.

§ 09

Third-party services

RunGuard integrates with third-party services such as GitHub, Stripe, Cloudflare, and optional AI or coding executors selected by you. Those services are operated by their own providers and are governed by their own terms, policies, limits, and pricing.

You are responsible for obtaining and maintaining any third-party accounts, seats, API keys, runners, billing arrangements, and permissions needed for your chosen workflow. RunGuard is not responsible for third-party outages, rate limits, pricing changes, security incidents, model behavior, generated output, or account decisions.

§ 10

Service availability and changes

10.1 Availability

We strive to maintain high availability but do not guarantee uninterrupted access. We may suspend or modify the Service for maintenance, security, abuse prevention, infrastructure changes, legal compliance, or other operational reasons.

10.2 Modifications

We may improve, modify, restrict, suspend, or discontinue parts of the Service. For material changes that negatively affect active paid subscriptions, we will use reasonable efforts to provide advance notice where practical.

§ 11

Billing and payment

11.1 Subscription plans

Free and paid plans may include limits for repositories, users, errors, incidents, fixes, executors, retention, or other product usage. Paid plans are billed monthly, annually, or as otherwise stated at checkout or in an order form.

11.2 Payment processing

Payment methods, invoices, plan changes, and cancellations are managed through Stripe or another payment processor we designate. You authorize us and our payment processor to charge applicable fees, taxes, and renewals using the payment method you provide.

11.3 Taxes

Prices are exclusive of taxes unless stated otherwise. You are responsible for VAT, sales tax, withholding tax, duties, and similar charges, except taxes based on our net income.

11.4 Compute is yours

RunGuard charges only for orchestration. The AI executor performing the actual fix work runs on your account — your GitHub Copilot seat, your Anthropic API key stored in your repository's GitHub Actions secrets (for Claude Code Action), or any other provider you bring as new executors ship. RunGuard never proxies or bills for AI tokens and never receives or stores your AI provider credentials.

11.5 Quotas and overages

We may enforce plan limits at ingest, dispatch, dashboard, or API level. If a plan page displays estimated overage amounts, those amounts are informational unless checkout, an invoice, or a signed order form states that usage-based charges apply.

11.6 Refunds

Unless required by law or stated in a separate agreement, monthly plans are non-refundable. We may offer prorated refunds for annual plans canceled within 30 days. Any mandatory consumer withdrawal or cancellation rights that apply to you remain unaffected.

11.7 Cancellation

You may cancel your subscription at any time through the Stripe portal. Cancellation takes effect at the end of the current billing period unless checkout, the portal, or a separate agreement states otherwise. You remain responsible for charges incurred before cancellation takes effect.

§ 12

Intellectual property

12.1 Your content

You retain all rights to your code and repositories. By using RunGuard, you grant us a limited license to access metadata and incident context solely for the purpose of providing the Service.

12.2 Output

Crash packets, GitHub Issues, and any pull requests opened by your chosen executor on your repositories are made available for your use, review, and modification. We do not claim ownership of your code or repository content.

12.3 Service IP

RunGuard and all related technology, trademarks, and intellectual property remain the property of Robion Systems BV or its licensors. You may not copy, sell, sublicense, host, or make the Service available to others except as these Terms allow.

12.4 Feedback

If you send us ideas, suggestions, or feedback, you allow us to use them without restriction or compensation to you.

§ 13

Confidentiality

Non-public incident data, repository metadata, business information, and account information exchanged through the Service should be treated as confidential. We will use your confidential information only to provide, secure, support, improve, and operate the Service, or as otherwise permitted by these Terms, the Privacy Policy, or law.

Confidential information does not include information that is already public, independently developed without using confidential information, lawfully received from another source, or approved for disclosure by the owner.

§ 14

Disclaimers

The Service is provided "as is" without warranties of any kind. To the maximum extent permitted by law, we disclaim all warranties, including implied warranties of merchantability, fitness for a particular purpose, title, non-infringement, availability, security, and accuracy.

RunGuard is not a substitute for observability, incident response, security review, human code review, CI, testing, backups, rollback planning, or deployment controls. You are responsible for validating all outputs and proposed changes before relying on them.

§ 15

Limitation of liability

To the maximum extent permitted by law, RunGuard is not liable for:

  • Bugs, errors, vulnerabilities, outages, data loss, or other issues introduced by code changes opened by your executor or merged by you
  • Production incidents, downtime, lost profits, lost revenue, lost business opportunities, reputational harm, or loss of goodwill
  • The behavior, output, cost, rate-limiting, outage, or account action of any third-party service
  • Indirect, incidental, special, consequential, exemplary, or punitive damages

To the maximum extent permitted by law, our total aggregate liability for all claims relating to the Service is limited to the fees you paid to us for the Service during the 12 months before the event giving rise to the claim.

Nothing in these Terms excludes or limits liability where doing so would be unlawful, including liability for intent, deliberate recklessness, fraud, or mandatory rights that cannot be waived.

§ 16

Indemnification

If you use RunGuard for a business or organization, you agree to indemnify and hold Robion Systems BV harmless from claims, damages, fines, costs, and expenses, including reasonable legal fees, arising from:

  • Your use of the Service
  • Your data, repositories, code, products, or services
  • Your violation of these Terms or applicable law
  • Your use, review, merge, deployment, or rejection of executor outputs
  • Your third-party accounts, integrations, or provider terms
§ 17

Suspension and termination

You may stop using RunGuard at any time. We may suspend or terminate access to the Service if you violate these Terms, create security or operational risk, fail to pay amounts due, misuse the Service, or if we are required to do so by law or a third-party provider.

On termination, your right to use the Service ends immediately. We may delete or retain data in accordance with the Privacy Policy, our retention schedules, and legal requirements. Sections that by their nature should survive termination will continue to apply, including payment obligations, intellectual property, confidentiality, disclaimers, liability limits, indemnities, and dispute terms.

§ 18

Governing law and disputes

These Terms are governed by the laws of the Netherlands, without regard to conflict-of-law rules. Subject to any mandatory law that gives you another forum, disputes relating to these Terms or the Service will be submitted to the competent courts in the Netherlands.

Before starting formal proceedings, both sides agree to try to resolve the dispute in good faith by contacting the other side and allowing a reasonable time for response, unless urgent legal relief is needed.

§ 19

Changes to terms

We may update these Terms from time to time. If changes are material, we will provide notice by email, through the Service, or by another reasonable method. The updated Terms will state their effective date.

For continuing paid subscriptions, material changes will take effect no earlier than 30 days after notice unless the change is required sooner for security, legal, or operational reasons. If you do not agree to updated Terms, you must stop using the Service and cancel your subscription. Continued use after the effective date means you accept the updated Terms.

§ 20

Contact

For questions about these Terms or RunGuard, contact Robion Systems BV at info@runguard.ai.