runQC
Home Features Pricing Docs About Contact Request access

Beta Program Agreement

Effective Date: June 5, 2026 · Last Updated: September 14, 2026 · Syntaxa LLC

This Beta Program Agreement ("Beta Agreement") is entered into between Syntaxa LLC ("Company," "we," "us," or "our") and the individual or entity participating in the runQC Beta Program ("Beta Participant," "you," or "your"). This Beta Agreement supplements and is incorporated into the runQC Terms of Service ("ToS"). In the event of a conflict between this Beta Agreement and the ToS, this Beta Agreement shall control with respect to the beta features and Beta Program participation.

BY PARTICIPATING IN THE BETA PROGRAM, YOU ACKNOWLEDGE THAT YOU HAVE READ, UNDERSTOOD, AND AGREE TO BE BOUND BY THIS BETA AGREEMENT, INCLUDING THE JOURNAL REVIEW AND DATA ACCESS PROVISIONS IN SECTION 5.


1. Beta Program Overview

1.1 Purpose

The runQC Beta Program ("Beta Program") provides early access to the runQC platform prior to general availability. The purpose of the Beta Program is to: (a) validate the Service's functionality, reliability, and user experience with real-world usage; (b) identify defects, performance issues, and areas for improvement; and (c) gather feedback to inform product development.

1.2 Beta Status

The Service is provided in beta and is under active development. Features, pricing, API interfaces, and data schemas may change materially during the Beta Program without notice. Beta features may be incomplete, contain defects, or function inconsistently.

1.3 Duration

The Beta Program begins on the date you accept this Beta Agreement and continues until: (a) Company announces general availability of the Service; (b) Company terminates the Beta Program; or (c) either party terminates this Beta Agreement in accordance with Section 8. Company will provide at least fifteen (15) days' notice before ending the Beta Program.


2. Eligibility and Access

2.1 Invitation

Participation in the Beta Program is by invitation or application. Company reserves the right to accept or reject any application at its sole discretion.

2.2 Beta Subscription

During the Beta Program, Company will designate the Subscription Plan tier applicable to your participation (which may be a beta-specific tier, or a standard tier at a reduced or waived fee). Any promotional pricing or credit allocations provided during the Beta Program are valid only for the duration of the Beta Program and do not create any obligation to continue such pricing after general availability.

2.3 Transition to General Availability

Upon general availability, Beta Participants will be required to select a standard Subscription Plan. Company will provide at least thirty (30) days' notice of the transition timeline and any pricing changes. Data created during the Beta Program will be preserved and migrated. After the transition, access to Journals and Test Results created during the Beta Program is subject to the viewing limits of your selected plan as described in Section 7.4 of the ToS, and those viewing limits are measured from the date each Journal is created.


3. Beta Participant Obligations

3.1 Feedback

Beta Participants agree to provide reasonable feedback regarding the Service, including: (a) bug reports and error descriptions; (b) usability observations; (c) feature requests and improvement suggestions; and (d) responses to surveys or questionnaires when reasonably requested. All Feedback is subject to the Feedback provisions in the ToS (Section 6.4).

3.2 Communication

Beta Participants agree to: (a) designate a primary contact for beta communications; (b) respond to Company inquiries within a reasonable timeframe; (c) participate in periodic check-ins or feedback sessions if reasonably requested.

3.3 Confidentiality

During the Beta Program: (a) the existence, features, performance characteristics, and limitations of the Service are Company's Confidential Information; (b) Beta Participants shall not publicly disclose, review, or benchmark the Service without Company's prior written consent; (c) Beta Participants may discuss their participation with their internal team members who need to know.

3.4 Responsible Use

Beta Participants shall: (a) use the Service in accordance with the ToS and Acceptable Use Policy; (b) report any security vulnerabilities, data breaches, or significant defects promptly to Company; (c) not rely on the Service as their sole quality assurance mechanism during the Beta Program, given the pre-release nature of the software.

3.5 Publicity

Beta Participant grants Company the right to identify Beta Participant by name and logo as a runQC beta participant on Company's website and in marketing materials. With Beta Participant's prior written approval of the specific text (such approval not to be unreasonably withheld), Company may publish case studies describing Beta Participant's use of the Service and testing outcomes. Beta Participant may revoke the rights granted in this Section prospectively at any time by written notice to [email protected]; revocation does not affect materials published prior to revocation.


4. Company Obligations

4.1 Service Provision

Company will use commercially reasonable efforts to: (a) maintain Service availability during the Beta Program, though uptime guarantees do not apply; (b) address critical defects and security vulnerabilities in a timely manner; (c) provide reasonable support to Beta Participants.

4.2 Communication

Company will: (a) provide advance notice of planned maintenance, breaking changes, and significant updates when feasible; (b) maintain a communication channel (email, Slack, or equivalent) for Beta Participant inquiries; (c) share relevant product roadmap information to the extent Company deems appropriate.


