Legal Framework

Terms of Service

Effective Date: May 28, 2026Operated by Buggu Labs, India

These Terms of Service govern your access to and use of the RuntimeHQ platform, APIs, SDKs, control dashboard, and associated operational support systems.

1. Platform Services

RuntimeHQ provides operational runtime-state infrastructure designed for customer-facing production systems. The platform enables corporate organizations to compute live edge state settings, coordinate incidents, schedule maintenance windows, distribute runtime-state updates using secure APIs/SDKs, and retain auditable history records.

Institutional Scope: RuntimeHQ is intended exclusively for organizational, administrative, SRE, and developer operational use. It is not intended for personal consumer use.

2. Eligibility & Administrative Accounts

Eligibility Scope

You may configure and access RuntimeHQ only if you are authorized to act on behalf of your legally formed organization, possess full authority to enter into binding agreements, and your use conforms to all local and international laws.

Administrative Duties

Organizations remain solely responsible for the safety of administrative credentials, securing API credentials, coordinating authorized dashboard operators, and validating all customer-facing state banners or message strings before triggering public activations.

3. Guided Evaluation Access

We may provide limited, temporary Guided Evaluation Access solely to demonstrate product value and evaluate operational compatibility:

Operator LimitsUp to 3Authorized Admin Users
App ScopeUp to 3Target Applications
Standard Window14 DaysDuration Period

Evaluation environments are strictly intended for testing, SRE operational rehearsals, and integration verification. RuntimeHQ reserves the absolute right to suspend, terminate, or restrict evaluation instances at any time without prior notice.

4. Subscription & Cancellation Terms

Subscription Billing

Commercial deployment requires a paid subscription under agreed invoice plans (annual, enterprise custom license, or onboarding packages).

Cancellation Policy

Customers may cancel services at any time via written notification. Unless agreed otherwise, active features remain accessible until the end of the paid billing cycle.

Strict No-Refunds

Because we provide Guided Evaluation Access to completely evaluate compatibility prior to purchase, all commercial payments are entirely non-refundable.

5. Acceptable Use Policy

To sustain the high-reliability edge framework for all integration nodes, customers strictly agree not to:

• Reverse engineer core APIs or SDKs
• Scrape control dashboards or APIs
• Execute unannounced security or penetration checks
• Run excessive load/stress tests on edge infrastructure
• Bypass credentials or session control checks
• Resell or white-label state distribution APIs

6. API Throttling & Rate Limits

RuntimeHQ enforces request limits, rate throttling rules, and security protection controls. We reserve the absolute right to limit, throttle, or temporarily restrict endpoint connections if necessary to preserve platform consistency, block DDoS attempts, or safeguard edge CDN pipelines.

7. Suspensions & Post-Account Retention

Platform Suspensions

We may suspend or restrict account credentials immediately for abuse, commercial non-payment, system vulnerabilities, unauthorized security checks, excessive API overhead, or legal requirements.

1-Year Audit Retention

Following account closure or subscription termination, operational logs, incident timelines, and audit trails remain securely archived for up to 1 year to preserve system-wide audit history and legal integrity.

8. Intellectual Property & System Feedback

Intellectual Property Ownership

RuntimeHQ and all associated software engines, dashboards, APIs, SDKs, design variables, and technical documents represent the exclusive intellectual property of Buggu Labs. Customers receive a limited, revocable, non-exclusive right to utilize integration endpoints in accordance with these Terms. No ownership transfers occur under any circumstances.

Feedback Ownership

Any technical feedback, feature suggestions, SRE workflow reviews, or documentation inputs provided voluntarily by customers may be deployed and implemented globally by Buggu Labs without restriction, cost, or royalty obligations.

9. Warranty Disclaimers & Limitation of Liability

Disclaimer of Warranties

RuntimeHQ is provided on an "as is" and "as available" basis. To the maximum extent permitted by law, Buggu Labs disclaims all warranties—express, implied, or statutory—including merchantability, fitness for specific operational tasks, non-infringement, or uninterrupted availability. Edge calculations are not guaranteed to prevent downtime or customer impact.

Strict Limitation of Liability

To the maximum extent permitted under applicable law, Buggu Labs and its partners shall not be held liable for any indirect, consequential, special, incidental, or exemplary damages—including business interruption, lost revenue, lost profits, lost datasets, system outages, data residency shifts, or third-party cloud provider failures.

Maximum Liability Cap: Under all legal theories, our total aggregate liability arising from or related to the services shall strictly not exceed the total commercial fees paid by the customer to RuntimeHQ during the 12-month period immediately preceding the event initiating the claim.

10. Governing Law & Dispute Resolution

These Terms of Service, all operational agreements, and subsequent customer integrations are governed exclusively by the laws of India. Courts located in Haryana, India hold absolute and exclusive jurisdiction over any legal claims or disputes arising under these Terms.

Commercial Inquiry

Establish Custom Enterprise Agreements

Connect with our commercial solutions SREs to outline bespoke licensing, custom SLAs, regional data replication protocols, or tailor liability cap allocations.

Book technical discussion

No sales pitch. Connect directly with our platform SREs to evaluate integration feasibility.

runtimehq-sre-shell
$ echo $SRE_EMAIL
Recommended Context

To help us prepare for our discussion, please share some context on your current outage banner workflow, such as:

  • Hardcoded banner deployments
  • Toggling CMS content manually
  • Editing feature flags during active incidents