5. Journal Review and Data Access

THIS SECTION CONTAINS IMPORTANT PROVISIONS REGARDING COMPANY'S ACCESS TO AND USE OF YOUR DATA DURING THE BETA PROGRAM. PLEASE READ CAREFULLY.

5.1 Journal Review Right

During the Beta Program, Company reserves the right to access, review, and analyze Journals stored in Beta Participant Accounts for the following purposes:

(a) Product Improvement: Evaluating the accuracy, quality, and effectiveness of the Service's AI-generated test questions, grades, findings, and recommendations to improve testing algorithms, grading calibration, and agent behavior.

(b) Defect Identification: Identifying bugs, errors, inconsistencies, or failure modes in the Service's operation by examining real-world test execution data.

(c) Performance Analysis: Analyzing run duration, cost patterns, credit consumption, and resource utilization to optimize Service performance and pricing models.

(d) Feature Validation: Assessing whether Service features (including test orchestration modes, agent selection, and reporting) perform as intended under real-world conditions.

5.2 Scope of Access

Company's Journal review may include access to:

  • Agent interaction records (questions generated by the Service and responses from your Target Agent)
  • Quality scores, grades, findings, and verdicts
  • Test suite definitions and configurations
  • Run metadata (timing, cost, model usage, error logs)
  • Context documents uploaded by Beta Participant

Company's Journal review will never include access to credential values you store in secret-designated fields (including target agent authentication tokens and BYOK LLM provider API keys). These values are stored in an encrypted vault (AWS Secrets Manager), are excluded from Journals, and are used solely to execute your test runs.

5.3 Limitations on Use

Company's access to Journals under this Section is subject to the following limitations:

(a) Purpose Limitation: Journal data accessed under this Section shall be used solely for the purposes stated in Section 5.1. Company shall not use Journal data for marketing to third parties, sale to third parties, or any purpose unrelated to improving the Service.

(b) Access Controls: Access to Beta Participant Journals shall be limited to Company personnel who require such access for the stated purposes and who are bound by confidentiality obligations.

(c) No Public Disclosure: Company shall not publicly disclose or publish any identifiable Journal data or Customer Data from Beta Participant Accounts without the Beta Participant's explicit prior written consent.

(d) Anonymization: To the extent Company uses insights derived from Journal review for general product improvements, benchmarking, or documentation, such use shall be in aggregated and anonymized form that does not identify the Beta Participant, their Target Agent, or their end users.

(e) No Model Training: Company shall not use Beta Participant Journal data to train, fine-tune, or improve third-party machine learning models. Company may use anonymized, aggregated insights to improve its own testing algorithms and heuristics.

5.4 Consent and Acknowledgment

By participating in the Beta Program, you expressly consent to Company's access to and review of Journals as described in this Section 5. You acknowledge that:

(a) This Journal review is a material condition of participation in the Beta Program, and the benefits of early access and beta pricing are provided in consideration of this consent.

(b) You have the authority to consent to this access on behalf of your organization and have informed relevant stakeholders within your organization.

(c) You are responsible for ensuring that any data submitted to the Service during the Beta Program (including Target Agent responses) does not contain data you are prohibited from sharing, such as protected health information, payment card data, or data subject to legal privilege.

(d) You may withdraw this consent at any time by terminating your participation in the Beta Program pursuant to Section 8, at which point Company will cease accessing your Journals for review purposes (though previously collected anonymized insights may be retained).

5.5 Notification

Company will not access Journals in real-time during active test runs. Journal review will be conducted on completed run data. Company is not obligated to notify Beta Participants each time a Journal is reviewed, but will respond to inquiries about review activity upon reasonable request.

5.6 Post-Beta Transition

Upon conclusion of the Beta Program or transition to general availability, Company's right to review Journals under this Section 5 will terminate. Thereafter, Company's access to Customer Data will be governed solely by the ToS and Privacy Policy applicable to the selected Subscription Plan.


6. Intellectual Property

6.1 Ownership

All intellectual property rights in the Service, including any improvements, modifications, or derivative works developed in whole or in part based on Beta Participant Feedback or Journal review, are and shall remain the exclusive property of Company. Beta Participant retains ownership of Customer Data as set forth in the ToS.

6.2 License to Feedback

Beta Participant grants Company a perpetual, irrevocable, worldwide, royalty-free, non-exclusive license to use, modify, incorporate, and commercialize any Feedback provided during the Beta Program.


7. Warranties, Disclaimers, and Liability

7.1 BETA DISCLAIMER

THE SERVICE IS PROVIDED ON A "BETA" AND "AS-IS" BASIS. IN ADDITION TO THE DISCLAIMERS IN THE TERMS OF SERVICE, COMPANY SPECIFICALLY DISCLAIMS ANY WARRANTY THAT THE BETA SERVICE WILL:

  • (a) BE SUITABLE FOR PRODUCTION USE;
  • (b) FUNCTION WITHOUT INTERRUPTION, ERROR, OR DATA LOSS;
  • (c) BE AVAILABLE AT THE PRICING, FEATURE SET, OR PERFORMANCE LEVEL OFFERED DURING THE BETA PROGRAM;
  • (d) BE CONTINUED BEYOND THE BETA PROGRAM PERIOD;
  • (e) PRODUCE RESULTS COMPARABLE TO THOSE THAT MAY BE PRODUCED BY THE GENERAL AVAILABILITY VERSION.

7.2 LIMITATION OF LIABILITY

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, COMPANY'S TOTAL LIABILITY TO BETA PARTICIPANT FOR ANY AND ALL CLAIMS ARISING OUT OF OR RELATED TO THE BETA PROGRAM SHALL NOT EXCEED THE GREATER OF: (A) THE FEES ACTUALLY PAID BY BETA PARTICIPANT DURING THE BETA PROGRAM; OR (B) ONE HUNDRED UNITED STATES DOLLARS ($100.00 USD).

COMPANY SHALL HAVE NO LIABILITY FOR:

  • (a) DATA LOSS OR CORRUPTION DURING THE BETA PROGRAM;
  • (b) SERVICE INTERRUPTIONS, DOWNTIME, OR PERFORMANCE DEGRADATION;
  • (c) CHANGES TO FEATURES, PRICING, OR APIS BETWEEN BETA AND GENERAL AVAILABILITY;
  • (d) ANY RELIANCE ON BETA FEATURES OR FUNCTIONALITY THAT IS MODIFIED OR REMOVED.

7.3 Assumption of Risk

Beta Participant acknowledges that participation in the Beta Program involves inherent risks associated with pre-release software. Beta Participant assumes all risk associated with using the Service during the Beta Program and agrees not to hold Company liable for any damages arising from such use, except to the extent caused by Company's gross negligence or willful misconduct.


8. Termination

8.1 Termination by Either Party

Either party may terminate this Beta Agreement at any time for any reason by providing written notice. Termination takes effect immediately upon receipt of notice unless a later date is specified.

8.2 Termination by Company

Company may terminate this Beta Agreement immediately if: (a) Beta Participant materially breaches this Beta Agreement or the ToS; (b) Company discontinues the Beta Program; or (c) Company determines, in its sole discretion, that continued participation is not in the best interest of the Beta Program.

8.3 Effect of Termination

Upon termination: (a) Beta Participant's access to beta features will be revoked; (b) Company will provide a reasonable period (at least thirty (30) days) for Beta Participant to export their data, unless termination is for cause; (c) Company's right to review Journals under Section 5 ceases (subject to Section 5.6 regarding previously collected anonymized insights); (d) the confidentiality obligations in Section 3.3 survive for two (2) years.


9. General

9.1 Entire Agreement

This Beta Agreement, together with the ToS, Privacy Policy, Acceptable Use Policy, and Data Processing Agreement, constitutes the entire agreement between the parties with respect to the Beta Program.

9.2 Amendments

Company may amend this Beta Agreement at any time by providing written notice to Beta Participant. Material changes will include a thirty (30) day notice period during which Beta Participant may terminate without penalty. Continued participation after the notice period constitutes acceptance.

9.3 Governing Law

This Beta Agreement is governed by the laws of the State of Delaware, consistent with the ToS.


10. Acknowledgment

By participating in the Beta Program, you acknowledge that you have read, understood, and agree to all provisions of this Beta Agreement, including:

  • The pre-release nature of the Service and the absence of uptime or reliability guarantees (Section 1.2)
  • The Journal review and data access provisions (Section 5)
  • The publicity and case-study rights granted to Company (Section 3.5)
  • The enhanced limitation of liability applicable during the Beta Program (Section 7.2)
  • The confidentiality obligations regarding the Service (Section 3.3)

11. Contact

For questions about the Beta Program or this Beta Agreement, contact:

Syntaxa LLC
Email: [email protected]
Website: https://runqc.ai


This Beta Program Agreement was last updated on September 14, 2026.

Other Legal Documents

  • Terms of Service
  • Privacy Policy
  • Acceptable Use Policy
  • Cookie Policy
  • DMCA Policy
  • Security Disclosure
  • Service Level Agreement
  • Data Processing Agreement
runQC

Comprehensive AI agent testing and verification platform for reliable deployments.

Product

  • Features
  • Pricing
  • Documentation
  • API Reference

Company

  • About
  • Contact
  • Blog
  • Careers

Legal

  • Privacy Policy
  • Terms of Service
  • Security
  • Status

© 2026 Syntaxa LLC. All rights reserved.

runQC - AI Agent Quality Control